Problem with Name order from GEDCOM file - Categorized in: Report a Problem

I have a GEDCOM file with names that have different orderings -- some names use a traditional ordering (Surname Middlename Givenname), and others use a modern ordering (Givenname Middlename Surname). For example:

0 @I1@ INDI
1 NAME Given1 Middle1 /Surname1/
2 GIVN Given1 Middle1
2 SURN Surname1
0 @I2@ INDI
1 NAME /Surname2/ Middle2 Given2
2 GIVN Given2 Middle2
2 SURN Surname2

For people like I2, Behold will print "For information about Surname2 Middle2, see ...". It looks like it is trying to parse everything up to the last word in NAME as a given name, instead of using the GIVN tag.

A simple solution would be not to even print the given name in this type of reference -- it's redundant, since the full name has just been printed. i.e. just go with ", see ...". That would also save an extra line which is critical for saving print space.

This type of ordering is very common for traditional Indian names, so I expect it will come up in many cases.

Thanks for the quick response. Surname2 Given2 would be okay as a shortened form of the I2 person. A further abbreviated form for these people would be S2 M2 Given2, where S2 is the initial of the surname, and M2 is the initial of the middle name.

Glad that I could provide a helpful suggestion :-) Good job on developing Behold. I like the concept and am looking forward to using it more.