Re: Split up .po files for Internationalization

Hi Tom,

Thanks for rectifying my answer.

On 6/24/2011 5:01 PM, Tom Evans wrote:
> On Fri, Jun 24, 2011 at 3:45 PM, Gelonida<gelonida@gmail.com> wrote:
>> Perhaps I'm wrong, but I thought it's enough to just create a
>> locale/<lang>/LC_MESSAGES/django.po file
>> in your project tree
>>
>> and then call manage.py makemessages -s -l<lang>
>>
>
> You shouldn't be manually creating these files at all, django provides
> tools that do that for you (and spell LC_MESSAGES correctly etc). You
> simply run django-admin.py makemessages -l<lang> from the top level
> of each app that is to be translated, and it correctly populates
> ./locale/<lang>/LC_MESSAGES/django.po with the translations that have
> been marked up in that apps templates and source code.

Fully agree. Just started working with Django. I used makemessages as
the doc (and you) suggested.

I just forgot about it when writing this post.
>
> I'd suggest a thorough re-read of the documentation if you ever find
> yourself manually creating pofiles.
>
> Cheers
>
> Tom
>

--
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+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.