What 𤾸 means
It preserves a Taiwanese source code for round-trip conversion. CNS 11643 — Taiwan's national character coding standard since 1986, expanded from two code planes to seven in 1992 — catalogs this written variant of 𤾸 as T7-537B, on the seventh plane that holds character variants. Unicode treats it as the same ideograph as 𤾸, but giving the CNS entry a code point of its own means text converted between the two standards comes back with exactly the code it started with.
𤾸 is one of 542 ideographs set aside for that one job. The character it encodes is genuinely rare: Taiwan's dictionary of character variants reads 𤾸 as wěi — 'a flower', or blossoms in full flush — and treats it as an old variant of 蘤; the CNS standard simply recorded this particular way of writing it. Historical characters like this live in standards tables rather than everyday writing, and the CNS repertoire still backs the codes Taiwan's household registration relies on for rare characters in names.
Why does 𤾸 turn into 𤾸?
Any normalization pass rewrites it as 𤾸. Normalization is the quiet cleanup systems run to give every character one preferred spelling, and 𤾸's canonical decomposition points at U24FB8 — so a normalized file always ends up holding 𤾸 instead. Search indexes, databases and form handlers often normalize text on the way in; the 𤾸 code point never comes back. The ideograph itself is unchanged, but a font may now draw the more common variant rather than the form CNS recorded.
When this exact written form must survive — a Taiwanese source that distinguished the variant, say — the sanctioned route is the sequence 𤾸︀: 𤾸 followed by variation selector UFE00, an invisible code that requests this glyph shape. Unicode defines that pairing for this character, and normalization leaves it untouched. It preserves the glyph, though, not the code point: to round-trip back to T7-537B exactly, 𤾸 itself is still the code.
Use 𤾸 for ordinary text; reserve 𤾸 for data that must keep its original CNS 11643 code.
Normalization quietly turns it into 𤾸 — don't count on it surviving a cleanup pass or an import.
Who writes 𤾸
Loading…
Don't confuse it with
1Worth knowing
- Unicode's own advice is not to write this code point at all: its whole block exists so old CNS data can pass through Unicode and come back unchanged — nothing more.
Questions people ask
3Are 𤾸 and 𤾸 different characters?
No. They are the same ideograph encoded twice; 𤾸 exists only to keep its Taiwanese source code, and normalization merges it into 𤾸.
Why does 𤾸 show as an empty box?
Your fonts lack it. The character lives in Unicode's supplementary ideographic plane, which everyday fonts often don't cover — a box means a missing glyph, not a fake character.
How do I keep this exact variant shape?
Write 𤾸 followed by variation selector UFE00 — the standardized sequence for this form. It survives normalization and keeps the glyph shape; it does not bring back the 𤾸 code point.
How to type or find 𤾸
- Search it as
- 2f93c · u+2f93c · 24fb8 · u+24fb8 · t7-537b · cns 11643 · compatibility ideograph · 𤾸
- Shows up in
- Anything that takes text · its shape is whatever your font draws
𤾸\2F93CCodes and encoding1 code points
A visible symbol can contain several code points. JS .length counts UTF-16 units; UTF-8 counts bytes.


