I discovered that the change history mechanism, i.e. using XML comments giving version details, was not compatible with the working of GenoPro's phrase editor. I have therefore ameded this to use additional 'V' (version) attributes to indicate changes. See head of Dictionary.xml for further information.

I have also changed the Config Param Dialogue so that each section is initially collapsed to make navigation easier.

Family relationship phrases now take better account of single parent families. So if only one parent is defined then there is no mention of husband/wife/partner or <Unknown> and phrases take the singular form.

Finally, as well as a few bug clearances, I have added, as a result of a suggestion from JCG, a 'random phrase' facility that can be used to break up the monotony of repeated phrases.

This involves having an 'X' attribute on selected phrases, indicating the number of eXtra variants of the phrase that are present. The additional phrase variants have the same key but with a _Xn suffix. The only example in the Dictionary at present is PhFR_LoveAffair, that has a X="1" attribute and an associated variant PhFR_LoveAffair_X1. You can of course add more of your own in a custom skin. Suggestions for more more variations welcome! This has only been implemened for the Narrative Report.

Similar Nars are also produced with some Cohab inputs. Perhaps the title 'Partner' could be capitalized?

3) Dic PhFR/Txt Phs:
Now that you introduced single parent, I need for my FR Rep a Gender ID param for the single parent.
4) I don't remember if it has already been mentioned but with Vista and Moz FF, the PDFs don't show up. Any settings you're aware of within FF?

That's all for now. Your Random Nar Variant Phs routine works fine.
Thank you Ron,
JC

Update for 4) : It's now OK. I right clicked one of my PDF file and opened it with FF. The file opened fine so the Report PDFs afterwards. Must have triggered an add-in!

Update2:
5) Single parent:
Should, in this case, 'They' be replaced by 'He'?

Descendants.js lines 329/340
Thanks Ron,
JC

Another example, probably related:
- The tree:

- The Nar (absence of the Cohab with André Loison):

... but appears in the name Index:

A.2) PhBurial:

A.3) Sources:
- the multi-lang Brief Description field has not been processed (checked as processed OK in the main Nar Rep).
- Perhaps 'The citation ...' Ph should start on a new line?

A.4) when a Family has initially been selected, the 1st heading No doesn't seem complete, i.e. '.1.' should be '1.1.'

... and when a Descendant type Rep has been selected, '.1.' should be '0.1.'.

A.5) I set a Max. Generations of 3 and the kids associated with the 4th gene are listed OK but their superscript Nos should not be shown, as no Nar 4.xx.
     This comment also apply for the Name Index.

B) FR Report specific:
B.1) PossessiveProperNoun
The Nar should say d' instead of de, according to the Dic template:

Thank you Ron,
JC

Update:
A.6) <PhFRTxt_CohabitationAndSeparation> in Dic:
If not mistaken, the beginning of the Ph is missing: T="[{4} ]{0}..."

Update 2:
A.7) On the Config param panel, the tooltip associated with 'Family or Descendant style report' doesn't come up. On my FR Rep Config panel, the tooltip is truncated at the 1st apostrophe location. So problem with Html encoding?
A.8) the button "Ok" should all be capitalized "OK" to match system buttons.
A.9) I noticed some differences in line spacing (it's with OO as MS Word's not installed).
The normal spacing on my screen is apparently about this one:

... and here are some samples of bigger spacing, depending on the narrated Ph:

The later, when showing a baptism Ph, is missing the end dot.

1) the '?' in IrfanViewPath & InkscapePath is converted by the script into the drive letter on which Windows is installed. I occasionally install Windows on D: and have seen H; used as well. So the default should work most of the time.

2) This is now fixed. However I also decided to remove the Family Relation phrase if nothing had been selected for it. (i.e. only report on data present, no comment if not). However I just realsed I need to change this again for the Descendants report

3) Added gender IDs for 1st family member {5} and partner/spouse {6}.

4) Thanks for the update on this - I tried it and had the same problem. I also have a problem with IE on Vista in that Acrobat Reader always launches in its own window. If nyone can fix this please let me know.

5) Fixed.

Missing {7} in Descendants PhFR phrases. Yep, must have just tested these with Phase Editor and forgot to test the actual report!

A.1) Seems OK now. Was probably due to missing {7}

A.2) - A.8) Fixed. With A.7, for some reason Util.HtmlEncode does not appear to encode apostrophe to &#39; so added an explicit replace.

A.9) Can't seem to reproduce this so a test .gno would help. Also still need to add that missing full stop.

B.1) Added possessive name params to HeadingDescendants {2} and FamilyChildren {3} phrases in Dict so yo can use these instead. Also changed {0} in the FamilyChildren to be gender ID of a single child so phrase can say son or daughter instead of child.

This is strange.  I checked the source code and the apostrophe are encoded as ' (because the entity ' does not work in IE).  Please notice the round apostrophe is not encoded however.

Again, I could be wrong on this, however the routine Util.HtmlEncode should take care of the apostrophe (which is visually the same as the single quote).

Yep, a very valid reason - ageing brain cells! I simply forgot to run the WinMerge check I normally do. Now corrected.

It is indeed very strange. I added a diagnostic line above line 117 in Code\IEForm.js of Descendants Report

this.Cell = function(oParent, sWidth, sAlign, sTip) { if (sTip) Report.LogComment(sTip + ''+Util.HtmlEncode(sTip)+''+Util.HtmlEncode(sTip).replace(/'/g,"&#39;") );   var oNode, sTitle = (sTip ? " title=\'" + Util.HtmlEncode(sTip).replace(/'/g,"&#39;") + "\'" : "");   oNode = oIEdoc.createElement("<td style='width: " + sWidth + "; text-align: " + sAlign + ";'" + sTitle + ">");   return oParent.appendChild(oNode);  }

and I got

I.e. Util.HtmlEncode on its own did nothing but adding .replace(/'/g, "&#39;") fixes it.

Yet other tests show HtmlEncode working correctly

In Config.xml

<Report Template="Main.js" OutputFormat="Text"/>

I have modified both routines Util.HtmlEncode() and Util.XmlEncode() to explicitly encode regardless of the output format.  Let's see if the fix will give the desired result.

The fix is available at http://www.genopro.com/download/InstallGenoPro.2.0.1.6.exe (notice this fix does not include the new updated skins).

a) Main Nar Rep
a.1) One of my dummy job didn't come up correctly in the TL:

I noticed in my .htm file, the icon is referred to as Occupations.gif but shouln't be Occupation.gif?

b) Desc Rep
b.1) B1 being my dummy Birth Source, the B1 index also comes up with one of my Rel?:

b.2) For the <PhSRTxt_xxx> phrases, I need a new 'possessive name' param associated with param {2}. This is to be able to make, e.g. 'Jean est le parrain d'Antoine'.
Furthermore, if it's not too much trouble, 'possessive name' param should also be handy for:
<FmtMetaDescIndividual1> associated with params {0}, {2} and {3}
<FmtMetaKeyWordsIndividual> assoc with param {0}

Thank you Ron,
JC

Update:
b.3) I set up a Social Entity and linked it with a 'manager' SR to an Ind but the SE's name didn't come up in the Desc Nar:

Also on their Ind pages, there is no mention at all of their quadruplets status with their other 3 sisters.

I also ran a Descendant Rep and didn't notice any mention of quadruplets anywhere in the Nar.
Thanks Ron,
JC

I have also added some code to go some way in providing a solution for Anna and other Swedish users regarding preferred first name. This uses a marker character (default underline) to indicate preferred first name. Work here is incomplete and not all name occurrences are processed. Only implemented for Narrative Report at present.

I anticipate that there will be no further development of the Narrative Report beyond this. The code has perhaps been patched too many times and some of the sticking plaster is becoming unstuck! Maintenance will continue.

Instead I am looking at things like GWT (Google Web Toolkit) and Ajax as a replacement report delivery tool.

A very worrying bug indeed. There appears to be a problem in the GenoPro Report Generator rather the Descendants Report script itself.

It is similar to the problem reported in http://support.genopro.com/FindPost22159.aspx, but affecting the children of a family and not families of an individual.

The Children collection for fam00012 in the Harry Potter sample .gno correctly shows 4 children, but the additional Children.Order collection has, incorrectly, six children, ie the four correct one and the two additional ones shown in your report. The script uses Children.Order if present to ensure the correct child order in the report.

The same problem is also exhibited in the 'Export to Gedom' Report.

Looking at the XML for HarryPotter.gno we find the erroneous Children Order

But there are only four PedigreeLinks for the children of this family.

Hopefully Dan can look at this and provide a solution.

The collection Children.Order is internally used by GenoPro to sort the collection Children.  Extra children in the collection Children.Order are ignored - it is a flaw in GenoPro, as they should be deleted by GenoPro.

I have also written a simple skin to check for this potential problem in a .gno file. Use the attached files in  a custom skin e.g. "Order Bug Check"

tester.js contains the lines

<%[ for (var iCnt = 0; iCnt < Individuals.Count; iCnt++) {         i = Individuals(iCnt);         if (i.Families.Order.Count != 0 && i.Families.Count != i.Families.Order.Count) Report.LogWarning(i.ID + " " + i + " Families count mismatch " + i.Families.Count + ", ordered " + i.Families.Order.Count);         if (i.Children.Order.Count != 0 && i.Children.Count != i.Children.Order.Count) Report.LogWarning(i.ID + " " + i + " Children count mismatch " + i.Children.Count + ", ordered " + i.Children.Order.Count); } for (var iCnt = 0; iCnt < Families.Count; iCnt++) {         i = Families(iCnt);         if (i.Children.Order.Count != 0 && i.Children.Count != i.Children.Order.Count) Report.LogWarning(i.ID + " " + i + " Children count mismatch " + i.Children.Count + ", ordered " + i.Children.Order.Count); } Report.AbortReport(); ]%>