From: John R. <jr...@ce...> - 2013-03-02 03:31:35
|
On Mar 1, 2013, at 5:08 PM, Paul Franklin <pf....@gm...> wrote: > On 3/1/13, Paul Franklin <pf....@gm...> wrote: >> As I don't understand Python "encoding" I don't feel qualified >> to search out every such instance in gramps and edit it somehow. > > On the other hand, are you telling me that all I have to do > is to delete every instance of > > .encode(sys.stdout.encoding, 'backslashreplace') > > that I can find anywhere in gramps40/trunk? > > If so, that's easy and I'm happy to volunteer! > > It is just that as an English speaker, with no "locale" > installed, I've always been reluctant to do anything having > to do with translation or different character sets -- since > I have no way to test the result. If you can't test it, don't touch it. OTOH, it's not that hard to set up a locale and start Gramps with LANG=fo_BA.UTF-8 python3 Gramps.py -l * and see if it's printing a byte literal instead of a string, or to run the GUI and see if you can find any English strings or goofy characters anywhere. Might be a bit challenging to navigate in Chinese, but any latin-alphabet language is pretty guessable. Regards, John Ralls *fo_BA is the foo language as used in Barland. ;-) |