How pages are researched, measured and checked

Every page on Fancy Text Styles makes claims of three kinds: what a character is (its code point and name), whether it displays on a given system, and what an app allows you to do with it. Each kind has its own source and its own check. This page describes them, so you can judge for yourself how far to trust what we publish.

1. Characters: the Unicode code charts

Every mapping used by the generators comes from the Unicode Consortium’s official code charts, read block by block: Mathematical Alphanumeric Symbols, Letterlike Symbols, Enclosed Alphanumerics and their supplement, Superscripts and Subscripts, the phonetic extension blocks, Halfwidth and Fullwidth Forms, and Combining Diacritical Marks. The charts mark positions that are reserved and empty; those 24 positions in the mathematical alphabets are filled from Letterlike Symbols, exactly as the charts direct.

Where a style has no character for a letter, we leave the letter unchanged and say so on the page. We do not substitute look-alike characters from unrelated scripts without telling you, because those carry different meanings and can confuse search, sorting and screen readers.

2. Display: measured on real system fonts

Claims about whether a style displays come from a measurement, not from impressions. On 27 October 2026 we read the character map (the table that lists which characters a font can draw) of every system font file on a Mac running macOS 26.5.1, 365 files in all. We left out the LastResort font, which exists only to draw placeholder boxes. We did the same for the fonts Android lists in its platform font configuration that cover the blocks these styles use. A character counts as displayable on a platform if at least one font there can draw it.

We report the limits of that measurement alongside it. Windows was not measured, because its fonts were not on the test machine. A font being present does not guarantee every app uses it, since some apps ship their own fonts, so measured coverage tells you what the system can draw, not what every app will show. When a page relies on the measurement it names the date and the systems, and the scripts that produced it are kept with the site so it can be repeated.

3. Platforms: their own documentation

Rules about where styled text can be pasted, such as which Discord fields accept special characters or how Discord’s message formatting works, come from the platform’s own help center. When a feature is documented only by the community, as Discord’s colored ANSI code blocks are, the page says that it is community-documented and not an official feature. When a platform documents nothing on a question, we say that too rather than guessing.

4. The source register and what we will not claim

Every source is recorded in a register kept with the site, with what it is good for and when it was last read. The register also keeps a list of claims we do not make because no source supports them: that a style “works everywhere”, percentages of devices that display a style, apps having a font setting they do not document, or characters Unicode does not contain. Phrases like “users report” are never used in place of a source.

5. Writing, AI assistance and review

Pages on this site are researched and drafted with AI assistance, then checked and edited by Sukie before publication. Every character mapping comes from the Unicode code charts, and the display measurements were made with the method described on each page. In practice, AI helps with research summaries and first drafts. Sukie decides what each page covers, checks every character and claim against the register, removes anything unsupported, and approves the page before it is published. Examples on the pages are produced by the same code that runs the generators, so what you read is what the tool outputs.

Before a page is published it must answer a question real people ask, which we confirm from public questions and search data, and it must offer something the existing results do not: a working tool, a measured table, or detail no one else states. Pages that cannot meet that bar are not published.

6. Keeping pages current

• Each page shows a “last updated” date that changes only when its content changes. It is never set automatically.
• The whole source register is reviewed once a year, because Unicode publishes a new version annually and platforms change the fonts they ship. The next full review is due in October 2027.
• Platform rules are re-checked whenever a reader reports a change or a platform publishes one.

7. Corrections

If you find an error, email sukielovesupport@gmail.com with the page and what is wrong (see the contact page for what helps us reproduce display problems). Confirmed errors are corrected on the page itself and the update date changes. Significant corrections, those that change advice, are noted in the text of the page.

8. Independence and advertising

Fancy Text Styles is independent and is not affiliated with any platform it mentions. Advertising, where shown, is labelled, is never placed over a tool, and has no influence on content. We do not accept payment to recommend a style, an app or a service.