Kenneth Gonsalves wrote:
> ProgrammingError at /web/admin/web/fosscalendar/add/
> ERROR: character 0xe28099 of encoding "UNICODE" has no equivalent in
> "LATIN1" INSERT INTO
> "web_fosscalendar" ("name","year","startdate","enddate","city_id","venue
> ","organiser","scope","website","contact") VALUES ('lll',
> 2007,'2007-11-01','2007-11-01','1','','ll','lll','','Users’ Group')
> Request Method: POST
> Request URL: http://nrcfosshelpline.in/web/admin/web/fosscalendar/add/
> Exception Type: ProgrammingError
> Exception Value: ERROR: character 0xe28099 of encoding "UNICODE" has
> no equivalent in "LATIN1"
Ah... So this is what you called "ascii cannot decode etc" in your
original post? This is an absolutely different issue that has nothing to
do with Python's default usage of ascii for decoding or even Django's
unicode internals.
What happens here is your Postgres database is configured to store data
in Latin 1 encoding. Thus it just cannot store any non-ascii characters,
including that curly single quote. If you want to do this you have to
either encode your data manually into something containing only ascii
characters (like using \u0000 or � escapes) or just convert the
database to be in a more capable encoding (any unicode that that version
of Postgres would support).
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to [email protected]
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
-~----------~----~----~----~------~----~------~--~---
