On 03/04/2011 07:12 AM, Ron Gregor wrote:
Just an update on this problem. It was found to be a bug and is going to be fixed in 3.4
I see a problem with the reply from Kohei Yoshida:
"Thanks for your bug report. This has been fixed in 3.4. Unfortunately
the change is very invasive that we can't backport this to the 3.3.x line."
Not necessarily that the problem isn't easy to fix in 3.3, but that the
bug is now marked as:
Status: RESOLVED FIXED
Were I you, I'd dispute that.
Primarily because: 1) tagging problems "RESOLVED FIXED" in the version
for the bug was reported (Version: LibO 3.3.0 release) and no backport
seems 'incorrect' to me, 2) there is no 3.4 version available to verify
I suppose that you'd be able to verify around April:
but without user verification prior to April 4, I suspect that you'll be
into another release cycle before it starts to get sorted out.
IMO the bug should remain open *until* there is verification that it has
been fixed in 3.4 *and* details as to why it can't/won't be backported
Perhaps Kohei Yoshida can comment/advise on this list?
Unsubscribe instructions: E-mail to firstname.lastname@example.org
List archive: http://listarchives.libreoffice.org/www/users/
*** All posts to this list are publicly archived for eternity ***
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