[odf-discuss] Does OO.o violate OpenDocument? If yes, where?
M. Fioretti
mfioretti at mclink.it
Sat Nov 18 03:13:20 EST 2006
On Fri, Nov 17, 2006 21:35:35 PM +0000, Daniel Carrera
(daniel.carrera at zmsl.com) wrote:
> On Fri, 2006-17-11 at 22:09 +0100, M. Fioretti wrote:
> > "since OO.o doesn't support all of ODF yet (1), today distributing ODF
> > files made with OO.o isn't at all a feasible solution for
> > "distributing documents in an advanced open standard like ODF".
>
> Bollocks.
Thanks (also to Marbux) for confirming it. I felt right away that the
way of reasoning was flawed, even before any conclusion it may lead
to.
> 2) Provided that, for some reason, the ODF files you produce must be
> absolutely flawless... then, as you suggested, all you have to do is
> avoid the features that are not fully supported.
I agree. The original question I quoted, however, came from a
discussion "limited" to OO.o <=> ODF. In that context, that is if you
only create ODF with OO.o, you *are* guaranteed (by definition) that
you won't introduce "ODF features not fully supported", right? In
other words, does OO.o behaves "creatively" in some cases?
> > The only way in which the statement above can be true is if OO.o
> > already supports a specific feature of OFD, but in a way that
> > actually and explicitly _violates_ the standard, right?
>
> It still wouldn't be necessarily true. Just don't use the feature
> that violates the standard.
I agree. My post here was mainly meant to find out if such "feature"
exist, which ones they are, and where they are officially listed.
I can always go back to that other list and tell the OP "please
_prove_ when and how OO.o violates the standard", but it would be
better, and more informative, if I could point to proofs that OO.o
never violates the standard (*) or that one must only avoid this or
that specific feature.
> If you would like to test OOo's output against the ODF spec, I would
> encourage you to try the ODF Validator
I was aware of such a tool, even if I'll confess that I had forgotten
its exact name and location. The original question may be rephrased as
"has any validator user already found any violation in ODF files
produced with OO.o?"
Ciao,
Marco
(*) as far as the file format, not the rendering, is concerned
--
The right way to make everybody love Free Standards and Free Software:
http://digifreedom.net/node/73
More information about the odf-discuss
mailing list