Localization

[stonith404]

This discussion is about everything related to localization. Feel free to engage in conversations about translation challenges and issues.

[SimonPistache]

Hi there! So the Crowdin system allow translators to raise and discuss issues with the dev team via the comments sections, usually at the key level like so:

I don't really know how it looks like from the admin perspective, though. But at least the GitHub should not be flooded :/

[stonith404]

You're right thanks! I'll leave this open for some general questions or discussions about translating.

[pierrbt]

Wow the french translations are already finished, I added small changes :

• Pot commun par partage inversé
• Courriel par mail ou adresse mail
• Surnom par Pseudo
  and few other things.

But apart from that, the translations are great so it can be integrated soon.

[SimonPistache]

@pierrbt I got carried :D (i'm Thoscellen btw)

Courriel par mail ou adresse mail

Not a fan, courriel is the official wording and it's understood nowadays so why not using it.

Surnom par Pseudo

I thought of that as well but pseudo looked too far from the original username,surnom felt welcoming and nice enough.

If it suits you, let's open a discussion on Crowdin so we can continue there.

[SimonPistache]

Hello @stonith404 , I would like to raise a question about the strings update process: I noticed something unusual whenever you push keys to translate, it looks like you rather replace the whole file in a way crowdin doesn't recall or bind back previous changes.

On my end, it looks like all the translations histories, suggestions, vote, etc get erased as you push the new file for translations, plus we don't know who made suggestions:

The big idea is that with time translations get built with suggestions so translations can be voted, discussed, etc

Something that also feel unsual is that it looks like we are translating the en-us.ts file rather directly, as opposed as using it as a source to generate translations (fr-fr.ts, de-de.ts, ...):

Imo crowdin should be able to generate the translations files at your will and maintain translations history, merging changes from your updates to the source file — and it looks like you partially do that manually.

sequenceDiagram
    stonith404->>+Github: Push en-us.ts
    Github->>+Crowdin: Pull en-us.ts
    Crowdin->>+Translator: Update Database with new tasks
    Translator->>+Crowdin: Edits translations for updated keys
    Translator->>+Crowdin: Suggest translations for new keys
    Crowdin->>+Github: Push fr-fr.ts

Loading

WDYT?

[stonith404]

Thanks for your observations, that's really useful because I didn't use such software before.

On my end, it looks like all the translations histories, suggestions, vote, etc get erased as you push the new file for translations, plus we don't know who made suggestions

That's extremely bad... I think the problem was that I've renamed the en.ts file to en-US.ts because since that change the histories etc. are still here. Could it be that this was the problem?

Something that also feel unsual is that it looks like we are translating the en-us.ts file rather directly, as opposed as using it as a source to generate translations (fr-fr.ts, de-de.ts, ...)

I'm not sure if I get your point. Do you suggest to add an example file that only has keys and no values? Currently I'm using en-US.ts as the source file.

[SimonPistache]

That's extremely bad... I think the problem was that I've renamed the en.ts file to en-US.ts because since that change the histories etc. are still here. Could it be that this was the problem?

That may be it… Should be working fine now on, I guess ^^

I'm not sure if I get your point. Do you suggest to add an example file that only has keys and no values? Currently I'm using en-US.ts as the source file.

I'm not suggesting anything because I don't have the answer :( But I wonder if crowdin allow such (and then if it's better). Looking at others project I participate, it looks like the English file is the source as we are doing now. Maybe crowdin is not at ease with .ts extensions (a json would work better?)?

Anyway it's not blocking us, it's just weird to see the raw file like this. Thank you for your involvement with us :D

[SimonPistache]

I just realized crowdin state 'no key' under each string and we can't filter or search by keys, so there is definitively something crowdin doesn't process correctly with the source file

[stonith404]

Yeah maybe we should try JSON but then the whole history is deleted again because we change the files. Additionally .ts files should be fully supported, they say.

I just realized crowdin state 'no key' under each string and we can't filter or search by keys, so there is definitively something crowdin doesn't process correctly with the source file

I absolutely have no clue why, but they leave the key empty but fill the key into the context field...

What I don't like about Crowdin is that there are almost no settings. I could give you admin access to the Crowdin project if you want to, maybe you find something that I've missed.

[lfac76]

Sorry if it a easy thing, but how I can get the docker image with pt-BR translation to find errors?

[pierrbt]

I think these translations have not been released yet so you have to wait for the next release in order to have the latest translations

[alexlehm]

This is not only about Translations but about the original English texts as well:

do you define a specific style for the messages, like using British English or American English or do you prefer a PC style like using non-specific pronouns, I read through the German texts and that uses tradition pronoun address which may or may not be an issue with some.

[stonith404]

Ideally, the texts should be in US English, but it's probably not really consistent.

What do you mean with "tradition pronoun address"? The "Sie-Form"? I would prefer texts written in the "Du-Form”, but I don't verify the translations, so this could be inconsistent too.

[alexlehm]

I noticed some text that assumes "Benutzer" is male
e.g. "Möchtest du wirklich diesen Benutzer und all seine Freigaben löschen?"
I am not completely sure how this is expected to be

[stonith404]

Oh you mean this. Yeah I'm not sure how we should handle this too.
We could use "BenutzerIn" but I don't really like this solution. Do you have a suggestion?

[alexlehm]

I am not really sure what is best, there are some terms in the english texts that could be changed and the german one could use Benutzer:in or BenutzerIn. Major internet sites in Germany now use mostly : notation, e.g. Vodafone Germany or Spotify

[stonith404]

Ok, in that case, I recommend using the : notation. Thanks for bringing this up for discussion :)

[TurtleException]

Right now, the german translations use a mix of formal ("Sie") and informal ("Du") pronouns. It would be nice if we could establish one or the other.
Alternatively, we could split them into 2 separate versions. I think I prefer this option because this way the user could choose what they prefer.

[stonith404]

Yeah that's not ideal. Unfortunately I didn't find a way to allow multiple language files for one language in Crowdin. I would prefer informal pronouns.

[TurtleException]

Sounds good, I'll get to work on replacing the formal pronouns.
I've never worked with crowdin before so I don't know how to implement the 2 separate versions. Maybe it's something like the chinese simplified / traditional differentiation?

[alexlehm]

i think the issue is that there is no convention for a language code that defines that, there is de_de, de_ch and de_at, but that would require an additional code like de_de_formal or so, which distinguishes both country and formality
the language code for chinese simplified is zh_cn, I am not sure what the traditional one is, that applies to the charset as well as the words
(or at least I think it does)