Cleanup languages/translations and limit them

[litetex]

Checklist

• I made sure that there are no existing issues - open or closed - which I could contribute my information to.
• I have read the FAQ and my problem isn't listed.
• I'm aware that this is a request for NewPipe itself and that requests for adding a new service need to be made at NewPipeExtractor.
• I have taken the time to fill in all the required details. I understand that the feature request will be dismissed otherwise.
• This issue contains only one feature request.
• I have read and understood the contribution guidelines.

Feature description

• Remove all languages that can't be displayed/are not supported by Android (mostly non ISO 639-1 derived)
• Remove all other languages that are not supported
• Remove all other languages that are irrelevant. This can be determined like this:
  • Only a small percentage of translation keys was actually translated
  • Translations were last updated many years ago
  • Language is effectively not present in our userbase (e.g. there will be like 2 users who use it → can be removed)
• Don't allow reintroduction of those languages on Weblate and block them and also block other irrelevant languages.
  • If possible configure weblate so that new languages must be approved by us

Why do you want this feature?

From @TobiGr

@litetex I think we need to go through Weblate and purge a few more locales. There are a bunch of locales which were added because it possible to add them (e.g. Dutch (Middle), English (Middle), English (Old), German (Low), Mainfränkisch)

Further context: #12093 (comment)

Note: @litetex updated the issue to better represent it's current state 2025-08-16

[litetex]

@TobiGr
It looks like I'm no longer part of the NewPipe project on Weblate. Could you re-add me?

[TobiGr]

A different approach would be to introduce a gradle task to remove those files when building on release or master branches.
What do you mean by

Remove all non ISO 639-1 derived languages as they can't be displayed

Others are also allowed as stated in the docs.

Any weblate changes should be done together with the corresponding repo changes. I added you to the weblate team.

[litetex]

What do you mean by

Remove all non ISO 639-1 derived languages as they can't be displayed

All languages that Android knows must usually start with an ISO 639-1 identifier.
Here is Android's list of all languages.
There are a few exceptions to this rule as some ISO 639-2 languages are also present, however this is quite rare. I only counted around 20 (without variants) inside the file in contrast of 600+ overall languages.

A different approach would be to introduce a gradle task to remove those files when building on release or master branches.

I think an easier solution is the following:

1. Set Adding new translations to Contact maintainers or Point to translation instructions URL.
   • If we chose Point to translation instructions URL we can reference a new issue template that explains what needs to be considered when doing so
   • Adding new languages happens quite rarely so I don't think this should be much of an effort
2. When adding a new language we should then check if this language is relevant and allowed by Android's list.

What do you think about this approach?

I added you to the weblate team.

Thank you for the invite. It worked :)

[enolp]

I think this issue needs more dicussion. Android supports ISO 639-2 locales but only shows a limited set of them depending on the device or custom ROM. For example, Asturian "ast" has no ISO 639-1 code but it is fully supported on LineageOS and partially hidden in other OEM roms. Maybe manufacturers hide locales from ICU library.

Language`is effectively not present in our userbase (e.g. there will be like 2 users who use it → can be removed)

You should not remove language based on the number of speakers. In fact, if you do that you're discouraging people from using your app. Free (as freedom) apps are a big opportunity for endangered and/or minorized languages because the they give visibility.

Only a small percentage of translation keys was actually translated

Translations were last updated many years ago

Why don't you call for new translators? "Hey, NewPipe needs your help and XXX locale wants you. Help us to translate NewPipe into XXX locale"

Don't allow reintroduction of those languages on Weblate and block them the and also block other irrelevant languages.
If possible configure weblate so that new languages must be approved by us

What would be the criteria for adding a language? Who or what would dictate what is useful or useless? "Blocking" languages is like "restricting" people of certain race based on (insert here your political trauma)

[ale5000-git]

What would be the criteria for adding a language? Who or what would dictate what is useful or useless? "Blocking" languages is like "restricting" people of certain race based on (insert here your political trauma)

I'm not related to this project but in my opinion it doesn't make sense to include a language if it isn't at least 50% complete.

Do you think it make sense to include a translation if a person translate maybe just 10 phrases and everything else is missing?

[litetex]

For example, Asturian "ast" has no ISO 639-1 code but it is fully supported on LineageOS and partially hidden in other OEM roms.

From my point of view, I would get mad if I see my contributions getting removed

It looks like you didn't read #12503 (comment) or had a look at the various commits in #12504?
Asturian is supported by Android and the translations of this language are also well maintained. So it can and should stay.

I'm not investing any further effort into a discussion here (or #12093 (comment)) because it's clearly not healthy to do one. The points why we need to do this have been described before and in the issue.