61–70 of 99 posts
I tried out the monospace font for terminal use, but some of the punctuation characters have terrible spacing, including : and ., so things like abc::xyz and some_expression .method() .method(); look awful.
Maybe that's on purpose to discourage airplane pilots from coding their own JS scripts inside the plane.
Earlier quoted context omitted.
Discussed in other comments... but the zero-with-slash is only used in the flight plan section of that display; all of the other zeros are without the slash. It seems they only use the zero-with-slash where there might be a risk of ambiguity between 0 and O... everywhere else where it's just numeric readouts, there's no slash because there's no risk of confusion, and I'm guessing they decided zero-with-slash is more…
> and I'm guessing they decided zero-with-slash is more visually ugly/less intuitive for quickly reading numbers than zero-without-slash. Yes, it can be confused with 8.
0 and O look almost exactly the same in the font, is the distinction of these not important on flight screens?
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…
According to the Github issue mentioning in a sibling comment:
> We designed the two zeros having in mind the slash one to be used in alphanumerical sequences, and the normal one to be used in numerical sequences. > > You can find it in the ‘private use area’
0 and O look almost exactly the same in the font, is the distinction of these not important on flight screens?
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.
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.
It’s very unfortunate that these glyphs are not available via OT features or font-variant in CSS. I assume the cockpit software uses glyphs directly instead of using OpenType. 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-5…
The only user who's demonstrated merge rights on the repo is the repo's Eclipse Foundation project lead, Laurent Spaggiari: https://projects.eclipse.org/content/laurent-spaggiari-proje...
Who's the only listed contributor on the repo: https://github.com/polarsys/b612/blob/master/CONTRIBUTORS.tx...
And who's been publicly inactive on GitHub since the repo's last merge in March 2019: https://github.com/LaurentSpaggiari?tab=overview&from=2019-0...
I don't think any amount of tooling knowledge could facilitate a contribution at this point. It's a dead project. The best anyone could do is apply the steps in issue #24 to a fork and start promoting it.