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


Hi :)
The strict vs transitional issue really doesn't bode well for future
implementations of the OOXML format.

Who would there be to notice when MS's implementation again deviates
from "strict"?  Is anyone or any organisation sufficiently well-versed
in the immensely wordy ISO standard for OOXML and would they notice
deviations?  Is there anything to stop MS from doing an "extended"
implementation?  Would there be anything to force them to properly
document any such extended bits?  Was there any adequate documentation
of the deviations between "transitional" and "strict"?

I think the whole issue about transitional vs strict is a question of
semantics to make promises that the future will be different when
there is nothing to ensure it will be so = except the promises of a
single profit-making company which would be ill-served if it did
fulfil it's promises and which doesn't seem to have fulfilled such
promises in the past.

Does anyone have good links to the court-case about the "Rtf" format?


ODF is set by a committee and has a history of real interoperability
between different programs made by different companies and
organisation.  The documentation set as the ISO standard is apparently
considerably shorter and easier to read.  Where programs fail to live
up to the standard it's relatively easy to see that and to see that
other programs are able to use that part of the standard.
Regards from
Tom :)








On 23 February 2014 20:41, James Knott <james.knott@rogers.com> wrote:
Stephan Weinberger wrote:
Maybe i'm not going to make friends, but OOXML "strict" actually *is* an open
standard. The real problem is, that MS-Office until 2013 was not capable of
creating "strict" files, but wrote OOXML "transitional" instead (which may -
and as a matter of fact always did - contain proprietary stuff).
So almost all OOXML files out in the wild today are in fact not 'real' OOXML
but just proprietary, legacy office formats encoded in an XML-structure.

IIRC, that "strict" OOXML, as rammed through ISO, contains a lot of
proprietary blobs.

--
To unsubscribe e-mail to: users+unsubscribe@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


-- 
To unsubscribe e-mail to: users+unsubscribe@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.