Please fill out the following sections to the best of your ability, it will help us investigate bugs if we have this information at the outset. Screenshots are especially helpful, so please provide those if you can.
Platform (Android, iOS, Website): Website
App version number, if a mobile app issue (shown under Settings or About):
Browser, if a website issue (Firefox, Chrome, etc) : Firefox
The place name preference is mostly for situations like in Latin America, where the same species may have a different Spanish common name in different countries/regions. So if you choose a place for your name preference, it uses the default common name attached to that place, regardless of your account’s locale. Since there’s only one name for Lycogala epidendrum that’s attached to Canada, that’s the one you see.
I don’t know whether this is a connected problem. I am mentioning it here in case it is. There is another French prioritization that puzzles me (I also live in Canada, if that matters). My default language is English but for some species the autocomplete suggestions give me French names in parentheses behind the scientific name, e.g. for Astragalus missouriensis:
This happens for example when I try to add an identification to an observation or when I enter a name in the Identify menu (see example above). I had Canadian names prioritized but the French name still pops up after I removed the place priority. [This happens on the website, and Firefox is my browser]. This is the case both on inaturalist.org and inaturalist.ca.
What puzzles me even more is where the French name is given: in parentheses behind the scientific name. The English name also shows as normal in the field for common names. My question is: why does the field for scientific names display common names at all? In my opinion, the field for scientific names should be reserved for them and never show common names, regardless of the language. There are not a lot of species for which this is the case but Astragalus missouriensis is not the only one. Astragalus spatulatus is another example. And there are others that I don’t recall anymore.
My preference would be not to have French names displayed but I don’t know how to turn it off.
So, could I add Wolf’s Milk Slime Mold as a common name to make it so that each language has a common name?
A few others like Crown Tipped Coral fungus also switched to french recently.
(edit: looks like Lycogala epidendrum has an english common name again, nevermind)
This has been happening with me as well. All observations for River Jewelwing (Calopteryx aequabilis) and American Pussy Willow (Salix discolor) now show up with the French names only, even when I am browsing other areas. My default language is set to English. This is not yet happening with other species, and recent curation history shows that recent name changes have been applied to those two species. So whomever is doing this, please stop. This is extremely frustrating for me when browsing observations. I do not speak French, nor do I desire to.
So the issue seems to be folks setting the curation of taxon with a regional over ride. In all the examples I noticed it was a specific curator that set the region to canada instead of quebec. The immediate solution will be to put in curation request for each one we encounter, though imo this should be a user preference, not part of curation, or maybe just a user preference to turn this off.
Hello everybody! Most of the instances that were shared in this thread seems to be my fault! I just wanted to apologize for the inconvenience. I have been adding a bunch of common names in French for many fungi that didn’t have any yet; some had one, but used the European one that isn’t used here in Canada.
It’s set to Quebec, CA. But I get the English common names for certain species (e.g. Omphalotus Illudens, Mycena leaiana), even though I created a regional (Quebec, CA) French common name for those. I noticed that an English regional (Canada) common name was created recently for both of those examples. I have this problem with many other taxons
That’s your place names preference, which is different from locale (it’s confusing, sorry). Locale is a differetn setting, choices are listed as languages. We use “locale” because choosing a langauge also determines how dates are displayed, etc. So which language are you using iNat in?
I think adding both a regional english and a regional french common name just for Quebec should cause the behavior to be as expected (correct language chosen in Quebec, global english name chosen elsewhere), is that right?
Well, when I first looked at it, the one from the original post had a regional common name for all of Canada in English and one for just Quebec in French. So I was wondering if the different regional targets was part of the issue?
This is a global bug.
Someone just set “djíngu” as the Kwe name for southern Africa, and now no matter what language you use as default, the name “Marabou Stork” which is the global default, is now overwritten for all users using southern African vernacular names.
The displayed vernacular should be in the language specified, and not be overwritten by defaults in other languages.
Otherwise I am going to have to flag hundreds of names - which will have to have the English names modified as the default for southern Africa - as more and more regional African language names are added to the names.
But this is an old problem and was reported years ago (and still not fixed).