#2 name parsing is too simple
the function parseName() in importGedcom.cpp is way too
simple. Although GEDCOM specification of names is itself
too weak, the name parsing function should handle some
distinguishable cases. i.e.
Given
/Surname/
Given/Surname/
/Surname/Given
Given/Surname/Suffix
Only the first 3 are handled now (and actually not even
these,
since the code is not multi-byte aware... a different bug).
Even better would be for the code to check if name pieces
are provided, and use these over the ones parsed from the
full name. It still needs to pattern match against the
full name to get and preserve the name order.
Also, genes needs to remember the name order, and preserve
it when displaying names (Chinese, Japanese and Korean
names are always displayed with the surname first).
It might create and save a template, a la,
strftime/date. e.g.
"%G" == GIVN
"/%S/" == /SURN/
"/%S/%G" == /SURN/GIVN
"%P %G /%p%S/ %s" == NPFX GIVN /SPFX SURN/ NSFX
etc.
Commercial genealogy packages (and PAF5) handle this
correctly.
Logged In: YES
user_id=18589
Is there some documention of possible formats ?