Iosevka – A Typeface for Code, from Code • Hacker News Board

Re: Iosevka – A Typeface for Code, from Code

#91

Post by gkya » Sat, Apr 01, 2017, 1:36 PM UTC

speleo_engr wrote: post #86

gkya wrote: post #75

Earlier quoted context omitted.

Not the commenter you're asking to, but ligatures, to me, are a print thing. They are not nice on the computer screen. I'm kind-of fine with fi and ffi with variable-width fonts, but the rest is geekery (which is fine in itself, but not practical). With print, you have to think about kerning and the flow of the ink, and the DPI of the printer, and many other variables, and some ligatures help with that (fi). Then the…

Monospaced fonts simply mean that the horizontal width is constant. While this also means there aren't any kerning pairs, it is a different concept. Simply disabling kerning does not mean a font is monospaced. Kerning is a table of pairs that allows them to have more aggressive advance values. For example, with a sequential 'V' and 'A', the 'A' could be moved closer to the 'V'. But kerning doesn't have anything to do…

And did I say otherwise?

Re: Iosevka – A Typeface for Code, from Code

#92

Post by nemoniac » Sat, Apr 01, 2017, 1:37 PM UTC

netgusto wrote: post #66

Very nice; I find Input Mono from Front Bureau to be a bit more readable, though: http://input.fontbureau.com/preview/?size=20&language=python...

It's a readable font but the 1 is too similar to the l for my taste. Iosevka has a 1 with no horizontal line at the bottom.

Re: Iosevka – A Typeface for Code, from Code

#93

Post by criddell » Sat, Apr 01, 2017, 1:47 PM UTC

jrwiegand wrote: post #85

I am currently using Source Code Pro. I find it very nice to use as my daily driver.

If I'm working on a hi-dpi display (most of the time I am), Source Code Pro is my font. It's not a great font at small sizes though.

Re: Iosevka – A Typeface for Code, from Code

#94

Post by haldean » Sat, Apr 01, 2017, 1:48 PM UTC

bandali wrote: post #10

Iosevka is indeed a very pretty typeface. I've been using it for a while now and been really enjoying it. Here's some Dafny code for your viewing pleasure: https://i.imgur.com/clxUR1y.png

How do you get the ligatures to work with vim? I've been trying to wrangle PragmataPro and gvim for a while but haven't managed yet.

Re: Iosevka – A Typeface for Code, from Code

#95

Post by boardwaalk » Sat, Apr 01, 2017, 1:50 PM UTC

tajen wrote: post #62

joatmon-snoo wrote: post #22

Earlier quoted context omitted.

Glancing at it I'm not sure if I would immediately be comfortable with it - it's a much narrower glyph than the type I'm used to. I think the lower width:height ratio is part of your whitespace issue, combined with the seemingly liberal kerning.

If anyone uses narrower fonts so they can see more on a single screen, here's exactly what you need: http://dotsies.org — It's a mysterious dot font that is not braille. Have fun (spoiler: I didn't succeed to use it).

That is cool. I wish it wasn't dependent on the vertical alignment so much (e.g. if you have a single character, you can't tell an 'a' from a 'b' from a 'c' -- heck if you have a 'ab' that could also be a 'bc' or a 'cd'). Maybe it matters less in practice than I think.

Re: Iosevka – A Typeface for Code, from Code

#96

Post by photon-torpedo » Sat, Apr 01, 2017, 2:09 PM UTC

haldean wrote: post #94

bandali wrote: post #10

Iosevka is indeed a very pretty typeface. I've been using it for a while now and been really enjoying it. Here's some Dafny code for your viewing pleasure: https://i.imgur.com/clxUR1y.png

How do you get the ligatures to work with vim? I've been trying to wrangle PragmataPro and gvim for a while but haven't managed yet.

If you use vim in the terminal, ligature support just depends on the terminal emulator. In Linux, qterminal and konsole work.

Re: Iosevka – A Typeface for Code, from Code

#97

Post by planteen » Sat, Apr 01, 2017, 2:13 PM UTC

gkya wrote: post #91

speleo_engr wrote: post #86

Earlier quoted context omitted.

Monospaced fonts simply mean that the horizontal width is constant. While this also means there aren't any kerning pairs, it is a different concept. Simply disabling kerning does not mean a font is monospaced. Kerning is a table of pairs that allows them to have more aggressive advance values. For example, with a sequential 'V' and 'A', the 'A' could be moved closer to the 'V'. But kerning doesn't have anything to do…

And did I say otherwise?

I guess I took your statement, "because there's no kerning (each character takes up equal space)" to mean "no kerning means each character takes up equal space". Maybe that's not what you meant with those parenthesis.

Re: Iosevka – A Typeface for Code, from Code

#98

Post by Kequc » Sat, Apr 01, 2017, 2:23 PM UTC

IshKebab wrote: post #67

debaserab2 wrote: post #16

I don't know what it is about this font but it doesn't feel monospaced. Using this font I constantly keep second guessing myself as to where I've placed whitespace. Maybe I just need to use it more, I don't know.

Another reason to use tabs...

Every time you press tab and your code editor actually inserts a tab, we are 1 step closer to the outcome from Terminator.

Re: Iosevka – A Typeface for Code, from Code

#99

Post by khaled » Sat, Apr 01, 2017, 2:24 PM UTC

tinza123 wrote: post #47

omgtehlion wrote: post #43

Earlier quoted context omitted.

Actually, it does pretty much ignore all other languages given its width. They did it as narrow as possible (with latin letters) and just shoehorned all others later. > Finally a font which thinks about other......but few take care to show it in their marketing material Almost all commercial fonts do this. Just take a look around.

They do take consideration about non-latin languages. For example, a Chinese character in this font has exactly twice of the width of an English character, which makes sense

CJK glyphs are always double width, there is no other way around it.

Re: Iosevka – A Typeface for Code, from Code

#100

Post by justinjlynn » Sat, Apr 01, 2017, 2:25 PM UTC

Illniyar wrote: post #89

justinjlynn wrote: post #72

Earlier quoted context omitted.

You're right, that's nice. However, Input is proprietary and requires agreeing to a _rather restrictive_ licence to download and use... http://input.fontbureau.com/license/

I don't find this license very restrictive. You can use it for personal use as much as you want. You can't put it on websites or use it in software you give out. Seems fair to me.

I am wary of licenses which attempt to narrowly define things like personal use with language that is incredibly legally vague.

> For the purposes of this License, Personal Use is defined as any use on your own computer that involves computer programming, software development, or the composition of plaintext documents in personal, professional, or non-professional contexts.

namely:

> composition of plaintext documents

just composition? What if I print it? Can I use it in a presentation? I would rather not agree to language which seems to imply a future requirement to purchase some "other" licence if I trigger any of those clauses.