Unicode 18.0.0

Why can a newly assigned character be missing from an older font?

DerivedAge lists U+209D as first assigned in Unicode 18.0. A font built before that assignment has no reason to contain a glyph for it. Code points: U+209D. Age is not a device, operating system, or application claim. Whether a particular font includes the glyph was not tested, except where the exact response includes a bundled preview cmap hit. No fallback is suggested. Font coverage, shaping, and application acceptance were not tested, so those results are unknown.

Code points

₝ U+209D

What was checked

Unicode age and older fonts

DerivedAge lists U+209D as first assigned in Unicode 18.0. A font built before that assignment has no reason to contain a glyph for it.

Age is not a device, operating system, or application claim. Whether a particular font includes the glyph was not tested, except where the exact response includes a bundled preview cmap hit.

Read visibility.age on the exact response. If the destination font predates that assignment, expect a missing-glyph sign or omission. Do not describe that as a firmware block.

What this does not prove

No OS, font, browser, application, field policy or rendering engine was tested. Unicode validity and segmentation do not establish actual display or acceptance.

Machine-readable JSON · Exact lookup · Markdown · Capability lab