You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1 NAME Hendrik /van Veen/
2 GIVN Hendrik
2 SURN van Veen
the first line results in 3 separate properties for Given, SurnamePrefix, and Surname, being "Hendrik", "van", and "Veen". And although that's not what I expected, it's not that bad either, especially because it creates a soundex for "Veen".
The third line, however, overwrites the Surname property with "van Veen", so in the end, the full name is "Hendrik /van van Veen/", and that's not right.
As far as I'm concerned, the above is proper GEDCOM, because it follows my choice to keep the full surname in one part, and the lack of a surname prefix in my data is properly translated to no SPFX being exported.
Any advice on how to solve this?
The text was updated successfully, but these errors were encountered:
When I import the following GEDCOM fragment
1 NAME Hendrik /van Veen/
2 GIVN Hendrik
2 SURN van Veen
the first line results in 3 separate properties for Given, SurnamePrefix, and Surname, being "Hendrik", "van", and "Veen". And although that's not what I expected, it's not that bad either, especially because it creates a soundex for "Veen".
The third line, however, overwrites the Surname property with "van Veen", so in the end, the full name is "Hendrik /van van Veen/", and that's not right.
As far as I'm concerned, the above is proper GEDCOM, because it follows my choice to keep the full surname in one part, and the lack of a surname prefix in my data is properly translated to no SPFX being exported.
Any advice on how to solve this?
The text was updated successfully, but these errors were encountered: