Created attachment 127845 [details] Demo of the results described in the report Importing from a csv (plain text file) there may occur fields containing a decimal mark (of the respective locale) and nothing else. In a column of 'Standard' type this results in a numeric 0 in the target cell. I tested with 5.2.2.2 rc with the dot in English locale and with the comma in German locale to the same result. To use a text delimiter was no rtemedy nor was preparing the cells of the sheet with format code "@" ('Text'). This is a regression! V5.1.4 did not show the bug. Steps to reproduce: 1. Create a virgin spreadseet document. 2. Make sure to know your decimal separator. 3. Copy the text lines (at least first 2) from the bottom of this post. 4. Go to your sheet and choose 'Paste special...' > 'Unformatted text' 5. Set the semicolon as the only separator. No 'Text delimiter'. 6. OK 7. Verify that the respective cells got the content 0 (numeric). 8. Change your import settings now to " as text delimiter and repeat tests. 9. Verify no change. There are a few additional statements in the attached example. My;first;test;.;is;this;. For;comma;locales;,;however;we have;also a;test;. My;first;test;".";is;this;"." For;comma;locales;",";however;we have;also a;test;"." "My";"first";"test";".";"is";"this";"." "For";"comma";"locales";",";"however";"we have";"also a";"test";"."
Can't reproduce, I don't get any 0 zero, neither with only the first two lines copied nor all. Which platform and locale are you on anyway? (assumed de-DE German Germany) See Help -> About, you can copy&paste that information.
I am on Win 10. My UI is English (UK) (and rarely changed). As locale I have mostly set German (Germany), but this changes as required. The bug itself did not occur during my regular work but was the background of a question posted here: https://ask.libreoffice.org/en/question/78855/period-in-cell-being-interpreted-as-0/. I tried to answer the question, requested additional infornation, and verified the claims. Thus: If the strange observation is due to specifics of my surroundings or to a flaw in my user profile, I am not the only one experiencing the issue. The attached example is no fake. It was actually created as described. Just the additional testing lines were created on the fly in this editor. Maybe 5.2.2.2 rc is the only version suffering from the bug.
OK. Suspended my user profile and created a virgin one. Tested again. Bug had vanished. How comes? These user profile issues tend to get creepy.
@Wolfgang: Do you happen to have the old profile still around? Or did you remove it? If it's still available you can zip it and send it to my email (it might contain sensible information so you may not want to attach it to the bug), you can also encrypt it to my GnuPG key if you wish: 0x6A6CD5B765632D3A
Zipped user profile sent.