> In other words, right now, Qt supports UCS-2, not UTF-16.
Yes. Sorry for the error.
> Does this mean that for now and the near future, with Linux/Qt/KDE,
> - no one can use the non-BMP private use area
Precisely. Unless "there is serious user demand for it", as I wrote.
> - new assignments and fonts for them cannot be prototyped for
Not in other planes, with our code. There's just so much we can do,
and that's one of the things that's so far down on the list that I
personally don't think it will get to the top.
> - the language tags in plane 14 that the Internet Mail Consortium proposes
> to use (prematurely I know since they are not really standard yet) cannot
> be used
> What is missing?
Time and testing, mostly. Supporting things takes time. We provide
what application developers need, and implementing something that
people aren't asking for and which we cannot test must obviously be
far down on the list of priorities.
Also, if Microsoft's Unicode implemetation doesn't implement it, Qt
won't provide it on X11. Qt is strictly platform independent: We
don't provide one-platform features. (FWIW, I don't know whether NT
does support this.)
> Please, I would appreciate seeing the general plumbing for UTF-16,
> including the part that sets it apart from UCS-2, in place sooner rather
> than later.
Will you pay for its development?
This archive was generated by hypermail 2.1.2 : Tue Jul 10 2001 - 17:20:43 EDT