Greetings Pyloneers, We see a log of people on #pylons who try to put unicode content in QuickWiki and immediately think that Pylons sucks at unicode. There is no reason for that, Pylons is probably the framework with the most transparent unicode support out there; it's just that QuickWiki, for some reason, makes a special effort to avoid unicode compatibility. So I decided to fix QuickWiki; here is my Mercurial branch with the fix:
static-http://ygingras.net/files/QuickWiki.hg But wait before you start to change the tutorial because I ran into problems too. There is some ugly mangling going on in h.draggable_element() It might be that stuff gets encoded twice or something like that but passing unicode or utf-8 to it result in undecodable garbage. The code in question is in controllers/page.py line 47 and templates/list-titles.mako line 3 and 5 It was easy enough to fix by manually encoding to utf-7 but I find this kind of ugly in a tutorial that aims to show how easy it is to use unicode with Pylons. Anyone knows why the mangling is happening in h.draggable_element()? What do we do with that? Use unicode only for the page body and not for the page title until we have a fix? That sounds like a good compromise; it shows how to use unicode with pylons without spawning a long discussion on ugly hacks to work around bug (accidental features?) in helpers. Any ideas on that? -- Yannick Gingras --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
