Skip to content
Locale Lab

Chapter 17·Strings, Names, and Input·~8 min·

Personal Names and Postal Addresses

Personal name structure and postal address schemas vary by country. Input forms must accommodate family-name-first ordering, single-token names, phonetic furigana fields, and country-specific postal address layouts.

addressCLDR person namesform design

Overview

Input forms that require `first_name`, `last_name`, `state`, and a numeric `zip_code` reject valid users across many regions. Personal name order varies by culture, and several territories do not use postal codes. Flexible schemas and CLDR address metadata prevent validation failures.

Core rule

Use a single full-name field unless a downstream system requires split parts, and drive address field order, labels, and validation from country-specific metadata.

Specification note: Hong Kong and the United Arab Emirates do not use postal codes. A required postal code field blocks every checkout address in those markets.

Failure mode

Forms that split names into required First name and Last name fields assume Western given-first two-part names. Hungarian, Chinese, Japanese, Korean, and Vietnamese place the family name first. Spanish-speaking markets use both paternal and maternal surnames, and many individuals in Indonesia and Southern India use a single legal name.

Postal addresses vary equally in field order, required subdivisions, and postal code syntax. Japanese addresses progress from largest unit (postal code and prefecture) to smallest unit, while Hong Kong, Ireland (prior to Eircode), and the United Arab Emirates operate without traditional numeric ZIP codes. Rigid US-centric schemas reject valid international customers or corrupt shipping and KYC records.

Stakeholder Teaching Aid & Novice Guide
Cross-functional alignment tool

Western assumptions about 'First Name', 'Last Name', states, and 5-digit postal codes break across most of the world. Forms reject valid users.

Business stakes & user risk

Strict US address and name forms cause international checkout abandonment. Demanding a 'state' in countries without states blocks orders completely.

Rule of thumb

Collect for purpose. Use a single 'Full name' field, and adapt address forms dynamically based on destination country.

The Novice Trap vs. Production Standard

Contrast the intuitive assumption with the architecture required for global releases.

Naive mental model

“Every person has a first name and a last name, and every address has a street, city, state, and zip code.”

Naive approach: Rigid US form fields

<input name="firstName" required /> <input name="lastName" required /> <input name="state" required />

Defect:Users in Iceland, Latin America, and Asia cannot enter their names accurately, and UK/UAE deliveries fail validation.

Production standard

Many people have a single name, multiple family names, or list family name first (Japan, Hungary). Many countries have no postal codes or provinces.

Production standard: Adaptive global form fields

<input name="fullName" placeholder="Full name" /> <AddressForm country={selectedCountry} />

Benefit:Accepts single and compound names gracefully, and renders address fields matching the postal rules of the destination country.

Cross-Functional Review Questions

Questions for product managers, designers, engineers, and testers to ask during sprint reviews.

For DesignQuestion #1

“Do our registration forms use a single 'Full name' field or allow optional middle/family names?”

What to look for: Sign-up forms that do not enforce rigid two-word naming constraints.
For ProductQuestion #2

“Does our shipping checkout dynamically reconfigure postal and administrative fields by country?”

What to look for: Integration with address validation libraries (such as Google Address Validation or CLDR postal schemas).
For EngineeringQuestion #3

“Are postal code validation regexes country-specific rather than hardcoded to 5-digit numbers?”

What to look for: Validation logic accepting alphanumeric UK postcodes (SW1A 1AA) and Canadian postal codes (K1A 0B1).
For QAQuestion #4

“Are checkout flows tested with addresses in Ireland (Eircodes), UAE (no postal codes), and Japan (reverse order)?”

What to look for: Verification that valid global addresses can place orders without triggering false validation errors.

Mechanism

Personal name and postal address schemas

Splitting personal names into required First name and Last name fields encodes an Anglo-American naming structure. Chinese, Japanese, Korean, and Hungarian place the family name before the given name. Spanish names use two surnames, Icelandic names use patronymics sorted by given name, and mononyms in Indonesia or South India consist of a single name. When a form only needs to display or greet a user, collect a single Full name field and an optional Preferred name or Sort as field.

In Japan, forms also collect phonetic readings (Furigana in Hiragana ふりがな or Katakana フリガナ) alongside Kanji names. Because a single Kanji sequence can have multiple valid pronunciations, phonetic fields are required for deterministic sorting and banking verification.

Postal addresses vary in field hierarchy, line order, and postal-code syntax across countries. Japanese addresses order fields from largest unit to smallest (postal code, prefecture, municipality, block, building, recipient). German street lines place the house number after the street name (Friedrichstraße 17). UK and Canadian postcodes are alphanumeric strings with embedded spaces, while Ireland's Eircode routes to an individual property. Render address fields and validation rules dynamically from country-keyed datasets such as Google's libaddressinput.

Interactive demo

Guided exercises

  1. 1
    Switch the country from United States to Japan and read the form top to bottom. The Japanese layout starts with the postal code (`〒`), moves from prefecture to city to block, and places the recipient name last with the honorific `様`.
  2. 2
    Switch to Germany. The street address places the house number after the street name (`Friedrichstraße 17`) and places the 5-digit postal code before the city name.
  3. 3
    Switch to the United Kingdom and look at the postcode. UK postcodes (`M14 5SR`) are variable-length alphanumeric strings with an internal space. Numeric-only postal validation rejects every UK address.
  4. 4
    Read the Name structures card: Spanish, Hungarian, Icelandic, mononym. Two surnames, family-name-first order, patronymics sorted by given name, and single-word names all lose structural data when forced into a binary `first_name` / `last_name` schema.
  5. 5
    Under “Run a persona through this form”, keep the persona on Japanese (family-given) and the “Form schema” on “First + Last, both required”. The family name `Nakamura` is stored in `first_name` and the given name `Haruki` in `last_name`, corrupting both greetings and directory sorting. Switching to “Single full-name field + optional 'sort as'” preserves both.
  6. 6
    Set the “Persona” to Mononym / single-name with “First + Last, both required”. Form submission fails because the required `Last name` field is empty. Switching to the single full-name schema allows submission.

Local address form

On the envelope

Alice Johnson

1600 Pennsylvania Ave NW Apt 4B

Washington, DC 20500

Updates as the form fields change.

City, state, and ZIP share one line: a comma after the city, a space before the ZIP. USPS prefers capitals on every line, for machine reading.

Name structures

Patrick McKenzie's Falsehoods Programmers Believe About Names lists forty falsehoods. A required last-name field breaks on these six.

Anglo (given-family)Alice Margaret Johnsonsort as: Johnson, Alice Margaret
Given (first): AliceMiddle: MargaretFamily (last): Johnson

Sorted by family name. Informal address uses the given name: 'Dear Alice'.

Spanish (two surnames)Gabriel García Márquezsort as: García Márquez, Gabriel
Given: GabrielPaternal surname (apellido paterno): GarcíaMaternal surname (apellido materno): Márquez

Both surnames are used, and sorting goes by the paternal one. 'Márquez' alone is a wrong citation; 'García Márquez' or 'García' is right.

Japanese (family-given)中村 春樹 / Nakamura Harukisort as: Nakamura Haruki
Family: 中村 (Nakamura)Given: 春樹 (Haruki)

Family name first in native order. Western media often reverse it ('Haruki Murakami'). Following a 2019 government decision, official documents have romanized Japanese names family name first since January 2020.

Hungarian (family-given)Bartók Bélasort as: Bartók Béla
Family: BartókGiven: Béla

Family name first, like Japanese, and unique in Europe. English sources reverse it to 'Béla Bartók'; Hungarian catalogs do not.

Mononym / single-nameMadonnasort as: Madonna
Mononym: Madonna

Stage names are a single name, and so are many Indonesian legal names (Sukarno, Suharto). A required last-name field blocks these users.

Patronymic (Icelandic)Björk Guðmundsdóttirsort as: Björk Guðmundsdóttir
Given: BjörkPatronymic: Guðmundsdóttir

The patronymic ('daughter of Guðmundur') changes with each generation. Iceland's phone book is sorted by given name, so Björk files under B; a CRM sorted by last name files her under G.

Run a persona through this form

Pick a persona and a form schema. The greeting, initials, and directory entry below use only the fields that schema stores.

What the database stores

first_name: Nakamuralast_name: Haruki

Where it renders downstream

Mail-merge greeting

Dear Haruki,

not this person's surname

Avatar initials

N.H.

computed from the stored name

Directory files under

Haruki

should file under Nakamura

The contact list, both ways

Sorted by the stored key

  1. Béla, Bartók
  2. Guðmundsdóttir, Björk
  3. Haruki, Nakamura
  4. Johnson, Alice
  5. (rejected: Madonna)
  6. Márquez, Gabriel

Sorted as each convention expects

  1. Bartók Béla
  2. Björk Guðmundsdóttir
  3. García Márquez, Gabriel
  4. Johnson, Alice Margaret
  5. Madonna
  6. Nakamura Haruki

Implementation rules

  • Collect a single Full name field whenever possible. When downstream systems require split fields, label them Given name and Family name, make the second field optional for mononyms, and format display order using CLDR PersonNameFormatter (UTS #35 Part 8).
  • Include phonetic name fields for Japanese forms. Collect Furigana (ふりがな in Hiragana or フリガナ in Katakana) alongside Kanji names so records can be sorted and pronounced accurately.
  • Drive address layouts from country metadata. Use the Google libaddressinput dataset to determine field order, required administrative subdivisions, and postal code patterns for each selected ISO 3166-1 country.
  • Remove US-specific postal and state validation rules. Do not require a state or province in countries that do not use them, and allow alphanumeric and hyphenated postal codes (such as SW1A 1AA in the UK or 100-0001 in Japan).
  • Do not restrict name characters with ASCII regular expressions. Allow single-character surnames, spaces, hyphens, apostrophes, and all Unicode letter scripts.

Operational context

Roles

EngineeringDesignProductCompliance

Workflow stages

  • ·Designing registration, checkout, and KYC identity flows
  • ·Building international shipping and billing address forms
  • ·Auditing form validation regular expressions

Production incident

Patrick McKenzie's 2010 essay “Falsehoods Programmers Believe About Names” documents forty assumptions that break production forms, including the assumptions that everyone has both a given name and a family name, that names contain only ASCII characters, and that names never change.

Falsehoods Programmers Believe About Names ↗

Terms in this chapter

Further reading

Related chapters