|
|
|
|
Customers
FamilyTrees.GenoPro.com
GenoPro version: 2.5.4.1
Last Login: Wednesday, June 2, 2021
Posts: 220,
Visits: 14,736
|
|
|
|
|
|
Administrators
Customers
Important Contributors
FamilyTrees.GenoPro.com
GenoPro version: 3.1.0.1
Last Login: Yesterday @ 9:20 AM
Posts: 3,396,
Visits: 26,180
|
There are already two mechanisms that allow two surnames to be treated as the same 'root' name
Firstly in Dictionary.xml set RootNameAffixes to automatically associate female endings with male surname
<!-- Conversion of masculine/feminine forms of names to a common 'root' name, usually the masculine form.
e.g. for Russian <RootNameAffixes T="ova$=ov:cka$=cki:"/> means replace ova at the end of a name with ov and replace cka with cki before sorting or grouping. The names will still be displayed in their original form --> <RootNameAffixes T="" /> |
If the the names cannot be paired using simple rules as above then you can also define individual pairs in the skin file NameDictionary.xml. Please read notes in NameDictionary.xml in Narrative Report skin e.g. example NameDictionary entry <N CS=Powerá CS_B=Powerý/>
'lego audio video erro ergo disco' or "I read, I listen, I watch, I make mistakes, therefore I learn"
Edited: Wednesday, September 18, 2013 by
genome
|
|
|
|
|
Customers
FamilyTrees.GenoPro.com
GenoPro version: 2.5.4.1
Last Login: Wednesday, June 2, 2021
Posts: 220,
Visits: 14,736
|
The conversion with RootNameAffixes would be nice, but it is not easy to write a regular expresion for Czech language. I have got rules to convert from male to female, but not opposite.
The second option is great and suitable.
Thanks for help
|
|
|
|
|
Customers
FamilyTrees.GenoPro.com
GenoPro version: 2.5.4.1
Last Login: Wednesday, June 2, 2021
Posts: 220,
Visits: 14,736
|
Last question to this topic. Is possible to define the variants of the surname not in NameDictionary.xml, but in dialog using a custom tag similar as Name.Locative?
|
|
|
|
|
Administrators
Customers
Important Contributors
FamilyTrees.GenoPro.com
GenoPro version: 3.1.0.1
Last Login: Yesterday @ 9:20 AM
Posts: 3,396,
Visits: 26,180
|
There is nothing in place for this at present but it is quite straight-forward for me to implement this.
I will add provision for custom tag Name.Root in the next release. Name.Root will have precedence over NameDictionary.xml entry which in turn takes precedence over RootNameAffiixes. You could therefore use a combination of these. E.g. use RootNameAffixes whenever possible e.g. regular form names, NameDictionary.xml for common non-regular names an use Name.Root for any others.
'lego audio video erro ergo disco' or "I read, I listen, I watch, I make mistakes, therefore I learn"
|
|
|
|
|
Customers
FamilyTrees.GenoPro.com
GenoPro version: 3.1.0.1
Last Login: Wednesday, January 15, 2025
Posts: 256,
Visits: 1,727
|
I added the following line to Dictionary.xml, (and moved the original file to another location), but it's not having the expected/desired effect.
<!-- Conversion of masculine/feminine forms of names to a common 'root' name, usually the masculine form.
e.g. for Russian
<RootNameAffixes T="ова$=ов:ева$=ев:ина$=ин:яя$=ий:ая$=ий:"/>
<RootNameAffixes T="ης$=η:ος$=ου:ής$=ή:ός$=ού:ας$=α:"/>
means replace ова at the end of a name with ов, replace ева with ев etc before sorting or grouping.
The names will still be displayed in their original form
-->
<RootNameAffixes T="" />
I tried it with the terms reversed first (η$=ης), and then in the format above, but neither seemed to change the list of names in the Name Index.
Did I not do it properly or not in the right place? Thanks .. (-η is the female version, -ης is the male version, etc in the examples above)
|
|
|
|
|
Administrators
Customers
Important Contributors
FamilyTrees.GenoPro.com
GenoPro version: 3.1.0.1
Last Login: Yesterday @ 9:20 AM
Posts: 3,396,
Visits: 26,180
|
Looks like you have added your line to a comment ( <!-- & --> are comment delimiters in XML)
You need to replace the blank entry below that comment with your requirement. i.e. replace <RootNameAffixes T="" />
with
<RootNameAffixes T="ης$=η:ος$=ου:ής$=ή:ός$=ού:ας$=α:"/>
'lego audio video erro ergo disco' or "I read, I listen, I watch, I make mistakes, therefore I learn"
|
|
|
|
|
Customers
FamilyTrees.GenoPro.com
GenoPro version: 3.1.0.1
Last Login: Wednesday, January 15, 2025
Posts: 256,
Visits: 1,727
|
Ah great ... worked great once I flipped the masculine/feminine forms.
Is there a way I can save that to the .gno file, in case Dictionary.xml gets updated in the future and I forget I have to add that tweak?
|
|
|
|
|
Administrators
Customers
Important Contributors
FamilyTrees.GenoPro.com
GenoPro version: 3.1.0.1
Last Login: Yesterday @ 9:20 AM
Posts: 3,396,
Visits: 26,180
|
It cannot be saved to .gno.
Instead I suggest make a copy of the {EN} Narrative Report folder and rename it say {EN} Custom Narrative. However Windows copy does not recreate the junction to the Narrative Common\Code folder but simply creates an empty folder named Code. To remedy this delete this empty Code folder and then when you 1st run the report a new junction link called Code will be created linking to Narrative Common\Code. Then when you install a new update of GenoPro 2016 your Custom Narrative folder will be unchanged and you can check if the modified date of the newly installed standard Dictionary.xml has changed, if so copy it to your custom folder and reapply the modifications.
'lego audio video erro ergo disco' or "I read, I listen, I watch, I make mistakes, therefore I learn"
|