On 2-11-2005, at 19:24, hugo wrote:
Actually I don't know any backward-incompatible changes, at least none
I am aware of. I think it should be possible to just run your project
after switching to the i18n branch without any _required_ changes.
When i18n branch is created I switched without any trouble, even my
custom (and now dead ;) ) database driven i18n code worked.
<title>{{ _('Title') }}</title>
Again, this is needed to mark the part that needs to be translated. If
I don't mark that part, but just use HTML, I would need the string
puller to know about HTML. But what if the user writes XHTML
templates?
Or when this is a YAML template? Or a simple CSV format?
And don't forget translating JavaScript files in admin. Probably they
can be feed trough the django template engine before sending them to
the user so they can be translated also (I have done similar thing
for some of my css files).
The translators will provide the forms that are needed by their
language and will provide a tag in the .po file that tells the system
to do the different pluralization. And if you think that's a rather
weird case, have a look at the "sr" language file in
conf/locale/sr/LC_MESSAGES/django.po - it's using pluralization. It
provides the "Plural-Forms" header for that purpose that defines the
rules when to pull what plural form. I don't even know wether the
python gettext library supports that fully, as it looks rather complex
Some examples at http://www.gnu.org/software/gettext/manual/
html_chapter/gettext_10.html#SEC150.
And yes, python gettext fully supports plural expressions.
---
Nebojša Đorđević - nesh
Studio Quattro - Niš - SCG
http://djnesh.blogspot.com/ | http://djnesh-django.blogspot.com/
Registered Linux User 282159 [http://counter.li.org]
