Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index

On Wed, 2011-01-19 at 14:15 +0900, Nguyen Vu Hung wrote:
On Wed, Jan 19, 2011 at 2:22 AM, Kohei Yoshida <> wrote:
Yes, it's a known issue which unfortunately didn't get fixed in time for
3.3.  The fix will be very x10 invasive, so we've decided to postpone it
until next minor release.

As far as I understand, supporting that feature will make LibO less compatible
when saving as other format other that .odt. Is that correct?

No, that's not correct at all.

Fixing it the right way will be very invasive, and risks breaking the
xls (not xlsx, xls the binary) import and export filters into utterly
useless state (I mean, really useless).  This is because so much code is
shared between the xls import/export filters and the xlsx export filter,
and the offending code is in the common part of the filters code, and
its effect is broad.

So, the fix has to be followed by intensive and comprehensive testing of
the xls import/export filters to make sure they work just as correctly
as they did before the fix.  Unfortunately it was much more
time-consuming than we had hoped & we didn't have enough time and
resources to pull that off for 3.3.  But we need to fix that sooner
rather than later, and I'm hoping that we will finally nail it in 3.4.


Kohei Yoshida, LibreOffice hacker, Calc

Unsubscribe instructions: E-mail to
*** All posts to this list are publicly archived for eternity ***


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.