Updating this after problem resolution, the issue was with the
translation (.po and .mo) files, not Django itself. Old gettext with
Windows may have been the culprit, found using Linux to create the
message files much more reliable.
On Feb 12, 10:21 am, Scott wrote:
> Hi Karen,
>
> Thanks for th
Hi Karen,
Thanks for the suggestion on upgrading, I followed the steps to bring
the Helper up to the latest revision hosted on Google code, but am
still seeing the UnicodeEncodeErrors (not to mention that the language
routing by cookie ceased to work).
Does anyone have a working build that can v
On Mon, Feb 9, 2009 at 12:21 PM, Scott wrote:
>
> Thanks for the quick reply - does anyone know if Django 1.0 is patched
> into the Google App Engine Django Helper?
>
Per
http://code.google.com/p/google-app-engine-django/source/browse/trunk/CHANGES
any reasonably current level of the app engine
Thanks for the quick reply - does anyone know if Django 1.0 is patched
into the Google App Engine Django Helper?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email
Quick edit, I meant to ask if it could be a problem with the '.mo'
files being created incorrectly...the '.po' files that contain the
unicode translations are UTF-8.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Dj
On Mon, Feb 9, 2009 at 11:27 AM, Scott wrote:
>
> Hello,
>
> I'm receiving the following error while running Django 0.96 with
> Google App Engine:
>
> UnicodeDecodeError at /
> 'ascii' codec can't decode byte 0xe3 in position 0: ordinal not in
> range(128)
>
> GET
> Request URL:http://localho
Hello,
I'm receiving the following error while running Django 0.96 with
Google App Engine:
UnicodeDecodeError at /
'ascii' codec can't decode byte 0xe3 in position 0: ordinal not in
range(128)
GET
Request URL:http://localhost:8080/
Exception Type: UnicodeDecodeError
Exception Value:
7 matches
Mail list logo