That error output message is gone. Thank you so much ^^
1 Like
I’m a bit confused @todoooo , could you clarify this change ? Is this a bug we should fix ?
It could be described as a bug or a contents error or both depending on your perspective.
Presumably someone using a non-US keyboard accidentally typed what looked like a hyphen, but which was actually an extended character, into the XML text. I haven’t checked whether or not the parser only expects ASCII text or can process UTF8 but anyway the extended character gets converted into garbled bytes when a non-English locale is used and the parser then fails.
Replacing the text resolved the problem so that change needs to happen in Paraview git. However this error could easily happen again so a useful fix would be a more descriptive error message to immediately identify the file name and offending text.
Ok, got it. This small change should be done definitelly.
A more complete correction would be nice indeed.