AppHelp guide
Unicode Escape and HTML Entity Encoding
Learn when to use Unicode escapes, HTML entities, and width conversion for text that must survive code, HTML, JSON, and documentation contexts.
Quick answer
Use Unicode escapes when a code or data context needs characters represented by code points. Use HTML entities when text must appear safely in HTML. Use width conversion when full-width and half-width characters need to be normalized for search, forms, or East Asian text cleanup.
Use Unicode escapes for code and data
Unicode escapes such as \u003c or \u4f60 represent characters by code point. They are useful when debugging JSON strings, JavaScript literals, logs, or payloads where visible characters may be hard to inspect.
- Use \u escapes for JavaScript and JSON string contexts
- Check whether the surrounding parser expects UTF-8 or escaped text
- Decode a copy before replacing source data
Use HTML entities for markup
HTML entities such as < and & keep special characters from being interpreted as markup. They are useful for examples, documentation snippets, and user-visible text inside HTML.
Normalize width only when meaning stays the same
Full-width and half-width forms can matter in names, product text, and search queries. Normalize them for matching or cleanup, but keep the original text when typography or language context matters.
Frequently asked questions
Should I use Unicode escapes or HTML entities in HTML?
Use HTML entities for HTML markup. Unicode escapes are mainly for code and data string contexts such as JavaScript and JSON.
Can width conversion change text meaning?
It can. Width conversion is useful for normalization, but preserve original text when typography, names, or language-specific formatting matters.