Hi Jim, On Sat, Feb 07, 2004 at 13:26:04 +1100, Jim Watson wrote:
> it does not seem correct to me. Well, it depends ;-) > The source csv file contains data such as 1.8526 > > The user does not know about that data, they only know what they see > when it is imported. As long as you don't change the column type it is imported the same way as if typed in. > The original problem remains that this data 1.8526 is imported and displayed > as a "date". > > For example with "Italian" the csv import dialog displays standard column > "1.8526" but the imported spreadsheet stored value is "01.01.8526". If I > select that cell it displays Sum="01.01.8526". The same if typed in. Whether that behavior is really what you want depends. In Standard column type mode, if no valid numeric input could be determined (and 1.8526 in it_IT locale isn't numerical since the decimal separator is the comma) several date representations are tried, [./-] are recognized date separators and if the remaining digit groups could form a valid date then this is taken. This recognition is the real thing what people bothers, also in keyboard data input, there isn't anything special about CSV file import. > The correct default (standard?) behaviour surely must be to import > and display the data exactly as it is stored in the csv source file? There is no locale assigned to CSV files.. so OOo uses the locale the user works with unless she changes the column type. Not that strange, is it? > I was not the reporter for this but I will make an IZ issue and put some > screenshots which will make it clearer. Oh no, please don't, it's perfectly clear ;-) Eike -- GnuPG key 0x293C05FD: 997A 4C60 CE41 0149 0DB3 9E96 2F1A D073 293C 05FD
