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


Well, we need to be able to import those transitional OOXML (2007-2010)
formats. If we can save to them, is not really necessary, (since MS office
suites 2007 & 2010 support MS-Office 2003 FF too), but is a nice to have
feature. The real ISO OOXML will be implemented by MS first on MS Office
2014. By them LibreOffice must be able to import and export that
format. They will depreciate the old format MS-Office FF when they finally
implement the ISO OOXML, which is not a complete open format since it still
has a lot of proprietary hooks, but at least the base is openly specified.

Even though I think it would be nice to be able to export to the
transitional formats too, I agree that it a pain in the a.... But that's how
MS is playing with the Open Standards and we have to win them in their own
game.

Cheers!

Jaime R. Garza

On Sat, Jan 1, 2011 at 23:29, Barbara Duprey <Barb@onr.com> wrote:


I don't think anybody is saying LibO should drop .doc export -- just not
try to export to the OOXML "Transitional" formats. In theory, MS will go to
OOXML "Strict" in the 2014 (or whenever) release, and that should by then be
a truly open format, if the comments submitted to the standards committee
are properly worked off. Meanwhile, exporting to the "Transitional" form for
new documents is specifically deprecated in the ISO standard; doing that
really plays into a possible MS strategy to continue to ignore the "Strict"
version forever, maintaining the proprietary lock-in while claiming to be
open.

Several of the comments here suggest a middle road, allowing the save but
with a message clarifying the limitations of the format (and perhaps
recommending use of the XP formats if interoperating with an MS-only shop;
their ODF support is not truly interoperable at a reasonable level, the
older formats come closer). That seems reasonable, at least for editing
documents that are received in these formats -- I'm not convinced it should
be allowed for new work, though. At the least, the SaveAs dialog should
label the format using the word Transitional. It probably makes sense to
start working towards OOXML "Strict" export as soon as that is a reasonably
stationary target, though. Wouldn't it be great if LibO were the first
implementation compliant with the ISO standard? And if the other FOSS
implementations also headed there, we could beat MS at their own game!


 It must be arrogant for them to send you a format you don't support.
Also, if the Win 7 users don't know what format the documents are in,
why does it matter if it's returned to them in a .doc format?

Think you hit the nail on the head, pal.
Those who ignore any notion of a file format, will do it both ways,
always, anyways...

 Office on-the-web only saves in docx.  Office 2013/4 will quite possibly
drop .doc export,
just as Word 6/95 export was dropped from Word 2003 - after a failed
attempt to drop it
from 2000.  MS can do this because they are the market leader.  To fail to
offer even
rudimentary docx export would damage LibO's market penetration.

my thoughts anyway!

zf



--
Unsubscribe instructions: E-mail to 
discuss+help@documentfoundation.org<discuss%2Bhelp@documentfoundation.org>
Archive: http://listarchives.documentfoundation.org/www/discuss/
*** All posts to this list are publicly archived for eternity ***



-- 
Unsubscribe instructions: E-mail to discuss+help@documentfoundation.org
Archive: http://listarchives.documentfoundation.org/www/discuss/
*** All posts to this list are publicly archived for eternity ***

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.