Saxon

Tricky one. There are two reasons for this:

(a) on many systems, console output doesn't display the characters correctly. It's probably capable of displaying them if configured correctly, but we have no control over that

(b) errors like this are often caused by using a character that is visually similar to the required character

Perhaps the right answer is to display it with the real characters followed by the hex in parentheses.

The other issue is that we are formatting it like this even when the message is written to an XML validation report. Really we should emit validation messages with structural markup and then render the markup according to the output destination.

On 18 Oct 2017, at 07:39, Saxonica Developer Community notifications@plan.io wrote:

I did some more tests and found this:

<xsl:stylesheet version="3.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">

<xsl:template match="/"  日本="">

	<xsl:日本/>

</xsl:template>

</xsl:stylesheet>

From the command prompt, this produces two errors messages, one of them is escaped, the other is not:

Static error in xsl:template/@?? on line 3 column 33 of ABC.xsl:

XTSE0090: Attribute @\u65e5\u672c is not allowed on element xsl:template

Static error at xsl:?? on line 4 column 12 of ABC.xsl:

XTSE0010: Unknown XSLT element: ??

Errors were reported during stylesheet compilation

In Java my error listener receives:

Attribute @\u65e5\u672c is not allowed on element xsl:template. <<< Escaped

Unknown XSLT element: 日本. <<< Not escaped

Also, one message is escaped, the other is not.

I would like to receive the error messages without Unicode escapes.