Maybe your JVM's default charset has changed? Try -Dfile.encoding="UTF-8"
when you start Java.
Even if that fixes things, it's perhaps still a bug. The tool should
probably not depend on the default charset, but should explicitly set its
expected input encoding. So, if that's the problem, please file an issue.
On Mar 17, 2017 2:06 AM, "nick lawson" <[EMAIL PROTECTED]> wrote: