hi Nice! Thank you for the attention. There is a good reason that I'm sure you deeply understand for me to be less connected... I've been finishing my mst. thesis. Work done, presentation finished more time free. Meanwhile, I've been working on some interesting projects including web2py based.
I've been digging on this problem and found out the source. It has to do with the lack of encoding definition in the Translation files. I added "#coding: utf8" and it temporarly worked, until I've added a new T() entry in the code which made web2py to rewrite the T files (so it would include the new key) and then the first line gone making the proper encoding go away. this can be considered a fix and it's backward compatible. A nice solution would be to define somewhere an encoding to apply to an application. -- 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.
translations_encoding.patch
Description: Binary data
