On Sat, 2008-07-05 at 12:42 +0200, Florencio Cano wrote:
> I had 'es_ES'. I have reviewed
> http://www.i18nguy.com/unicode/language-identifiers.html and I see
> that for spanish (Spain) I have to use 'es-ES'
Well, that's some draft document with no actual standing. Django uses
the HTTP header version of combined languages, so it would be "es-es".
However, for "Spanish from Spain", simply "es" will do ("es-es"
shouldn't hurt anything, however, since it will fall back to "es").
> so I change it, execute
> manage.py syndb and execute the tests but I get the same. Now I try
> with 'es'. The same process and I get the same...Could be the problem
> in other place?
Try import settings from django.conf and printing out the value of
settings.LANGUAGE_CODE just before one of your strings that is meant to
be translated in the tests. For example, in a doctest you could write
>>> from django.conf import settings
>>> settings.LANGUAGE_CODE
It will end up as a failing test (since it prints out something and
nothing was expected), but you'll at least see what the value is set to.
I don't know what else to suggest. I did some quick checking over here
and changing the LANGUAGE_CODE setting changes the locale used to
translate the error strings.
Malcolm
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
