On Fri, Mar 6, 2009 at 11:21 PM, Malcolm Tredinnick
wrote:
>
> On Fri, 2009-03-06 at 07:01 -0800, patrickk wrote:
>> so, now here´s a little tutorial for translating app-names throughout
>> the admin-interface:
>
> Nice summary. :-)
>
>> 3. change app-names in index.html /// on line 18 replace {%
On Sat, 2009-03-07 at 12:21 +1100, Malcolm Tredinnick wrote:
[...]
> All of those are bugs (the same bug: not marking app name for
> translation). If you'd like to open a ticket and drop in a patch, it's
> an more-or-less obviously correct set of changes to make.
>
> Put it in the "internationali
On Fri, 2009-03-06 at 07:01 -0800, patrickk wrote:
> so, now here´s a little tutorial for translating app-names throughout
> the admin-interface:
Nice summary. :-)
> 3. change app-names in index.html /// on line 18 replace {% blocktrans
> with app.name as name %}{{ name }}{% endblocktrans %} wit
so, now here´s a little tutorial for translating app-names throughout
the admin-interface:
1. define the app-names: I´m currently using the __init__-file of my
blog-application. it looks like this:
from django.utils.translation import ugettext_lazy as _
_(u'auth')
_(u'configuration')
_(u'commen
you´re talking about the models name, not the applications name ...
@nadya: with changing index.html the way you did it works for me as
well.
for changing the breadcrumbs (which obviously is a "must" if you
change the app-names) you have to change change_list.html and
change_form.html
replace {{
i dont understand..
do u wanna mean your app name?
if u wanna tell about your app name in admin panel
i think u can use
*USE_I18N = True
in settings.py*
and
* class Meta:
verbose_name_plural = "Your App Name"
in models.py*
try it and write me answer please
2009/3/4 patrickk
>
I put my translations in the django.po file and also changed a little
bit the admin's index.html template.
Replaced this:
{% blocktrans with app.name as name %}{{ name
}}{%
endblocktrans %}
I put my translations in the django.po file and also changed a little
bit the admin's index.html template.
Replaced this:
{% blocktrans with app.name as name %}{{ name
}}{%
endblocktrans %}
well, I tried some things within the last couple of hours (like
changing upper/lowercase), but it still doesn´t work.
although automatic extraction of app-names would be perfect,
translating the names manually is totally fine for me (if it works).
it just want to get rid of that language-mix (eve
On Wed, 2009-03-04 at 23:30 -0800, patrickk wrote:
> great - a gleam of hope ... but what do you mean with "put each of
> your app names into a file ..."? what file? where?
Any file. It doesn't matter. Some file that "makemessages" will pick up
and read, so best make it a .py file. It could be an
just tried to write the app-names to my applications __init__-file.
the po-file is generated fine, but the translation still doesn´t work.
On Mar 5, 8:30 am, patrickk wrote:
> great - a gleam of hope ... but what do you mean with "put each of
> your app names into a file ..."? what file? where?
great - a gleam of hope ... but what do you mean with "put each of
your app names into a file ..."? what file? where? can I use
__init__.py within my app and just put the app-names there and mark
them as to translate?
I already tried to translate the app-names by using a translation-file
(django.
On Wed, 2009-03-04 at 09:39 -0800, patrickk wrote:
> so far, it doesn´t seem possible to translate the app-names within the
> admin-interface, which results in a strange index-site with mixed
> languages.
>
> any updates on this issue? any ideas?
If you put each of your app names into a file tha
so far, it doesn´t seem possible to translate the app-names within the
admin-interface, which results in a strange index-site with mixed
languages.
any updates on this issue? any ideas?
thanks,
patrick
--~--~-~--~~~---~--~~
You received this message because you
14 matches
Mail list logo
