Comment # 36 on bug 952855 from Stanislav Brabec

openSUSE:Leap:42.1 inherited a really old version of translation-update. This
should never happen: In openSUSE, translation-update has only a small meaning
(releases of GNOME are done early after upstream, and amount of new upstream
stings translated in time between freeze and release is low).

The glibc patch for locale-langpack support is very inferior, and if
translation is found in usr/share/locale-langpack, no more files are searched.

=> Leap inherited translation-update with strings for GNOME 3.10 in a snapshot
from February 2013, but Leap contains GNOME 3.16. => Bad translation things
will happen for the whole GNOME.

Releasing an online update with empty translation-update packages would be
probably the easiest way to fix this problem.


With that inferior way locale-langpack, I would stay away from including any
translations into this package. In difference to SLE, where customers are not
allowed to arbitrarily upgrade packages without losing support, Leap users
probably want to do it. With locale-langpack files, translations for version
upgrades will never be picked.

There is plan to refactor tools, and make translation update process part of
-lang package generation. It will solve this problem.