The same character can have different glyph forms across regions

What it is

Locale-specific glyph variants are different conventional visual forms of the same Unicode character across languages or regions. Character encoding identifies an abstract character; a glyph is its concrete rendering. A shared code point does not require readers of Simplified Chinese, Traditional Chinese, Japanese, and Korean to receive identical stroke structures.

Why it happens

Han unification follows rules concerning character identity, semantics and abstract shape, and mappings from source standards; it does not merge forms merely because they share an origin. Regional forms can come from distinct region-specific font families, a Pan-CJK font's OpenType locl and language systems, or language-aware fallback. Document and span language metadata supplies necessary context for those mechanisms, but a tag cannot guarantee switching when the font or renderer lacks the relevant implementation.

Where it stops holding

Regional glyph variation is not Simplified–Traditional conversion. The latter can involve different characters, vocabulary, and semantic choices and cannot be performed by changing fonts. Not every shared character has a salient variant, and cross-region forms are usually still recognizable, though education, publishing, names, and formal text may require local convention. An Ideographic Variation Sequence can request a specific glyph identity when supported; it is not a general Simplified–Traditional conversion mechanism.

Applying it

• Set explicit BCP 47 metadata at document and span level—such as zh-Hans, zh-Hant-TW, zh-Hant-HK, ja, and ko—so font selection and shaping receive language, script, and regional context.
• Configure and verify font families, locl/language-system behavior, and fallback separately for Simplified Chinese, Traditional Chinese, Japanese, and Korean; do not assume the tag repairs every font.
• Keep content conversion and glyph selection separate; do not substitute a font change for vocabulary or character conversion.
• Ask target-region readers to review frequent prose, headings, names, and legal text, comparing supported platforms for foreign forms, mixed faces, and unsupported variation sequences.

Related

• Same group: S1.03.1 Missing glyphs trigger fallback and change layout · S1.03.3 Emoji and symbol rendering varies across platforms · S1.03.4 Character count is not proportional to display width
• Adjacent: S4.02 Separating locale from language · S4.05 Localization quality acceptance criteria
• Search terms: locale-specific glyphs · CJK glyph variants · localized forms