Symbols—currency signs, mathematical operators, dingbats—usually arrive as Unicode characters inside UTF-8 documents.
Authoring tips
- Use OS character palettes or Unicode escapes in editors.
- Specify fonts supporting uncommon scripts.
- Fall back to descriptive text when fonts might fail.
Advanced notation
Complex equations often require MathML or server-rendered images/SVG with accessible descriptions.
Combining characters
Diacritics may compose via combining code points—ensure normalization (NFC/NFD) matches backend expectations.
Font fallback reality
Rare symbols render as “tofu” boxes if font stacks omit coverage—pair symbols with text fallbacks in UI copy, not only in CSS.
Example — common symbols (character + reference)
<p>© © · € € · × × · ± ± · π π (when defined)</p>Rendered output
© © · € € · × × · ± ± · π π
Important interview questions and answers
- Q: What is the safest default character encoding for modern HTML?
A: UTF-8, declared early with `` and matched by server `Content-Type` headers. - Q: When are HTML entities still useful in UTF-8 pages?
A: For reserved characters (`&`, `<`) and contexts where explicit escaping avoids parser ambiguity. - Q: What is the key difference between HTML5 parsing and XHTML parsing?
A: HTML5 recovers from many errors; XHTML (XML) treats many parse errors as fatal.
Tip: Declare charset UTF-8 so symbols render without numeric entities.