On środa 18 grudzień 2002 10:55 am, Angus Leeming wrote: > On Wednesday 18 December 2002 3:45 pm, Kuba Ober wrote: > > Would it make any sense to use something like this: > > typedef uint16_t lchar_t; > > typedef std::basic_string<lchar_t> lstring; > > > > "l" stands for LyX (or low-overhead-in-conversion-to-QString) ;-) > > SMiyata (sp?) suggested something similar to this some time ago when > describing what CJK-LyX needed before the two codes could be merged. He > noted that wchar_t is shot on several different platforms.
Not only shot, but possibly too wide as well. I don't think we really need 32 bits per character. Having 16 bits per character works fine in QString, so I presume that's all that's needed. Now, the question is whether that's something to be done for 1.3.0. I presume it could clean up the code a lot, so maybe it's worthwile... Cheers, Kuba Ober
