https://bugs.kde.org/show_bug.cgi?id=496215
--- Comment #2 from Alexander Semke <alexander.se...@web.de> --- (In reply to Alex E from comment #0) > SUMMARY > > I tried to import a CSV file but the app refused to see it. Passing the file > through LibreOffice Calc and copy/pasting the data led to text columns and > trying to convert to numerical crashed the app. I then tried to read the > same file in a Python script and that's when I realized that it was encoded > in UTF-16. Opening with Kate and saving as UTF-8 solved all the issues. > > The file in question was either generated as such by a scientific > instrument's software (it's spectrometer data), or it was passed through > Microsoft Office and somehow ended up with UTF-16. Either way, I think it's > possibly a common occurrence and potential source of frustration for > scientists who aren't very code savvy and have to work in a Microsoft/Origin > dominated ecosystem. > > It would be nice to have at least a more verbose error message, if not full > support for files with such weird encodings. Thank you for reporting this issue. We implemented an error message that is shown in the import dialog for such files, it will be part of the next release 2.12. Above you mentioned a crash of the application when working with utf16. In case this is reproducible for you, can you please provide the steps for how to reproduce this issue? -- You are receiving this mail because: You are watching all bug changes.
