Robin Munn wrote:
Dealing with Unicode makes your life more complicated, so it's easy to
see why you'd want to get rid of it. But that would be a mistake,
IMHO. Unicode is not going to go away, no matter how much you might
want it to, so the best thing is to just learn about it. If you
haven't yet read http://www.joelonsoftware.com/articles/Unicode.html,
read it -- it's the best "The basics of Unicode and why you should
care" article I've found.
OK. I've read the article and am appropriately shamed. I've changed my
<meta> to specify utf-8 and the W3C validator is very happy with me now.
(It used to complain that it couldn't find an encoding.)
As I move from php to python I'm trying to learn better programming
habits. So what's next?
Should I be using UnicodeCol() instead of StringCol()?
And I'm not certain I understand the SQLObject docs on the matter. If I
understand correctly, SQLObject will then handle encoding and decoding
the data going in and out of the database properly, but it is still my
responsibility to see that parameters to queries are utf-8 encoded. Is
that right? Is there more I need to do to handle utf-8 correctly?
Thanks,
Steve Bergman
