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

Question on tooling #226

Closed
TheTFo opened this issue Jan 27, 2017 · 1 comment
Closed

Question on tooling #226

TheTFo opened this issue Jan 27, 2017 · 1 comment

Comments

@TheTFo
Copy link

TheTFo commented Jan 27, 2017

Can you recommend a tool and configuration for using react-18next with a translation key extractor? I'm unsure of the best way.

Thanks

@jamuhl
Copy link
Member

jamuhl commented Jan 27, 2017

There is:
https://github.com/i18next/i18next-parser
https://github.com/i18next/i18next-scanner

both are active projects...so might be a matter of taste - best ask there if having a concrete question regarding the usage - as i personally did never use them. Sorry.

An other option, which also will support the future development of react-i18next and i18next is using http://locize.com our localization as a service tier. This is also what we use in our personal projects. To get a picture of how it simplifies localization i strongly recommend reading: http://locize.com/2016-11-16-localization-fun/

@jamuhl jamuhl closed this as completed Feb 13, 2017
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