To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=66939
------- Additional comments from n...@openoffice.org Thu Feb 26 09:01:43 +0000 2009 ------- nemeth, this is fantastic news! I'm looking forward to browsing the "doubleaffixcompress" source, and seeing if I can incoporate it or something similar in the hspell distribution (so that doing "make hunspell" will create an optimal hunspell dictionary). The numbers you report, 5.5 MB runtime memory use, 2 MB disk use and "few tenth of a second" are very encouraging. For the average user, they not too far from the optimal we've been able to achieve in hspell (as I described in previous comments) - 4 MB, 0.1 MB and 0.05 seconds respectively. --------------------------------------------------------------------- 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...@framework.openoffice.org For additional commands, e-mail: issues-h...@framework.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org