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. Accordingly, Vim can't support them in an appropriate way and needn't. 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. 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.
