string,unicode <--> wxString conversions

Robin:

Those are all supposed to be nearly equivallent, and my tests work okay
so far on each, but the "nearly" worries me a bit that there may be
subtle differences in a single app when run on the different platforms.

...supposed to be nearly equivalent... : This gives me jitters.
...and my tests... : Did your tests also include the euro sign, the european
currency symbol?

Jean-Michel Fauth, Switzerland

Jean-Michel Fauth wrote:

Robin:

Those are all supposed to be nearly equivallent, and my tests work okay so far on each, but the "nearly" worries me a bit that there may be subtle differences in a single app when run on the different platforms.

...supposed to be nearly equivalent... : This gives me jitters.
...and my tests... : Did your tests also include the euro sign, the european
currency symbol?

Take a look at the three modules in the encodings package in the Python library. (iso8859_1.py, cp1252.py and mac_roman.py)

For iso8859-1 the characters (128-255) are the unicode values 128-255, (using make_itendity_dict().) The other two start out with with the same values but then override several of them, and they are overridden quite differently.

ยทยทยท

--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!