-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Globalization and localization #493
Comments
This issue has been marked stale because it has not seen activity within six months. If you believe this to be in error, please contact one of the code owners, listed in the |
This issue has been marked stale because it has not seen activity within six months. If you believe this to be in error, please contact one of the code owners, listed in the |
This issue has been closed due to continued inactivity. Thank you for your understanding. If you believe this to be in error, please contact one of the code owners, listed in the |
We should start globalizing all string messages used in loopback-next to allow localization. IMO, we should be extracting strings from the original TypeScript sources, not from the transpiled result.
Things to investigate - must have
Extract strings from TypeScript sources strongloop/strong-globalize#113: how to extract strings from TypeScript
Add TypeScript bindings strongloop/strong-globalize#114: type definitions for strong-globalize API
how to setup strong-globalize in lerna monorepo - we need to run strong-globalize locally in each package
Should have
The text was updated successfully, but these errors were encountered: