Hi Chris (Mellon)
> I'm not sure how that is relevant to the discussion, then - you've got
> a customized environment that suppresses errors, but that's obviously
> not the best general case solution, and it's got nothing to do with
> ascii vs unicode mode wxPython or support for cp1250 in python.You don't get the point or I did not explained it correctly. The problem
here is not only a wxPython ansi/unicode problem. It lies in the fact, that
if a developper has to use the unicode build, she/he has probably to deal
with all this unicode encoding/decoding struff. I have also tried to show, that
the solution as proposed by Chris Barker, using u' ' strings is not the
panacea. From this point of view, I think it fits very well with the concerns
of the original message posted by Donn Ingle.
If you can use an ascii build without trouble, then you won't have any
*more* trouble using a unicode build. If you have encoding issues in
unicode builds that you don't have in ascii, your application still
has the errors - they're just working by happenstance.
If you need to support multiple languages and locales and encodings,
then it doesn't matter what build you use - you have to deal with
these issues one way or another. Using unicode literals is not a
panacea, but it's an important step if you're supporting a non-ascii
encoding.
I'm visiting enough French fora to know, this Python unicode encoding/decoding
stuff is a nightmare for a lot of developpers. (I, too, have sometimes to think
twice on this field).
Once you understand the fundamental difference between unicode and raw
bytes, it's really not that difficult to understand, and
encoding/decoding isn't that complicated. Figuring out what encoding
you need, and all the other issues related to i18ln are another story,
of course.
> My terminal seems to be using cp1250, ...
cp1250, alias windows-cp1250, corresponds to the setting for Central and Eastern
Europe languages.
My terminal displays characters encoded using cp1250 as expected. This
may just be due to overlap - I'm not an expert on windows code pages -
or it may do something more complicated. The DOS terminals behavior in
this regard doesn't seem to be well documented.
ยทยทยท
On Dec 21, 2007 3:54 AM, jmf <jfauth@bluewin.ch> wrote: