2008/12/4 Malcolm Tredinnick <[EMAIL PROTECTED]>:
>
>
> On Wed, 2008-12-03 at 12:51 +0100, Elvis Stansvik wrote:
>> Hello django-users, first post to this list :)
>>
>> I often use the i18n support of Django in my projects, and I have a
>> small annoyance/problem that maybe someone can help me with.
>>
>> If I decide to customize e.g. admin/index.html, by copying it over
>> from django to my project, strings in that template such as "My
>> Actions" will now be treated as untranslated by manage.py makemessages
>> -a, even though they are indeed translated in Django's own django.po.
>>
>> This is all logical and all, and I can see why it is so, but it makes
>> my project's django.po unnecessarily cluttered with "untranslated"
>> strings that I in fact don't have translate, since they are translated
>> in Django's own django.po.
>
> There isn't a way to do this. Worth looking at whether there's a simple
> way to do this, although I can see it being slightly controversial: if
> some string is in Django's core, but not translated for language X,
> people are going to complain that they cannot translate it in there PO
> file because it's not included and they're being held hostage by the
> upstream Django translator. Adding yet another option is a possibility,
> although it's way down the list of preferred options, since adding
> options is always sub-optimal.
I can see the problem yes. I can only say that I would personally
_really_ like an option for this.
It think this option could be e.g.:
-m POFILE, --merge=POFILE
Merge the pulled messages with the specified .po file.
Use -m multiple times to specify several files.
I'm not very gettext savvy, but to me it seems this would be a simple
msgmerge invocation. Would it be okay if I file a wish for this? I
might even look into making a patch, but not right now as I'm kind of
busy.
Thanks for your input Malcolm. Anyone else who feels something
strongly about this or have a better idea?
Elvis
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
