Comments on: Dynamic Translation Apps for Django

By: gonz

gonz — Mon, 18 Jan 2010 18:01:03 +0000

Nice post muhuk.

Just wanted to share with you that django-pluggable-model-i18n has become very active this month (after a 7 month hiatus) and, although we're still in a pre-alpha experimental stage, alpha is getting closer so we're pretty excited about it and we hope to have a 0.1 release soon.

By: Artmama

Artmama — Mon, 11 Jan 2010 22:07:39 +0000

I love the way your blog looks!! (Although django apps are not my thing).

By: Atamert Ölçgen

Atamert Ölçgen — Sun, 10 Jan 2010 08:39:08 +0000

I would like to apologize for the delay in approval of comments. I couldn’t connect to Internet for the last two days. And I will have limited connectivity for the next few.

By: pawnhearts

pawnhearts — Fri, 08 Jan 2010 10:01:12 +0000

one little thing – i only add columns, default language column is not modified and not renamed, only additional language columns have underscore postfix(e.g. _es, _de)

By: pawnhearts

pawnhearts — Fri, 08 Jan 2010 09:58:01 +0000

if i’ve seen transmeta before writing multilang, i would’t write it. idea is basically the same, and they do the same thing in a very similar way. (main difference – i used class decorator, transmeta’s author used metaclass) i think our approach is the only real solution, because it does’t need heavy queries with joins, etc. we’ve used it to add another language support for models in existing big and serious application…

By: Metin Amiroff

Metin Amiroff — Fri, 08 Jan 2010 09:43:39 +0000

Nice writeup! Multilingual sites are getting more and more popular nowadays. Looking forward to see your implementation.

By: Jeff Balogh

Jeff Balogh — Fri, 08 Jan 2010 05:43:54 +0000

addons.mozilla.org has a pretty janky way of doing this: all translations are stored in one table, and you look up an (id, locale) pair to get a string. I want to change it eventually, but right now we’re stuck maintaining compatibility with the legacy site.

My take on this is in http://github.com/jbalogh/zamboni/tree/master/apps/translations/ (fields.py and models.py are interesting), with docs at http://github.com/jbalogh/zamboni/tree/master/apps/translations/. But the docs are directed more to the people who already know how the system works.

By: Simon

Simon — Thu, 07 Jan 2010 20:38:39 +0000

An alternative approach — http://bitbucket.org/drmeers/django-dbgettext/wiki — “Extracts translatable strings from Django models for handling via Django’s standard i18n mechanisms.”

By: Atamert Ölçgen

Atamert Ölçgen — Thu, 07 Jan 2010 19:29:30 +0000

@Jef, @pawnhearts: I have just took a quick look at your apps. They both look interesting, they both differ from the 6 above in unique ways. I would love to take a closer look and perhaps write a review later.

Thanks for sharing.

By: pawnhearts

pawnhearts — Thu, 07 Jan 2010 19:03:00 +0000

there’s also my http://tabed.org/software/django-multilang/ but it very similar to transmeta