Am 12.09.2011 02:28, Edwin Powell wrote:
If LibreOffice and OpenOffice.org did not support M$ Office file
formats, nobody would support them. Like it or not, the M$ Office file
formats, both the older ones and the newer XML based ones, are the
defacto industry standards. The greatest marketing point that OOo and
There is only one file format which
- resembles the whole feature set of OOo/LibO (which comes very close to MS)
- is perfectly well documented and supported
- without being technically too difficult to implement (even partial
implementations give valid documents)
- is implementable without any legal issues, disclosure agreements,
patent fees, binary enclosuers nor vendor specific implementation details.
Such a file format will never be actively supported by Microsoft. This
was the core point why the whole software project around ODF started in
the first place. And we were going to win the race until Novell entered
the scene.
Controlling the daily used file formats _in_whatever_software_product_
is the strategic key point why MS formats are de-facto standards without
implementing any standard at all.
--
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.