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


On 19/11/2012, Dennis E. Hamilton <dennis.hamilton@acm.org> wrote:
The OOXML specifications are at least as complete and rigorous as the ODF
ones.

Every indication is that the ODF 1.2 support in Office 2013 is quite good.
Of particular importance to many users is that OpenFormula is now supported,
and this will provide a tremendous improvement in interop between
LibreOffice Calc and MSO 2013.  Whether this becomes a preferable path
between Office and LibreOffice instead of relying on OOXML conversion in LO
is an open question.

That ODF12 is supported by m$ is useful to know, thanks. This means
that LO users will be able to send ODF12 documents and when recipients
complain that they can't read it, the recommended options are to
upgrade to m$ or use LO/another ODF compliant program.

As mentioned before ad nausem, those unhappy with LO should simply revert to m$.

The best way to solve these endless questions about "compatibility" is
not to use LO as a m$ clone. Use it to create odf documents or buy m$.

-- 
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted

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.