The major change here is rationalising the configuration parameter handling. Configuration parameter descriptions have been moved from Dictionary.xml to Config.xml, as per the Descendants report. Additional information for some parameters is also available as a 'tooltip' on the Config settings form, taken from a new 'Desc' attribute for each parameter. The move to Config.xml should mean that the two Dictionary.xml files are interchangeable (for the same release level).

Other changes are:

1. a fix for the double window for any individual external hyperlink, reported elsewhere.
2. a <?url?> custom markup instruction as suggested by BobWebster
3. a <?plain?> custom markup instruction for text that is only for the non-html report(s).
4. gender param for education termination. possible to translate education achievement passed/failed.
5. maybe others!

1) in Dic, <PhBloodTypeTxt>:  1st curly bracket to be removed after T="
2) in Util.vbs, <PhTL_Birth & _Died>: strGender should also be added at the end of the param lists in lines 968 & 973 as I got this error message:

3) the lookup (for places & occupations) in NameDic doesn't seem to work.
Thank you,
JC

Also I got a bit tired of answering the 'View/Amend config params' prompt, so I have added something so that a Document Custom Tag named ChangeParameters can be used to control it. Set to 'Y' to cause the change params dialog to always appear without prompting, set to 'N' to stop the prompt (and dialog) from appearing. By default if this custom tag is not set then behaviour is unchanged.

The result looks fine but again to be checked for optimization and coding potential bug.
Thank you Ron,
JC

Also added narrative for grandparents whre mother/father was adopted and Extant custon tag for relationships to allow past tense when individuals still alive. Set Extant to N if relationsips is no longer current.

Update: 2008/03/18:  see later post in this tread for an updated skin.

ran Narrative Report revision 2.0.1.5RC3 and received following error..

I tried to understand your new <PhGrandParentsAdopted> Ph and drawn up this tree, having made Francine adopted by Pierre & Marie:

I then 'made label/excluded from Report' the grand-father Pierre and got this:

Oops, gender problem.

Update: I also noticed this with param <LangShowOthers> = "Y":

Thanks Ron,
JC

Could it b that you have managed to pick up an old report skin? I can't find b.PregnancyLength.Month anywhere and not on line 124 of Lang.vbs. It was changed some time ago to PregnancyLength.Months

Thanks JC. There was a problem with 'single parent' adopters that I have now fixed in the attached, also dual lang. city/state/country etc.

1) Pict slideshow Interval:
The entry in my FR Dic is: <PV_Speed T="Régler l'intervalle de pause"/>.
The tooltip shows as truncated:

I then removed the apostrophe and the tooltip shows OK:

Possibly another Unicode or char incompatibility problem?

2) the places still show code 'garbage' as on my above screenshot. With <LangShowOthers> = "N", the Places Nar are OK.
It is because the input country of some places are of Dual-field nature:

I removed the dual-fields leaving only France (actually I typed another name to differenciate it) and the system picked up the correct FR name in NameDic.
3) Inconnu (M gender) & Inconnue (F gender):
Marie is 'excluded from Report'. The narrative says Inconnu (for a male). Is it normal?:

Also, as already mentioned by some Users, Marie's name should not appear in the SVG because 'excluded from report'!

Voilà. C'est tout. That's all.
Thank you Ron,
JC

2. I have retested and cannot find a fault. My test produces the correct result. It could be that you have not noticed the subtle change in the PhPlaceDescription phrase in the Dictionary - the address components now have the 'h' html suffix. These appear to be absent in your Dictionary posted elsewhere.

3. Gender for 'Unknown'
The individual is not presented to the script hence its gender cannot be determined precisely. However it can be determined from the gender of the partner if a hetrosexual relationship is assumed.  I have put code in place for this. (Still need to test it!)

4. Make Label / Exclude from report with SVG GenoMaps
This is a tricky point. The 'Make Label / Exclude from Report' option is used for legends, if I suppress these on the SVG then legends will not appear. Also if the display of the Individual or Family is suppressed then the associated pedigree links, relationships and twin links should also be removed.

To cope with the first point I have decide to introduce another Custom Tag 'HideLabel' which when set to 'Y' in addition to 'Make Label' being set will now cause the removal of that Individual/Family and associated links from the SVG GenoMap.

Attached is another revision with all the above changes.

P.S. I will shortly post a new topic with some documentation on Customising Reports, covering Custom Tags, Config Params and Custom Markup.

To JC, sorry about the slider tooltip oversight, for some inexplicable reason I had assumed PV_Play instead of PV_Speed, which also had the same issue. Both should now be OK.

<?movie type pictureID name width length[ align][ quality][ wmode][ backgroundcolor]?>

Where 'type' must be Flash, name is alphanumeric identifier e.g. mymovie (no spaces) and [...] indicates optional params. You will need to add your .swf files as GenoPro 'pictures' in order to obtain a 'pictureID' for it (save the .gno to generate IDs). Although GenoPro itself will not be able to show them, the path is stored in the .gno and can be used in reports as here and the file gets copied into the report pictures folder.

Haven't tested it much and have just noticed I left a diagnostic logging of this into the message log that I will remove. (now done in RC6a)

An interesting bug:
2) The CT I set up is actually a mixture of Dual Lang fields and Urls Custom Markup, i.e.:

My CT entry: {?EN:<?url http://en.wikipedia.org/wiki/Versailles?>}{?FR:<?url http://fr.wikipedia.org/wiki/Versailles?>}
The Rep shows no link as, apparently, not properly parsed/formatted:

On the other hand, the link is present and works when generating an EN Rep without the associated <PhCT_...>:

3) + this little typing error in the comment line 974 of lang.vbs: indidiuals

Thank you Ron,
JC

Ref. your above post 21198 concerning the Custom Markup (CM) <?movie ...?>

I managed to setup a little .swf movie as a Pict. It basically shows OK. I would like to explore more of this feature but before going further, could you answer this simple silly question:

In which field do you input the CM? Pict Name or elsewhere?

Thank you

JC

I suggest the movie Custom Markup is placed in the Comments or _Narrative Custom Tag for the Individual, Family, Place etc. that the movie relates to. It can also appear in a Custom Tag of your choice that is referenced in another Custom Markup clause such as notes or subsection. I'll provide examples at a later time once 2.0.1.5 is sorted.

The 'Alternative name' problem with 'right to left' text has been fixed. If the Full Name format includes the Alternative name then no change is made. Otherwise the phrase template is now taken from a config param and not the Dictionary as before. Thus it can be easily changed.

Also hopefully fixed is the '_Exclude' picture Custom Tag feature.

2) Dual Lang Fields (DLF):
Following your above post 21280 phrase 'Both delimiter formats can be used elsewhere.', I changed some of my DLFs from {?...} to {¿...¿} and got these errors:

Is it preferable, for simple DLFs, to keep the '?' delimiter?
For info:
a- 5 of these errors are related to marriage dates on the Fam lines and one is an ER comment.
b- I also changed to {¿...¿}, a DLF Edu Program/Discipline & an Ind general comment. These ones are shown OK in the Rep and of course without errors.

3) PhMovie: maybe your routine is still under development but I noticed:
a- I set this movie as an Ind Pict but I got this Gene error:

On the Rep, the movie used to be listed in the Pict index but not anymore. 

b- I had a quick look on Adobe site and noticed that the following bold parts should be corrected (of course to be thoroughly checked by yourself):
 [{?2}WIDTH=&quot;{2}&quot; ]...
 &lt;PARAM NAME=movie VALUE=&quot;{0}&quot;&gt;
 ...
 &lt;EMBED src=&quot;{0}&quot;
  [{?5}quality={5} ]...

and 4) PhCTs in Document:
I'm totally lost with this new feature. You have to provide examples of location of input and input (screenshots will be welcome).
a- Shall all these PhCTs be input in Tools->Tag Editor->Doc tab?
b- Shall all these PhCTs be grouped under a particular Layout Name?
c- In which field the 'T=...' phrase be input?
d- Shall the input be, for example for my <PhCT_UrlInfo>:
     1- <PhCT_UrlInfo T="Address: {10}"/> (similar to Dic)
or   2- T="Address: {10}"
or   3- "Address: {10}"
or   4- Address: {10}
?

Thank you,
JC

1) is 'by design' The script just puts the primary picture here. I reasoned if a user has elected to exclude it, then he doesn't want one shown here. Ordinarily I suggest the primary picture should be one you want shown.

2) Yep a little bug in the StrPlainText routine that I missed. Now fixed.

Up to you which format but better to be consistent throughout, so {¿...¿} is more universal, but ¿ is hard to type.  

3) You can now '_Exclude' such movies to avoid this error appearing. They still get used in any 'movie' custom markup. Since these files cannot be rendered directly, they are not on the picture index any more. Ta for pointing out PhMovie format issues. Now amended.

4) PhCTs. I have updated How to customise your Report to give an example. I have also changed the script to clear a couple of problems.

a. All Custom Tags must be defined using the tag editor, including these.
b. Can be grouped into one or more layouts. Suggest a Layout for each object type. 
   e.g. all Individual Custom Tag phrase templates under one layout.
c. To input the template itself, use File/Properties then whatever 'layout name' tab
     and enter the phrase template in the appropriate field.
d. 4 (or actually Address: {10h}

Still playing around, I generated an ES Report and got the error 800A0009. I then added up a 'Report.LogError strText' debug line in Util.vbs just before line 1033 and on seing the content of the variable strText, I noticed that the error was due to a missing {¿ES:...¿} input string:

I was suprised as I thought this problem was fixed but noticed that, in fact, the param <LangShowDefault> is implemented for the Descendants Rep only but not for the Main Nar Rep. So Ron, Is it on purpose or is it to come?

Also is it possible to make such ErrMsg a bit more informative? In my example, we can see that it is my own gene page which is involved but that's all. The display of the involved field (in ma case, the General Comment field) would be a must. May be difficult/not easy to implement if it's an MS VBScript system error!

Finally I suggest a few required ortho corrections in Data.xml, lines:

56 milliseconds
107 111 hierarchical
179 183 Ids -> IDs better ??
183 For  Unknowns
199 change
200 216 suppress Suppress
204 208 initially
239 Timeline
255 min.  events
283 translkate
304 langauges
316 l name (default=Name.Nick)
331 in index (to match 327)
339 343 hierarch.
593 ther descriptivetext fields ...
593 dispalyed
593 anecedotes
+ :
258 "LangPOssessiveLookup1" ??
262 263 xLangPossessiveLookup ??
'Google Map' in text: please keep consistancy: GoogleMap, , Googlemap, Google Map or Google map ??
same for 'Genomap'

Thank you Ron,
JC

There was an error in the script causing the 800A0009 error that is now fixed in the attached.

It is very difficult to provide extra diagnostics when a MS script error occurs. If I know where such errors occur then the script must be changed to avoid them, so this is a catch 22 situation. In an ideal world the script would be good enough to prevent all such errors.

The missing LangShowDefault was an oversight, it is now implemented for the Narrative Report.

Finally I have updated CustomReport.gno with your recommendations and updated it in the original post.

Update 2008/04/19 Fixed problem with StrFormatText affecting Custom Tags and other fields

This may have been intentional as an example of an invalid instruction (that's my excuse anyway)

Hmmm, something is wrong here, I'm investigating.....................

2) Perhaps this tooltip should say 'groups and organizations' instead of '&' to match some other tooltips.

3) To implement a 'floating' icon system when scrolling a list/index. I think this sub may have already been mentioned somewhere in this forum but not sure. An example at:
 http://www.javascript-fx.com/experiments/float/index.html#

but this particular example requires a separate scrolling area for the menu! Probably not suitable for the 'restricted' frame system?
Another method would be to provide smaller 'Fixed icons' similar to the SVG ones? At least it will be handy for the long lists, e.g. indexes and galleries.

4) Multi-Languistic fields: something's wrong. It's a bit everywhere:

5) Not a big deal but on a Fam page without 'Children', the 'Collapse/Expand' icon is not provided.

6) I think this one has already been mentioned somewhere: in the Timeline, can the internal scrollbar be removed as it doesn't scroll anything! Probably part of the 'Simile' object?

7) Is it possible to Right Justify texts?:
For info, it would also look good on a Descendants Report, if feasible.

8) Occupancy: The phone and fax No. are shown in the Report but not the Mobile No.

9) I created a dummy Social Entity and defined an Occupancy place on the Contact tab.
I personally don't grasp the concept but it's beside the point.
The point is I noticed this occupancy appears in the RP Contacts page but not in the LP index/list?:

10) Bug (already mentioned in my post 19040):
 a) Open the calendar with the main icon,
 b) untick the Bday or Anniv box then -> Apply Changes,
 c) close the Popup pane,
 d) bring up an Ind or a Fam page,
 e) click on the green tree or on the TL icon,
 f) it opens up in a new window. Sometimes a blank one.
All subsequent clicks on a TL icon, on a green tree, on a place, on a Pict name or even on the Cal itself will open in a new window. It seems that the frameset (or only just the popup frame) has been disrupted. Clicking on the main 'Home' icon resets the matter to cool normal operations.
This is with MS-IE. I Didn't try with Moz FF nor with Opera.

That's me. Thank you Ron,
JC

Damn, and there I was looking forward to a day off. Ah well, I can always dream

So, back to work:

1) & 2) Yes easily sorted. As probably gathered I'm not one for dotting the 'i's or crossing the 't's but not adverse to putting things right.

3) The example link runs a bit jerkily. I'm hopefully going to revamp the layout of the Narrative Report this summer so I'll add this to the list.

Update: 2008/4/24 Dictionary.xml in attachment updated with modified PhContact(Summary)

4) You appear to be missing the extra ¿ before the closing }. e.g. {¿EN:GenoMap¿}{¿FR:GenoCarte¿} I have added some more validation to check for this.

5) Yes I overlooked this when I made the 'Personal Details' a collapsible section. Now fixed.

6) This I believe is an issue with the quirky MS IE browser. Firefox does not exhibit this problem. There must be untold thousands of man days wasted searching for hacks to overcome these annoying quirks in IE. I have spent many hours doing just this in the past. I have had a quick look for this one but as yet have no solution that does not break FF. So it will remain on the 'outstanding bugs' list.

7) Not sure exactly what youy mean by right justify. Right aligned text to me looks a bit odd in parts. Justified text, i.e. aligning to both left and right margins, looks OK and can be achieved with a custom style entry of body {text-align: justify;} (or body {text-align: right;} if that is what you wanted)

8) In all this time I have never noticed the mobile field before. now added to the report.

9) Again it was relatively recently I became aware of the fact that Social Entities could have Contact details. I will need to add a higher level group in the index for object type, i.e. Individuals and Groups and Organizations (Social Entities). Added to the 'to do' list.

10) I tried this with FF and it works fine, so yet another IE quirk. At present I have no idea how to start addressing this problem, as I do not understand how IE is 'losing' the target 'popup' frame.

Revised skin RC10 is attached.

That's that then, time to put my feet up.

Update 2008/04/25 attachment updated
Update 2008/04/29 attachment really updated this time!
Update 2008/04/20 again for RC10b

Regarding the Social Entity, I don't plan to have any in my tree but for some other Users, I wonder if a green tree next to the name should be provided, just to locate it on the SVG graph?
3) point 7: I meant left + right justify.
 
JC

Update:
you forgot to add the Mobile param in Dic <PhContact> and <PhContactSummary> phrases.
JC

2) They are not MLFs because the SVG relies on GenoPro's arrangement of the text. This is why I added a Language custom tag to labels, social entities and social relationships. You need two or more versions of each, one overlaying the other and the script will chose the correct one according to the Language setting.

Good suggestion linking to the SVG for Social Entities. On the 'to do' list.

3) I thought so.

update) yes I had changed and tested them put forgot to update the zip. Now done.

This kind of pre-processing should be done by GenoPro, such as processing the {¿EN:...¿}, {¿FR:...¿}, {¿ES:...¿} and various tags.  After processing those tags, GenoPro could re-compute the text layout for labels and other objects having a layout dependent on the supplied.  This would simplify the code to maintain the report templates.

2) for info, I don't think a 'Social Relation' needs this 'Language' CT field as this SR object is MLF supported (it's only the 'Comments/Data Tip' field!), same as an ER.
3) For info, this observation isn't a big deal but I explain: a shape has a 'Comment/Data Tip' field. When filled in, it shows on Genopro graphic, when hovering, but not on a Report SVG. May not be processed?
Thanks,
JC

Skin RC10 in earlier post updated once more (a man's work is never done!)

1) fixed SE list to exclude those with Language CT <> Skin Language. Don't understand how you originally had multiple entries in index and on SVG. Entities without Language will always show, so could be considered a default,  except possible issues with SRs in narrative.

2) with specific SEs for each Language, also need specific SRs, otherwise narrative is wrong. Hence Language CT on SR.

3) Add code to display Shape Comment on mouseover on SVG, however puzzled by the fact that mouseover event does not fire on some parts of a Shape, both on IE and FF. Some you win, some you lose.

Did you update RC10?

JC

For your info, you've got 2 .bak files that you're trailing for a while now,

JC

JC

I agree that calculated/derived dates and ages should be annotated as being as such. At present the Report skin cannot detect whether or not an age, date of birth or death is derived from other data via existing properties.

Therefore a change to GenoPro is required (in Gamma?). I suggest a boolean property associated with each of the three fields (e.g. IsDerived). In addition Genopro should set Approximation (~) if the date(s) and age used in the calculation or not exact ie.e. do not have a 'days' portion' or are marked as approximate.

1. I have two sisters in my tree, both married, but she don't want to see their husbands in the tree, so I´ve excluded from the report: marriages, husbands, and descendants.

In one of the ladies, the report shows just her. For the other, the report shows: Details of Name's family with <Unknown>, but no link there.

2. Error Messages:

Thank you,

Can you (or anyone) combine your Descendants Report with the Ancestors Report?

What I would like to have is an 'up-side-down' report, starting with the youngest generation (e.g. ME) with all the ancestors and their brothers/sisters and so on.

Looking forward to se a beta ;-)

Jack

2) Looks like your Dictionary.xml is missing the Education Termination section:

For privacy I sent you a Private Message with the gno file.

The Education Termination section phrases are OK. Maybe I have a problem with the gno file.

Thank you,

The same file also provides a fix for the PhET_StillAttending error. Because the attribute T in the Dictionary is blank (i.e. T="") then GenoPro treats it as missing. I have changed the script to overcome this.

These fixes should appear in the next GenoPro release.

  Your wonderful and ever continuing fixes and updates makes me wonder:

Do you have a change list of items you make between versions?  Particularly, in the event that my translation project does actually bear fruit, I will constantly need to keep up with your changes. 

But nowadays the changes are quite minor. I suggest you use WinMerge to compare the two English Dictionary.xml files and change your own version appropriately.

On a separate note, I noticed that PhFR_LegalCohabitationAndDecease may have the incorrect text associated with it (perhaps it is the version I have)?  Please check.