Hello Charles,
2011/1/4 Charles-H. Schulz <charles.schulz@documentfoundation.org>:
Jesper,
We are not interested in OOXML, a standard that became one only after a
campaign of deception and unacceptable pressures driven by Microsoft. We
are interested in ODF, an open standard developed by many players including
Microsoft.
We are only offering convenience to our users by letting them interact with
the poprietary formats of ms office product range. Therefore the OOXML
standard is not really something we are interested to help.
I think I was misunderstood.
:o)
I was not so much asking you guys to help us in SC34/WG4. With
implementers at Microsoft Office, ORACLE OpenOffice, LibreOffice,
Kingsoft, DataWatch etc, I think we are pretty well covered as it is.
(I'd personally be interested in what you find, but that's a whole other story)
I was suggesting that making your findings public (if you indeed find
some), you'd be able to help other OSS projects with focus like yours
(which is "users" and not promoting OOXML), and in addition you'd be
helping people like Leif and companies like ORACLE, IBM etc who are
actively fighting OOXML in governments etc.
Win-wn?
--
Jesper Lund Stocholm
www.idippedut.dk
SC34/WG4 http://www.itscj.ipsj.or.jp/sc34/wg4/
--
Unsubscribe instructions: E-mail to discuss+help@documentfoundation.org
Archive: http://listarchives.documentfoundation.org/www/discuss/
*** All posts to this list are publicly archived for eternity ***
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.