David Stanek <[EMAIL PROTECTED]> writes: > Yeah. This is important to note because it has a nice side effect. All > strings are interpreted as ISO-8859-1 in Python, not just strings in Kid. So > if you get UTF-8 or some other encoding you will have the same issue all > over again. I would actually recommend that you convert your strings into > unicode and pass those to Kid.
It is easier to work this way IMHO. You declare your strings as UnicodeString in your model, configure your system for UTF-8 (or your text editor...), make sure your database encoding is correct for UTF-8 as well and remember to use u'string' when it has an accent (i.e., only for text in your Python code). Now you won't rule out 1 billion of Chinese from your system, plus a few million of Arabs, plus Japanese, plus Indian, plus ... :-) The first setup is a bit harder if your operating system doesn't help, but from the second and on, it will be simpler for you. :-) -- Jorge Godoy <[EMAIL PROTECTED]>
