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


I use GNU Linux Debian and LO is the same code & many developers as the
previous OO that was released with this distro.

That said , the LO devs are doing a lot of work on the code, cleanups, their
words, and I have noticed some 'enhancements' in LO 3.4.3. 

LO ver 3.3.4 looks & acts the same as my previous ver, OO 3.2.1, for my use.
The enhancement to how Tables line styles is configured has changed, and it
is not rendering double lines the same as ver 3.3.4 and previous OO
versions.. If your documents, the archived ones, have tables, they won't be
readable with LO ver 3.4.3. There are bug(s) filed against this issue,
something like #38542. 

I would say LO ver 3.3.4 is a replacement for all previous versions of OO 
and in time LO version 3.4.x will be even better. No need to run multiple
versions.

--
View this message in context: 
http://nabble.documentfoundation.org/Dead-End-or-Evolution-tp3352009p3357342.html
Sent from the Users mailing list archive at Nabble.com.

-- 
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted

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.