Hi all, ... Just want to let you know I m still working on the integration of the ATSUI rendering code into MacVim. The rendering code itself is not a big
Message 1 of 2
, Nov 11, 2007
On Nov 12, 2007 4:13 AM, björn <bjorn.winckler@...> wrote:
> That's the good news. The bad news is that this implementation still
> is not 100% correct. Most problems spring from the fact that Vim
> thinks a certain sequence of UTF8 bytes should be rendered one way
> whereas Cocoa thinks something else entirely. At the moment I know
> that nonspacing marks may cause problems. They should render on top
> of the previous character according to Vim, but Cocoa doesn't always
> agree (sometimes it renders after). Another problem is that Cocoa
> sometimes hides glyphs and pretends like they don't exists, but Vim
> always thinks that a glyph should be rendered (this causes the cursor
> to be displayed in the wrong place). If you find more problems,
> please let me know, but I'm not sure I will want to fix them. You'll
> just have to patiently wait for Jiang's magic.
Just want to let you know I'm still working on the integration of the ATSUI
rendering code into MacVim. The rendering code itself is not a big deal,
but I have to figure out how to make it interact with rest of MacVim
and without reducing performance. I'm not that familiar with MacVim and
some problems are not very easy to debug, so I don't have any progress to
Thanks for all your patience, I hope finally we could settle up a foundation
which could benefit to both MacVim and vim-cocoa, or even Carbon Vim.
You received this message from the "vim_mac" maillist.
For more information, visit http://www.vim.org/maillist.php
Your message has been successfully submitted and would be delivered to recipients shortly.