Start a new pull request in StackBlitz Codeflow.

We use ISO-639-1 library, and the library has a few entries with lower case languages.

Okay then, so it's another issue.

no, browser Intl functions also showing magdar, I'll check using also country, preparing small script...

you can open chrome/firefox dev tools (pressing F12 key), then paste this code on console tab:

new Intl.DisplayNames(
    ['hu'],
    { type: 'language', languageDisplay: 'standard', localeMatcher: 'lookup' },
  ).of('hu')

and

new Intl.DisplayNames(
    ['hu-HU'],
    { type: 'language', languageDisplay: 'standard', localeMatcher: 'lookup' },
  ).of('hu-HU')

Chrome:

Firefox:

https://mastodon.social/settings/preferences/appearance

This is the same in Mastodon UI. I think those language names are written in each language. Although I have little knowledge of Hungarian, I guess the lowercase one ("magdar") is a formal spelling in Hungarian in terms of the language name? Wiktionary also writes "magdar" in Hungarian but "Magdar" is English spelling.

ref.

• English: Magyar - Wiktionary - https://en.wiktionary.org/wiki/Magyar
• Hungarian: magyar - Wiktionary - https://en.wiktionary.org/wiki/magyar

Here some pairs from iso-639-1 and Intl.DisplayNames`:

magyar is a noun, but Magyarország is proper noun in English.
What confused me was that not all items capitalized.

When "magyar" is not a wrong case, I think the confusion is due to inconsistency with the above "Language" section. This capitalized one is hardcoded here:

so we should use the same case as the below ISO 639-1's ones.

@shuuji3 as I mention, we use iso-639-1 library, rn that library and Intl.DisplayNames seems to match, in Language section we're using the i18n entries (i18n.ts module in conf folder).

Maybe we can update i18n.ts module to use same lang names.

Yes, that's my understanding👍🏻 Can I try updating i18n.ts to use the same names?

I'm going to check if we can infer display names in node side (no idea if Intl in node is fine)

I'm checking some spanish "languages" like es-419, ca-valencia, ca-ES, eu-ES and gl-ES:

Firefox (seems to be fine):

Chrome (seems to be fine, some missmatch with FF):

It is a style thing or it is language thing to have the first letter uppercase in lists? As a designer it is more important to have all first letter uppercase. I propose Magyar could be better in every language related list IMHO. And also important to have the same usage in every circumstances. It's only my opinion, I do not want to intervene in Elk development.

@iamdtms it is a problem with the language: for example, week days in Spanish are no proper names (in Spain) and so the names should be in lowercase (with some exceptions), but anyone may want to use first letter in uppercase: monday (en) => lunes (es) => Lunes (es) (ofc, Lunes is wrong)

selector:first-letter { text-transform: uppercase } also an option for proper display with no text replacement?

That css hack is wrong, not all languages using language names as proper names, in Spain spanish is español and not Español (in fact conf/i18n.ts is wrong, we should update lang names there properly).

From Intl and iso-639-1 library, the correct name seems to be magdar and not Magdar (or both are wrong, I have no idea about it)

I understand. Good luck with that multilingual thing.

(screenshot translation): the words used to designate the different languages are common names, which is why they must always be written with a lower case letter: spanish is the most studied language in the world after English.

I'm going to prepare a PR to use Intl/ISO-639-1 language names in config/i18n.ts: this way Language and Translations will match.

@iamdtms with #2817 should be fine, languages and translations in settings language will show the same names (from conf/i18n.ts), we can change the names in conf/i18n.ts if we want

Thank you!