and replace for example StrHtmlHyperLink(i.Father) with StrHtmlHyperLinkAlt(i.Father)

It would be most useful if Dan could also provide this extra functionality in the ToHtmlHyperlink method. This would also allow simplification or even redundancy for the function StrHtmlHyperlink.

This is a good suggestion.  Ron, you pushed the report generator beyond anything I could dream of.  I realize some of the core routines, especially the ones creating hyperlinks have limitations.  One feature I have in mind is having an object containing all the parameters to create hyperlinks.  This way, instead of passing half a dozen of parameters, a single object would do the trick.  New parameters could be added without having to change the prototype of the function.

At the moment, I cannot give an ETA.  Tomorrow I have a meeting with a CEO to get a crash course how to structure an organization.  I need someone to handle the sales, marketing and some of the support so I can focus on research and development.

a. Your understanding is not quite correct. When PlurialCardinal is invoked the first part is only taken from _FmtPlurial when the count supplied to PlurialCardinal is > 1 and the target Dictionary element has no 'P' attribute.

e.g. in Lang.vbs line 624 we have

b. I assume from this question you are attempting a dual language report using a single Dictionary.xml. This is always going to be problematic because as yet the Dictionary does not support multiple language alternatives. One way it could be achieved now is to use separate elements for each language. And so as well as the existing

c. The C1, C2 etc. forms are used when the count n matches the Cn value. Note that the C1 form is only used with Dic.PlurialCardinal and not Dic.Plurial. So Dic.PlurialCardinal("Sibling_M", 1) returns 'a brother' and not 'one brother', but Dic.Plurial("Sibling_M",1) returns 'brother'. Dic.PlurialCardinal("Twins",3) returns 'three triplets' but Dic.Plurial("Twins",3) returns 'triplets'.

d. Normally a new topic should be posted as a new thread/topic. But since you are the originator of this thread/topic and the original topic has been dealt with then I guess it is OK. I think a lot depends on the original title - if you had called it 'Problems translating to Telugu' you could include all related queries in the one thread.

i.e. it is the last name of the 1st parent/spouse, unless this is blank, in which case the last name of the 2nd parent/spouse is used.

When there is a change of family name then it is written to the report at line 895

f.Parents, f.Husband & f.Wife are arrays so an index qualifier is required. Using Parents rather than Husband & Wife is probably better in case of any same sex relationships so I suggest

Util.IfElse(fParents(0).Name.Alternative <> "" And f.Parents(1).Name.Alternative <> "", f.Parents(0).Name.Alternative & " & " &  f.Parents(1).Name.Alternative, Util.FirstNonEmpty(f.Parents(0).Name.Alternative, f.Parents(1).Name.Alternative, f.Name))

It's a bit of a mouthful, but basically it is :

if alternative names are present for both spouses , join with '&' otherwise use any available alternative and failing that use the GenoPro family name.