the documentation saying that the developer should use ugettext_lazy
for the language name if they want it translated *or* at least use a
unicode string.
--
Henrique Romano
In the face of ambiguity, refuse the temptation to guess.
-- Tim Peters
--
You received this message because you a
On Wed, Jan 22, 2014 at 12:43 PM, Ramiro Morales wrote:
> You aren't telling us all the story. there are many missing parts in your
> description of the issue you are finding so far so I don't think it's right
> to jump straight to the "As per the documentation, it is not clear that
> you _must_
result.append(lang)
29 get_cms_setting('LANGUAGES')[site_id] = result
30 return result
In the code above it is trying to translate the language name and it is
resulting in an error since the name isn't an unicode string. I understand
that this is happening in d
as necessary. That's what I'm suggesting here, to make it explicit that
the language name string must be a unicode string.
--
Henrique Romano
In the face of ambiguity, refuse the temptation to guess.
-- Tim Peters
--
You received this message because you are subscribed to the
byte 0xc3 in position 7:
ordinal not in range(128)
So, I'm not sure what you are talking about.
--
Henrique Romano
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubscribe from this group and stop receiving emails fro
Hi,
On Wed, Jan 22, 2014 at 12:37 AM, gilberto dos santos alves <
gsa...@gmail.com> wrote:
> please see that it is python directive not django. for all sources it is a
> good practive for all we that use pt-br utf-8 explicit this on second line
> of file python code
>
> # -*- coding: utf-8 -*-
>
ser should always
use an unicode string for the LANGUAGES setting?
[1] https://docs.djangoproject.com/en/dev/ref/settings/#languages
--
Henrique Romano
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubscribe from this group and stop receivi
On May 6, 2009, at 7:23 AM, Russell Keith-Magee wrote:
> Like many things, it sounds like a good idea, but the devil is in the
> details. A tool like this is really only useful if it provides triage
> data that is both accurate and useful. Here's a quick checklist of the
> basic questions a manua
On May 5, 2009, at 7:03 PM, Jacob Kaplan-Moss wrote:
>
> On Tue, May 5, 2009 at 11:56 PM, Almad wrote:
>> Cool for me, but have enough pet projects so now, but if anyone have
>> spare weekend to implement it? :)
>
> Unfortunately, Anyone doesn't have a lot of free time these days (nor
> does hi
