fisharebest / webtrees

Online genealogy
https://webtrees.net
GNU General Public License v3.0
419 stars 290 forks source link

Inconsistent Name Display When GIVN Missing #4918

Closed miqrogroove closed 5 months ago

miqrogroove commented 6 months ago

The first problem is just a data entry issue. The arrangement of the NPFX field before the GIVN field sometimes leads me to put the name in the wrong place. That's not so bad.

Unfortunately, when NPFX is supplied without GIVN, webtrees never displays the missing name placeholder.

Example:

1 NAME Karen /Smith/ 2 NPFX Karen 2 SURN Smith

Expected Display:

Karen ... Smith

Actual Display:

Karen Smith

This leaves no indication that the GIVN is missing. Is it possible to change this so it's more obvious?

arbor95 commented 5 months ago

Do you want a Baron ... Kennedy instead of Baron Kennedy: I think no.

miqrogroove commented 5 months ago

Is Baron the GIVN? Is Kennedy the GIVN? Is GIVN missing? Without some display consistency I can only guess how the name was entered.

arbor95 commented 5 months ago

Baron is surely always NPFX. If it was GIVN there are never ... in the presentation.

arbor95 commented 5 months ago

but sure you can never concluse the name parts from the NAME.

miqrogroove commented 5 months ago

For me, the answer is yes, I would want

1 NAME Baron /Kennedy/ 2 NPFX Baron 2 SURN Kennedy

Expected Display:

Baron ... Kennedy

This indicates to me that the given name is missing. But for every family tree in the world, I'm unsure of the implications.

Norwegian-Sardines commented 5 months ago

The NAME tag does not have to be equal to the subtags! For example:

1 NAME Jon Erik /Andersen/ 2 GIVN Jon, Erik 2 SURN Andersen

1 NAME Maria /Zawadzka/ 2 GIVN Maria 2 SURN Zawadzk

1 NAME Johan /von Trapp/ 2 SURN Trapp

For many people they want their simple names to be equal, but in more complicated situation they can be different.

The NAME tag (without the slashes) is for display, the Name_Pieces are used for indexing.

miqrogroove commented 5 months ago

I've never tried to customize the NAME value so I wasn't aware it was being treated as separate from the parts. I will have to consider this more.