Rob Weir explique ça très bien : http://www.robweir.com/blog/2008/01/standard-trolls.html
Or, in plain English, in order to be able to claim conformance with OOXML, an application must not crash when presented with a valid OOXML document, or must be able of producing at least a single valid OOXML document. This is not exactly a high threshold.
Some examples of applications that support OOXML by that definition:
1. The DOS "copy" command is a conforming OOXML consumer and producer, since it can accept and produce valid OOXML documents.
2. The DOS "del" command is a valid OOXML consumer, and one which I heartily recommend.
3. WinZip, PkWare and every other Zip application out there are also conforming producers and consumers of OOXML.
4. Every text editor and every XML editor and every other application that can consume text or XML also supports OOXML.
etc
On est ravis d'apprendre que les commandes copy et del sont couvertes par OSP.
[^] # Re: Une bonne nouvelle
Posté par IsNotGood . En réponse à la dépêche La guerre des formats de bureautique normalisés ISO commence. Évalué à 6.
http://www.robweir.com/blog/2008/01/standard-trolls.html
Or, in plain English, in order to be able to claim conformance with OOXML, an application must not crash when presented with a valid OOXML document, or must be able of producing at least a single valid OOXML document. This is not exactly a high threshold.
Some examples of applications that support OOXML by that definition:
1. The DOS "copy" command is a conforming OOXML consumer and producer, since it can accept and produce valid OOXML documents.
2. The DOS "del" command is a valid OOXML consumer, and one which I heartily recommend.
3. WinZip, PkWare and every other Zip application out there are also conforming producers and consumers of OOXML.
4. Every text editor and every XML editor and every other application that can consume text or XML also supports OOXML.
etc
On est ravis d'apprendre que les commandes copy et del sont couvertes par OSP.