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

Hi :)
+1 to both points.

The UI issue is cropping up more often but many people, get over their
initial dislike and prefer the return to sanity because it makes it easier
to find things and easier to learn new stuff.

The formats issue is mostly one of perception.  People still believe the MS
formats have longer longevity despite the fact they, almost daily, find
problems sharing such files with each other.

Just as Italo said and Jay agreed i've never had problems with any version
of LO myself (or with clients) but i know there have been many over the
years and even a couple of theoretical security issues.  However i (well,
my clients) run into problems with MS Office quite often, despite seldom
actually using it myself.  I originally joined this mailing list to learn
about current problems and work-arounds in order to be ready for client's
questions.  I've always been over-prepared as a result = so thanks to all
of you for that :))
Regards from
Tom :)

On 11 October 2015 at 18:01, Jay Lozier <> wrote:

On 10/11/2015 12:48 PM, Italo Vignoli wrote:

On 11/10/15 11:44, Alex Thurgood wrote:

I would suggest putting yourself in an admin's place where they have
probably invested long hours in developing a turnkey
OpenOffice/LibreOffice solution for their group of users, then finding
one day that that longstanding behaviour has changed because someone
else has not thought through a code change due to the tentacular nature
of the code base with no one having an overarching knowledge of it all,
and you will perhaps understand Andreas' frustration (which I happen to
share and have voiced it on the mailing lists in the past).

During the last four years I have helped to migrate to LibreOffice
several Italian organizations - especially public administrations - for
a total of over 30,000 PCs. Today, I am helping the Italian Defense to
migrate to LibreOffice 150,000 PCs.

I might be incredibly lucky, but I have never experienced significant
stability issues with LibreOffice, since version 3.5. Of course, when I
say "I have never experienced" I mean that none of the organizations I
have helped has experienced significant stability issues. Again, we
might be extremely lucky here in Italy.

Hi Italo,

The only consistent complaints I hear about LO is that the UI is different
from various MSO office versions and concerns about handling MSO file
formats. The first is complaint was often due to user unwillingness to
learn anything new - not an uncommon problem. This is not an LO specific
issue. The second issue, to me, is more legitimate. I have seen many
proprietary document formats for office documents come and go over the last
30 years. I can appreciate the concern about being able to open documents
in a non-native package in the future.

I have not heard of any (my very limited sample) stability issues that
could be attributed to LO. The stability issues I was seeing were Windows
issues seen in many packages.

I suspect your stability experience is the norm, LO is very stable. If
there are issues they are often user unwillingness to change or system
problems outside of LO.


To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


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.