JWt

Currently JWT uses NanoXML (n3). This is a old library that no longer maintains support.
We should switch to a more modern library, that is still supported.

The case that performs the check on unicode is very straightforward though, the StdXMLReader.read() checks a character's range.
This range omits some non-character items. But seems to omit too many. An example is "🔥" (read as integer 55357 AND 56613, or HEX value 0xD83D AND 0xDD25). Unicode specifies this at 0x1F525, but this is being read as UTF16.
This leads the characters to fall into the range of high surrogates. Currently unused values, but valid nonetheless.

They should be included (and allowed) when parsing.