Titles and honorifics vary by locale

What it is

Localized forms of address combine name parts with titles or honorifics for a target locale, level of formality, and addressing-versus-referring context. The engineering task is not to build a fixed country-to-title table. It is to make titles optional, localizable, and user-confirmable, with safe omission when the correct value is unknown.

Why it happens

Unicode LDML Person Names can place a supplied title in a pattern and select different arrangements for usage=addressing or referring and formality=formal or informal; the name data source may also supply grammatical variants. CLDR explicitly does not define regional lists for Mr, Ms, Mx, Dr, or comparable titles, and it does not decide which title applies to a person. CLDR formats a title value already supplied; the product, an authoritative directory, or the user must supply that value.

Where it stops holding

A title can encode office, qualification, marital status, gender, or relationship, and those categories are not interchangeable. It cannot safely be inferred from a name, gender field, or locale. Some official or sector workflows require a particular title, while many products need none. LDML formatting also does not by itself solve every inflected name form; a data source or inflection engine must provide vocative or other grammatical variants where needed. A linguistically correct title list still does not prove that one title applies to a particular person.

Applying it

• Make title optional by default. Collect it only for a concrete communication, credential, or workflow need, and provide none, other, or free-entry paths rather than making marital status or gender a required proxy.
• Have target-market language or content owners maintain title values, abbreviations, punctuation, formality, provenance, and context. Do not treat CLDR as a regional honorific dictionary.
• Pass a user-confirmed title to a Person Name formatter for addressing versus referring and formal versus informal output. Do not concatenate “title + surname” inside translation strings.
• Test notifications, letters, and credentials with no title, multiple offices, custom titles, missing name parts, and names needing inflection. Preview consequential output to the named person.

Related

• Same group: S2.05.1 The order and number of name parts are not fixed · S2.05.2 Split name fields can exclude users · S2.05.3 Middle names, patronymics, and suffixes need distinct handling · S2.05.5 Character-set restrictions reject valid names
• Adjacent: S3.05 Politeness levels and tone · S1.04 Plural, gender, and grammatical variation
• Search terms: forms of address · honorific title · CLDR person names