New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NICK names - 2.0.0 #1401
Comments
I agree. The nickname should not be printed as part of the given names. The given names are a persons official names. The nickname is the name to indicate how the person actually was called. These two should not be mixed up in the given name part. |
This functionality was removed because it cannot be made to work reliably. Imagine we have
If this is an English name, then we might jwant to display Also, the So, we should not try to add it it this name
But should we add it to this name?
Personal names have much complexity. If we attempt to automatically process them, we will always find exceptions and special cases. The only solution is to simply display the name as it is entered. It would be straightforward to write a batch-update plugin that adds the |
The first one is correct. Why not leave it as is?
Probably. But adding the NICK to the NAME should not be the only option. I rather enter the names as found in the birth certificate or other official records. The NICK is not retrieved from those records. And if this is a language thing, why not add a configuration option to keep everybody happy. |
I agree - The logic should be left as it is. Or at least add a configuration option, as suggested. By the way, if the nickname is part of the name, why enter it separately at all? You can already mark part of the given name as "Rufname" (via asterisk). |
The GEDCOM 5.5 standard did not have name parts ( It said that the nickname should be written in quotation marks. e.g.
This was because there was nowhere else to store the nickname. Since GEDCOM 5.5.1, we have name parts. In the "Changes from 5.5" section, it says:
If you want to store the nickname in the But this should not be automatic. For example, it may be appropriate in some names, but not others. e.g. some nicknames may be used only by close family. Also, for diminutive names, these are better placed after the full name. e.g. compare
|
I don't get it - This is not about storing the nick name in the gedcom (or about changing the way it is stored), but about displaying the nick name. Several comments here indicate a preference for keeping everything as it was before, or at least making it configurable. This doesn't seem that complicated to me. Why can't we have this configuration option for everyone who was ok with the way things were? |
It is about AUTOMATICALLY analysing a name and deciding where to insert a nickname. This cannot be done automatically. IMHO It is not possible. Consider these two names. How can a computer identify the name parts and correctly insert a nickname.
It was not OK for everyone. It was not OK for users with Hungarian relatives, or any other place where given names come after the surname. |
But it's currently (1.7.9) done automatically. I get that it's maybe not possible to be correct in all cases - but these are edge cases many users do not care about!
I didn't say that. That's exactly why we request a configuration option - so that people can decide for themselves. |
Since you are describing them as edge-cases, the largest cultural group would likely be Han Chinese speaking Mandarin, for whom /Surname/ 'Usename' Givenname 'Intimate_Nickname' would likely be the standard format. And by your logic that should be the default for everyone. |
No, I didn't say that either - I (and others) would just prefer a configuration option for this! How is that so hard to understand? |
I understand exactly what you want. But it is not as simple as you think. For example, we store the full name in the database (for sorting and searching). We also need to match the name of an individual to a name in the database. |
ok, now I finally get it. The 'full name' stored in the database includes (in 1.7.9) the nickname (taken from 2 NICK): I agree this isn't a good idea. I always thought this was just about displaying the name (by including the nickname on-the-fly, whenever the name is printed). Maybe the two aspects could be separated? Not sure how this would work for searching though. |
By the way, how is this handled when upgrading from 1.x to 2.x? The format of the full name stored in the database table has changed with regard to the nickname; is it therefore advisable to re-import when upgrading? |
I have over 2000 individuals with one or two nicknames. Could we add a utility that would add the nickname in ""-s to the end of the Given name and the Givenname in the Name and remove the nickname? We should ensure that the name sequence is not changed. |
I would like to print the NICK name on my site as we used to print between the Given name and the Surname. Almost all my site nick-names originate from given names. My users have seen the nicknames the old way for some 13 years. Several have problems when the site's look and feel changes.
Perhaps the administrators could be able to define for each site if the NICK names should print as they used to print or at the end of the name?
The text was updated successfully, but these errors were encountered: