On 1/10/07, johnny <[EMAIL PROTECTED]> wrote: > I have read the django book at djangobook.com. What I wanted to know > now is, how the database content related to the i18n handled. Do I > have to create a separate tables for each language. I have looked at > symfony-project.com i18n > http://www.symfony-project.com/book/trunk/i18n, a php framework, it > manages that part nicely. "For each table that contains some i18n data, > it is recommended to split the table in two parts: one table with no > i18n column, and the other one with only the i18n columns."
I'll be adding a section to that chapter about how strategies for internationalizing data. Adrian -- Adrian Holovaty holovaty.com | djangoproject.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
