How you put information into \u0192h<\/span><\/span> is very much determined by how you want information to come out. You may also be influenced by what you think is right, what living subjects think is right, what your audience thinks is right, and what you understand as generally accepted practice.<\/p>\n Names and naming can be very sensitive, and in particular it is very easy to get foreign names wrong due to:<\/p>\n However, the result has to be understandable and unambiguous – but someone will still claim that a particular name should be formatted and presented in a specifically different way.<\/p>\n This is not helped by ambiguities in what is meant by apparently innocuous words like “surname” or even “name”.<\/p>\n (The author is Anglo-Saxon with some possible Gaelic\/Scots\/Pictish influences.)<\/p>\n The most typical name structure in \u0192h<\/span><\/span>‘s original market (the United Kingdom) is Given Names followed by Surname. In normal usage these names are entered in the Name field (saved in Because of some of the ambiguities in naming, this article often contains explicit references to data items. These items contained between % signs are what GEDCOM (and \u0192h<\/span><\/span>) understand as Data References.<\/p>\n The For more details see How to Handle People With Multiple Names<\/a>.<\/p>\n The surname is assumed to be the last word (identified by the space before it), unless the user puts slashes elsewhere to delineate the surname. For Example in ‘Ralph \/Vaughan Williams\/’ Vaughan Williams is an unhyphenated two word surname.<\/p>\n Setting the option in Tools > Preferences > Property Box tab >Show Surnames Between Slashes<\/a> can ensure that \u0192h<\/span><\/span> always puts slashes around what it is interpreting as the surname so they clearly show in edit fields. Whilst \u0192h<\/span><\/span> does not display the slashes in diagrams and reports etc, it will capitalise the deemed surname when displaying it – unless the user switches that option off in Tools > Preferences > Property Box tab >Display surnames in upper case<\/a>. <\/tt><\/p>\n The First Given Name is assumed to be the Preferred Name unless the Given Name Used field is completed in the Names and Titles dialog<\/em> (behind the More (+) … <\/a> in the main Property Box).<\/p>\n Note in the above illustration:<\/p>\n The Name field Name qualifiers are \u0192h<\/span><\/span> specific and will not be found in the GEDCOM standard.<\/p>\n Where an individual has name parts that are put before or put after the name they are entered as Name Prefixes (e.g. Dr., Sir., Lt., Monsieur le Professeur, Frau Doktor Doktor, etc.) or Name Suffixes (e.g. PhD., QC, CEng, MP, ONZ, COG, SP, etc.) in the Names & Titles dialog (behind the\u00a0More (+) …<\/a> ) in the main Property Box.<\/p>\n Prefixes and suffixes can be a minefield and we need to remember that we put in to \u0192h<\/span><\/span> what we want to get out. Typically they contain adornments that get added to a name as they may appear on a formally addressed envelope. For example:<\/p>\n\n
Parts of Names<\/h2>\n
%INDI.NAME%<\/code>).<\/p>\nData References<\/h3>\n
[1]<\/code> index in data reference such %INDI.NAME[1]%<\/code> handles the case where an individual may have more than one name. For instance Lewis Carroll was the pen name for Charles Lutwidge Dodgson. In this case alternates name could be added in the Names & Titles<\/em> dialog (behind the More (+) … <\/a>) in the main Property Box and they would take the field names %INDI.NAME[1]%<\/code> and %INDI.NAME[2]%<\/code>. Varying the index allows the user to specify a specific version or variant of a person’s name.<\/p>\nName Parts 1: Surname and Given Name<\/h3>\n\u0192h<\/span><\/span> then has various ways to show parts of a name entered in the Name field.<\/p>\n
Surname – Basic<\/h4>\n
Given Name<\/h4>\n
![\"Use](\"https:\/\/fhug.org.uk\/kb\/wp-content\/uploads\/2022\/06\/pasted_image-300x126.png\")
Examples 1 – Surname, Given, and First Names<\/h4>\n
![\"Query](\"https:\/\/fhug.org.uk\/kb\/wp-content\/uploads\/2022\/06\/pasted_image001-300x41.png\")
<\/a>\n
Name Formats 1 – Surname, Given, First<\/h4>\n
%INDI.NAME%<\/code><\/tt> as described above handles many of the common variations – although the above example also uses the separate non-standard Given Name Used field %INDI.NAME._USED%<\/tt><\/code>. The underscore in the data reference is to highlight that this is a non GEDCOM reference that can probably only be interpreted by \u0192h<\/span><\/span> or anther program’s input routines that have been specifically coded to expect that data reference.<\/p>\n\u0192h<\/span><\/span> uses the colon “qualifier” to extract particular name formats from the %INDI.NAME%<\/tt><\/code> Field. The examples above use some of the most common – found in help under Name Formats<\/a>.<\/p>\n\n
%INDI.NAME:SURNAME%<\/tt><\/code> – extracts that part of the %INDI.NAME%<\/tt><\/code> field between the slashes – or the last word in the Name field if there are no slashes<\/li>\n%INDI.NAME:GIVEN_ALL%<\/tt><\/code> – extracts all of the %INDI.NAME%<\/tt><\/code> field except text between the slashes<\/li>\n%INDI.NAME:GIVEN%<\/tt><\/code> – is the first of the Given Names unless the Given Name Used field (%INDI.NAME._USED%<\/code>) is completed in which case it is displayed by %INDI.NAME:GIVEN%<\/tt><\/code><\/li>\n%INDI.NAME:FIRST%<\/tt><\/code> – is the always the first of the Given Names<\/li>\n<\/ul>\nName Parts 2: Prefixes and Suffixes<\/h3>\n
![\"Use](\"https:\/\/fhug.org.uk\/kb\/wp-content\/uploads\/2022\/06\/pasted_image003-300x130.png\")
![\"Query](\"https:\/\/fhug.org.uk\/kb\/wp-content\/uploads\/2022\/06\/pasted_image002-300x24.png\")
<\/a>![\"Using](\"https:\/\/fhug.org.uk\/kb\/wp-content\/uploads\/2022\/06\/pasted_image008-300x205.png\")
![\"Using](\"https:\/\/fhug.org.uk\/kb\/wp-content\/uploads\/2022\/06\/pasted_image007-300x115.png\")