Translation features

[aapeliv]

• [ ] Multiple fallback languages: there's been a request from the translation team to have multiple fallback languages, e.g. French (Canadian) falls back to French (France) and then to English.
• [ ] Language picker: obviously, but also they want to preview different languages
• [ ] Easier previewing of current translations (before they get pushed to prod; also an easy link for translators to the vercel preview on weblate branch)
• [x] An allow list of languages to be used (e.g. so that a language that has only been started isn't viewed, as it can look pretty harrowing)
• [x] Not dev related: someone to review English copy

[comradekingu]

1.Setting more fallback languages in the web browser is the better way to do so? It is a corollary to having those languages to show in the first place.

2. What type of preview? Overview of completion, or a comparison outside of actually switching?
3. Previewing PRs before they get merged seems reasonable. Or you can get updates from Weblate once something happens.
4. I don't understand why some translations isn't better than no translations. Seems like a lot of effort to make sure nobody sees their own mistakes. Naturally a lot of users aren't inconvenienced by this since the usergroup is also bound to be small, and they won't expect wonders. @aapeliv Happy to help review strings. Can you add nb_NO (Norwegian Bokmål) so I can get something more out of doing so?

Edit: I am https://translate.couchershq.org/user/kingu/

[aapeliv]

1.Setting more fallback languages in the web browser is the better way to do so? It is a corollary to having those languages to show in the first place.

We'll let users switch languages as they wish. It's better we define the fallbacks so that we can know what it looks like for users.

2. What type of preview? Overview of completion, or a comparison outside of actually switching?

I meant that language switching needs to be done for the obvious reason (so normal people can use the platform in their language) + also it makes previewing easier for translators so they don't have to tweak browser settings.

3. Previewing PRs before they get merged seems reasonable. Or you can get updates from Weblate once something happens.

A vercel preview of the weblate branch, I think. We don't want translators to have to hang out on github, it's too complicated.

4. I don't understand why some translations isn't better than no translations. Seems like a lot of effort to make sure nobody sees their own mistakes. Naturally a lot of users aren't inconvenienced by this since the usergroup is also bound to be small, and they won't expect wonders.

This was/is discussed by the language leads, I don't have an enlightened opinion on it.

@aapeliv Happy to help review strings. Can you add nb_NO (Norwegian Bokmål) so I can get something more out of doing so?

Please fill in the translation form: https://couchers.org/translation-form. I'll also ping the translation lead.

[alesdvorakcz]

1. Fallbacks in browser settings is different - that one will choose first available language. But what we probably want is to fallback not translated strings from lets say Brazil Portuguese to standard Portuguese (if its already translated in there). And ideally to english when it is not available even in standard Portuguese

2. This one is tricky and maybe needs more discussion. Translation team is afraid we will have many languages in progress and actually not a single one complete. We could motivate translators by saying a language will get live if some threshold is passed (for example 50% of strings are translated)

[comradekingu]

1. I understand.
2. I am on the translation team now, and nb_NO has coverage. You don't motivate scarce resources by capping the labours of their efforts.

I'll do a PR for all the source strings when I find the time to do so :)