-
Aleksander Morgado authored
If the input file is not valid UTF-8, we now try: * UTF-16, if NUL bytes are found in the string (windows-1252 and locale encodings are not expected to have NUL bytes within the string). * If locale encoding is not UTF-8, try with the locale encoding. * If locale encoding didn't help, try with windows-1252. Fixes GB#655383.
9b8010c6