Charles de Miramon <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
|
| > That might be the easy way out.
| >
| > IMHO it is a pity that Qt only supports ucs-2 and not ucs-4.
| > (not even for individual codepoints)
| >
|
| I thought that utf-32 (ucs-4) does not work on Windows and that utf-16 is
| the way to go for cross-platform.
No. Ucs-4 would work quite nicely on windows (internally). Towards
external interfaces utf-8, utf-16, ucs-2 or ucs-4 will have to be used
anyways, depending on the external interface.
Btw. Does Qt even support utf-16? I thought they only supported ucs-2.
AFAICS there is not support for surrogate chars in Qt.
| Would you consider using Qstring for storing unicode strings ? Qstring is
| now part of QtCore a subset of Qt.
I'd hope to not do that.
Currently I am still exploring storing ucs-4 codepoints in the
std::vector that contains the characters of the document. Also quite
luckily codepoint conversion is quite fast.
--
Lgb
