From the Edit menu, select Clear selections in all GenoMaps.

Yes, select that genomap in the drop down list under Report Data Source

I'm no genealogist either. Betty's other son is a half-brother. At present the report does not consider half-blood relationships e.g. half-brothers half-cousins etc. I will look into the possibility, but for now the message should perhaps read 'are not full blood relatves'

Hi Ron,

I have used this facility in Legacy in the past though finding the relatives to choose was not easy.

I have a problem with your invention in that I can't seem to "select" two people.

Perhaps you could indicate how to do this.

This idea is a great one and will be very handy when finished.

Select the 1st individual on the genomap with a mouse click, then, without clicking anywhere else on the genomap first (which would cause deselection of the 1st individual), hold down the Shift key whilst clicking on the 2nd individual. The 2nd individual can be on a different GenoMap, just click the tab for the required genomap before selecting the 2nd individual.

I haven't considered all 'localization' issues as yet. I will add two extra params to all the narrative phrases giving the gender ID (M, F, or P) of the two individuals concerned so that it can be tested directly in the phrase.

Also added gender IDs for each individual as paramters to the phrases.

and the calculator correctly returns:

and if I select f1 and either s1 or s2 then a a mother-son relationship is correctly shown.

Have you checked that the pedigree link from Betty to George is a biological link? What does the calculator indicate for the relationship between George and his half brother?

I will be happy to take a look if you send be a sample .gno via GenoPro's built in Send facility on the File menu.

Adopted and step children are still not blood relatives, hence the word 'blood' appearing in the current message when no relationship found.

Some further items I have on my 'to do' list' :

• Produce an HTML page showing the pedigree links from the common ancestor to the two selected individuals.
• In some countries, e.g. Germany I believe, cousins but of different generations are not described as 'n'th cousin 'x' times removed , but as [[[great]...]grand]son/daughter of 'n'th cousin
• For 'half' blood relationships, the 'half-' suffix should immediately precede the type of relationship, i.e. cousin/nephew/niece and not any great or grand adjective, e.g. great great grand half-nephew, not half-great great grand nephew.
• Appleshaw's problem was caused by having two biological fathers for and individual. This was a mistake but GenoPro does not flag this as an error when the relationship is created. Perhaps it should do and this is also one for the proposed 'Problem Spotter' enhancement to GenoPro. Maybe this report should flag such situations. The only time this would be valid is when the user wishes to express uncertainty as to the father. There have been dscussions elsewhere in this forum regarding a 'possible child' pedigree relationship but this has yet to be implemented.

Excellent job on the Kinship Calculator, but I have found an occasion where a little error checking may be required.

In the case where first cousins marry:

if you run the kinship calculator on the husband and wife the result is, as expected:

However, if you break the link between Father (W) and the grandparents, the result is:

whereas it should indicate no blood relationship. The result is the same for any husband and wife unrelated by blood.

It is proving difficult at the moment to show all possible relationships for some pairings where their paths cross higher up the tree, so for now it will just show the 1st one discovered.

A sample report however is attached to this post.

there is a gender problem on the new report when selecting in-laws. For the following family:

running the report on the highlighted individuals results in this report:

Despite, I suppose, that you're not focusing on the translations facility yet, I anticipate the requirement for the following F gender provisions:
- a <KinshipCousin_F>
- a <KinshipCousin1_F>
- a <KinshipGreatGrand_F>
- a <KinshipHalf_F>
- a <KinshipInLaw_F>
- a <KinshipPartner_F>
- a <KinshipPerson_F>
- a <KinshipUnion_F>

The above ph could be replaced by provision of gender ID as {params}.
JC

Have updated skin to fix this. Thanks for reporting.

I have made some changes here but I need to add a stylesheet to the skin to make it easier to change fonts, colours etc.

Yep, the deeper you go the more complex it gets. Plenty of info on the web re full blood relations, but when you get to half, step and in-laws less so.

I have added some gender params but others may require further coding (e.g. Half). Please advise on specifics if and when you try translating.

1) Ref: the end of your posting 23088: I need for sure an '_F' variant (or sexe ID as param) for:
- <KinshipHalf>
- <KinshipInLaw>
- <KinshipPerson>
- <KinshipUnion>

2) I noticed some wrong reported sexe in the chart. Here are 2 samples:

3) <KinshipCousin> and <KinshipCousin1>:
I don't know what to do with these Ph. In FR it's totally different.
I managed to get an informative (quite complete I suppose) table showing the various names of pedigree links based on the positions of Ind1 and Ind2 in relation to a common ancestor. It is actually quite complicated.
The table, in FR, can be seen at http://pages.videotron.com/veeren/Parente.html.
With all these links names, I don't think the 2 Ref Ph are suitable.
I wonder if the solution isn't to provide a proper 2 Dim array which will be accessd, based on the position/depth of Ind1 and Ind2?
If so, M and F sexes should also be supported, maybe meaning 2 arrays?
If you need some more explanations about this table, don't hesitate to ask.
Thank you Ron,
JC

A grandson becomes in German "Enkel" and a granddaughter "Enkelin". This phrase is only needed if you want to check on one of the direct ancestors and a person down below the line.

Using these in my English Dictionary I get

I have not added prefix(e.g. half-) and suffix  (e.g. in-law) details as I do not know where to put them

Note for JC: The 'depth' param I use is actually one less than that in your 'Sommes-Nous Cousins?' chart as the common ancestors is deemed to be depth 0 and not 1.

Several issues with HTML validation - output now passes XHTML 1.0 Transistional validator.
If couple selected they were reported as not related. Now indicated as partners.
Optional double gender variants (_MM, _MF, _FF & _FM) added to the three 'cousin' phrases.
Hopefully fixed wrong gender for some relationships when selection order reversed.

I was wondering...

Is it possible to write a PHP script that would create this feature online from the "server" side?

I mean that any user  will choose 2 individuals from a list (which will be created from the genopro.xml), and then a php script would create and display the "Kinship.htm" file of the "chosen" two individuals

Not as it stands. It relies heavily on the objects and methods/properties of GenoPro's SDK. I wonder if it is possible to make the SDK available as a free standing ActiveX control? But I don't suppose that would be any good on a non-MS server.

I have been considering a possible 'next generation' of the Narrative Report. I would like it to be dynamic, driven straight from the .gno XML and use an open source CMS for styling purposes. I am wondering if I can provide some of the functionality of the SDK in a javascript object and use AJAX to retrieve bits of the .gno XML from a server as required in a 'widget' design approach. One big problem I see would be the phrase generator. But maybe.....

What does this mean? I am using the latest version.

It means that having found and recorded a path up to the common ancestors, the script cannot find its way back down again!  I'm stumped as to what is causing this at the moment. My only guess is that it has something to do with hyperlinks - do you have hyperlinks in the affected relationship chain? If so try changing line 295 of Kinship Calculator.js
from

The most likely cause is that you have inadvertently created a loop in your tree, e.g. making a child the parent of one of his/her own ancestors. I have managed to create the same error by doing this.