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

Define a convention for i18n of Python applications #29

Open
benoit74 opened this issue Feb 19, 2024 · 1 comment
Open

Define a convention for i18n of Python applications #29

benoit74 opened this issue Feb 19, 2024 · 1 comment
Assignees

Comments

@benoit74
Copy link
Contributor

  • What is the conventional library for i18n of our Python applicatins?
  • Is it possible / desirable to have the same solution (or at least a share core) for Vue.JS codebases? (TbD as well, see Define a convention for i18n of Vue.JS applications #28)
  • What is the conventional way of using the library? (default settings, file names and locations, ...)

Requirements:

  • TranslateWiki must be able to process this format (very light requirement given the fact that TranslateWiki is capable to process almost any file format)
  • Right To Left, Pluralization, Placeholders, ... (quite obvious as well)
@benoit74
Copy link
Contributor Author

First implementation / PoC might be done with openzim/gutenberg#56

TbC because while it is a very important project where i18n is needed, it is also the one with the most custom existing codebase around i18n (almost no library has been used AFAIK, everything is custom-made so effort to integrate with TranslateWiki / adopt a conventional library has to assessed)

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

No branches or pull requests

1 participant