Georg Baum wrote:
Am Freitag, 1. Dezember 2006 21:08 schrieb Andre Poenitz:
On Fri, Dec 01, 2006 at 05:26:43PM +0100, Georg Baum wrote:
Yes. Then you make it clear that the qt4 frontend can only handle ucs2.
Which is wrong as far as I have been told. Qt 4 is supposed to be able
to render the full unicode set.
Well, I was talking about the LyX qt4 frontend, not qt in general. In the
very beginning the conversion docstring<->QString used iconv and could
therefore handle the full ucs4 range.
"Could" is the important word here. "Slow" is another important word
that I may add.
This is not the case anymore, the
conversion was replaced by a simple cast. Therefore any code point that is
not in ucs2 will not be converted correctly. See ucs4_to_qchar and
qchar_to_ucs4 in src/frontends/qt4/qt_helpers.h.
As I said in another post, we can change that once we know how to to
handle that in a reliable and fast way. But for the time being, I'd
rather let is like this and even put an assertion for out of (16 bit)
range values. Before the 1.5.0 release, we can replace the assertion
with and "if" and returns an interrogative mark for those unsupported
characters.
Abdel.
