Check a decorated display name before sharing it

Keep an ordinary-text version

Try the fictional name Atlas Desk in the Text Style Converter. Keep the ordinary spelling in a separate note: it is the version people can type, search for, and use in instructions without needing the decorated characters.

Atlas Desk

𝐀𝐭𝐥𝐚𝐬 𝐃𝐞𝐬𝐤

The converter replaces supported letters with different Unicode characters. It does not apply rich-text bold or install a font. Another service receives those replacement characters, rather than Atlas Desk with a bold style attached.

Inspect what changed

Inspect the whole result when the input contains accents, another script, punctuation, or emoji. The supported mappings do not cover every character. Unmapped characters stay in the output and are reported; review a mixed result rather than deleting part of the name to make it look uniform.

Test the intended destination

• Paste into a draft or preview field first and check the platform’s rules for display names.
• Read the result at its actual display size, including a narrow screen if relevant.
• Check whether search, selection, or a copy-and-paste round trip changes the text.
• Retain the ordinary label wherever another person needs to identify or type it reliably.

Mathematical letters may be pronounced differently by screen readers or missed by a search for the ordinary spelling. Keep the plain name visible wherever readers need to find or identify the project. If the decoration makes that harder, use the plain name on its own.

Do not treat normalization as a general undo

For the bold A in this example, NFKC produces the ordinary A. You can preview that compatibility change, but it is not a universal way to recover an edited name. Other changes may remain, and normalization can remove distinctions you meant to keep. Retain the original rather than relying on a later repair.