[Kbabel] Two bugs?

Stanislav Visnovsky visnovsky at kde.org
Wed Aug 20 12:07:55 CEST 2003


Dňa St 20. August 2003 10:55 Hasso Tepper napísal:
> Ühel kenal päeval (kolmapäev, 20. august 2003 10:08) kirjutas
>
> Stanislav Visnovsky:
> > http://bugs.kde.org/show_bug.cgi?id=56082
> >
> > And it seems a fix is CVS HEAD for some time now.
>
> No. It isn't this one. I don't have spellcheck enabled. Something is
> wrong with searching from database. I have new installs - one in
> KDE_3_1_BRANCH and other in HEAD. Problem appears in both with kbabel
> from HEAD.
>
> If there is exact match, there is no problem - search finds this one
> quickly and that's all. But if there isn't, sometimes search takes
> ages (more than 30 sec. in my 1,5GHz centrino laptop) founds nothing
> or a lot of "matches".
>
> For example - msgid "Name=cql" in koffice_desktop.po. If there is no
> exact match in database it searches about 45 sec. and finds 1026
> matches with most of them common part is only "Name=". If there is
> exact match (I just translated it) and move back to the string only
> exact match is found and search takes fraction of second. I don't
> remember such behaviour in older versions.
>
> If I'm not mistaken then all msgid's I had this problem with have a
> lot of %X substrings or are "Name=", "Comment=" strings in
> x_desktop.po files.
>
> I thought about compiling older kbabel from KDE_3_1_BRANCH to look at
> search defaults from there, compare configurations (maybe that's only
> conf?), but it doesn't compile with flex 2.5.31 and I can't downgrade
> at the moment.
>
> I hope that it will help.


So it is a different bug than the KSpell one (and I've replied to a wrong 
message then, sorry).

The behavior is quite expected: the exact matching does not work, use
non-exact search. This can take a lot of time and yes, Name=bla
is similar to Name=cql. The higher speed of the older version is because
it uses "good keys" (something Andrea must comment on).  However, if
there are no good keys, the full database search is used instead. The behavior 
changed because I've fixed a problem when there were no good keys, but
the search engine thought there are, leading to non-stopping searches and
crashes.

Stanislav



More information about the kbabel mailing list