Skip to main content

Answers

Short, direct answers to common questions about text styling.

Short, direct answers to the questions that come up most often. Each one leads with the actual answer rather than three paragraphs of preamble, then explains what to do instead when the answer is no.

If a question here has a longer treatment, it links through to the relevant guide.

A note on how these are written: where the honest answer is 'no, and here is why', we say that rather than inventing a workaround. Most of the limits described here come from how Unicode itself works, and no generator — ours included — can engineer around them. Knowing which constraints are real saves more time than a clever-sounding trick that fails silently in production.

If a question here changes because a platform changed its rules, the answer changes with it and the updated date moves.

What you'll learn

  • Which constraints are genuine limits of Unicode rather than gaps in a particular tool
  • When the honest answer is no, and what the sensible alternative is
  • Whether styled text can be found by search — and what that costs you
  • What an empty box on someone else's screen actually means
  • Why a display name accepts styled characters but a username refuses them
  • How styled headings affect the keywords a page ranks for
  • How to convert styled text back into ordinary letters

All pages in Answers (5)

Common questions

Why are these so short?
Because most of these questions have short answers, and padding them out wastes your time. Where the reasoning genuinely matters, the page links to the guide that covers it properly.
The answer to my question is 'no'. Is there a workaround?
Usually there is a different approach rather than a workaround. Each answer ends with what to do instead, because the underlying constraint is normally in how Unicode works and cannot be bypassed.
Can I suggest a question?
Yes — the contact page explains what to include. Questions that come up repeatedly get added here.

Related topics