Skip to content

Comment on B612 Font Family

Comments

Ahhh fonts, where everyone gets an opinion and they're all super important.

If you're designing a font not just for legibility, but primarily for safety, then it seems extremely important that each glyph is uniquely distinguishable from other glyphs. Although this font has different characters for 1/I/l, at a quick glance an uppercase i could still be confused with a pipe (|), and 0 (zero) and O (capital o).[1] I'm sure there are more. So from that standpoint, this font fails for me for legibility/safety.

Also a nitpick, but assuming Chrome is using 60pt B612 font for the title (../fonts/B612-Regular.woff), the "B/6/1" glyphs are hideously formed (that "1" puke) and make me doubt the rest of the character set.

[1] e.g., the FAA has already addressed this with tail numbers: https://www.faa.gov/licenses_certificates/aircraft_certifica...

The font has a slashed 0 for use in alphanumerics and an open 0 for use in numerics. There's discussion of it in other comments here.

I imagine pipes aren't used beside uppercase I in cockpits.

The odd serif on the 1 is to ensure it degrades correctly at low resolution.

When you design for safety, you also have to ask "safety in what context". It's neat that they released the font with an open license, but they didn't design it for anything other than Airbus cockpits.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.