use language code or names and not flags
publié leDécrivez votre problème, votre suggestion
Flags are a bad representation of languages: https://www.flagsarenotlanguages.com/blog/why-flags-do-not-represent-language/
I suggest:
- to remove the flags
- to use the ISO639-1 and ISO639-3 language code for the current language (French is FR, English is EN, etc.)
- to keep the language full name when displaying the language list
- to display a category (add your language with a link to https://translate.codeberg.org/projects/cartes)
- add an "announcement" to https://translate.codeberg.org/projects/cartes with a link to the translation guide https://codeberg.org/cartes/web/src/branch/master/TRANSLATION.md
- see weblate's doc: https://docs.weblate.org/en/latest/admin/announcements.html
I guess a lot of this is done in https://codeberg.org/cartes/web/src/branch/master/components/LanguageSwitcher.tsx, but going further goes beyond my skills.
Système d'exploitation
No response
Navigateur
No response
laem
Hi, thanks for your message ! It's already discussed here : https://codeberg.org/cartes/web/issues/1864
In French, so no wonder you didn't find it :)
(We NEEEED Codeberg issue comment translation on click :/)
Résumé : yes, flags are not good representations of languages, but our languages have been coded as per-country : the French version is the version of France, not the version of Québec. It's a hard problem, removing flags and adding locale information like "Français (France)" makes the Switcher less intuitive to the general public.
Lots of work will be needed on this switch though, e.g. adding other flags when we think the language is tailored to other locales, or grouping different locales by main language.
laem
Your comments about Codeberg translate will interest @severo
jibecfed
I looked at your repo, I saw English in the last issues and assumed only English is used. I searched for "flag/flags" ;)
#1864 starts from user interface and moves to locale support I'm part of https://languages-in-floss.eu and Fedora localization, localization and internationalization is my focus of interest, I'll be happy to provide guidance if of some interest.
If you want to adapt content to a specific culture, translation and application's behavior should be splited in multiple ways. I suggest to keep the "locale content adaptation" (point of interest, units, etc.) to be covered in another subject.
Request without explicit language info should fall back to user's preference, if none consider Accept-Language values, otherwise English. I feel like this is the same as described in https://codeberg.org/cartes/web/issues/1863
By the way, you wrote in https://codeberg.org/cartes/web/issues/1864#issue-3931065 that only two letters code are supported, this is really a subject of improvement.
As far as I know, the standard for the web and "Accept-Language" is BCP-47, you can ask weblate to use these codes in project's configuration: https://docs.weblate.org/en/latest/admin/projects.html#component-language-code-style