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

Hi :)
The format your script is currently written for is more stable than
the more recent MS formats such as XlsX.  Ods is far more stable for
the future and even MS Office 2013 & 365 can use it.

Unfortunately MS Office 2010 and earlier can't handle Ods due to MS's
bad implementation.  Prior to 2013 they replaced all formulae with
just the value that happened to be in each one at the time.  However
it sounds like your company might still be largely on MSO 2003 or
earlier which is kinda helpful for once.

So they might have 3 ways to upgrade for the future
1.  Rewrite the script for XlsX only and hope that the changes in that
format between different versions of MSO are not enough to break the
2.  Rewrite for both XlsX and Ods so that everyone's happy (ie when
'one' format breaks one script (naming no names) then the other is
available and still working
3.  Rewrite for just Ods.  Sadly this best option is the least likely
4.  No re-write and then over the years watch everything fall apart as
MS start to withdraw support for their older versions

I'm still wondering if Regina or Brian or someone has a better answer
that does work in the format you really need in the here&now!
Regards from
Tom :)

On 10 December 2013 15:01, Maxime Bégnis <> wrote:
Hello, thanks for your answer. :-)

We have a script and some XSLT to do indeed funny things, and it would be
easier for us to keep it as it is. However, dealing directly with ODS format
to extract what we need from the file would be less tricky of course, but it
would be much more work. Anyway, doing what you suggest might save us some
time and troubles in the end...


Maxime Bégnis

Le 10/12/2013 15:45, Tom Davies a écrit :

Hi :)
Do you really have to have it in that format?  Straight Xls is easier!
 XlsX and Ods are both Xml formats.

If it has to be Xml to allow some scripts to do funny things to it
then perhaps Ods itself might be valid?
Regards from
Tom :)

On 10 December 2013 11:28, Maxime Bégnis <> wrote:

Hello list,

My question is quite technical, but I hope I will have an answer. I need it
very badly... :-

On some documents (Excel .xls) I wish to convert to "Microsoft Excel 2003
XML" I have exactly this bug:

Doing some research, I found out I can make it work if I:
1. convert the document to ODS
2. unzip the ODS
3. run the attached XSLT on "content.xml"
4. zip it back, open it, save it as "Microsoft Excel 2003 XML"

The xslt remove any "table:number-rows-repeated" attributes.

So my question is:

By doing what I describe in this procedure is there a risk to break the
content of the file or to make the file not a valid ODS file?

Thanks a lot!

Maxime Bégnis

*Maxime Bégnis*
Tél: +33 (0)
5, rue de la Touloubre
13770 Venelles

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


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.