On Tue, Jan 26, 2010 at 8:19 PM, Edward K. Ream <[email protected]> wrote:
> The problem is easily stated: there is a confusion, perhaps within qt, > about what character indices mean for unicode characters requiring > more than one byte internally. This is a fertile source of bugs. This > might or might not be a Leo problem. Theory - QChar type (used by QString) is utf-16. Possibly characters beyond 16 bits cause position to no longer represent the character index within the row string. This is hardly a showstopper. Perhaps leo could give a warning when reading such (rare?) files, or something. -- 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.
