On 06/14/15 12:40, Italo Vignoli wrote:
You should never generate XLSX files with LibreOffice, unless you need
to exchange them with MS Office users.
*I* know (and never use anyhing else but OpenDocument).
My customers know (if they listen to me and trust me).
Then again, whether this knowledge has any practical effect or they
still use XLS[X] is another matter...
Still, besides format wars, we have a serious bug here.
If XLSX is supported, it should work; losing data because it doesn't
work properly is not a good thing :-(
With MS Office 2013 users, you can use ODS files.
MSO2013's support of ODS is still far from optimal (this of course falls
again in their lock in strategy).
Besides there are still many 2010s, 2007s and even some 2003 around.
Is there any way to tell by opening/unzipping/looking at the files?
Of course not, this is part of the lock in strategy applied to pseudo
standard formats. You can possibly understand it from the namespaces
(which are different, but undocumented, for every version).
If I understand it correctly 4.4 is about to be published: I'll try
whether this bug is gone.
Still, I'm open to reports from other people who might have seen the
same problem, suggestions where to look and what for, tests to do, etc...
To unsubscribe e-mail to: email@example.com
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
Impressum (Legal Info)
: 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