Add support for translation backends other than gettext
|Reported by:||Marinho Brandão||Owned by:||nobody|
|Cc:||ethan.jucovy@…, aurelio@…, ojiidotch@…, kitsunde@…, stas@…, rtnpro||Triage Stage:||Accepted|
|Has patch:||yes||Needs documentation:||yes|
|Needs tests:||no||Patch needs improvement:||yes|
Using gettext has been a problem on many projects. It's weird to translate and is limited to (static) potfiles (nothing convince me that Pootle Server and Rosetta are great ideas, actually they are just quick fixes for a bad implemented tool).
So, I'd like to suggest you to make a contrib app to have all i18n functions.
Not only the existing functions but provide backend system for alternative ways to make translations, to replace gettext for database stored message strings, or dynamic/smart translations.
Would be helpful also if the same application has a way to translate database objects, like django-multilingual (1) and polyglot (2) do.
I can work on it if the idea get approved.
Change History (19)
comment:1 Changed 6 years ago by
|Component:||Uncategorized → Internationalization|
|Triage Stage:||Unreviewed → Design decision needed|
comment:7 Changed 5 years ago by
|Triage Stage:||Design decision needed → Accepted|
comment:9 Changed 5 years ago by
|Summary:||Contrib application for i18n functions → Add support for translation backends other than gettext|