Saxon

Sigh, apologies for the duplication. The "Edit" button is apparently "Add Comment". The original description the escaping was unescaped. The comment reflects the escaping as required.

I tried "& a m p; q u o t ;" but that just ended up as "& a m p; q u o t ;" in the output.

Oh right, I failed to spot that you were actually serializing this twice, first with character maps and then without. If the first serialization phase puts an "&" into the output, then the second serialization phase will output this as "& a m p ;".

I don't think there is anything you can input to the second serialization phase that will force it to produce "& q u o t ;" in the output, without further use of character maps. Presumably you are doing it this way, rather than using xsl:character-map, because you don't want the character map to apply globally. But I think you will need a character map for the final serialization, whether or not you use one initially.

Perhaps your output:serialization-parameters should map x34 to something like §§§§ that is not going to appear anywhere else (you can use Private Use characters if you want), and then the final xsl:output should use a character map that maps §§§§ to "& a m p ; q u o t ;".

Thanks, I failed to realize I was serializing this twice myself. This solution worked. Thank you for your help.