> > 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. Vainiohttp://tinyurl.com/vainio
I'm not a QT person, and I'm not too familiar with Leo's internal, esp. wrt QT, but I do know that a common confusion when dealing with UTF-8/Unicode is chars vs. bytes. I hope this is the case, since it will be easy to solve, but I can only point to this hoping it will make sense somehow. Gil -- 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.
