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


Am 03.10.2011 12:30, Pedro wrote:

This is not a matter of being a clone. If a user or company wants to migrate
(and I believe that TDF and LO want that in spite of your personal opinion)
from MS Office to LO they need to be able to convert their existing
documents.


But then you need a software which supports each and every aspect of the foreign file format in the same way. This comes very close to writing a clone of the other software. This is why the Sun ODF plug-in for MS Office amounts to 80+ MB. It produces perfect ODF because it basically installs a clone of OOo 3.2 under the hood of the other office suite.

The dilemma is perfect when the application's native file format provides only a sub-set of the attributes that can be stored in the foreign format. This is why life would be so much easier if MS would support ODF. Their "bigger" software could do this much easier than our software will ever support their formats, particularly when they constantly "extend" their own formats in order to be as incompatible as possible.


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