On 7/6/07, Chris Shenton <[EMAIL PROTECTED]> wrote:
>
>
> I had issues in the past with (for example) umlauted-chars being
> entered into my data that then couldn't be rendere by Myghty with the
> default ascii codec; changing python's sitecustomize.py to use:
>
> sys.setdefaultencoding("utf-8")
>
> has fixed this -- until now.
>
> My user uploaded a CSV file using a Myghty web form, processed by
> Pylons, and stored through SQLAlchemy into MySQL. When Pylons and
> Myghty try to render one of these names it breaks:
1. Check that the data is stored correctly (using mysql console). Doing "set
names utf8" and "select *" should render correct data.
2. Check SQLAlchemy decodes Unicode properly: use latest mysqldb release,
add charset=utf8 to your dburi.
3. Check Unicode literals are renderred correctly. Pass some u"" string to
Mighty template and check if it renders OK. Check the docs if it doesnt
(Mako does out of the box).
HTH,
Max.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"pylons-discuss" 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/pylons-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---
