Tatu Saloranta

I don't have time or interest to work on this issue, but if someone wants to try come up with a change to allow better handling of non-well-formed content, would...

Please include a (unit) test to reproduce the problem. Textual explanation and exception is unfortunately not enough to have an idea of what might be happening.

Also: this may well be a limitation of Multi-Schema Validator (component Woodstox uses for validation modes other than DTD), so if there's a test, probably would need to file an...

Thank you for reporting this. I do not know for sure whether this is supportable: since actual validation logic is provided by MSV (multi-schema validator), that would give the ultimate...

For what it is worth, Woodstox is using the latest release of MSV, 2013.6.1: http://mvnrepository.com/artifact/net.java.dev.msv/msv-core otherwise only found this: https://java.net/jira/browse/MSV-24 which could suggest that validation is not supported. On the...

Hmmmh. I have to think about this -- it will add measurable performance overhead for all use, regardless of whether user actually needs or wants this location information. It probably...

There is currently no way to do that at this point; you would need to catch exception and create a replacement. If someone wanted to implement a feature like that...

Added a label to indicate that I probably won't have time to work on such a feature myself, but would be happy to help getting a PR merged (and suggests...

All validation wrt XML Schema is done indeed by MSV; however, Woodstox parser core will need to feed the content so it is also possible that Woodstox might not be...

I would need a reproduction in code form: existing should work as expected wrt surrogate pairs. But would this character actually be a valid XML character as per XML 1.0...