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

[i18n] how to best support a library author providing translations for their library #36757

Open
xiaoxiangmoe opened this issue Apr 22, 2020 · 3 comments

Comments

@xiaoxiangmoe
Copy link

@xiaoxiangmoe xiaoxiangmoe commented Apr 22, 2020

We should discuss how to best support a library author providing translations for their library.

@petebacondarwin
Copy link
Member

@petebacondarwin petebacondarwin commented Apr 22, 2020

I am working on a PR that would support merging multiple translation files when translating an application. So if a library author provided a set of translation files it would be possible to combine them with the application translations.

This would then need to be integrated into the Angular CLI.

Further, we should look into how best to make this seamless. For instance agreeing on a file naming convention (or perhaps a property in package.json) that told the CLI where to look for such files.

@petebacondarwin
Copy link
Member

@petebacondarwin petebacondarwin commented Apr 22, 2020

I also have a PR in the works for doing $localize based i18n message extraction from distributable files. We need to ensure that we can avoid extracting messages that came from libraries and were bundled into the main.js for example.

@xiaoxiangmoe
Copy link
Author

@xiaoxiangmoe xiaoxiangmoe commented Apr 23, 2020

Can we use merging multiple translation files in angular 10?
I am currently using loadTranslations to solve the problem of multiple translation files.


By the way, is the dynamic switching of languages not supported by ivy?

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

Successfully merging a pull request may close this issue.

None yet
4 participants
You can’t perform that action at this time.