[libreoffice-users] Re: Odt size difference between MS Office 11 and LO 3.3.2

plino <pedlino -AT- gmail.com>
Wed, 25 May 2011 11:09:44 -0700 (PDT)

The simple explanation is that the MSO file is missing many ODF features ;)

Interestingly both your files fail the ODF validation on this site

http://tools.odftoolkit.org/odfvalidator/

Does it make any sense that only when I create an identical file under OOo
3.4 Beta the file is valid?

Should LibreOffice worry about this?

Is the validator an accurate tool? Shouldn't OASIS be providing such a
tool???

--
View this message in context: 
http://nabble.documentfoundation.org/Odt-size-difference-between-MS-Office-11-and-LO-3-3-2-tp2978634p2985444.html
Sent from the Users mailing list archive at Nabble.com.

-- 
Unsubscribe instructions: E-mail to users+help@libreoffice.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/www/users/
All messages sent to this list will be publicly archived and cannot be deleted

Context

Re: [libreoffice-users] Odt size difference between MS Office 11 and LO 3.3.2 (continued)
- [libreoffice-users] Re: Odt size difference between MS Office 11 and LO 3.3.2 · Twayne
- [libreoffice-users] Re: Odt size difference between MS Office 11 and LO 3.3.2 · plino
  - Re: [libreoffice-users] Re: Odt size difference between MS Office 11 and LO 3.3.2 · Tom Davies
    - [libreoffice-users] Re: Odt size difference between MS Office 11 and LO 3.3.2 · plino

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.