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

Look into using standard tooling for translations #8

Open
goodmami opened this issue Apr 24, 2019 · 0 comments
Open

Look into using standard tooling for translations #8

goodmami opened this issue Apr 24, 2019 · 0 comments
Labels
enhancement New feature or request

Comments

@goodmami
Copy link
Member

The MultiString class for managing translations of the documentation was intended for use with a templating system like Jinja2. This works fine for now (although we haven't made much use of it yet), but we may want to eventually consider a more standard tool for this, such as the gettext module in the standard library. Maybe we could wrap gettext's class-based API with something to maintain a similar usage to MultiString.

@goodmami goodmami added the enhancement New feature or request label Apr 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant