String Freeze and State of translations - Foreman 3.16

Hello,

We are currently in the process leading up to branching 3.16 and just wrapped up extracting the strings. Branching 3.16 and pulling in translations will be occurring on 2025-08-12. As part of this process, we update translations before each release candidate and the final GA release. Depending on the number of release candidates, there will be approximately 2 to 4 weeks to translate the new strings.

If you are a plugin maintainer, please extract the strings so translators can do their work.

The RC1 and RC2 dates are 2025-08-12 and 2025-08-26.

Please refer to the scheduling and planning post for more information and dates: Foreman 3.16 Schedule and Planning

Below are the stats for all languages we currently have translations for in repositories, out of 14.6k source strings (including strings from plugins):

Language Language code Percentage
English [source language] en 100.00%
French fr 97.84%
Japanese ja 97.65%
Chinese (China) zh_CN 97.61%
Korean ko 91.16%
Georgian ka 87.99%
German de 77.29%
Spanish es 75.02%
Portuguese (Brazil) pt_BR 72.04%
Russian ru 44.07%
Chinese (Taiwan) zh_TW 41.64%
Czech (Czech Republic) cs_CZ 38.96%
Italian it 34.55%
Catalan ca 26.43%
all languages - 21.55%
Polish pl 21.08%
Greek el 13.30%
Swedish (Sweden) sv_SE 13.21%
English (United Kingdom) en_GB 12.55%
Dutch (Netherlands) nl_NL 11.40%
Galician gl 10.32%
German (Germany) de_DE 4.94%
Gujarati gu 4.12%
Odia or 3.65%
Hindi hi 3.63%
Panjabi (Punjabi) pa 3.53%
Marathi mr 3.51%
Telugu te 3.50%
Kannada kn 3.50%
Bengali (India) bn_IN 3.50%
Tamil (India) ta_IN 3.47%
Tamil ta 2.55%
Bengali bn 2.53%
Slovenian sl 2.38%
Indonesian id 2.12%
Turkish tr 1.09%
Hebrew (Israel) he_IL 0.65%
Romanian (Romania) ro_RO 0.10%
Portuguese pt 0.09%
Vietnamese (Viet Nam) vi_VN 0.00%
Vietnamese vi 0.00%
Romanian ro 0.00%
Polish (Poland) pl_PL 0.00%
Malayalam (India) ml_IN 0.00%
Luri (Bakhtiari) bqi 0.00%
German (Austria) de_AT 0.00%
Estonian (Estonia) et_EE 0.00%
English (United States) en_US 0.00%
Chinese zh 0.00%

If you are a native speaker of any of the above languages and would like to contribute to the translations, please see Translating - Foreman for more information about how to do so. The procedure is very straightforward, as it is carried out using an easy-to-use web application that shows the strings to be translated and requests input. Please contact me if you are an active translator and want to become a coordinator or reviewer for your language.

If you believe that certain languages should be added or that we should avoid pulling translations for some languages that may have a poor translation rate, please let us know in the comments section below.

Looking at the table and think about

Currently, Foreman ships en_GB locale, so I wonder if we should ship also all other languages that have equal or higher completion than en_GB. If that’s the case, we should get Swedish (sv_SE) and Greek (el) in.

This feels arbitrary to me. Why not also include Dutch and Galician? (Disclaimer: also arbitrary at the double digit percentage.)

I cannot make any good argument either way, just thinking out loud.

en_GB’s inclusion makes sense to me since we can fall back to untranslated strings (en_US) without any issues for UK readers. The same standard wouldn’t hold for Greek. In my opinion, the current translation cutoff makes more sense.

1 Like

I’d agree with @qcjames53. The inclusion of en_GB makes sense due to the fallback to the untranslated strings.

Therefore, if no one objects, I won’t pull in new languages into 3.16.