Platform: web (with implications on the apps as well)
URLs (aka web addresses) of any relevant observations or pages:
Content and Display Settings page
Description of problem:
The “Select a lexicon” dropdown contains both “Hungarian” and “magyar” options. Note that “magyar” literally means “Hungarian” in the Hungarian language.
Selecting the “magyar” option doesn’t trigger the Hungarian (=magyar) taxon names to be shown, only selecting the “Hungarian” option does (at least for the few taxons I tested, e.g. https://www.inaturalist.org/taxa/199266-Dysgonia-algira)
This could be confusing to users, as selecting “magyar” doesn’t result in the intended effect. Wondering what’s the source of the “magyar” lexicon and why does it appear together with the “Hungarian” lexicon in the drop-down?
NB: If the web UI is set to Hungarian and when adding a new taxon name, the default lexicon is “Magyar”, and there is no “Hungarian” option. If you set the language to English, the same lexicon drop down on this page contains both “Magyar” and “Hungarian”.
Lexicons should be English. There are 209 entries for lexicon magyar.
Lexicon magyar has language und so the are not connected with a language. The normal hungarian common names have a connection with the locale/language hu.
The base name of the lexicon should be in English. Other names for the lexicon, including the endonym (what speakers of the language call the language) should be entered as translations using Crowdin.
For example, Hungarian is translated to Ungarisch when the site is run in German, and to magyar when the site is run in Hungarian.
Yes, but some lexicons are not languages. The lexicon magyar does not have a locale, but the lexicon Hungarian has a locale hu. You can choose the locale at the right bottom of the iNaturalist page.
My point is that there should not be a lexicon called “magyar”. There should only be a lexicon that is called “Hungarian” when the site is run in English, and that is called “magyar” when the site is run in Hungarian.
