Hi Omar,
Your message saved my day, I didn't think it would be because of such
a simple reason that make-messages.py omits my template files. I
actually just opened make-messages.py and changed '.html' to '.htm' in
two places, and that solved it. I just have to watch out the next time
I do an update, I guess.
Cheers,
Ulas
On Apr 30, 2:48 pm, omat <[EMAIL PROTECTED]> wrote:
> And ...
>
> If you would like to add a few words to the translation, like menu
> items, etc. without going into views and database, donotput them
> into the .po file directly. They will be commented out each time you
> run make-messages. Also there can be duplications that will result in
> errors.
>
> More maintainable (though hacky) way is to create a template file such
> as translation.html and put the strings to betranslatedinto that
> file such as:
>
> {% load i18n %}
> {% trans "Home page" %}
> {% trans "Continue" %}
>
> On Apr 30, 3:14 pm, omat <[EMAIL PROTECTED]> wrote:
>
> > Hi,
>
> > I was wondering why my emailtemplateswerenotgettingtranslated. It
> > took me hours before I check the bin/make-messages.py and figure out
> > that only some files, depending on their extensions, aretranslated.
>
> > I thought make-messageswereworking in more django-aware manner and
> > inspects the projects (settings, models, views, etc) to find related
> > files and extract text to betranslated.
>
> > The way it actually is is more simple and straight-forward, so it is
> > quite ok. But dependency on file extension (especially fortemplates)
> > was something I wouldn't expect.
>
> > Regards,
> > omat
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
