Invalid Charset Encoding breaks Win32 GUI
When running the attached shape file through the Win32 GUI, the charset has invalid characters according to the log (though, really, something else is probably going wrong, like things not being transcoded at all, since all the bytes in the stream can be transcoded from WIN1252, they just might get transcoded to the wrong codepoint). Anyhow, things break. Probably we need to expose the new "ignore failures" option and also review whether things are even being transcoded at all, and possibly consider aborting the whole translation when a failure is hit: as it stands, the GUI just starts logging piles of errors.
Invalid Charset Encoding breaks GUI → Invalid Charset Encoding breaks Win32 GUI
new → closed