View Issue Details
|have not tried
|Fixed in Version
|0019101: saveTextToFileAsync needs an option for saving ANSI files and UTF-8 files without BOM
|I have the old add-on which has such option to choose if you want UTF-8 files with or without BOM.
I didn't tried the saveTextToFileAsync method yet, but its web description mentions only UTF-16 and UTF-8 for encoding. What about ANSI? It is not the same as UTF-8, even if you use only first 255 characters from the Unicode.
|No tags attached.
|Fixed in build
|Fixed in 22.214.171.12450 + added the ANSI option also to the loadTextFromFileAsync
|How about UTF-8 without BOM? Some users reported that their media players support only such playlist files.
|Reopen Some devices (Samsung BD-Player) fail to load video nfo as assume UTF-8 and fail to import files with BOM, no issues with files without BOM.
Note that the current default encoding is UTF-8 without BOM
Unicode standards are saying that BOM is not recommended, specifically:
... Use of a BOM is neither required nor recommended for UTF-8, but may be encountered in contexts where UTF-8 data is converted from other encoding forms that use a BOM or where the BOM is used as a UTF-8 signature.
But seeing this document: http://www.unicode.org/L2/L2021/21038-bom-guidance.pdf
it is not that clear for BOM specifically not recommended for UTF-8.
So I added new option 'UTF-8 BOM' in build 126.96.36.19900
Tested ANSI, UTF-8 and UTF-8 BOM