Bug 88361 - Excel file (MSO 2003 XML format) corrupted after save as
Summary: Excel file (MSO 2003 XML format) corrupted after save as
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
(earliest affected) release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
Depends on:
Blocks: MSO-XML2003
  Show dependency treegraph
Reported: 2015-01-13 09:44 UTC by mr_smyle
Modified: 2019-06-08 02:55 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

document for example (18.42 KB, application/xml)
2015-01-13 09:44 UTC, mr_smyle
xls mime (18.42 KB, application/xls)
2015-01-13 09:45 UTC, mr_smyle
in windows (118.04 KB, image/png)
2015-01-13 18:57 UTC, mr_smyle
Other example (889.49 KB, application/xls)
2015-01-14 14:08 UTC, mr_smyle

Note You need to log in before you can comment on or make changes to this bug.
Description mr_smyle 2015-01-13 09:44:00 UTC
Created attachment 112154 [details]
document for example

I create file with FastReport and export it to Excel (XML)

Open it in windows - show fine formatting as expected

Open it in Lunux (Ubuntu 14.04) - wrong formatting:
 - seems like rows heights are ignore height
 - line breaks in cells not recognized.

After editing in windows and saving, issue in Linux still present.

LibreOffice on both Linux and Windows
Comment 1 mr_smyle 2015-01-13 09:45:27 UTC
Created attachment 112155 [details]
xls mime
Comment 2 Urmas 2015-01-13 13:06:33 UTC
There are no any linebreaks in cells in your file.
Comment 3 mr_smyle 2015-01-13 18:57:30 UTC
Created attachment 112176 [details]
in windows

Attached screenshot from first open file in windows. Linebreaks in section (1) gone away after save.

Rows heights in section (2) in linux not recognized. Both before and after save in windows.
Comment 4 mr_smyle 2015-01-13 18:58:44 UTC
I can send source file to PM - it have confident information.
Comment 5 raal 2015-01-14 07:39:57 UTC
(In reply to mr_smyle from comment #1)
> Created attachment 112155 [details]
> xls mime

I tried to open this file in Excel 2010 and cannot open - error message: File corrupted, cannot open.
I can open file in LO 4.3.5, win7

Because cannot open file in excel I'll set status as notourbug. Seems to be bug in FastReport.
Comment 6 mr_smyle 2015-01-14 14:08:08 UTC
Created attachment 112217 [details]
Other example

Raal, I add other example, please check!
I'm sure LO corrupt file during save and Excel cannot open it after.
Comment 7 raal 2015-01-14 19:07:25 UTC
I can confirm with Version:
Build ID: b460414bcd1dfd2f260696e306c49c56585c6464
TinderBox: Linux-rpm_deb-x86_64@46-TDF, Branch:libreoffice-4-4, Time: 2015-01-11_05:32:52

Steps to reproduce
 -  open second file (it's xml file with .xls suffix) in LO. This file i can open in excel.
 - Save as this file in LO. XML format.
 - Close, reopen in LO. 
 - Open in excel 2010
errors :
 - in LO are borders 4 pt width
 - in Excel I cannot open -  error.
Comment 8 mr_smyle 2015-01-15 06:59:03 UTC
raal, file corruption is the second issue. What to do with different representation file on screen (rows heights and line breaks) in Ubuntu and in Windows with same LO version? Fill other one issue?
Comment 9 raal 2015-01-15 07:29:00 UTC
(In reply to mr_smyle from comment #8)
> raal, file corruption is the second issue. What to do with different
> representation file on screen (rows heights and line breaks) in Ubuntu and
> in Windows with same LO version? Fill other one issue?

Better is to have 1 bugreport = 1 bug. You can link this bugreport because I can confirm both issues:
 errors :
 - in LO are borders 4 pt width
 - in Excel I cannot open -  error.

If I remember, linebreaks in A1 was correct, row heights not (smaller value).
Comment 10 mr_smyle 2015-02-11 14:07:23 UTC
I found the reason row heights corruption.

In source xls (with xml format) we have tag
<Row ss:Height="27.47">

After modify row heights in LO and saving this file we have tag:
<Row ss:Height="14,1449">

So, I think, this is parsing error: dot and comma as separator.
Comment 11 mr_smyle 2015-02-11 14:18:50 UTC
About line breaks:
In source file xls (with xml).

<Data ss:Type="String">Отчет КО&#10;за период с 02.02.2015 по 11.02.2015</Data>

String "&#10;" not recognised by LO as line break.

Line break in lo is #10 char in line.
Comment 12 mr_smyle 2015-02-11 14:27:50 UTC
comments 10 & 11 are for Ubuntu Linux LibreOffice (not for Windows)
Comment 13 Mario Diaz 2015-07-23 15:16:09 UTC
Corrupt save from LO to Excel damage file.
Comment 14 QA Administrators 2016-09-20 10:19:01 UTC Comment hidden (obsolete)
Comment 15 Timur 2018-06-07 16:19:15 UTC
If this is xml file with .xls suffix, then we rename to .xml.
Open in MSO and try to save as .xml. MSO says "cannot save, no XML mappings". Save as XML 2003. 
Open in LO and try to save as .xml but not possible, no more .xml in newer versions from LO 6.1. 
So having this bug open is pointless. 
If you think there should be a bug, please test with 6.1 or master that have new XML import filter and save with some other format.
Comment 16 Timur 2018-11-01 18:14:25 UTC
Actually, File-Save has been moved to File->Export for XML. Please test.
Comment 17 QA Administrators 2019-05-08 18:28:17 UTC Comment hidden (obsolete)
Comment 18 QA Administrators 2019-06-08 02:55:53 UTC
Dear mr_smyle,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team