Re: [tdf-discuss] Initial Reactions to 4.0.0
2013/2/10 Andrew Douglas Pitonyak <firstname.lastname@example.org>
I have not been able to install the final release, but I have a copy of
RC2 installed. I have not yet had significant experience with it, but:
First the bad:
I only found one problem (new bug introduced into the macro language that
prevents a struct from being assigned to a property in another struct), but
Noel Power fixed that for release to 4.0.1 Sadly, the fix did not make it
into 4.0.0. I found a work around, but I hate to change my existing macros
for a bug that will be fixed soon. When will 4.0.1 be released?
Now the good:
My entire impression on the good is based on the fact that it just seems
to render better. I don't want to go back just because it looks better.
Unsure what was done with respect to fonts and rendering for this to be the
case; maybe it is all in my head.
Sadly, I have been significantly busier than usual, so I cannot comment on
many other aspects of the release.
The team has done a very good job.
Andrew, the version available for download from the LibreOffice site as of
yesterday, when I did so, was 188.8.131.52, so I presume that the bug you
mentioned has been corrected. Perhaps you would care to check ?...
Unsubscribe instructions: E-mail to email@example.com
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.documentfoundation.org/www/discuss/
All messages sent to this list will be publicly archived and cannot be deleted
Impressum (Legal Info)
: 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