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


On 18 February 2011 10:25,  <ashleyt@arcet.com> wrote:
The biggest reason is our users do not remember to save in MS format when
sending files to customers and vendors. I am not sure a single customer of
ours could open an .odt file, for example, so we have to use formats our
customers and vendors can open.

Yes, I can see having LO/OO.o saving in MS formats by default for
accessibility for others. That is (unfortunately!) the reality.

Our IT departmnet prefers OO/LO not only due to licensing costs,
but also because the OO/LO interface is more familiar to most people.
 MS Office 2007 and 2010, with the ribbon interface, does not look
much like MS Office 2003.

AMEN!!!

I've started a new position and am **trying** -- I really am -- to get
used to that damn ribbon. But it is *really* slowing me down. I'm
really close to installing LO just so I can get some work done. It
took me nearly 10 minutes the other day just to get the paragraph
markers (something like ❡) to display! Grrr.


-- 
T. R. Valentine
Your friends will argue with you. Your enemies don't care.
'When I get a little money I buy books; and if any is left I buy food
and clothes.' -- Erasmus

-- 
Unsubscribe instructions: E-mail to users+help@libreoffice.org
List archive: http://listarchives.libreoffice.org/www/users/
*** 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.