On Sun, Aug 30, 2009 at 5:54 AM, Ville M. Vainio <[email protected]> wrote:
> > http://mail.python.org/pipermail/python-dev/2009-August/091363.html The insulting comment in this post that people don't understand unicode may be true, but they are in no way helpful. I certainly do not pretend to understand unicode issues in detail. The master plan in Leo is simple: convert to unicode on input, convert to encoded strings on output. Of course, this leaves unanswered the essential question of what encodings to use when reading or writing! This is a complicated subject and it depends on what files are being read or written. Having admitted my basic cluelessness about unicode, if you want me to do something about Leo's encodings, you must explain in detail how Leo's code could be improved. Generalities are useless: I have to have some plan for making what presumably would be substantial changes to Leo's code. Better yet, I would like to see a branch that handles encodings in a better way. It's possible that major improvements can be made now. It is even more likely that improvements can be made when moving to Python 3.x. However, the notion that setting sys.setdefaultencoding('utf-8') in sitecustomize.py is somehow "evil" does not make sense to me. Indeed, without this setting, print(x), where x is a non-ascii character, produces byte hash. With this setting, all works as expected. This is a strange kind of evil. Edward --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~----------~----~----~----~------~----~------~--~---
