Platform(s), such as mobile, website, API, other: probably all?
Description of need:
May not solve the issue globally, but may resolve the issue for Canada where the algorithm seems confused by Canadian common names.
Feature request details:
This request was inspired by this thread: https://forum.inaturalist.org/t/multiple-languages/75760
Canadian users have repeatedly had an issue with French and English getting muddled. From what I can see, this seems to be solved on the website, but is still an issue on the app. The fact it hasn’t been resolved on the app indicates an underlying issue, and I was informed on the linked thread that it is likely related to how iNat’s algorithms prioritize common names.
I do understand that Canadian French and European French likely have different common terminology. I’m presuming that this is why Canadian French terms are being treated as local common names instead of language-based ones. However, as a result, this is causing Canadian English speakers to get muddled up languages.
–[It would appear to me that the cleanest solution would be making Canadian French a distinct language option. This way, Francophones outside Quebec have a simple option without the risk of it being muddled with European French and Canadian English (idk if that’s happening, but seems plausible based on other factors), and Anglophone Canadians inside and outside of Quebec can get a more consistent user experience.] –
edit see below.
I checked the app’s language settings and it does appear this is already a distinct option. That tells me that cross language locale prioritization is getting mixed up. So, I originally thought this request was going to be for a language addition, but seeing as it’s already there, I’m adjusting the request for an algorithm adjustment. Maybe those common names need to be placed as the Canadian French dictionary terms instead of as local common names?