On 5 August 2014 04:48, Tony Mechelynck <[email protected]> wrote: > The Vim-specific coding necessary to fetch these "replacement" glyphs is > (IIUC) minimal; it just consists of calling the proper APIs from the GTK2 > interface. *If* similar APIs exist in other GUI backends, and *if* they can > handle a fixed-size character cell in spite of fetching glyphs from various > fonts, then by all means such APIs should be called; but these two are big > "if"s, especially considering that GTK2 is the single gvim GUI flavour which > can use non-monospace fonts (with ugly results, it is true, but without > overstepping the character cell's bounds).
Reiterating, my patch, which simply removes use of an unsupported OS flag which comments in the Vim code seem to imply was only used in the first place for a speed boost which is imperceptible to me on modern hardware, handles all of these "if"s simply by letting the OS do it. Could people with experience with large-scale use of non-ASCII fonts give this patch a try and see if it works as expected? Tony, could you check how it fares with your pointed Arabic example? Or could you at least explain to me how I (as a non-Arabic speaker) could reproduce and identify the scenario you describe, and I'll try it out. Paul -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
