Standards are there for information exchange. Therefore, good
practice requires that there are (at least) two independent
implementations of the standard.
(This is what is severely missing with the OpenDoc (OOo2)
standard.)
That's what I mean, we've got, what? Two office suites using
OpenDocument? And really, neither one is using them for real yet. OOo
2.0 (that great mythilogical beast) *will* use it, but KOffice
doesn't yet, and OOo doesn't yet.
Eh??
We've been using OOo2 exclusively in our office with essentially ZERO
problems for the last 6 months, so don't know where that 'mythological
beast' comment came from. The dev builds of OOo2 have been *much* more
stable than *any* of the OOo1 builds ever were, at least in our small
office of 40 users, and with much less file format compatability issues
to boot.
And when they do, what is that - maybe 10% of the market share (which
I highly doubt, but that number was quoted to me eariler). But that
just means 10% of the market share will have access to it - not
actually use it in everyday life.
I'm just curious... isn't it possible to create third party add-on file
filters for Microsoft Office products?
Why not simply create an OASIS file filter for Microsoft Office that
anyone can d/l and install with just a few clicks of a button? Then, to
get *FULL* file format interoperability, all a MSO user has to do is
install the filter.
Such a filter should be an *official* add-on written and/or approved of
by the OOo devs, for respectability purposes.
Maybe such a thing is impossible, but I don't really see how it could be
any more difficult than reverse engineering the MSO fornmats themselves...
--
Charles
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
