Variation Selector-123

No; it requests a glyph only as part of a supported pair.

A variation sequence puts the selector immediately after a base character. The base supplies the context; the registered sequence specifies which glyph subset to use. If the pair is invalid or unsupported, the base displays normally and the selector stays invisible.

The IVD sequence file dated 2026-08-03 contains no registered sequence using this exact selector. Making up a pair does not create a variant that other systems will recognize.

How do I use variation selector 123?

Put it after its base, in a documented variation sequence.

A Chinese or Japanese input method may offer a registered glyph variant with its base character. In code, keep the two characters adjacent and use a font and renderer that support the full sequence. An editor or search tool that ignores selectors is behaving normally if it does not support variation sequences.

It does not make text bold, italic, or decorative. A variation selector can choose a glyph variant for one base character; it is not a formatting control for a span of text.

Why was the selector range created?

To preserve glyph distinctions in plain text.

The idea was documented as a Plane 14 Variant Tag in 1997, and the supplementary range entered Unicode 4.0 in 2003. This lets text keep its underlying character while also recording a documented glyph choice for a font or record that needs it.

The selector number has no universal visual meaning; the base and its collection define the distinction. The IVD release dated 2026-08-03 has separate collections for Japanese administrative records and Chinese cultural digitization. Other selector systems serve emoji presentation and Mongolian script.