id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
14974	Add support for translation backends other than gettext	Marinho Brandão	nobody	"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.

 * (1) http://code.google.com/p/django-multilingual/
 * (2) http://reddes.bvsalud.org/projects/clinical-trials/browser/trunk/opentrials/polyglot"	New feature	new	Internationalization	dev	Normal			ethan.jucovy@… aurelio@… ojiidotch@… kitsunde@… stas@… rtnpro Andi Albrecht Ülgen Sarıkavak	Accepted	1	1	0	1	0	0