[Translators-l] Ready for early translation: Tech News #08 (2017)
niklas.laxstrom at gmail.com
Fri Feb 17 07:33:36 UTC 2017
2017-02-16 23:38 GMT+02:00 Stryn <strynwiki at gmail.com>:
> just a few questions regarding translation memory:
in short, it is a known issue (T101236).
To alleviate performance issues, the algorithm of the translation
memory was changed as follows: load N items in the source language
that match most closely to the string in translation. Then load the
translations for them (if any exist). If we do not get more results,
repeat the same for M more items. Currently N = 100 and M = 500.
It so seems that if there are many untranslated strings, we often fail
to choose the ones which would have translations. In addition I think
we have some sort of matching and ranking problem as well, since top
600 matches should definitely contain the previous translations.
It is easy to rule out an updating problem, since I can find those
translations with translation search . And this search  shows
that there are many untranslated ones.
You are probably interested when this will be fixed. I don't know the
answer for that. It is a non-trivial amount of a work, and it requires
some expertise in algorithms suitable for this purpose. Comments (in
here and Phabricator) which explain how this issue affects you and
wastes you time and how extensive the issue is are welcome and helpful
to show that it is an important issue.
More information about the Translators-l