Issue 125175

Summary: reading .csv dates depends on language
Product: Calc Reporter: TAB <TorrAB>
Component: open-importAssignee: AOO issues mailing list <issues>
Status: CONFIRMED --- QA Contact:
Severity: Normal    
Priority: P3 CC: kschenk, TorrAB
Version: 4.0.1   
Target Milestone: ---   
Hardware: All   
OS: All   
Issue Type: DEFECT Latest Confirmation in: 4.1.0
Developer Difficulty: ---
Attachments:
Description Flags
csv file with dates none

Description TAB 2014-06-28 19:45:58 UTC
Created attachment 83622 [details]
csv file with dates

Read 1403.csv (as provided by my bank) with options: separated by Comma; Detect special numbers, Language: EngUSA. The dates in col.A have the year truncated to '14'; they can be converted, eg, to the ISO format, eg: 03/12/14 --> 2014-03-12. Good.
	Close the file without saving the changes, and re-read it with: Language: EngCanada. The dates are now read as text, eg, '03/12/2014', left-justified (like text, not numbers). They cannot be converted to another date format unless the leading apostrophe in the InputLine is deleted first.
	There should not be such a difference between variants of English.
Besides, the format mm/dd/yyyy is not specifically Canadian; the US government uses it.
Comment 1 Kay 2014-07-07 23:20:27 UTC
Using Linux-32, version --
AOO411m1(Build:9770)  -  Rev. 1604099
2014-06-30_07:13:14-Rev.1606633

4.1.1-dev


Confirmed that something very odd is happening here.

When I change the type of field from "standard" to "date" when opening the csv (on import), everything is fine in either version of English -- US or CA.

When I leave the field definitions unchanged on import, even I try to change the definition for what we assume is the date column -- Column A -- after opening, nothing happens. No change in date format.

So why? Then I notice on import with this option, no additional field specification on import, I see a tick mark (') in the front of the date value thereby throwing the formatting change off. Once I remove this tick mark form both dates, everything works as expected.

I am not sure why this mark was inserted. This DEFINITELY needs attention.

Changed component to "open-import" instead of formatting.
Comment 2 Oliver-Rainer Wittmann 2014-07-08 07:58:49 UTC
reset field Target Milestone as we are in general set this field when it is more or less 100% clear in which version a solution for the issue will be available.