You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a string is untranslated in the user's preferred locale, iD currently falls back only to English. However, modern browsers let users specify multiple ordered language preferences. iD should attempt to fallback to one or more of these before English.
I did this! iD will now attempt to use all the user's specified languages before defaulting to English. In the below example, the set locale is Greek, but untranslated terms fallback to the user's next language, German. Since I did #7994, and German currently has 100% coverage, the English locale is never loaded at all 💪
In addition, iD will now fallback to generic locales from regional locales when possible, e.g. pt-BR to pt.
Include all preferred and fallback langauges in coreLocalizer.localeCodes even if higher-priority ones have 100% string coverage
Fallback to the user's preferred languages instead of directly to English when querying OSM wikibase documentation and Wikidata (re: #7996)
Add `lang` attribute to tag documentation text loaded from OSM wikibase or Wikidata (re: #7963)
If a string is untranslated in the user's preferred locale, iD currently falls back only to English. However, modern browsers let users specify multiple ordered language preferences. iD should attempt to fallback to one or more of these before English.
Re: #7713
The text was updated successfully, but these errors were encountered: