Hi, Qt uses harfbuzz to get the information. You can do the same. John
On 28 January 2013 10:45, Jürgen Spitzmüller <sp...@lyx.org> wrote: > Jean-Marc Lasgouttes wrote: >> What I had in mind is the helper functions isHebrewComposeChar or >> isArabicComposeChar in Encoding.cpp. Actually, I am not sure why these >> could not just be 'isComposeChar'. What does the language has to do >> with it? Is there a reason for testing the language as well as the code >> point? > > I understand that a compose char is a compose char. But how many compose chars > are there over the whole unicode range? My point is: If Qt already knows this, > and if we can catch this information, why should we hardcode a list of code > points ourselves? (Note that I do not know whether Qt _really_ provides this > information). > > Also, can you remember me why we paint char by char at all? If I set > \force_paint_single_char to false, the ligatures automatically get painted > correctly. > > Jürgen
