Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Localization Support for Both Simplified and Traditional Chinese #69

Open
josephk96 opened this issue Dec 6, 2023 · 2 comments
Open

Comments

@josephk96
Copy link

Hello,

We have encountered an issue with the localization feature in FusionAuth themes. Despite configuring the localized_messages map to include both Simplified Chinese (zh_CN) and Traditional Chinese (zh_TW), the language dropdown in our forms is only displaying one option for Chinese.

Here's the snippet from our _theme.tf file (we are using the FusionAuth Terraform Provider:

localized_messages = {
  "zh_CN" : file("${path.module}/../../themes/tpl/i18n/messages_zh_CN.properties"),
  "zh_TW" : file("${path.module}/../../themes/tpl/i18n/messages_zh_CN.properties")
  "ko" : file("${path.module}/../../themes/tpl/i18n/messages_zh_CN.properties"),
}

Please disregard the fact that all the languages are pointing to the same .properties file, we implemented this only for testing purposes to ensure that locales/languages that have not been added to this GH repository can be added manually.

As seen in the attached screenshot, only one Chinese option appears alongside English and Korean. We expect to see both Simplified and Traditional Chinese as separate options.

Could you please guide us on how to properly set up the localization for both Simplified and Traditional Chinese?

Thank you!

image

@josephk96
Copy link
Author

We also tested by going to the FA dashboard and manually adding locales without the use of Terraform, and the result was the same - when more than one Chinese variation has been added, only Chinese will be shown in the Languages dropdown in the form(s).

CleanShot 2023-12-06 at 18 23 18@2x

CleanShot 2023-12-06 at 18 23 39@2x

@mooreds
Copy link
Contributor

mooreds commented Dec 6, 2023

Thanks for filing! We'll be tracking this issue under FusionAuth/fusionauth-issues#2568 .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants