This is not supposed to be a problem because web2py only passes utf8 encoded data to the database, which means that, even if the database does not know it is utf8, it is just a string with regular characters. The database does not need to know which encoding is used and long one uses it consistently.
This is not to say that may not be a bug. The email from Lorena seem to indicate that there may be a bug. I need to learn more to understand what is causing this. If you feel I am wrong about collations could you provide an example that breaks the current system? Massimo On Dec 15, 8:22 pm, achipa <[email protected]> wrote: > In european languages "Ã..." is usually a sign you have utf8 > characters in latin 8bit fields. > > Massimo, I can see that for MySQL you do other=' ENGINE=InnoDB > CHARACTER SET utf8;' but I fail to see a similar statement for MSSQL > or other databases. How do you make sure they create tables in utf8 ? > > Also, what is perhaps missing is the collation. Character sets are > cool, but if you want to use the DAL with 'orderby' on a non-english > (>128 ascii actually) language table, you're in trouble without > collations. > > On Dec 15, 8:27 pm, mdipierro <[email protected]> wrote: > > > Can you be more explicit? How are you inserting the character and > > getting it out? > > > Massimo > > > On Dec 15, 9:37 am, Lorena <[email protected]> wrote: > > > > Hello, I have a problem with accented characters like "à". Using > > > SQLform in my mssql table shows the character "Ã". Can anyone help me? > > > Thanks Lorena 1000 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" 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/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
