in the meantime, you can translate app names like this: http://groups.google.com/group/django-users/msg/ef5a723983e56e96
the whole discussion is here: http://groups.google.com/group/django-users/browse_thread/thread/f8fcbe25e3327c5d/ef5a723983e56e96?#ef5a723983e56e96 it´s over-complicated to translate app-names right now, which is a shame IMO. regards, patrick On Sep 21, 12:04 am, Ramiro Morales <cra...@gmail.com> wrote: > On Sun, Sep 20, 2009 at 4:22 PM, SaiaGo <sai...@gmail.com> wrote: > > > I'm trying to make an Israeli site (which means it should be written > > in Hebrew) using the latest SVN and so far Django made it so easy I > > can't believe it's free. I got a simple magazine app with up and > > running in less then a day, and I barely know Python! > > My only problem so far is application names in admin pages. I can't > > seem to find a way to translate application names. > > > As far as I understand from the docs app names are chosen based on the > > directory name they reside in. so mysite/magazine should be > > "Magazine", which is what admin pages display. > > I tried making a .po file and translating "Magazine" (assuming my app > > is in "mysite/magazine") like so: > > msgid "Magazine" > > msgstr "מגזין" > > But this approach isn't working. > > > Is there a way to explicitly set an app name so I could set it to > > ugettext("Magazine") or some kind of special msgid I have to use to > > translate app names, or is this functionality not implemented yet?(In > > which case I would happily implement it myself) > > Corrently in Django we have both problems related to this: > > First, the long shot problem: The one about providing and > documenting an official way to app author to specify or mark > the app name so it can be somethingg different to the module > name, to allow translating it in the admin app (and other places?), etc. > This is a missing feature that need design, discussion and > implementation. > > Second, the fact that even when using the module name > as the app name in the admin as we currently do, what you have > done (i.e. providing a translation for that literal it in your .po catalogs > in the hope of getting it translated) doesn't work. This is a bug that has > been present in Django code for more than three years. This bug has > been reported as ticket [1]10436 in our bug tracking system, and it > has a patch attached to it. You can try it if you need this functionality > and know how to work with patches (and please report back > your experiences). > > At least one core developer thinks all this is something worth fixing in > one swoop and the second problem isn´t worth fixing alone. I'm keeping > the above mentioned ticket (and patch) up to date in the hope it is > fixed ASAP. > > Regards, > > -- > Ramiro Moraleshttp://rmorales.net > > 1.http://code.djangoproject.com/ticket/10436 --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
