Unreadable programme names can result from interpreting text bytes with the wrong character encoding. The content may be intact while the displayed characters are wrong. Replacing every unfamiliar symbol by hand can destroy information and make a later correct decode impossible.
Start with the original file and its declared encoding where present. XML has rules for identifying and declaring text encoding. The declaration, actual bytes and importer behaviour need to agree; merely editing the declaration does not convert the text.
Recognize the pattern
If many accented letters become the same odd sequences, a systematic decoding problem is more plausible than hundreds of independent spelling errors. If only one title is wrong while the rest of that language reads correctly, the source record itself may need attention.
Missing-glyph boxes are another possibility. The player may have decoded the characters correctly but lack suitable font coverage. That is a display issue rather than proof that the source bytes are damaged. Compare the same text in an appropriate local viewer before rewriting it.
Preserve before converting
Do not repeatedly save the same damaged-looking text through guessed encodings. An initial display mistake can become permanent data loss if unsupported characters are replaced during saving. Retaining the original gives a recovery point.
- Keep the original guide unchanged and work on a private duplicate.
- Inspect any encoding declaration and identify the actual text format.
- Compare a few known words across the source and player display.
- Use a real encoding conversion only when the original interpretation is established.
- Reimport a small sample and check several languages or scripts represented in the file.
Keep language metadata separate
The language of a description does not define its byte encoding. A multilingual guide can represent several scripts in one suitable Unicode document. Changing a lang value does not repair text that was decoded incorrectly, just as changing a filename does not transform its contents.
For support, provide a harmless short example of the expected word and the displayed result, along with the encoding declaration and player version. Avoid copying long programme summaries or private source URLs. State whether the problem affects all text, one script or a single record. That pattern helps distinguish a source error, decoding mismatch and font-display limitation without forcing a broad destructive cleanup.
Useful answers
Does changing the XML encoding declaration convert the bytes?
No. A declaration and an actual encoding conversion are different operations.
Can missing character boxes be a font problem?
Yes. Correctly decoded characters can still lack display glyphs.
Does the description’s language tag determine its encoding?
No. Language metadata and byte encoding serve different roles.