views:

67

answers:

2

Hi -

I'm trying to figure out the best way to translate actual database values (strings, not date formats or anything complicated) when i18n-ing my application. The most logical thing I could come up with is either hold a column for every language ('description_en', 'description_de', 'description_fr', etc) or have a different db for every language (schema_en, schema_fr, schema_de, ...). Are these the best options, or is there something else I'm missing? thanks.

+2  A: 

You could take a look at the following thread which seems to be the same question you're asking here.

I wouldn't mind hearing the solution you eventually will be using as sometime in the future I might have the same question:)

extraneon
+1  A: 

I was reading up on my django extensions, and found the django-modeltranslation plugin. It seems to do exactly what you want it to do. If not, leave a comment and I'll delete this answer :)

extraneon
looks good at first glance, I'll have to play with it a bit - thanks!
sa125