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
Hey @JosefJezek, our localization mechanism generates a new binary per language. This works by importing a specific binary based on a specific language (you shouldn't import all languages at the same time). You should be able to build your own language change mechanism based on that, for example, you could have the language in the url path and based on the path always import the specific localized binary.
Even if we support dynamic languages change, it is unlikely we will bundle all the translations into one binary (there are a lot of languages that we support). A server round trip will still likely be required.
Activity
bojeil-google commentedon Dec 8, 2020
Hey @JosefJezek, our localization mechanism generates a new binary per language. This works by importing a specific binary based on a specific language (you shouldn't import all languages at the same time). You should be able to build your own language change mechanism based on that, for example, you could have the language in the url path and based on the path always import the specific localized binary.
Even if we support dynamic languages change, it is unlikely we will bundle all the translations into one binary (there are a lot of languages that we support). A server round trip will still likely be required.
JosefJezek commentedon Dec 8, 2020
Could you create a base module + small modules per language?
landsman commentedon Jul 27, 2021
Exactly, this can be dynamically loaded after the user selects the language.
Good inspiration: https://lingui.js.org/guides/dynamic-loading-catalogs.html#final-i18n-loader-helper
landsman commentedon Jul 27, 2021
Okay, now I realized how this is made 🥵 :
firebase/firebaseui-web-react#21 (comment)
landsman commentedon Dec 7, 2021
Related with #662.