51–60 of 99 posts
BTW, I'm used to FontForge (which is not the most amenable to collaborative work) and would love to know what other font designers use and what would be a good collaborative workflow for open source fonts.
Earlier quoted context omitted.
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.
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.
There are two open tickets about it, the second is almost four years old, maybe someone here who is familiar with the tooling could contribute?
https://github.com/polarsys/b612/issues/24
https://github.com/polarsys/b612/issues/20#issuecomment-5448...
Welp, it's a failure because the capital "i" does not have crossbars... making it indistinguishable from a lower-case L. Such a tiresome defect in one font after another.
It's not a failure if it meets its stated goals. It's not trying to be a programmer's font, a terminal font, etc. It's specifically only trying to be a font for cockpit displays. On that front, there isn't really a context where I and l would be ambiguous in context. The only place I can think of would be waypoint names, but those are always all caps, so I and L don't present any problem. On the other hand, putting c…
So for example IATA and ICAO airport codes are not within the context of an airplane cockpit?
And the visual difference between "laa" and "Iaa" doesn't matter?
The first one is Lamar Municipal Airport, while the second one is Igarka Airport.
Welp, it's a failure because the capital "i" does not have crossbars... making it indistinguishable from a lower-case L. Such a tiresome defect in one font after another.
I wouldn't say it's indistinguishable - the lower case L has a curved bottom.
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…
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.
Yeah, that always bugged me! The zero-with-a-slash only seems to be used in that flight plan section of the screen; all of the other zeroes are without the slash. And the "5" and "4" next to the zero-with-a-slash in the waypoint 5240N is clearly the B612 glyphs. So it makes me think that in the Airbus software, in contexts where there might be ambiguity between 0 and O or where there are mixed letters and numbers, th…
When alphanumeric, put the slash, when only numeric leave it out?
Another font that has a similar aim is https://en.wikipedia.org/wiki/Atkinson_Hyperlegible I find that it strikes a balance between aesthetics and legibility. Two differences I noticed immediately are the 0 and I characters which are much more difficult to distinguish with this font.
Also noticed the slash in the 0 runs top left to bottom right, rather than the far-more-common [in my experience] top right to bottom left
Any idea why that decision was made?
Another font that has a similar aim is https://en.wikipedia.org/wiki/Atkinson_Hyperlegible I find that it strikes a balance between aesthetics and legibility. Two differences I noticed immediately are the 0 and I characters which are much more difficult to distinguish with this font.
That font does look really nice! Also noticed the slash in the 0 runs top left to bottom right, rather than the far-more-common [in my experience] top right to bottom left Any idea why that decision was made?