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] embedded internationalization (i18n) #12

Open
puzrin opened this issue Mar 26, 2019 · 0 comments
Open

[request] embedded internationalization (i18n) #12

puzrin opened this issue Mar 26, 2019 · 0 comments

Comments

@puzrin
Copy link

puzrin commented Mar 26, 2019

I'm hot sure how to post request right, so posting to issue, according to template. Correct me, if i do something wrong.


No i18n (gettext), suitable for embedded use

Existing i18n crates have heavy extra dependency, ok for desktop, but not suitable for restricted embedded requirements.

Also, gettext prefer use PO-files, but yaml (like in ruby's i18n) is more human-friendly.

Success Criteria

Create a set of tool + runtime to translate texts the same way as gettext.

  • Phrase scanner - creates YAML files, to be translated by humans,
    • optionally, for import/export to web translation services
  • "Renamer" - if source phrase changed and you need to update key in all translations
  • Compiler - take YAML files and build rust code

Work in progress

  • lv_i18n - i did tool with node.js for C. This may look strange, but is has verified workflow, data structures and API features set. Now it's possible to skip top level architecture design and just implement similar thing in Rust.
@ryankurte ryankurte changed the title [request] embedded i18n [request] embedded internationalization (i18n) Mar 26, 2019
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