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
The mechanism for populating the State/Province dropdown after a user selects a country does not respect the user's selected language, as it does not have any notion of i18n or l10n. This hasn't been an issue in practice yet, as state/province names in Spain, Mexico, and Japan can be statically translated and displayed in Spanish and Japanese respectively.
However, this model will break down if TMI ever operates in a multilingual country (e.g. Canada), or if we want to accommodate users residing in a country who aren't fluent in the dominant language (e.g. Spanish-speaking Americans).
This is relatively low-priority in relation to other development items, but a future solution would ideally allow flexible multilingual displays for any given country without forcing every state in every country to be translated into every language the TMI platform is available in.
The text was updated successfully, but these errors were encountered:
The mechanism for populating the State/Province dropdown after a user selects a country does not respect the user's selected language, as it does not have any notion of i18n or l10n. This hasn't been an issue in practice yet, as state/province names in Spain, Mexico, and Japan can be statically translated and displayed in Spanish and Japanese respectively.
However, this model will break down if TMI ever operates in a multilingual country (e.g. Canada), or if we want to accommodate users residing in a country who aren't fluent in the dominant language (e.g. Spanish-speaking Americans).
This is relatively low-priority in relation to other development items, but a future solution would ideally allow flexible multilingual displays for any given country without forcing every state in every country to be translated into every language the TMI platform is available in.
The text was updated successfully, but these errors were encountered: