On Thu, Jun 18, 2009 at 7:02 PM, Edward K. Ream<[email protected]> wrote:
>> Yeah, that's why we shouldn't use g.toUnicode with QStrings (i.e. we >> shouldn't change unicode() to g.toUnicode in qt ui). > > These kind of details are why there is a separate g.app.gui.toUnicode > wrapper in the qt plugin. Let's call it something else than toUnicode then, to avoid the confusion. We need a version that never decodes, and use that as much as possible. > Thus, it appears that QString is an encoded string, **not** a unicode > character (at least on xp). That is, s2 is a wrapper for a utf-8 encoded No, QSting is a real unicode string. QByteArray is what qt uses for binary data (e.g. QString has toUtf8 that gives QByteArray). > My hair is turning ever grayer...Maybe this will work better for Py3k?? It works better with Py3k in that it fails earlier and more often :-). But we should be very strict about bytes/unicode distinction already. -- 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 -~----------~----~----~----~------~----~------~--~---
