How We Test Display

Every “Where it displays” table on this site marks a cell “not checked” until we have a real test behind it, with a date. This page explains exactly what counts as a real test here, so you can judge how much to trust a result.

Font glyph coverage

Each style on StylishText replaces ordinary letters with separate Unicode characters from specific blocks (Mathematical Alphanumeric Symbols, Enclosed Alphanumerics, and others). Whether a style displays correctly on a given system first depends on whether that system’s fonts actually contain those code points. We check this directly: we inspect the character map of the common fonts a desktop or Android system ships with — Noto Sans, Noto Sans Math, Noto Sans Symbols, Noto Sans Symbols 2, DejaVu Sans and Open Sans — and record what share of a style’s characters those fonts can draw. A style scoring under 100% coverage is marked accordingly, with the date we checked.

Rendering in a real browser

Alongside the font check, we load the live tool in an actual desktop Chromium browser to confirm the styled result renders, copies, and displays as expected — not just that a font file theoretically contains the glyph.

What “not checked” means

We do not have an iOS device fleet, and Apple does not publish its system font’s character coverage, so iOS results stay marked “not checked” rather than guessed. The same applies to any specific app version we have not personally tested. “Not checked” means exactly that — unknown — never “assume it works.”

Updating a result

When we (or a reader, through the “suggest a fix” box on a style page) run a new real test, we replace the relevant cell and its date. Results can go stale as apps update their fonts and filters, so a result’s date is part of the result — treat an old date as due for a recheck, not as permanent.