https://bugs.documentfoundation.org/show_bug.cgi?id=165209
Mike Kaganski <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEW CC| |[email protected] --- Comment #6 from Mike Kaganski <[email protected]> --- This works as designed; but in this specific case, I'm inclined to agree that this is a bug. The reason of the problem is, that the settings chosen in the text import dialog are *completely not* about how the result should *look like* (be formatted in when imported), but how Calc should *read* the text values from the CSV. The process is: 1. User chooses locale (and other settings) in the dialog. Suppose "en-US"; 2. Calc reads a text like "abc", or "123", or "$1,234.56", and tries to interpret the text into a number *using the locale that user specified*. Given the locale chosen above (en-US), the program would keep "abc" as text, but would convert both "123" and "$1,234.56" into numbers 123.0 and 1234.56 (and will additionally remember, that the last value was imported using a currency number format - just *some* currency, not "US Dollar" - the same as when it imports a date, it converts it to the serial date number, and remembers, that it was *some* date format, not "long date format of Netherlands"); 3. After interpreting the values, it puts them to cells of a newly created Calc spreadsheet (having the locale configured for the whole program by the user; in this case, comment 0 tells us, that the program locale is en_GB). Putting a number with "currency" "tag" means, that the current cell's locale is used to choose the default currency format - the same, again, as we have for dates. But while with dates it's more than reasonable (a user from Europe, who imported a date written in en-US custom, would dislike to discover that they have to read it in an opposite direction, and what they perceived "5h of October" was in fact "10th of may", and they missed the deadline), with currencies, it's different. When a price is in USD, it's not the same as same amount of GBPs. -- You are receiving this mail because: You are the assignee for the bug.
