Issue 25201 - csv decimal values imported as date value
Summary: csv decimal values imported as date value
Status: CLOSED DUPLICATE of issue 1145
Alias: None
Product: Calc
Classification: Application
Component: code (show other issues)
Version: OOo 1.1.1b
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: ooo
QA Contact: issues@sc
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-02-07 02:44 UTC by sparcmoz
Modified: 2008-04-11 08:12 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
english lang (107.00 KB, image/png)
2004-02-07 02:46 UTC, sparcmoz 		no flags Details
normal import (81.15 KB, image/png)
2004-02-07 02:47 UTC, sparcmoz 		no flags Details
expected result (104.20 KB, image/png)
2004-02-07 02:48 UTC, sparcmoz 		no flags Details
non english lang (106.53 KB, image/png)
2004-02-07 02:49 UTC, sparcmoz 		no flags Details
non english import dialog (80.81 KB, image/png)
2004-02-07 02:50 UTC, sparcmoz 		no flags Details
displayed as date?? (104.32 KB, image/png)
2004-02-07 02:51 UTC, sparcmoz 		no flags Details
US english - but why? (83.97 KB, image/png)
2004-02-07 02:52 UTC, sparcmoz 		no flags Details
a comma is displayed -- is that US or icelandic? (104.27 KB, image/png)
2004-02-07 02:54 UTC, sparcmoz 		no flags Details
test file (83 bytes, text/plain)
2004-02-07 03:01 UTC, sparcmoz 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description sparcmoz 2004-02-07 02:44:40 UTC 
See Screenshots attached.
(a) expected correct behaviour
lang-1 --> my language settings
dial-1 --> csv import dialog
result-1 --> 1.8526 displayed a sdecimal value

(b) unexpected behaviour
lang-2 --> select Icelandic (or any non english)
dial-2 --> csv import dispalys source as standard - 1.8526
result-2 --> a date value ??

(c)
dial-2a --> if i select US english for that column
result-2a --> displayed as 1,8526

Comment:
(1) how would users know they need to touch that coulumn? the error is only seen
because it is so obvious in a small dataset

(2) why would an icelander need select "us-english" to display 1.8526 as 1,8526
instead of 01.01.26??

Hope this helps a little ...
Comment 1 sparcmoz 2004-02-07 02:46:22 UTC 
Created attachment 12954 [details]
english lang
Comment 2 sparcmoz 2004-02-07 02:47:25 UTC 
Created attachment 12955 [details]
normal import
Comment 3 sparcmoz 2004-02-07 02:48:21 UTC 
Created attachment 12957 [details]
expected result
Comment 4 sparcmoz 2004-02-07 02:49:33 UTC 
Created attachment 12958 [details]
non english lang
Comment 5 sparcmoz 2004-02-07 02:50:33 UTC 
Created attachment 12959 [details]
non english import dialog
Comment 6 sparcmoz 2004-02-07 02:51:37 UTC 
Created attachment 12960 [details]
displayed as date??
Comment 7 sparcmoz 2004-02-07 02:52:40 UTC 
Created attachment 12961 [details]
US english - but why?
Comment 8 sparcmoz 2004-02-07 02:54:24 UTC 
Created attachment 12962 [details]
a comma is displayed -- is that US or icelandic?
Comment 9 sparcmoz 2004-02-07 03:01:06 UTC 
Created attachment 12963 [details]
test file
Comment 10 ooo 2004-02-09 00:33:12 UTC 
Hi Jim,

Including more or less my commments from the debian-openoffice list:

Parsing of CSV data works the same as if typed in to a cell. In Standard
column type mode, if no valid numeric input could be determined (and
1.8526 in is_IS 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.

Discussion of this behavior isn't new, and issue 1145 can be regarded as
a placeholder.

Eike

*** This issue has been marked as a duplicate of 1145 ***
Comment 11 ooo 2004-02-09 00:34:09 UTC 
Close dupe.
Comment 12 mfrasca 2008-04-11 08:12:50 UTC 
if you stumble on this issue, you might want to check
http://www.openoffice.org/issues/show_bug.cgi?id=87999
(which is still open) and vote for it.