Opened 15 years ago
Closed 11 years ago
#1033 closed feature-request (WontFix)
Switch from gettext to Babel
Reported by: | s0undt3ch | Owned by: | andar |
---|---|---|---|
Priority: | trivial | Milestone: | Future |
Component: | Unknown | Version: | |
Keywords: | i18n | Cc: |
Description
Would there be interest into switching from gettext to Babel?
- All built in python
- Glade string extraction support(extension)
- Javascript support (for webui).
- Catalog Extract/Complile/Merge/Update plus translated statistics for each or all catalogs, which can be as simple as
python setup.py extract_messages
, etc... - Available at least on debian/ubuntu(I don't run any other distros) as a package.
If there's enough interest, I'd be happy to create the necessary code changes to be reviewed by a developer.
Change History (4)
follow-up: 2 comment:1 by , 15 years ago
comment:2 by , 15 years ago
Replying to andar:
Would the template extract be compatible with gettext? Would we still be able to use launchpad's translation service?
Babel is fully compatible with the gettext tools.
Regarding lauchpad's translation service(never used it), you upload the generated po files into it right? If so, can't see why it would be incompatible.
comment:3 by , 15 years ago
Milestone: | 1.3.0 → Future |
---|---|
Version: | 1.1.9 |
comment:4 by , 11 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
Although might be nice to move to Babel, I have recently made improvements to the translation scripts in develop
so that the webui translations are included so don't think there is any major benefit to changing the current setup.
Would the template extract be compatible with gettext? Would we still be able to use launchpad's translation service?