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
All manifest strings can be able to use localized strings for internationalization.
They should support at lease two types of definitions:
Direct one string for one language only
"name": "Web App" // English only
or
"name": "网站应用" // Chinese Only
Multiple languages support
lang: "en", // fallback language if browser meets none locale strings listed
"name": {
"en": "Web App", // fallback for all en-* browsers or for general en-* users
"en-US": "Web App", // specific string for localized en
"zh": "网站应用”, // fallback for all zh-* browsers or for general zh-* users
"zh-CN": "网站应用”, // specific string for localized zh
...
The text was updated successfully, but these errors were encountered:
@calidion Thank you for reporting this issue. We are currently addressing this scenario as part of PR #1101. Feel free to subscribe to this PR and join the discussion there. I will close this issue as a duplicate of #676.
All manifest strings can be able to use localized strings for internationalization.
They should support at lease two types of definitions:
or
The text was updated successfully, but these errors were encountered: