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



Tom wrote:

Many programs don't fully comply with their own specs.  


The fact that many programs do that makes it correct?


Tom wrote:

OpenSource ones tend to try to fix that through bug-reports and such-like. 
We often grumble when we find an example of a proprietary program, such as
MS Office, not complying with it's specs.  


The fact that you can report bugs isn't synonymous that someone will try to
fix it ;)

MS doesn't have to publish any specs. And most MS formats are closed source.
It is in their best interest that only their program is 100% compatible.

If you bother to create an open format so that any program can open it (and
therefore freeing you from vendor lock), any incompatibility with the
standard is bound to create problems when you try to open the document in
another program...

--
View this message in context: 
http://nabble.documentfoundation.org/OASIS-Standard-ODF-1-2-Approved-tp3384139p3396840.html
Sent from the Users mailing list archive at Nabble.com.

-- 
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
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

Context


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.