https://bugs.documentfoundation.org/show_bug.cgi?id=158025
--- Comment #5 from Jonny Grant <[email protected]> --- (In reply to Ming Hua from comment #4) > (In reply to Jonny Grant from comment #0) > > Description: > > Calc Open CSV Chinese characters for UTF8 file after UTF16 file with BOM > > > > Steps to Reproduce: > > 1. Open UTF-8 CSV file (no BOM) utf8.csv - click through the import dialog. > > 2. Open UTF-16 CSV file with BOM utf16.csv - click through the import > > dialog. > > 3. Open utf8.csv again and observe that it shows corrupted chinese text in > > the import dialog. > > Screenshot attached. > The screenshot shows that "Character set" is set to "Unicode (UTF-16)", so > of course the UTF-8 encoded file can not be displayed properly. > > I assume the import will be OK if the user manually set "Character set" to > UTF-8 manually in step 3? > > If so, then the bug is that CSV import dialog doesn't remember the choice of > encoding last time a file is opened. I'm positive I've seen such a bug > before. Dear Ming Hua Thank you for your reply. The bug appears to be that a UTF16 BOM in a genuine UTF16 file, is remembered by Calc. It then stays in UTF16 mode. It does not return to a default of UTF8. The test files are attached. Note, my UTF8 file does not contain a BOM. -- You are receiving this mail because: You are the assignee for the bug.
