When migrating an application from the version 1.67.1 to the most recent one (1.76.3 ), I encountered the following problem:
Text, coded as UTF-8, entered in a textarea, processed by the application and served after processing in another view, yielded perfectly readable text with all the non-ascii characters perfectly displayed (german alphabet, russian alphabet, etc ...) in the version 1.67.1 of Web2py. However in the version 1.76.3 the non-ascii characters are displayed as question marks instead of characters. - Have I done something wrong ? - has the way Web2py deals with unicode changed ? - is there a bug ? Thanks, Serge Hulne -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web...@googlegroups.com. To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
