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
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When a language name is the same in both English and that language, logic treats this as if the translated form is not available for that locale, and falls back to the Intl.DisplayName JavaScript library. In certain cases this is undesired, such as with Tagalog, whose name is the same in English and Taglog, falls back to the JS library and results in "Filipino" (but we already have Filipino specifically.
Adds a boolean forceLocalName to the I18nLocale type (adding intellisense documentation for future clarity) to to override this and use the locale name instead
Adds "language-tl": "Tagalog", to both en/common.json and tl/common.json files
Description
When a language name is the same in both English and that language, logic treats this as if the translated form is not available for that locale, and falls back to the
Intl.DisplayName
JavaScript library. In certain cases this is undesired, such as with Tagalog, whose name is the same in English and Taglog, falls back to the JS library and results in "Filipino" (but we already have Filipino specifically.forceLocalName
to theI18nLocale
type (adding intellisense documentation for future clarity) to to override this and use the locale name instead"language-tl": "Tagalog",
to both en/common.json and tl/common.json filesRelated Issue