Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

B612 Font Family

b612-font.com

Post reply on HN
Print view View original

31–40 of 99 posts

Re: B612 Font Family

#31

Post by nottheengineer »

devit wrote: post #29

Seems really bad to me. There's a lot of distracting glitches like the K and Q having small gaps where strokes come together, and even glyphs like the N, M, Y and Z have weird little gaps at the joints, the F and B have a bizarre overhang at the upper horizontal stroke, the 1 and 6 have a weird cut in their strokes. There are lots of weird confusing choices like the parenthesis being a round rect instead of a bow sha…

It seems to me that those choices are made with low DPI in mind. Those cuts probably make sure that letters don't become blurry.

I think I'll try this one on my 1080p monitor for a day and see how it goes.

Re: B612 Font Family

#32

Post by mdekkers »

devit wrote: post #29

Seems really bad to me. There's a lot of distracting glitches like the K and Q having small gaps where strokes come together, and even glyphs like the N, M, Y and Z have weird little gaps at the joints, the F and B have a bizarre overhang at the upper horizontal stroke, the 1 and 6 have a weird cut in their strokes. There are lots of weird confusing choices like the parenthesis being a round rect instead of a bow sha…

Have to agree. There is a lot of wild stuff going on that is visually tiring and hampers readability

Re: B612 Font Family

#33

Post by rbanffy »

zauguin wrote: post #26
Gare wrote: post #23

Earlier quoted context omitted.

Checked the Github repository, there are indeed separate "zero" and "slashedzero" glyphs.

While there is a glyph like that there's no nice way to access it. There is no font feature to enable slashedzero by default and slashedzero is not mapped to U+0030 U+FE00 (Unicode's standard variant for an explicit slashed zero). Instead it's only accessible using the private use codepoint U+E007 and then typically doesn't get copied as a regular zero. But more generally the font has an empty GSUB table which would…

Still a worthy bug to be submitted.

Re: B612 Font Family

#34

Post by [deleted] »

atoav wrote: post #17
futureduck wrote: post #15

Strange, the background image of the site's header shows a very nice cockpit font indeed, but the actual B612 font is quite different - for instance zeros have no line through them. Though the oxygen indicator seems to use this font.

I think the goal of the designers wasn't to recreate the font in the plane, but to create their own inspired high legibility font.

[deleted]

Re: B612 Font Family

#35

Post by naillo »

I wonder when we'll consider fonts as a 'solved' problem. I keep seeing designers making more of them, I guess it's just a tradition and hobby at this point

Re: B612 Font Family

#36

Post by reacweb »

livrem wrote: post #16
futureduck wrote: post #15

Strange, the background image of the site's header shows a very nice cockpit font indeed, but the actual B612 font is quite different - for instance zeros have no line through them. Though the oxygen indicator seems to use this font.

The image shows a 0 without a line as well. Maybe the other one is a Ø? Or maybe there are conventions to use slashed zeroes in some places an non-slashed in other places?

Yes. 0 (not slashed) is ambiguous only in fields that accept also letters.

Re: B612 Font Family

#37

Post by croisillon »

naillo wrote: post #35

I wonder when we'll consider fonts as a 'solved' problem. I keep seeing designers making more of them, I guess it's just a tradition and hobby at this point

not so sure about that, my boss calls me a pedant when i write reports in cuneiform

Re: B612 Font Family

#39

Post by reacweb »

tangwwwei wrote: post #7
brandonasuncion wrote: post #4

I really like the font aesthetically, and I'd use it as a coding font. However, the brackets and parentheses look too similar at smaller sizes, and arrows (ie. -> and =>) don't quite line up properly.

i used it as a coding font for awhile then realized that i cant distinguish between comma and fullstop on my ide setup

I always put a space after a comma. Never after a fullstop. Coding rules improve readability.

Re: B612 Font Family

#40

Post by eesmith »

adastra22 wrote: post #28
userbinator wrote: post #2

Unfortunately the name has been collided into by several other, more popular and newer, things since its creation. However, 46610 is still available as a font name.

B612 is from The Little Prince.

"46610 Bésixdouze ... is a bright background asteroid .. named after "B-612", home of The Little Prince. ... The title character lived on an asteroid named B-612, which is the number 46610 written in hexadecimal notation." - https://en.wikipedia.org/wiki/46610_B%C3%A9sixdouze
Post reply on HN