I've noticed something odd. If you import GED 5.5 files where a person has multiple names listed in given name, it will automatically take names 2 through whatever and place them in middle names. For example:

John J. J. Smith becomes

given name: John
middle names: J. J.
last name: Smith

If this person is a "parent" in the family group list, then their name is properly displayed under parent1 or parent2 column: John J. J. Smith

If you import someone with no middle name (or create a new person) and they are a parent in the group list, there is no space between the last middle name and the last name, so our example becomes: John J. J.Smith

The names appear to be displaying properly everywhere else, so I'm really confused as to why this is happening.

I also noticed that if you go to edit a person with no middle name or create a new person, the cursor appears to "jump" about a tab space in the middle name field when you focus it.

Comments

sugardave’s picture

sugardave commented

I've begun working on my own API-type module that processes GEDCOM files. While researching the last GEDCOM spec (5.5) I noticed that there is no such thing as "middle name." There is only NAME in the format of:

My Given Name /Last Name/

I understand that you are "creating" the middle name, but there is a problem. How can you be sure you are correct when choosing which piece of the name should be first name and middle name(s)?

For instance, what if there is a person named John David Russel McGillicutty, and his parents have called him "John David" all his life and Russel is his "middle" name?

So, in my module, I only make the distinction between given name and last name. When I process my results through your code to create nodes, everything appears to work, but I think you should re-think/remove "middle name."

sokrux’s picture

sokrux commented

I would agree that most programs are only distinguishing between the Given and Surname. Getting rid of the distinct middle name field should save the module from having to try and deal with parsing it out.

The only drawback I can see is in some of the lists, like the Group dropdowns, using the full given name (first and middle) will make those fields longer.

jerdiggity’s picture

jerdiggity commented
Assigned: Unassigned » jerdiggity

Re the original issue:

I haven't encountered this issue yet, but try this (please) and let me know if it changes/fixes/breaks anything:

Inside the common.inc file (at ≈ line 97), change this

  • $name=$firstname .' '. $middlename.$surname;

    • to this

  • $name=$firstname .' '. $middlename .' '. $surname;

(well, technically there should be a space surrounding the = operator but whatever...)

If it helps then I'll make a patch and commit it. Thanks for all the input!

j

jerdiggity’s picture

jerdiggity commented
Status: Active » Fixed

Please see the 2.0 beta release.

Thanks!

j

Status: Fixed » Closed (fixed)
Issue tags: -middle name

Automatically closed -- issue fixed for 2 weeks with no activity.

Issue tags: +middle name

Restoring issue tags, see #2125755: System messages removed all issue tags during D7 upgrade.