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


On 2 January 2011 17:19, Barbara Duprey <Barb@onr.com> wrote:
On 1/2/2011 2:29 PM, Italo Vignoli wrote:

On 1/2/11 8:15 PM, Barbara Duprey wrote:

[snip]

It would be good to know which works better for interoperability when sent
to an MS-only shop -- ODF or the current OOXML. In other words, is the LibO
version of OOXML a better product than the MS version of ODF? Very
interesting, if so. I'd like to know which to recommend. And of course the
Sun(free)/Oracle(not free) plugin for MS Office is a player in this
question, too. I know it's better than the MS ODF, but how does it compare
to the LibO OOXML?

OOXML wins hands down in this use case. Not because the LibO/OOo OOXML
is better than the Microsoft ODF or Sun/Oracle plugin for MS Office
but because the vast majority of MS-only shops don't bother installing
support for ODF in the first place. I went through this with a
customer recently: it ended up being a lot easier for me to output
OOXML or good old DOC than for them to install the right plugins to
read ODF. This is compounded by the fact that a lot of MS-only shops
are large companies that still use Windows XP with an old version of
Office.

Bruno

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