Bug 7150 - Exporting xls files from Libreoffice Calc causes considerable increase of file size
Summary: Exporting xls files from Libreoffice Calc causes considerable increase of fil...
Status: RESOLVED WONTFIX
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 2
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: D Morgan
QA Contact:
URL: https://bugs.freedesktop.org/show_bug...
Whiteboard:
Keywords: NEEDINFO, PATCH, UPSTREAM
Depends on:
Blocks:
 
Reported: 2012-08-23 08:03 CEST by egc
Modified: 2013-06-10 10:19 CEST (History)
2 users (show)

See Also:
Source RPM: libreoffice-calc-3.5.5.3-0.3.mga2
CVE:
Status comment:


Attachments

Description egc 2012-08-23 08:03:52 CEST
Description of problem:
I am getting huge XLS files when saving spreadsheets as XLS with spreadsheets
that previously were similar size or slightly smaller in XLS form than in ODS
form.
Now the XLS file is well over 50 times bigger than the ODS file!

Links to the fix on the Freedesktop.org bug reports:
https://bugs.freedesktop.org/show_bug.cgi?id=51200
https://bugs.freedesktop.org/show_bug.cgi?id=50304


Version-Release number of selected component (if applicable):
V 3.5.5.3


How reproducible:
Allways, this bug is valid for Mageia 2
The bug is fixed in Libreoffice 3.6

Steps to Reproduce:
1. Open a spreadsheet ODS
2. Save spreadsheet as XLS file
3.
Comment 1 Manuel Hiebel 2012-09-13 18:32:40 CEST
btw: there is libreoffice 3.5.6 in testing maybe you can test it, don't how to check if the fix is here too

Keywords: (none) => PATCH, UPSTREAM

Comment 2 egc 2012-09-14 14:11:09 CEST
thank you! i tested version 3.5.6 from testing and the bug is still valid.
in fact, as i read in one of the links i gave above, this bug is fixed only in version 3.6.x
Comment 3 Manuel Hiebel 2012-09-15 15:02:16 CEST
ok, 
dmorgan can you backport the patch ?

Assignee: bugsquad => dmorganec

Comment 4 egc 2012-12-02 08:30:26 CET
hi there! no solution for this bug?
Comment 5 egc 2013-02-09 18:17:25 CET
this bug is still valid in 3.5.7.2
Comment 6 egc 2013-02-26 07:34:38 CET
ok, since there is no reaction here i installed the newest libreoffice packages from libreoffice.org.
I think in the future I will limit my bug reports to a very minimun ...
And please stay consequent and don't answer on this post. Thanks!
Comment 7 John Hendy 2013-03-20 19:13:20 CET
I recently experienced this and think I have an idea about what's going on. Information:

$ uname -a
Linux hostname 3.8.3-2-ARCH #1 SMP PREEMPT Sun Mar 17 13:04:22 CET 2013 x86_64 GNU/Linux

$ libreoffice --version
LibreOffice 4.0.1.2

I believe that for some reason, some cell in distant rows/columns gets registered as containing a value, despite being blank. When exporting to xlsx, I think Libreoffice is storing some sort of value in all columns/rows up to that distant cell, or potentially storing some sort of data in all blank rows/columns instead of just leaving them absent.

I suspect this, as on a hunch I selected the first blank column of my data and did Ctrl + Shift + Right Arrow. This selects all columns up to AMJ. Then right click and choose "Delete columns."

Repeat for rows and do Ctrl + Shift + Down Arrow and delete all blank rows.

I then did "Save as..." from .ods -> .xlsx successfully. Before doing this a ~20kb .ods was creating a 3.4mb .xlsx. After deleting blank rows/columns as described above, I get a ~21kb .xlsx.

CC: (none) => jw.hendy

Comment 8 Thierry Vignaud 2013-06-07 17:15:40 CEST
This should be reported upstream then.
But I suspect they won't fix anything on 3.5.x branch.
Can you upgrade to Mageia3 and check if it's OK with libreoffice-4.0?

Keywords: (none) => NEEDINFO
CC: (none) => thierry.vignaud

Comment 9 egc 2013-06-08 01:30:53 CEST
It's ok with libreoffice-4.0 in Mageia 3
Comment 10 Thierry Vignaud 2013-06-10 10:18:58 CEST
Closing a

Status: NEW => RESOLVED
Resolution: (none) => WONTFIX

Comment 11 Thierry Vignaud 2013-06-10 10:19:29 CEST
s wontfix for mga2 as upstream will probably not touch 3.5.x

Note You need to log in before you can comment on or make changes to this bug.