Kuba Ober <[EMAIL PROTECTED]> writes:
>> Unicodification is a big and dangerous job, and we will /still/ need
>> from/toqstr unless we use QString in lyx itself, which we probably do
>> not want to do.
>
| If the issue is to use std::string as the basic unicode-enabled string type,
| and easily use such strings in Qt environment, then I presume a very
| effective zero-copy translation function could be hacked if std::string is
| reference counted. It will be somewhat dependent on version of qt and std
| implementation, but I presume that ifdef's in performance-critical code are
| sorta allowed ;-).
>
| AFAIR, std::string and QString have exactly same internal unicode
| representation (UTF-16 ???). I hope so, at least (/me shrugs if they are
| different).
They are different ... std::wstring (not std::string) is on most gcc
platforms UCS-4. (I do not know that they are different I just
assume...)
--
Lgb
