Jean-Baptiste <jean-baptiste(a)holcroft.fr&gt; さんはかきました: Yes, I think that is better. I’ll take the current push request as it is, having it in pt_PT is better than nothing, but I think it is better if it moves to pt. Currently it is like that on Linux. If a user runs in pt_BR.UTF-8 locale, translations are first searched in /usr/share/locale/pt_BR/LC_MESSAGES/ibus-typing-booster.mo if that doesn’t exist /usr/share/locale/pt/LC_MESSAGES/ibus-typing-booster.mo is tried as a fallback. If a user runs in pt_PT.UTF-8 locale, translations are searched first in /usr/share/locale/pt_PT/LC_MESSAGES/ibus-typing-booster.mo and if that doesn’t exist again /usr/share/locale/pt/LC_MESSAGES/ibus-typing-booster.mo is tried as a fallback. As the two variants of Portuguese are apparently quite close to each other, it makes sense to have one of them as a fallback for the other. So it makes sense to put the translations for one of them into /usr/share/locale/pt/LC_MESSAGES/ibus-typing-booster.mo and the other variant into the more specific directory. Apparently on Linux it has been the custom to put Portuguese as spoken in Portugal into /usr/share/locale/pt. CLDR does it the other way round, as you can see here: https://github.com/unicode-org/cldr/blob/master/common/main/pt_BR.xml the pt_BR.xml is practically empty, so it just falls back to https://github.com/unicode-org/cldr/blob/master/common/main/pt.xml which contains the Brazilian Portuguese translations. And https://github.com/unicode-org/cldr/blob/master/common/main/pt_PT.xml is not empty but contains the translations where Portuguese in Portugal is different from Portuguese in Brazil. I fill the Chinese case is somewhat different as simplified Chinese is not a good fallback for traditional Chinese and traditional Chinese is not a good fallback for simplified Chinese. I don’t think we would gain anything to move to zh-Hant and zh-Hans on Linux and cause a lot of trouble with locales and backward compatibility. Yes. I think it is OK as it is now that Weblate offers the choice and the projects/translators can decide which codes to use. Btw, in ibus-typing-booster I started a zh_TW translation and translated just one single string, just to make the zh_TW translation exist already in ibus-typing-booster. If somebody starts translating ibus-typing-booster into traditional Chinese, he will see that zh_TW exists already and use that and there is danger to accidentally choose zh_Hant. -- Mike FABIAN <mfabian(a)redhat.com&gt; 睡眠不足はいい仕事の敵だ。