Precomposed and Combining Characters

Quick copy

Details for U+00E9

LATIN SMALL LETTER E WITH ACUTE

Exact sequence: é

U+00E9

Details for U+0065 U+0301

LATIN SMALL LETTER E + COMBINING ACUTE ACCENT

Exact sequence:

U+0065 U+0301

Click a character to copy it. Use Details for its technical record.

The strings é and e followed by combining acute can look alike while storing different scalar sequences. Copying should preserve the sequence you selected.

U+00E9 is a precomposed character. U+0065 U+0301 is its canonical decomposition. NFC composes eligible sequences; NFD decomposes and canonically orders them. Both forms retain the canonical relationship, but their bytes and scalar counts differ.

Not every base-and-mark combination has a precomposed character. Q followed by combining acute remains a sequence under NFC. Do not invent a single code point for a glyph that your font happens to draw as one unit.

Kana demonstrates the same distinction outside Latin: U+3070 decomposes to U+306F U+3099. Font rendering may vary; a screenshot does not identify the underlying sequence.

Exact examples

Details for U+0051 U+0301

Exact sequence

Exact sequence:

U+0051 U+0301

Details for U+3070

Exact sequence

Exact sequence:

U+3070

Details for U+306F U+3099

Exact sequence

Exact sequence: ば

U+306F U+3099

Original code pointsNFCNFDNFKCNFKD
U+00E9é
U+00E9

U+0065 U+0301
é
U+00E9

U+0065 U+0301
U+0065 U+0301é
U+00E9

U+0065 U+0301
é
U+00E9

U+0065 U+0301
U+0051 U+0301
U+0051 U+0301

U+0051 U+0301

U+0051 U+0301

U+0051 U+0301
U+3070
U+3070
ば
U+306F U+3099

U+3070
ば
U+306F U+3099
U+306F U+3099
U+3070
ば
U+306F U+3099

U+3070
ば
U+306F U+3099

Try the normalizer · Split clusters · Inspect encoded candidates · Precomposed and combining text

Sources, versions and limits

Encoded properties
Properties use Unicode 17.0.0. Normalization follows UAX #15; grapheme boundaries follow UAX #29. Script associations describe encoded properties, not language use.
Language evidence
CLDR 48.2and the IANA registry dated 2026-08-08. Main and auxiliary exemplars are distinct. CLDR exemplars are not complete orthographies.
Review and limitations
The dataset is derived from the sources above. Editorial guides cite additional scoped authorities. No native or specialist orthography approval is implied. Release scope date: 14 September 2026. Historic or specialist usage needs separate evidence. Registry-only records have unknown orthography in this release.
Reproduction and corrections
Downloads and licences · Coverage and held routes · Suggest a source-backed correction