To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=87999
------- Additional comments from [EMAIL PROTECTED] Mon Apr 7 11:52:37 +0000 2008 ------- no, I do not instruct OpenOffice to import my data (see original post) as US English and the whole point is that I would like not needing that. the data is not US English data and my colleagues here see this behaviour in OOo as an extra non obvious step as compared to M$Excel. at home I have a linux-powerpc machine, with locale set to 'en_DK.UTF-8' and I don't experience this defect there. here at office they gave me a windows machine (XP), Dutch localized. I installed the English version of OOo 2.4 (same as at home). I don't know where to look, in windows, for the answer to "What is the local setting of your OS?" but I assume it's Dutch (context menus in explorer are in Dutch). the OOo locale is set to Default Is in "Tools>...>Decimal seperator key" the option "Same as local setting" checked? setting or unsetting this option does not alter the behaviour "type/import 1.13 and get 13-01-08" as I see it, my locale settings say that I should type "13-1" to mean 13th of January of the current year. the same setting also say that I should type 13,1 if I mean 13+1/10. so actually the string 13.1 should either be left uninterpreted as a string (does not respect any known format) or if the program wants to be kind and helpful, it could be interpreted as a floating point number, which I believe would be the case in most cases. interpreting it as a date is based on the German format for dates, where the Germans use the '.' to make an ordinal number out of the preceding cardinal number, but the fact is that: 1) both day and month should be followed by that dot in the German notation for dates 2) Dutch, Italian, French, Spanish, are all not German and we all don't understand why 13.1 should mean January 13th at all... I notice that the English (Eire) locale comes quite close to what I expect and I think I can live with this. but I insist that you reconsider the fallback to parsing as date (using a sloppy rule from a different locale) as a default behaviour for unparseable input (which would be parseable as float in the most widespread locale) --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
