https://bugs.documentfoundation.org/show_bug.cgi?id=172905
--- Comment #5 from ady <[email protected]> --- To expand or to clarify what I posted in comment 1, I am not sure that I fully understand the report. If indeed the original csv file is (somehow) "exclusively" encoded as "Latin1", then setting that locale in the import dialog _once_ should import the csv correctly, and then it should keep that locale as default for the next time the import dialog is used (until you manually change it). The part that I don't fully understand from the report is how exactly Calc should know to "automatically" set the locale to "Latin1" in the import dialog. Since I am able to copy the content from comment 0 and build from it a UTF-8 encoded csv file, then the problem could potentially be focused on how the original csv file is built in some non-Unicode way, rather than on Calc's import dialog. Since we don't have access to an original sample csv file nor to the way it is created / built, I am not sure how exactly we could improve Calc in any way. IOW, we would need more details. -- You are receiving this mail because: You are the assignee for the bug.
