On 15 Jul 2011, at 16:34, Matthias Melcher wrote:

> 
> It works perfectly well on OS X. I am sorry that I can't say anything for 
> Linux.


I just tested this on my Mac, and in a VM running ubuntu 11.04.

I'm not entirely sure what the correct rendering of the labels is, but:

- Under OSX, the text appears to be the same in Mail, Xcode and in the fltk 
example when it runs.

- Under linux, the text appears the same as the above when viewed in gedit (I 
don't have kdevelop installed so can't say how it looks...) but looks different 
in the fltk example when it runs. The ordering of the displayed glyphs appears 
to be different, though I do not know what would be considered correct or not, 
for the two strings indicated in the comments, whilst the other two strings 
appear to be OK...

I'd have to guess that this is a consequence of what I mentioned in my previous 
email, that the canonical ordering of the characters in the string does not 
match the rendered order on the display once the string is composited, but 
really I am out of my depth here, I do not know any Indic languages... Gedit 
uses PanGo for its compositing so (presumably) gets it right, and I'd assume 
the Apple applications also get it right (they use ICU under the covers, I 
think?)

Why the fltk app appears correct on OSX I am not sure - it may be that the 
Apple text renderer under Quartz is "fixing" things for us, which I find 
unexpected.

I do not know.

OK - I just fed the string "उपस्थिति" into Packetizer.com as you suggested, and 
it displays the individual glyphs in what I assume is the canonical ordering, 
and that looks a lot like what the fltk-linux version is showing, except that 
the fltk-linux version is joined up rather than single glyphs.

So, I guess that's what the issue is - you need to pass the fltk rendering code 
the strings composited into the display order (at least under linux, anyway) 
and then they will probably display OK.

For that, you'll need to look at ICU or PanGo or something for preparing the 
text strings, as that's way beyond the scope of what fltk can do.



_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev

Reply via email to