On 10/08/2009 21:02, Pavel Sanda wrote:
Abdelrazak Younes wrote:
1) Disable inline spellchecking. Measure the time to load the User Guide.
Do it twice in order to have the file in cache.
cant be this solved by asynchro call for inline spellcheck similarly we do
for images loading?
Abdelrazak Younes wrote:
> 1) Disable inline spellchecking. Measure the time to load the User Guide.
> Do it twice in order to have the file in cache.
cant be this solved by asynchro call for inline spellcheck similarly we do
for images loading?
pavel
Jean-Marc Lasgouttes wrote:
I am not sure if it is spell() or suggest() that is so slow but I will
investigate.
Both are very slow (maybe 10 or 20 times as slow as aspell).
Can it be related to this thread
http://www.mail-archive.com/d...@lingucomponent.openoffice.org/msg01827.html
>> I am not sure if it is spell() or suggest() that is so slow but I will
>> investigate.
>
> Both are very slow (maybe 10 or 20 times as slow as aspell).
Can it be related to this thread
http://www.mail-archive.com/d...@lingucomponent.openoffice.org/msg01827.html
Did you check with different lan
Abdelrazak Younes wrote:
At least on Linux/ubuntu On Windows, with my self compile
hunspell, it seemed quite fast.
Just do this test:
1) Disable inline spellchecking. Measure the time to load the User
Guide. Do it twice in order to have the file in cache.
2) Enable inline spellchecking and
At least on Linux/ubuntu On Windows, with my self compile hunspell,
it seemed quite fast.
Just do this test:
1) Disable inline spellchecking. Measure the time to load the User
Guide. Do it twice in order to have the file in cache.
2) Enable inline spellchecking and select "aspell" spellchec