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


On 30/12/10 20:23, RGB ES wrote:
2010/12/30 Gordon Burgess-Parker<gbplinux@gmail.com>:
OOXML will spread anyway because MS Office 2007 and 2010 use this format by
default. Nothing you can do about it I'm afraid....

That means nothing. MSOffice will be able to read the previous formats
for a while, I think...

That's not the point. Many users of MS Office don't know how , or can't be bothered, to change the default document format from OOXML back to previous format, especially as Windows 7 (by default) does NOT show the file extension, so users don't even KNOW they are using OOXML. (I have personal experience of this from Users I "support"). Therefore the use of OOXML will spread insidiously as the take up of Office 2010 (particularly) and Windows 7 speeds up. And I'm afraid there is nothing that can be done to stop this as MS Office almost completely dominates the Office suite world, particularly in corporate environments. And if you are sent an OOXML document to edit and return then it's bad manners not to send it back in the format it was sent to you, just like it's bad manners to receive a plain text email and reply in HTML....

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