Detailed explanation
HTML entities and Unicode characters belong to different layers of text handling. Unicode is a standard that assigns code points to characters, such as U+0041 for A and U+00A9 for ©. UTF-8 is an encoding that stores those code points as bytes. An HTML entity, more precisely a named character reference, is HTML source syntax that represents a character: © represents ©, while & represents &. The distinction matters because character encoding and HTML parsing solve different problems.
When a browser loads an HTML document, it decodes the document’s bytes into characters using the selected encoding, then parses those characters as HTML. During parsing, character references in ordinary text and attribute values are resolved to their corresponding characters. For example, <p>© 2024 MyCompany</p> and <p>© 2024 MyCompany</p> produce the same text content when the document is decoded correctly. Numeric references also work: © and © both represent ©. These use decimal and hexadecimal Unicode code points respectively, rather than a predefined name.
For modern pages, save the file as UTF-8 and declare <meta charset="utf-8"> early in the document’s head; ensure the HTTP encoding declaration is consistent too. You can then write characters such as ©, ₹, and Hindi letters directly. However, UTF-8 does not remove HTML’s syntax rules. In ordinary HTML text, write < when you mean a literal less-than sign, since < can start markup. Use & for literal ampersands to avoid accidental character-reference interpretation. The example <p>5 < 10 & 10 > 5</p> displays “5 < 10 & 10 > 5”; escaping > is usually optional in ordinary text.
Interviewers expect you to distinguish representation from identity: a reference is a way of writing a character in HTML, not a separate character set. They may also check context awareness. Inside a double-quoted attribute, " represents a quote without ending the attribute value. Character references are not interpreted the same way everywhere; for example, they are not expanded inside script elements. For dynamic content, use context-appropriate escaping or safe DOM APIs such as textContent rather than assuming UTF-8 alone prevents markup injection.
Key points to remember
- Unicode defines characters and code points; UTF-8 encodes them as bytes.
- Named references such as © and numeric references such as © represent characters in HTML source.
- Raw © and © produce the same text when the document is decoded correctly.
- UTF-8 supports directly written multilingual text but does not escape HTML syntax.
- Escaping depends on context: ordinary text, quoted attributes, and scripts have different parsing rules.
Common mistakes candidates make
- Treating Unicode and UTF-8 as interchangeable terms, or describing entities as an encoding.
- Assuming UTF-8 makes literal < and arbitrary ampersand sequences safe in HTML text.
- Assuming HTML character references work everywhere, including inside script elements.
Likely follow-up questions
What is the difference between named and numeric character references?
Named references use predefined names, such as ©. Numeric references specify Unicode code points in decimal or hexadecimal, so © and © represent the same © character.
Must every special character be written as an entity?
No: correctly encoded UTF-8 HTML can contain characters such as © and ₹ directly. References are useful for syntax-sensitive characters and for making invisible characters, such as , explicit in source.
How should user-provided text be inserted safely into a page?
For plain text, assign it through textContent rather than innerHTML so the browser does not parse it as markup. When generating HTML on the server, use the template engine’s context-appropriate escaping.
Interview tip: Define Unicode and HTML references separately, compare © with ©, then explain why reserved syntax still needs escaping.