True. However, the good news is that the 2007 and 2010 formats are largely
similar and are XML based. The old formats were binary and kept changing.
Since the format isn't changing as much, and the new format is easier to
reverse-engineer, now is a good opportunity for OOo/LibO to "catch up" and
improve their compatibiltiy filters.
In some ways, OOo/LibO is better at opening old MSO documents than MSO
itself. Why not continue to improve that?
The difficult argument for many people has been to switch to a new document
format that most users can't open. But if you convince people that your
product is easily the best solution for opening the millions of
2003-and-before documents, then that is a clear advantage for your product.
It could be the killer feature that helps convince people to migrate.
Are the areas of poor compatibilty enumerated somewhere? Are these unknown?
Should users continue to report speciifc documents and features they have
-- T. J.
On Tue, Nov 2, 2010 at 3:06 PM, Charles Marcus <CMarcus@media-brokers.com>wrote:
On 2010-11-02 12:05 PM, Frank Esposito wrote:
File compatibility should be a priority, in the very least opening and
saving MSO files with full compatibility
There will *never* be 100% compatibility... like I said earlier, even
Microsoft doesn't achieve that between different versions of its own
Unsubscribe instructions: Email to email@example.com
Posting guidelines: http://netmeister.org/news/learn2quote.html
*** All posts to this list are publicly archived ***
- Re: [tdf-discuss] Re: Old Bugs (continued)
Impressum (Legal Info)
: 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