Uploading names starting with a lower case character
In the Netherlands, we have quite a lot of family names starting with a lower case letter, such as 'van der Steen' or 'de Groot'. Let us consider a gedcom file that contains '1 NAME Klaas /de Vries/'. I upload this file to Genealogies and use Compare to make a View. Suppose that the person Klaas de Vries is in the list of persons to be added to FamilyTree. His name is then correctly shown as Klaas de Vries. But when I add this person, his name changes to Klaas Vries.
On the other hand, when I manually add a person to FamilyTree, I can enter 'Klaas' in First Names, 'de Vries' in Last Names and the name becomes Klaas de Vries, as it should be.
How can I prevent this name reduction when adding a person of an uploaded tree to FamilyTree?
Best Answer
-
The bug is repaired! Thank you very much.
0
Answers
-
Could you share screenshots of this happening? To fix a problem, the engineers will generally need to see exactly where and when it is happening.
0 -
Is this OK? I have no experience in taking screenshots ...
2 -
@FredSimons Yes, that screenshot should suffice.This is the GEDCOM compare process.
It would be interesting to note if the person were entered into the third-party tree management application with native language template - if this would resolve this issue? @Gordon Collett could probably comment with more familiarity - I would just suspect if the GEDCOM doesn't contain that language template for the person (perhaps entered in English template) there are probably different rules for compare/import which are creating this issue?
So a related question is - how did you create the GEDCOM for this person?
1 -
Ah, this suggests that I did something wrong, or at least not well enough. My genealogical software is a program that I developed during the last 25 years, now written in Python, and the genealogical trees that I upload to Genealogies are generated by this program. I am only a beginner in gedcom, and I have never heard of something like a native language template. This is the HEAD of my trees:
0 HEAD
1 GEDC
2 VERS 5.5.5
2 FORM LINEAGE-LINKED
1 CHAR UTF-8
1 FILE gendata.ged
1 LANG English
Do you suggest that I could try 1 LANG Dutch or something like that? Or do I have to include more in the HEAD? Many thanks for your answer!
1 -
Can you copy paste the portion of the GEDCOM for this person?
Use the code block option here so it doesn't get reformatted. Over your mouse in the left gutter beside the comment box, click on the paragraph symbols, and select code block from the pop-up menu.
0 -
I am sorry that I could not do this within FamilyTree. But I downloaded the View, and here are the HEAD section and the INDI section of the person. To my surprise, it shows the correct name.
0 HEAD
1 GEDC
2 VERS 5.5.1
2 FORM LINEAGE-LINKED
1 CHAR UTF-8
1 FILE gendata.ged
1 LANG English
1 NOTE Unified System GEDCOM Standardizer 1.0
----
0 @15748@ INDI
1 NAME Adriaantje /van de Santberg/
1 SEX F
1 FAMS @2896R15748@
1 _LHASH 27094298d6a07dfa39d94afce2804190
1 _HASH c4d36eb34bfffdd7083202f580f7fb26
1 -
I'll have to plead complete ignorance here. The GEDCOM file looks fine with the last name properly delimited. It also imports fine into Genealogies as the screen shots show and as seen here: https://www.familysearch.org/ark:/61903/2:2:7WKM-Y1V.
That the name gets clipped when imported into Family Tree must be a bug in that importing routine.
1 -
The GEDCOM file looks fine with the last name properly delimited.
Yes, it does. That isolates the problem in the FamilySearch code that creates the new profile from the GEDCOM data.
A test would be to make a GEDCOM of a random person with a double last name, run it through the same steps, and see what FamilySearch does with it.
0 -
I did the test. Only the first name is used and clipped.
1 -
I guess until FamilySearch gets around to correcting this compare/import bug (which probably will be far away or never?) - the only solution is to correct the Name(s) on the profile once imported (there you can choose the language template and enter the name correctly).
0 -
Okay, I raised a flag asking mods to escalate to the engineering team.
In the meantime, one possible workaround is to use an offline genealogy software that reads GEDCOM and can synch with Family Tree.
If you have one surname like this you may have many more, so this bug could be very time consuming.
1 -
Moderator Note: Thank you so much for bringing this issue to our attention. This has been verified as a bug. The engineering team has been made aware of it.
Maile :)
1
