Never heard about google either? CLDR can hardly be a common acronym.
Django has a complete implementation of internationalization. It knows
how to extract translations from python files, from HTML files, from
JS files and compile them into catalogues.
You want to have django magically extract ad
I solved it by creating a new python file with:
# -*- coding: utf-8 -*-
from django.utils.translation import ugettext as _
translation_strings = [
_(u'string'),
_(u'another string'),
...
]
So easy :)
Martin
On Thu, 02 Sep 2010 13:33:36 +0200, Martin Tiršel
wrote:
Hello,
I
Never heard about CLDR before, so your answer doesn't give much sense to
me :( Django doesn't have complete implementation of internationalization?
makemessages is then useless if I can not add custom strings without
overwriting them by Django. Or is there really something I don't know
abou
On Thu, Sep 2, 2010 at 2:15 PM, Martin Tiršel wrote:
> I tried to create second .po file with manual translations, but had no luck
> either :( `compilemessages` creates the second .mo file, but doesn't use it
> in the app. Only django.mo is used, but all my translations in django.po
> file are com
I tried to create second .po file with manual translations, but had no
luck either :( `compilemessages` creates the second .mo file, but doesn't
use it in the app. Only django.mo is used, but all my translations in
django.po file are commented out after I run `makemessages`.
In the document
Hello,
I can not find in Django documentation a word about translating variables
or strings with variables. I have:
...
{% trans question_category %}
...
django-admin.py makemessages creates .po but without a mention about this
template line ({% trans "some text" %} is ok). It is clear, th
6 matches
Mail list logo
