What to do when Tamino rejects documents with & and & auml;


as has been pointed out several times, Tamino will insist on well-formed XML. Some of you have wondered what to do with (presumably generated) HTML style documents, where the unescaped & (like in “Fish & Cage”) never before posed a problem, but now Tamino won’t load the document.

A similiar problem appears when having charakters like