Issue 54341 - Save to Text CSV Inconsistencies (Errors ??)
Summary: Save to Text CSV Inconsistencies (Errors ??)
Status: CLOSED DUPLICATE of issue 4925
Alias: None
Product: Calc
Classification: Application
Component: save-export (show other issues)
Version: 680m125
Hardware: PC All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: spreadsheet
QA Contact: issues@sc
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-07 23:49 UTC by sblass
Modified: 2005-09-08 10:43 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description sblass 2005-09-07 23:49:13 UTC
1.  Numbers formatted to display decimal positions (e.g. #,##0.00) in Calc will
lose their formatting upon file conversion to CSV. That is, 123,456.70 becomes
123456.7; 123,456.00 becomes 123,456; etc. If I have two decimal positions
displayed in Calc, then I want to see the same number of decimal positions - NO
TRUNCATION - in the CSV file.

To combat the problem, I have to create a temporary column and use the Text
function (e.g. =Text(L1;"0.00") to get a column of text that will yield the
expected result.

2.  Date values displayed with YYMMDD format (e.g. date 1/22/2004, displayed in
Calc as 040122) will not carry through in the same format to the CSV file.
Instead, using the same example, the date field gets expressed in the CSV file
as 01/22/2004.
Comment 1 ooo 2005-09-08 10:42:49 UTC
Duplicate.

*** This issue has been marked as a duplicate of 4925 ***
Comment 2 ooo 2005-09-08 10:43:18 UTC
Closing dup.