2009/3/29 Ron Aaron: > On Mar 28, 12:41 am, björn wrote: >> >> Thanks, I see the problem now. I am aware that composing characters >> are problematic and I am not sure how easy it will be to fix with the >> default and ATSUI renderers. Still, I will take another look to >> refresh my memory (and it is good to have some example file to work on >> as a test). >> >> Failing that there is much more hope for the half-finished CoreText >> renderer I have yet to finish and push to the repo -- I am confident >> that I can get composing characters working properly with it. So, I >> might take another look at that as well. Anyway, I'll post again when >> I have something more to say on this. > > I'll be anxious to test any such changes!
Please test the Core Text renderer patch I posted in a separate thread and let me know what you think -- your test file renders much better with that patch. I was struggling for a couple of hours with the current renderer to get it working with composing characters but I don't understand what is going wrong. The Cocoa text system gets the correct characters (letter + composing char) but then decides to render it as two glyphs: letter first, then composing character next to it (and then the composing character ends up on top of the next letter). I don't know if I have the energy to sort this out at the moment -- I might try asking for help on the cocoa-dev mailing list. Björn --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_mac" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
