[libvoikko] HFST/ooovoikko slow startup

[Harri Pitkänen]

On Sunday 14 November 2010, Flammie Pirinen wrote:
> Ok, one of the problems I've been  having lately with ooovoikko is:
> 
> src/grammar/GrammarChecker.cxx:127: error: call of overloaded
> 'valueOf(int&)' is
> ambiguous /usr/lib/openoffice/basis3.2/sdk/include/rtl/ustring.hxx:1360:

Thanks, it should hopefully work now that I changed that slightly. Not that I 
have ever seen this error, probably something to do with how these sal_ types 
are defined on 32 vs. 64 bit platforms.

> I cannot get any debug to appear; I did try:
> 
>   522  make VOIKKO_DEGUB=FULL
>   523  make VOIKKO_DEGUB=FULL oxt
>   524  sudo unopkg list --shared
>   525  sudo unopkg remove --shared org.puimula.ooovoikko
>   528  sudo unopkg add --shared build/voikko.oxt
>   529  oowriter
>   533  /usr/lib/openoffice/program/soffice -writer
>   536  /usr/lib/openoffice/program/soffice.bin -writer
> 
> Without any debug printed to terminal. I will investigate it further
> later on.

Ah sorry, there was a (very stupid, I admit) quirk that the debug version of 
the extension was built as build/voikko-dbg.oxt. And of course that was not 
documented anywhere. I changed that now, if you do "svn update" and try again 
it should work, the debug extension now has the same file name as ordinary 
version.

> No, one thing I think commonly happens is that going to settings of a
> some sort, maybe even font settings, which has the language setting to
> change, may cause a reload, even when I've thought I hadn't changed
> anything relevant, but I have to recheck.

I can't reproduce this. In fact the only way of forcing a reload that I know 
is to go to Tools->Options->Language Settings->Voikko and change the
dictionary variant.

Just guessing here but maybe initialization of ooovoikko is failing somehow, 
this might explain why it would be retried every now and then.

> Shouldn't make a difference, if you check the other patch, you'll see
> the optimized stuff I've used for testing loads nothing in
> HfstMorphology nor HfstHyphenation. Anyways, they should also
> implemented so that they can share the automata, as long as linguist
> does not require different automata for different tasks, for whatever
> reason.

OK, then the problem is not there.

Harri