Issue 1507 - Problem with CSV files in spreadsheet
Summary: Problem with CSV files in spreadsheet
Status: CLOSED FIXED
Alias: None
Product: Calc
Classification: Application
Component: code (show other issues)
Version: 633
Hardware: PC Windows 98
: P3 Trivial (vote)
Target Milestone: ---
Assignee: frank
QA Contact: issues@sc
URL:
Keywords:
: 1528 (view as issue list)
Depends on:
Blocks: 2139
  Show dependency tree
 
Reported: 2001-08-20 16:15 UTC by Unknown
Modified: 2013-08-07 15:13 UTC (History)
1 user (show)

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

Attachments
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 Unknown 2001-08-20 16:15:09 UTC 
This relates to opening CSV (comma-separated-values) text files with
the spreadsheet. The problem is that the quotes (") are imported along
with the text fields. The quotes are supposed to be the boundaries of
the text, not part of it.

This worked fine in StarOffice 5.2.
Comment 1 peter.junge 2001-08-24 09:55:49 UTC 
Hi William,
IMO this is no bug. I think it is mismatch of encodings. That means 
the character set that was used to create the file (e.g. ISO-8859-1) 
doesn't fit to the one proposed in the 'text import' dialog. At the 
top of this dialog you will find a select box called 'character set'. 
Please toggle through the different options and have a look at the 
preview. There you will see the quotes disappear if the right set is 
choosen.
IF this doesn't behave as I discribed then we have a real problem. 
Otherwise it would be usefull for the FAQ.
Please add what you found out to this bug.

Thanks, Peter
Comment 2 peter.junge 2001-08-27 10:02:31 UTC 
*** Issue 1528 has been marked as a duplicate of this issue. ***
Comment 3 peter.junge 2001-08-28 09:57:31 UTC 
Finally reproduced it.
I don't know why but it only happens on W9x. There shouldn'tbe any
difference between different OS in handling of low ASCII.
Does not happen anymore in current builds although I couldn't find
anyone who fixed it.

Peter
Comment 4 peter.junge 2001-08-28 09:58:29 UTC 
Works in 638r.
Comment 5 peter.junge 2001-08-28 09:59:03 UTC 
Fixed
Comment 6 Unknown 2001-09-01 23:37:52 UTC 
There is no change in the problem in build 638.
I have tried every possible text "encoding" without sucess.
Comment 7 frank 2001-09-03 08:21:54 UTC 
Fixed in next build.
Comment 8 frank 2001-09-03 08:23:03 UTC 
.
Comment 9 stx123 2001-11-12 12:30:10 UTC 
please verify
Comment 10 peter.junge 2001-11-15 17:01:51 UTC 
Hi,
not found in soon released 641. ->CLOSED
regards, Peter
Comment 11 peter.junge 2001-11-15 17:05:30 UTC 
Sorry,
I meant status set as fixed. We close it when 641 is public available.
;-), Peter
Comment 12 peter.junge 2001-12-03 16:57:30 UTC 
verified in 641. ->Closed