Bug 133277 - FILEOPEN importing csv file results in error message and rather garbled spreadsheet
Summary: FILEOPEN importing csv file results in error message and rather garbled spre...
Status: RESOLVED NOTABUG
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
6.4.3.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-05-22 15:31 UTC by Dirk Munk
Modified: 2020-05-23 09:55 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Attachments
The file that I was trying to import (1.94 MB, text/plain)
2020-05-22 15:34 UTC, Dirk Munk 		Details
The resulting spreadsheet (601.32 KB, application/vnd.oasis.opendocument.spreadsheet)
2020-05-22 15:41 UTC, Dirk Munk 		Details
Text import dialog for the Semicolon separated CSV attachment 161149 (48.97 KB, image/png)
2020-05-22 16:43 UTC, V Stuart Foote 		Details
csv import dialog (46.36 KB, image/png)
2020-05-22 17:52 UTC, Dirk Munk 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dirk Munk 2020-05-22 15:31:05 UTC 
Description:
I'm trying to import a semi-colon separated csv file with rather long records (> 1024 char). It ends with the message that the import was unsuccessful because of to may characters in a cell. Alos the columns can be very wide or very narrow, and some of the import records of the csv file can be found in one cell, incl. the semi-colons.

Steps to Reproduce:
1.Import attached .csv file
2.
3.

Actual Results:
1. I got an error statin that there were to many characters in a cell, so that the csv file could not load properly.
2. the resulting spreadsheet looked rather garbled, very wide and very narrow columns, and csv imput data (incl. semicolons) in cells. 

Expected Results:
a nice looking spreadsheet


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 6.4.3.2 (x64)
Build ID: 747b5d0ebf89f41c860ec2a39efd7cb15b54f2d8
CPU threads: 8; OS: Windows 10.0 Build 18363; UI render: default; VCL: win; 
Locale: nl-NL (nl_NL); UI-Language: en-GB
Calc: threaded
Comment 1 Dirk Munk 2020-05-22 15:34:04 UTC 
Created attachment 161149 [details]
The file that I was trying to import
Comment 2 Dirk Munk 2020-05-22 15:41:56 UTC 
Created attachment 161150 [details]
The resulting spreadsheet
Comment 3 V Stuart Foote 2020-05-22 16:43:17 UTC 
Created attachment 161154 [details]
Text import dialog for the Semicolon separated CSV attachment 161149 [details]

I had no issues importing the CSV using the Text Import dialog.

I had to be sure the locale set used comma as decimal separator (Tools -> Options -> Languages) and on the Text Import dialog, to set the Searator Options to _just_ the Semicolon check box. I also set the Fields column type to correct date format determined visual scan of the preview.

On import sheet is created with 7109 rows, no LO complaint/warning and visual inspection all cells seem correctly populated with no run overs.
Comment 4 V Stuart Foote 2020-05-22 16:45:38 UTC 
Can not confirm on Windows with
Version: 6.4.4.1 (x64)
Build ID: b50bc319eca5cd5b66fbfe2ebd0d3bd1eed099b5
CPU threads: 8; OS: Windows 10.0 Build 18362; UI render: GL; VCL: win; 
Locale: nl-NL (en_US); UI-Language: en-US
Calc: CL

Please retest but correctly configure the local and then the CSV filters from the Text Import dialog.
Comment 5 Dirk Munk 2020-05-22 17:52:28 UTC 
Created attachment 161157 [details]
csv import dialog

This is my import dialog box, doesn't change anything I'm afraid.
Comment 6 QA Administrators 2020-05-23 03:44:57 UTC Comment hidden (obsolete)
Comment 7 Dirk Munk 2020-05-23 09:55:57 UTC 
I found the problem. It was the string delimiter > ' < . Many names of streets and places look like 's-Gravenhage, and that is where it went wrong.