On 26 November 2010 18:36, tonnzor <[email protected]> wrote: > Dear Django developers! > > Please, look at the table auth_persissions - it has following > structure (and data - trimmed): > Here's a small piece of data: > {{{ > +-----+----------------------------------------------- > +-----------------+----------------------------------------+ > | id | name | > content_type_id | codename | > +-----+----------------------------------------------- > +-----------------+----------------------------------------+ > | 1 | Can add permission | > 1 | add_permission | > | 2 | Can change permission | > 1 | change_permission | > | 3 | Can delete permission | > 1 | delete_permission | > }}} > > As you see - codename is in English and may be - and it is done - > easily parsed - that should stay English for sure. > > "name" is human-readable name that is not used for parsing and SHOULD > be translated into the user language. > > See more rationale on http://code.djangoproject.com/ticket/13861
IMHO, the list of duplicates give a pretty good overview of how this should (and how it shouldn't) be solved. Inserting translated content into the database doesn't solve anything, because different users can have different language settings (if you don't care about users with different languages this is already doable). Thus, a good solution would be some kind of support for retrieving multilingual content from the database. This doesn't necessarily mean storing translations in the database, but you need some kind of API to retrieve the translated name from the model. My 2 cents. -- Łukasz Rekucki -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
