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

On 2011-01-02 12:07 PM, Mark Preston wrote:
Please remember that both LibO and OpenO can already *read* the
formats and the issue is whether or not it is practical or pragmatic
to put effort into developing something to *write* the OOXML form.

Eh? It already can write them. Why go backwards? There definitely needs
to be a warning when doing the Save-As, but going backwards (ie,
removing the ability to write them) would be counter-productive at best.

FLOSS philosophical arguments have no place here. They are fine for a
philosophical debate, or even for some of our LibO Marketing efforts,
but pointless in interacting in the practical reality of a Microsoft
dominated Corporate software landscape.

One thing that could probably help a lot in this regard would be a page
or two with specific details on how to Save-As to the different formats
that LibO users could link to in emails they send to their
Clients/Customers/Vendors when requesting a document in a different
version. These pages could go to great care to be non-political, but
also provide links to other on-line resources that discussed the
philosophical differences, while refraining from engaging in any
negativity about Microsoft or any other commercial software vendors...


Best regards,


Unsubscribe instructions: E-mail to
*** All posts to this list are publicly archived for eternity ***


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.