> If you could let us know exactly what the difference is between > GTK/MacVim as regards Hebrew support then I (or anybody else interested, > of course) could look into fixing this. The problem, for me, with > adding support for other languages (than English) is that I simply do > not know how they are used, and hence I have no idea as to what > works/doesn't work. I would really appreciate if you could post a list > of test cases (to vim_mac, since this is Mac specific) and say how they > should behave.
I will aim to do this for you soon. I would love it if you could fix it! > The code I pointed you to before (in gui_macvim.m) will work even > without the GUI, but it is written in objective-c so you would need to > enable obj-c compilation. One way of doing this is to create a new .m > file (os_macosx_objc.m?), and copy the two functions I mentioned in > there. It would probably be easier to just take the relevant code from > gui_mac.c and put it inside os_macosx.c, but I haven't given this much > thought. Yeah, I tried that, but it didn't work, which is why I think there must be some initialisation code or something. Maybe a reference to the clipboard is in a global/static variable that is initialised at GUI startup. I will look into it. Shouldn't be hard to find. One issue, though. If we move the clipboard support into os_macosx.c will it break MacVim by having those functions doubly defined? Does it need some conditional compilation #ifdefs, and if so, what? Or would you just remove the MacVim clipboard support if the other worked without the GUI? Ben. Send instant messages to your online friends http://au.messenger.yahoo.com --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
