To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=114492
------- Additional comments from f...@openoffice.org Wed Sep 15 10:41:52 +0000 2010 ------- No, 3.2.1 is not likely to be developed any further. 3.3 is in Beta state, but in this phase of the release cycle, it is unlikely that a bug like this will be accepted, since it exists since at least 3.1.1 (probably longer). So, your options are: - wait for 3.4 - build an OOo 3.2.1, including the patch, yourself - convince the release team that this issue here is worth being fixed in 3.3 (done by sending a mail to relea...@openoffice.org, explaining why you think the issue is worth to block the 3.3 release) --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@dba.openoffice.org For additional commands, e-mail: issues-h...@dba.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
