Bug 134154 - Unknown symbol in cell and contents overlap
Summary: Unknown symbol in cell and contents overlap
Status: RESOLVED NOTABUG
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
6.4.3.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-06-19 16:03 UTC by Alexander Kurakin
Modified: 2020-06-20 17:19 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
Original file (5.18 KB, application/vnd.openxmlformats-officedocument.spreadsheetml.sheet)
2020-06-19 16:04 UTC, Alexander Kurakin
Details
CSV representation (67 bytes, text/csv)
2020-06-19 16:04 UTC, Alexander Kurakin
Details
First screenshot (13.16 KB, image/png)
2020-06-19 16:05 UTC, Alexander Kurakin
Details
Second screenshot (13.18 KB, image/png)
2020-06-19 16:06 UTC, Alexander Kurakin
Details
Import window configuration screenshot. (25.88 KB, image/png)
2020-06-19 23:21 UTC, m_a_riosv
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Kurakin 2020-06-19 16:03:41 UTC
I have a file, see attachment.

Its CSV representation is:
    "15.06.2020";"QWERTYUIOPQWERTYUIOP";;"ASDFGHJKLASDFGHJKLASDFGHJKL"

I see two display artifacts:

1) unknown single quote symbol in the cell (see first screenshot);

2) the contents of cells are displayed on top of each other (see second screenshot)

Is it intended behavior?

Thanks!
Comment 1 Alexander Kurakin 2020-06-19 16:04:07 UTC
Created attachment 162211 [details]
Original file
Comment 2 Alexander Kurakin 2020-06-19 16:04:39 UTC
Created attachment 162212 [details]
CSV representation
Comment 3 Alexander Kurakin 2020-06-19 16:05:34 UTC
Created attachment 162213 [details]
First screenshot

1) unknown single quote symbol in the cell (see first screenshot)
Comment 4 Alexander Kurakin 2020-06-19 16:06:25 UTC
Created attachment 162214 [details]
Second screenshot

2) the contents of cells are displayed on top of each other (see second screenshot)
Comment 5 Durgapriyanka 2020-06-19 21:07:53 UTC
Thank you for reporting the bug. I can confirm the bug present in

Version: 6.4.0.0.alpha1+ (x86)
Build ID: ec7374ff84c71edfbb30d6e4dc5b486b6df7107f
CPU threads: 2; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: default; VCL: win; 
TinderBox: Win-x86@42, Branch:master, Time: 2019-11-10_21:37:30
Locale: en-US (en_US); UI-Language: en-US
Calc: threaded
	

and in

LibreOffice 3.3.0 
OOO330m19 (Build:6)
tag libreoffice-3.3.0.4
Comment 6 m_a_riosv 2020-06-19 23:21:34 UTC
Created attachment 162220 [details]
Import window configuration screenshot.

Not a bug, it's only a matter of a proper import configuration.
See attached screenshot.
Comment 7 Alexander Kurakin 2020-06-20 06:21:41 UTC
(In reply to m.a.riosv from comment #6)
> Created attachment 162220 [details]
> Import window configuration screenshot.
> 
> Not a bug, it's only a matter of a proper import configuration.
> See attached screenshot.

I didn't import it. The XLSX file is original.

I show you CSV representation for  understanding it's real content.
Comment 8 V Stuart Foote 2020-06-20 17:11:37 UTC
The single quote tic just shows the numerical cell value is being handled as text on import. And, that is the way to enter numerical data as text via the Formula bar.

Without the original OOXML document to judge its column formatting the filter import of the sheet is not incorrect.

And as noted, the CSV import filters would need to match if you had exported the OOXML to CSV with semicolon column separators and quote mark text delimiter.
Comment 9 Alexander Kurakin 2020-06-20 17:19:21 UTC
(In reply to V Stuart Foote from comment #8)
> The single quote tic just shows the numerical cell value is being handled as
> text on import. And, that is the way to enter numerical data as text via the
> Formula bar.
> 
> Without the original OOXML document to judge its column formatting the
> filter import of the sheet is not incorrect.
> 
> And as noted, the CSV import filters would need to match if you had exported
> the OOXML to CSV with semicolon column separators and quote mark text
> delimiter.

Thanks!

> Without the original OOXML document to judge its column formatting the
> filter import of the sheet is not incorrect.

Do you mean, XLSX saved my Microsoft Excel not LibreOffice?

And am I correct that you talk about the second issue, too?