# \[Weblate configuration\] Automatic language adding
**URL:** https://forum.antennapod.org/t/weblate-configuration-automatic-language-adding/6809
**Category:** Translations
**Tags:** all-languages
**Created:** [June 22, 2025, 8:20am UTC](https://forum.antennapod.org/t/weblate-configuration-automatic-language-adding/6809 "2025-06-22T08:20:55Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@keunes](https://forum.antennapod.org/u/keunes)
#### Post date: [June 22, 2025, 8:20am UTC](https://forum.antennapod.org/t/weblate-configuration-automatic-language-adding/6809/1 "2025-06-22T08:20:55Z")
Following up on this:
> [@Looking forward to become a dedicated translator/reviewer for pt-BR](https://forum.antennapod.org/t/looking-forward-to-become-a-dedicated-translator-reviewer-for-pt-br/6795/3):
>
> Hey, @delthia ! Lately, I’ve been making good progress on the App translation, but as for the website, there are no components available for Portuguese (Brazilian). Is it necessary to request their addition in a fresh new post and should I mention anyone in specific? Thanks!
I think it’d be handy if for the website we can just add one language, and then it gets applied to all other website components. Especially if we [drop md2po](https://github.com/AntennaPod/antennapod.github.io/issues/325) which currently collates all our website texts into 4 files (which would mean we’ll have a gazillion components in Weblate to which the languages have to be applied).
However, the [‘Add missing languages’ add-on](https://docs.weblate.org/en/latest/admin/addons.html#addon-weblate-consistency-languages) applies to the whole project - all components where this plugin is enabled. This means Android’s language code specifics would conflict with our website language codes: with the add-on enabled on all components, we’d get Android-specific language codes in our website and generic strings in our Android translations.
# Solution
## a) Set Language filter
Set a [language filter](https://docs.weblate.org/en/latest/admin/projects.html#component-language-regex) on the components:
- App
- Play store
- Website
For the app and website, in principle only all two-letter codes, with exceptions where languages differ greatly between countries (this is of course up for discussion)
- Portuguese / Portuguese Brazil
- Norwegian: only Bokmal
In RegEx: `^(?!no$)(..|(nb|pt-BR))$`
For Play store, there is a specific list of languages that can be supported: [Translate and localize your app | Play console help](https://support.google.com/googleplay/android-developer/answer/9844778?hl=en#zippy=%2Cview-list-of-available-languages#:~:text=view%20list%20of%20available%20languages)
## b) Activate ‘Add missing languages’ add-on
We can start with doing this only on the website components.
Later we can enable it also for the app and app store components, so that we get app store descriptions for all languages that we have in the app. For this we would need to:
- Make the long description a single string (now it’s split in multiple strings)
- Set the [`max-length:N` custom check flag](https://docs.weblate.org/en/latest/admin/checks.html#custom-checks#:~:text=offered%20for%20translation.-,max-length%3An,-Limit%20the%20maximal) on the play store [full description](https://hosted.weblate.org/projects/antennapod/app-store-listing/full-description/en) strings (4k) (the same flag is already set on the [short description](https://hosted.weblate.org/translate/antennapod/app-store-listing/short-description/en/))
* * *
WDYT @ByteHamster @delthia?
# Other thoughts
I see we [currently support](https://github.com/AntennaPod/AntennaPod/blob/c3a1f3a98e8040f10a862fc7acac56810f5a586a/common.gradle#L5) down to Android 5.0 (API level 21). Would it simplify matters if we move up to Android 7.0 (API level 24), given that this version and up has better language resolution?
I see we have a [languages list in common.gradle](https://github.com/AntennaPod/AntennaPod/blob/c3a1f3a98e8040f10a862fc7acac56810f5a586a/common.gradle#L13) - how is that constructed again? Is it coming from Weblate? (I’m wondering if we could apply that list to Weblate, and maybe update it automatically [like Grist did](https://github.com/gristlabs/grist-help/pull/327). But if the list is coming from the languages on Weblate in the first place, there would be no point.)
Resources / related:
- Languages supported in [Android 16 release 2](https://android.googlesource.com/platform/frameworks/base/+/android-16.0.0_r2/core/res/res/values/locale_config.xml)
- How language support is organised in Android:
- [https://developer.android.com/guide/topics/resources/internationalization#nougat](https://developer.android.com/guide/topics/resources/internationalization#nougat)
- [https://developer.android.com/guide/topics/resources/multilingual-support#postN](https://developer.android.com/guide/topics/resources/multilingual-support#postN)
- [Option to switch app language by Nymuxyzo · Pull Request #7214 · AntennaPod/AntennaPod · GitHub](https://github.com/AntennaPod/AntennaPod/pull/7214)
- [Best practices for your store listing - Play Console Help](https://support.google.com/googleplay/android-developer/answer/13393723?hl=en-GB&sjid=5921349094232073672-EU#:~:text=a%20full%20description%20allows%20for%204%2C000%20characters).
---
### Author:  [@system](https://forum.antennapod.org/u/system)
#### Post date: [October 20, 2025, 8:21am UTC](https://forum.antennapod.org/t/weblate-configuration-automatic-language-adding/6809/2 "2025-10-20T08:21:52Z")
This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.