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

Request for general guidance on @fundamental-ngx/i18n #12875

Open
amakarenko-sap opened this issue Dec 23, 2024 · 0 comments
Open

Request for general guidance on @fundamental-ngx/i18n #12875

amakarenko-sap opened this issue Dec 23, 2024 · 0 comments

Comments

@amakarenko-sap
Copy link

amakarenko-sap commented Dec 23, 2024

Hello,

Our team is trying to figure out if it's safe to use the @fundamental-ngx/i18n to support multi-language and multi-locale in our Angular application. We actively use @fundamental-ngx/core and @fundamental-ngx/cdk in our project, so there is an idea to also use @fundamental-ngx/i18n to translate not only fundamental components but the entire application.

There is some public API available to use like fdTranslate pipe or TranslationResolver. As I see under the hood it's built on top of https://formatjs.github.io/docs/intl-messageformat/ library, so it fully supports ICU Message syntax. It also supports real-time translations, which is good. I did some experiments and it seems to me that the @fundamental-ngx/i18n might be a good fit for our needs.

So I have 2 questions just to be on the safe side:

  1. Is it safe to build a translation mechanism on top of the @fundamental-ngx/i18n library? Is it stable enough and no breaking changes expected?
  2. Can we use ICU Message syntax and assume that the @fundamental-ngx/i18n will continue supporting it in the future?

Thanks

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

1 participant