A nanopublication cannot be changed once published, so a query whose SPARQL does not parse would be broken permanently: it could never run, and the only remedy would be publishing a corrected version.

Since nanopub-java 1.94.0 both signing and publishing refuse such a nanopublication, reporting the parser's own error, and check reports it as an issue. This catches the doubled-backslash mistake at signing time rather than after publication.

Where the parser stops at a character outside ASCII, the message names it, because these queries are more often broken by a character picked up from a word processor or a web page than by a mistyped keyword. A non-breaking space, for instance, is reported as Encountered: '160' (160).

Older versions of the tool have no such check: they sign and publish the nanopublication, and only the query API rejects it afterwards.