On 04/08/14 14:34, Christian Brabandt wrote:
Hi Tony!
Hi Christian
[...]
And since this seems to work with the GTK2 build (I didn't test it), I
see no reason, why this behaviour should not be also enabled on other
GUIs.
The reason, IIUC, is that searching other fonts is how Pango and Cairo
(which are part of GTK2) find their glyphs. This is documented under
":help guifontwide_gtk2" in the sentences starting "if 'guifontwide' is
empty". The glyph finally used is sometimes noticeably different in
style from those belonging to the font named in 'guifont', as I have
sometimes seen with pointed Arabic (i.e. Arabic with the short vowels
written, but especially the hamzat, maddat, waṣlat, which exist as
precomposed glyphs).
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).
Best,
Christian
Best regards,
Tony.
--
hell, n.:
Truth seen too late.
--
--
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.
