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



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
 
On 12/30/2010 12:27 PM, Larry Gusaas wrote:
I will not support or use LibreOffice
until it stops helping spread OOXML by enabling writing in this
file format. There is absolutely no need to write in this
proprietary format. To do so is contrary to the principle of using
ODF and open source formats.

On the other hand . . . isn't that doing exactly what MS does? Do two
wrongs make a right? I thought the idea behind this particular office
suite was to make any file accessible to the extent possible. That's
why I use it. Regardless of what LibO does, MS is going to continue to
use OOXML, and if the open source suites don't support it, then they
are shooting themselves in the foot and essentially doing MS's bidding
by ensuring that people who want to exchange files in that format have
to buy MS products.

- -- 
Steven Shelton
Deputy Undersecretary for Made-up Titles
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
 
iEYEARECAAYFAk0c6CIACgkQO+AD2HqgRoAFmACeJfN63kpY0scYYf4nh9HI6M3d
m18AoMuiy7TqhzLg8pxuMEch0eDp2nKD
=Lj+L
-----END PGP SIGNATURE-----


-- 
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.