Locale Issues Megathread

[PrestonN]

Hey everyone,

I'll be the first to admit that the way that locales are setup isn't perfect. There are a few inconsistencies between languages that need to be fixed. Some smaller, some larger.

I'd like to compile a list of all of the problems that are out there. Fixing these issues will likely end up being done all at once in their own development cycle. I'd like this thread to be the location for all issues related to localization changed.

Note: If the issue is about a certain wording of a translation, it may be best to have that discussion over in Weblate as I won't be too helpful with that. This thread is more for stylizing and formatting issues.

What I need from translators / native speakers is the following.

1. The language that needs changes
2. The formatting / stylized change that needs to be made
3. How it's currently formatted
4. How it needs to change
5. Anything else you feel may be helpful

Once the problem has been fixed, I will hide your post to make you aware that it's resolved.

Thanks for the help!

[milotype]

@PrestonN Should I simply link my issues/merge request here one by one in order not to repeat myself, and so you could remove them if needed? Or am I missinterpretating the intention for this thread?

[PrestonN]

Go ahead and link the issues that you've created. Also go ahead and please close them if they are not already.

[milotype]

Alignment and typography corrections https://github.com/FreeTubeApp/FreeTube/pull/653#issuecomment-708464187 The issue about a separator charater between "value" and "extension" remained unsolved.

[Elaborendum]

• Selecting System Default when the computer is using any Latin American Spanish (excluding, I assume, Mexican Spanish) results in the Locale not being found and the app defaulting to English. I assume this happens for other locales that are specified to a region (like maybe Belgian French?). This happened on Windows 10.
• I don't really agree with the idea of having multiple Spanish translations in projects that aren't very big, as I've seen that a lot of the time one ends up being very under worked because translators probably feel like it's tedious to do most of the same work twice. But since this project has both UK and US English, I'll assume this shall follow suit in this case.
  • Anyway, onto the actual issue. I don't really think it's necessary to have a third Spanish translation (the Argentinian Spanish one), as the Mexican Spanish translation could cover Latin American Spanish in general, plus, it's already under worked in comparison with the other two.

Is this the right place, or should I file a separate issue for each one?

[GilgusMaximus]

Well, we are using Weblate. If the language is not translated over there, then it will not be found.

We want to keep the diversity, as we are no language experts who can tell which language differences matter and which not. E.g. Norwegian Bokmal and Nynorsk or chinese. So there are three possible solutions here:

Either changing system locale to a supported language, choosing an available language, or someone could go ahead, copy the language file, rename it according to standard to their language accent and make a PR.

Or translate on weblate alternatively.

[Zakret]

Hi! I have an issue with this string https://hosted.weblate.org/translate/free-tube/translations/en/?checksum=ab977b817b746e15. There is not enough space for the translated string. Polish: Deutsche:

[efb4f5ff-1298-471a-8973-3d47447115dc]

Hi @Zakret i think ur problem is actually related to https://github.com/FreeTubeApp/FreeTube/issues/1300

Edit: @Zakret u dont have to worry about that anymore this is fixed in PR https://github.com/FreeTubeApp/FreeTube/pull/1767

[70h]

I have completed the Lithuanian translation, but the last three versions still won't allow me to select it in the language settings. Is there something more that should be done or am I just to impatient? Thanks!

[peepo5]

Is it hidden? I do not see any lithuanian there. That is weird.

[kubo6472]

Hey there, I just updated 🇸🇰 translation. I've come around this error, not sure if it has been seen yet.

The following occurrences were found:
Language code | Suggested individual language codes
ku | ckb, kmr, sdh

[Zakret]

Hi! It looks like there are strings for the title menu on the Weblate page, but the translations are not applied

[Zakret]

There seems to be a problem with the Urdu yaml file on the Weblate:

The translation is temporarily closed for contributions due to maintenance, please come back later. The translation was automatically locked due to following alerts: Could not parse translation files. static/locales/ur.yaml 'expected , but found '' in "", line 132, column 5:\n General Settings: 'عام ترتیبات'\n ^ (line: 132)'

[sveinki]

There seems to be a problem with the Urdu yaml file on the Weblate:

The translation is temporarily closed for contributions due to maintenance, please come back later. The translation was automatically locked due to following alerts: Could not parse translation files. static/locales/ur.yaml 'expected , but found '' in "", line 132, column 5:\n General Settings: 'عام ترتیبات'\n ^ (line: 132)'

Meanwhile all the other translations are blocked...

[absidue]

@sveinki @Zakret We've fixed the issue in the Urdu file, hopefully weblate will unlock the languages for you soon.

[sveinki]

@sveinki @Zakret We've fixed the issue in the Urdu file, hopefully weblate will unlock the languages for you soon.

Weblate unlocked, thanks a lot!

[ghost]

The Russian translation is not displayed in the places on the attached screenshots (the player has all the buttons without translation).

[ghost]

[maboroshin]

[REDACTED]

Reason: Spam/offtopic

[Zakret]

Weblate seems to be locked due to parsing errors in several translation files: https://hosted.weblate.org/projects/free-tube/translations/#alerts

The translation is temporarily closed for contributions due to maintenance, please come back later. The translation was automatically locked due to following alerts: Could not parse translation files.

Filename	Error
static/locales/bs.yaml	'could not find expected ':' in "", line 189, column 1:\n Playlist:\n ^ (line: 189)'
static/locales/eo.yaml	'could not find expected ':' in "", line 153, column 1:\n Playlist:\n ^ (line: 153)'
static/locales/fa.yaml	'could not find expected ':' in "", line 357, column 1:\n Playlist:\n ^ (line: 357)'
static/locales/fil.yaml	'could not find expected ':' in "", line 138, column 1:\n Playlist:\n ^ (line: 138)'
static/locales/gsw.yaml	'could not find expected ':' in "", line 149, column 1:\n Playlist:\n ^ (line: 149)'
static/locales/la.yaml	'could not find expected ':' in "", line 211, column 1:\n Playlist:\n ^ (line: 211)'
static/locales/si.yaml	'could not find expected ':' in "", line 134, column 1:\n Playlist:\n ^ (line: 134)'
static/locales/ti.yaml	'could not find expected ':' in "", line 142, column 1:\n Playlist:\n ^ (line: 142)'
static/locales/tok.yaml	'could not find expected ':' in "", line 147, column 1:\n Playlist:\n ^ (line: 147)'

[maboroshin]

He closes and locks the issue that is still having problems. This is a very closed attitude that is against GitHub guidelines. However, the following are still ongoing translation issues. Perhaps it should be reported here.

• "Japanese translation discussion" https://github.com/FreeTubeApp/FreeTube/issues/714 : Japanese translations are reverted to low quality.
• "Weblate's poor functionality" https://github.com/FreeTubeApp/FreeTube/issues/648 : The problem could also be due to the developer's choice of Weblate.