Bug 124117 - FILESAVE: Wrap Text is not saved to *.xls
Summary: FILESAVE: Wrap Text is not saved to *.xls
Status: RESOLVED DUPLICATE of bug 97106
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: filter:xls
Depends on:
Blocks:
 
Reported: 2019-03-16 13:13 UTC by jcrmatos
Modified: 2024-10-04 11:39 UTC (History)
6 users (show)

See Also:
Crash report or crash signature:


Attachments
The .xls that shows the bug. (15.50 KB, application/x-ole-storage)
2019-03-16 13:23 UTC, jcrmatos
Details
Example xls document with wrapped text created with MS Office 2016 (25.50 KB, application/vnd.ms-excel)
2019-07-03 21:24 UTC, Bartosz
Details
Comparison of test.xls document under Libreoffice and MS Office 2016 (125.07 KB, image/png)
2019-07-03 21:38 UTC, Bartosz
Details

Note You need to log in before you can comment on or make changes to this bug.
Description jcrmatos 2019-03-16 13:13:22 UTC
Description:
When I close the .xls and reopen it, the wrapping of the text in the cells is wrong.

Steps to Reproduce:
1. Open the .xls file.
2. Correct the wrapping of the cells.
3. Save it. Close it and reopen it.

Actual Results:
The wrapping of the text is wrong.

Expected Results:
The wrapping of the text should be maintained.


Reproducible: Always


User Profile Reset: No


OpenGL enabled: Yes

Additional Info:
I even tried to copy the cells to a new .xls file, but with the same results.

If you want I can send you the .xls file for testing.


[Information automatically included from LibreOffice]
Locale: en-US
Module: SpreadsheetDocument
[Information guessed from browser]
OS: Windows (All)
OS is 64bit: yes

[Copied from Help - About LibreOffice]
Version: 6.2.0.3 (x64)
Build ID: 98c6a8a1c6c7b144ce3cc729e34964b47ce25d62
CPU threads: 8; OS: Windows 6.1; UI render: default; VCL: win; 
Locale: pt-PT (pt_PT); UI-Language: en-US
Calc: threaded


[Copied from OpenGL Extensions Viewer 5.2.0]
Renderer: ATI Mobility Radeon HD 5730
Vendor: ATI Technologies Inc.
Memory: 1024 MB
Version: 3.1.9210 Forward-Compatible Context
Shading language version: 1.50
Comment 1 Oliver Brinzing 2019-03-16 13:22:13 UTC
Thank you for reporting the bug. 
Please attach a sample document, as this makes it easier for us to verify the bug. 

(Please note that the attachment will be public, remove any sensitive information before attaching it. 
See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)

I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided.
Comment 2 jcrmatos 2019-03-16 13:23:58 UTC
Created attachment 150013 [details]
The .xls that shows the bug.

The .xls that shows the bug.
Comment 3 jcrmatos 2019-03-16 13:25:02 UTC
Included the .xls file in attahcment.
Comment 4 Oliver Brinzing 2019-03-16 13:37:02 UTC
(In reply to jcrmatos from comment #3)
> Included the .xls file in attahcment.

>2. Correct the wrapping of the cells.

Please add a detailed description how the bug can be reproduced.
Which cells did you format? Did you change row height and/or column width?

I have set the bug's status to 'NEEDINFO'. 
Please change it back to 'UNCONFIRMED' once the requested info is provided.
Comment 5 jcrmatos 2019-03-16 13:47:10 UTC
I select column A to E, rows 38 to 45.
I press the Wrap text button on the toolbar.
The text looks fine.
Save the file.
Close the file.
Re-open the file, and the text on column A and E is no longer correct.

I don't change the column width or height in this process.

If you want I can send you a print-screen of the before and after.
Comment 6 Oliver Brinzing 2019-03-16 14:07:31 UTC
(In reply to jcrmatos from comment #5)
> If you want I can send you a print-screen of the before and after.

thanks, i can reproduce it with: 

Version: 6.1.5.2 (x64)
Build ID: 90f8dcf33c87b3705e78202e3df5142b201bd805
CPU threads: 4; OS: Windows 10.0; UI render: default; 
Locale: de-DE (de_DE); Calc: 

Version 3.6.7.2 (Build ID: e183d5b)

and even with AOO 4.1.5

- open attached file
- select cell A39
- press "Wrap Text" from Toolbar
  -> layout changes
- save *.xls
- reload *.xls

btw: works if saved as *.ods file
Comment 7 Bartosz 2019-07-03 21:24:47 UTC
Created attachment 152543 [details]
Example xls document with wrapped text created with MS Office 2016

After export .xls file by LibreOffice, wrapped text are gone
Comment 8 Bartosz 2019-07-03 21:38:31 UTC
Created attachment 152544 [details]
Comparison of test.xls document under Libreoffice and MS Office 2016

It looks like the same document looks differently under LibreOffice and MS Office. It means that it is an import issue.
Comment 9 QA Administrators 2021-07-03 04:03:24 UTC Comment hidden (obsolete)
Comment 10 QA Administrators 2023-08-22 03:05:45 UTC Comment hidden (obsolete)
Comment 11 ady 2023-08-22 18:48:20 UTC
(In reply to Oliver Brinzing from comment #6)

> - open attached file
> - select cell A39
> - press "Wrap Text" from Toolbar
>   -> layout changes
> - save *.xls
> - reload *.xls

It still fails for these STR on the attached file from comment 2 – whether setting "wrap text" ON or OFF, the changed attribute is not saved to the file.

The attribute (ON or OFF) is saved correctly in a new clean file (such as in attachment from comment 7).

IDK what exactly triggers the problem. I wonder whether it can be reproduced with some other file, or in safe mode, or...
Comment 12 Stéphane Guillou (stragu) 2024-01-25 04:27:08 UTC
Let's consolidate into bug 97106.

*** This bug has been marked as a duplicate of bug 97106 ***
Comment 13 Justin L 2024-10-04 11:39:40 UTC
This bug shows the Excel BUG of not being able to have multiline content without being wrapped. It can never be fully solved (limitation of MS implementation) but is being changed via bug 158460.

This particular report seems more to do with Calc failing to set an optimal height on import - which is also an existing bug report so I won't bother making any changes to this bug's meta data.