Tatu Saloranta

But Woodstox should handle encoding from Java modified UCS-2, with surrogate pairs, into UTF-8 output (or whatever encoding is used) without problems. Unless these characters are outside range of what...

Good suggestion on API. While I'd love to be able to combine accessors into one, this would have benefit of allowing check for type first (bytes or chars).

No. Pull requests welcome.

When constructing `String` out of broken UTF-8 content, what happens? I am guessing invalid byte gets decoded as "question mark": https://www.fileformat.info/info/unicode/char/0fffd/index.htm which will then add garbage to attribute value. I...

Quick note: although validation is accessed via Stax2-api, implementation is provided by Woodtox. So will transfer issue to woodstox repo.

Woodstox has MSV-based validator implementation, and MSV has not been developed for years. If you or someone else finds alternate validator that can work on incremental/streaming input, it is possible...

@michaelhkay unless I misunderstand what you mean by Saxon's schema validator running in push mode, this seems compatible with the way Woodstox works both for Stax (pull) and SAX modes...

@michaelhkay yes, right, makes sense. For practical reasons (to be able to use MSV validators), validation approach is pull/push combination with a simple interface to allow plugging in different backends...

First things first: shaded dependencies are only needed for XML Schema based validation, so in theory they could be extracted as separate artifacts. This probably would require creation of new...

@adamretter Hi there! Yes, Woodstox does actually cache DTDs already. I forget class names, but it should be relatively obvious; but if you can't find it let me know and...