Description: The input is ok for date,numeric and text fields but appears to fail by generating odd symbols for a currency field with a leading dollar sign but the cents component appears Ok. The data was input succesfully into Openoffice 4.1.14 and files of this type could be read by all previous versions of Libre office. I am presently using 25.2.2.2 X86_64 Build 7370d4be9e3cf6031a51beef5... The data was of the form as successfully read by Libre Writer 26/04/2025,"-15.34","WOOLWORTHS 1080 QUEANBEYAN NSW AU","+6732.34" 26/04/2025,"-18.56","ALDI STORES - QUEANBEY QUEANBEYAN AU","+6747.68" Steps to Reproduce: 1. It is bank transaction information data converted to .CSV by my bank 2. A sample read by Libre Writer is given and a sample of the fault generated by Libre Calc is given as a screen shot 3. This should be sufficient. If not please advise Actual Results: see jpg file Expected Results: see description above Reproducible: Always User Profile Reset: No Additional Info: I have never submitted a BUG report before and if the sequence of my information is inconvenient I apologise. I have been using spreadsheets since Lotus 123 in the 70's. I am now 86. Should the jpg attachment be done after the bug is "filed' rather than "filled"
Created attachment 200576 [details] a screen shot of the calc actual initial data form of CSV data as observed
(In reply to oscar Newberry from comment #1) Why do you have that UTF-7 as the encoding ("charset")? I would expect e.g. UTF-8.
(In reply to Mike Kaganski from comment #2) > (In reply to oscar Newberry from comment #1) > > Why do you have that UTF-7 as the encoding ("charset")? I would expect e.g. > UTF-8. Interesting, I see UTF-7 in more reports, see bug 166238 and bug 166208. Looks like something wrong in charset detection..
(In reply to raal from comment #3) And also in bug 166211. Somehow I feel that it's related to bug 152336 and its fix - commit 2feda8ba21acdcf33a9b4ba94742f574c17839bd "Detect charset and separators for csv files".