Hi, > I just tested the X11 and Gtk1 in my Debian box. X11 front-end failed > to compile. Gtk1 front-end compiled OK, but doesn't work properly. I'm > afraid I'll not be able to make these two "so old" front-ends work > properly. > > Could you just send out the first patch for screen.c first? Then all > the other front-ends, including GTK2, GNOME2, Windows, will work fine.
I tested the screen.c-only patch on ubuntu (terminal and gui), os x (terminal and gui) and windows (gui only), with the default os settings. Encoding was set to utf8, and everything was compiled with --enable-multibyte. By default, neither ubuntu nor windows seem to have unicode fonts installed. Results look good on osx, okayish for gtk and windows gui (both have some redraw problems, but nothing serious. And this problems also occur with some BMP characters that are already supported at the moment). gtk terminal (well -- ubuntu terminal :-P) however doesn't display characters >= 0x10000 at all. `cat` doesn't display them either, so this might not be critical. Screenshots are here: http://amnoid.de/tmp/osxgui.png http://amnoid.de/tmp/osxterm.png http://amnoid.de/tmp/gtkgui.png http://amnoid.de/tmp/gtkterm.png http://amnoid.de/tmp/windraw.png http://amnoid.de/tmp/winredraw.png (the last screenshot shows that the "new" character is drawn twice: once at its original position, and once one to the right). The file I used for testing is attached. I'd vote for using this patch and working on the display problems after that (except for the windows case, these display problems already exist with the current version, as the first line in all screenshots shows). Nico --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
asdfsdfâasdf asdfAasdf asdfãasdfsdf asdfãasdf asdfＡsdf ð´ asdf
