Bug fixed. The culprit is exactly the utf8 encoding. Javascript only accepts Unicode string, not utf8. Most browsers stick to this standard, only Chrome can accept utf8 also.
The fix is mentioned in http://code.google.com/p/web2py/issues/detail?id=260 By the way, my another fix to http://code.google.com/p/web2py/issues/detail?id=221 is still not accepted into trunk? Regards, Ray Luo (a.k.a. Iceberg) On May 4, 11:17 pm, Iceberg <[email protected]> wrote: > As expected, that causes a ticket. Because my source code file is > already in utf8 encoding, and you can not do a "already-utf8- > string".encode('utf8') > > On May 4, 9:37 pm, Massimo Di Pierro <[email protected]> > wrote: > > > > can you try replace > > > response.flash = 'Erro na inserção' > > > with > > > response.flash = 'Erro na inserção'.encode('utf8') > > > On May 4, 5:39 am, Iceberg <[email protected]> wrote: > > > > Hi there, > > > > I just noticed that, component's non-ascii response.flash does not > > > show well in IE7, IE8, Firefox 3.0.19. > > > > def visit_me(): > > > return {'':LOAD('default', 'component.load', ajax=True)} > > > def component(): > > > response.flash = 'Erro na inserção' > > > return {'':'Testing'} > > > > But Chrome 11.x is fine. > > > > So I guess that means the flash string is properly transfered to > > > client but, for some reason its encoding is not properly indicated > > > therefore incorrectly handled. > > > > Is this a bug? Is there any workaround? > > > > Regards, > > > Iceberg
