On Tue, 2009-03-10 at 13:15 +1100, Malcolm Tredinnick wrote:
> On Mon, 2009-03-09 at 07:55 -0700, Tipan wrote:
> >
> > > Do you mean they are inserted into the source as "ó" and so
> > > the user sees, literally, "ó"?
> > >
> >
> > Yes. The string has the html code for the accent as you s
On Mon, 2009-03-09 at 07:55 -0700, Tipan wrote:
>
> > Do you mean they are inserted into the source as "ó" and so
> > the user sees, literally, "ó"?
> >
>
> Yes. The string has the html code for the accent as you show above.
I showed two possiblities. Which one is it? If the string is be
> Do you mean they are inserted into the source as "ó" and so
> the user sees, literally, "ó"?
>
Yes. The string has the html code for the accent as you show above.
> This could be a bug. Any strings provided by Django itself (and this
> includes translated strings, although we don't mak
On Sun, 2009-03-08 at 04:55 -0700, Tipan wrote:
> I'm trying to pass a translated string to a select box using a Forms
> Select widget and it always presents the output string with all the
> accent HTML entity codes.
>
> In my models file, I have a range of subjects:
>
> Models.py
> from django.
I'm trying to pass a translated string to a select box using a Forms
Select widget and it always presents the output string with all the
accent HTML entity codes.
In my models file, I have a range of subjects:
Models.py
from django.utils import translation
from django.utils.translation import ug
5 matches
Mail list logo
