To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=101726
------- Additional comments from [email protected] Tue Dec 8 08:17:48 +0000 2009 ------- @os First of all let me thank you for interest and time spent on this topic. I have some thoughts to share. 1- speeding up the loading of that list with so many entries is probably not an easy match. I understand this. And it's up to you to see if this is technically feasible... If it's not I suggest to cosndierer Issue 101714... this new feature would prevent loading the slow table and add new autocorrect entries in few seconds, saving time and produictivity. 2- the slow loading time issue is also present with non saturated acor.dat files... as I told in previous posts, with a virgin .dat file the table loads in less than a second then its performance progressively declines... 5 seconds with 4K entries... 4 minutes with 36K entries... 10-15 with >50K entries apart from my case (65K) which may not be a common situation, you still have long loading times even for smaller databases like 36K. The time your OOo gets stuck to load the table hurts productivity. I had to disable the Ctrl+H hotkeys since I experienced accidental hits that meant OOo freeze and wait or Ctrl+Alt+Canc. Maybe something may be done for speeding the table in earlier phases of filling (i.e. 36K example). 3- sooner or later other users will accumulate high numbers of autocorrect entries. I understand I'm a particular case but my job consists of writing medical reports all the day, so the more I write, the faster I type, the higher numbers of errors I do which I send to autocorrect to avoid future mistakes. However I took 2 years to fill the first acor.dat file... I started using OOo in march 2006 and reached the 65K limit in march 2008 when I reported the issue... then from april 2008 to december 2009 I added other 53234 entries in another acor.dat file (do you remember my workaround using the italian acor.dat file and the global acor.dat file). So, I expect that even if other users do a less intensive use of that feature, with time they will reach my point... there's people who's using OOo from earlier versions and is accumulating entries overs entries will certainly experience progressive slowness of the replacement table (= reduced performance) and 65K limit crash and autocorrect database implosion (= loss of data) 4- thanks again for your attention. according to my estimates I still have 5-6 months left to reach again the 65K limit or to learn to type without errors.... :-) --------------------------------------------------------------------- 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: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
