Hi Kazunobu, On Monday, 8 August 2016 18:31:40 UTC+2, Kazunobu Kuriyama wrote: > 2016-08-08 23:06 GMT+09:00 manuelschiller.pimail via vim_dev > <[email protected]>: > > > On Monday, 8 August 2016 15:39:02 UTC+2, Kazunobu Kuriyama wrote: > > > If your windowing system is a recent X11 with fontconfig, do > > > > > > $ fc-scan <your favorite ligature font file> > > > > > > > > > then you'll have something human readable. > > > > > > > > > Take a look at an item called 'spacing.' > > > > > > > > > If you have none or the number zero, then the font is proportional. > > > If you have the number 90, then the font is dual. > > > If you have the number 100, then the font is monospace. > > > If you have the number 110, then the font is charcell > > > > Thanks, this is getting us somewhere. :) > > > > I've run a couple of checks with the commands you suggested, and I get the > following results: > > - DejaVu and PragmataPro Mono do indeed have the spacing attribute set to 100. > > - Hasklig and PragmataPro do not, in fact they do not show a spacing > attribute. (However, as I tried to explain in that previous post in my own > frightfully limited way, they're effectively monospaced, and after glyph > shaping where appropriate, things will line up with the character cell layout > that the rendering code assumes, I think...) > > > > By "if you have none..." I meant "(fc-scan) do(es) not show a spacing > attribute." > > > Therefore, the conclusion is that both Hasklig and PragmataPro are > proportional. No matter how they appear "effectively" monospaced to our > eyes, no rendering engine handles them as such.
I understand that now. > > Accordingly, Vim can't support them in an appropriate way and needn't. > No, it need not do so, and for the general case of proportional fonts, I'm not trying to convince you, or anyone else. But the change required isn't a big one, and all it costs at runtime is a slightly more complicated initialisation of the cache bypassing the shaping, and a bit more memory for it (both of which are likely unnoticable among all the other things that gvim needs to do before it can start drawing characters in the edit section of the window). It also costs one left shift for the index into the cache. That's not what I'd call resource-hungry, or bloated. While I understand that vim wouldn't claim support, wouldn't it be nice if these effectively monospaced fonts would work to that extent at least? > > Do you know any other fonts which have ligatures and are truly monospaced? > For such fonts, if any, I think there's room for consideration. > > > > > So, apparently, there's monospaced fonts, and fonts that just happen to have > individual glyphs an intger multiple of the same width. I freely admit that I > did not know about this, and apologise if I have given offence in the process. > > > > To my mind, the question the list now needs to decide is this: Do we want to > support these "effectively monospaced" fonts like Hasklig, or not? (I think > we should, but I'll abide by your decision, of course. :) > > > > I haven't seen this community works like that. Needless to say, it's only > you who can make a decision as to your way to go. > Well, I have my patch which does what I want. :) If you think there's something salvagable from it (e.g. reworking the bit of the cache that has the assumption that pango shaping will give one glyph per input character), let me know, and I'll see what I can do in my free time. But from what I gather from your reaction (if I read between the lines correctly), you'd rather not include any of it because the fonts in question are not truely monospaced in the sense you indicated. Fair enough. All the best, Manuel > > Cheers, > Kazunobu > > > > > If the answer is yes, we can discuss which bits of the patch you'd like > cleaned up, and I'll do my best to provide something that's acceptable. Sorry > again for the "exchange of fire" earlier, I certainly didn't mean to hurt > anyone's feelings. > > > > Best regards, > > > > Manuel > > > > -- > > -- > > 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. -- -- 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.
