Hi, I noticed today that we have been handling conversion between UTF8 and wxString wrong _all over_, leading to some interesting encoding issues (UTF8 strings were being converted in the encoding of the current locale, not UTF-8). Following a bit of discussion with Wayne I went through and fixed all the instances of this I could find [1].
There is a high chance that this will uncover latent bugs in our encoding handling - e.g. places where people have unwittingly compensated for this bug instead of fixing it. Anyone who has an unusual locale setup - in particular, non-UTF-8 encoding - PLEASE TEST footprint library loading, footprint library writing, rendering of footprint and symbol names in the GUI, and anything else you can think of related to the interface between library ID objects and the greater KiCad environment. Thank you. [1] https://git.launchpad.net/kicad/commit/?id=4011ed4e31c77d9ee885cc9262d0f0f89cad4fc6 -- Chris _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
