On Thu, Jun 18, 2009 at 5:18 PM, Edward K. Ream<[email protected]> wrote:
> P.S. The reason I keep going on about g.toUnicode is that it is the > foundation of Leo3k. In particular, the 'unicode' function does not exist > in Py3k, and so it must be wrapped. But then it should be just aliased to str. It definitely shouldn't do any encoding - because if we "fall back" to encoding, we are hiding bugs. There are 2 separate operations: - Extract unicode object from QString - Read file, producing unicode These are unrelated, apart from the fact that the return value is unicode object. -- Ville M. Vainio http://tinyurl.com/vainio --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
