XML uses special characters as syntax, so literal text sometimes needs escaping. An unescaped ampersand in a programme title can make an otherwise readable guide fail XML parsing. If maintaining a personal guide, use an XML-aware tool rather than editing raw text through uncontrolled replacements.
Separate text from markup
A programme title belongs inside a text field. Characters that look harmless in prose can have structural meaning in XML. Correct serialization preserves the intended title while making the document readable by a parser.
Avoid double escaping
Escaping text that was already escaped can make entities appear literally on screen. A title containing & after import may have been escaped twice. Keep the original source value and let a proper XML library serialize it once.
Validate locally with a small sample
A parser error can identify a line near the problem, but the actual malformed character may appear just before it. Work on a private copy and retain the exact error message. Do not upload credential-bearing guide resources to public validators.
A practical sequence
- Use an XML-aware editor or library.
- Escape text once during serialization.
- Test a small local sample before replacing the complete guide.
An example
A title written as Arts & Science needs the ampersand represented safely inside XML text. The viewer should still see the ordinary ampersand after the reader parses it.
Questions about this topic
Should viewers see XML entities in titles?
Normally no. The reader should decode them into text.
Will changing the filename repair malformed XML?
No. The content structure must be corrected.
