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.
And I wonder if there's a 0-with-a-slash in the downloadable version of the font, enabled with an OpenType stylistic set number or feature or something, or if that zero-with-a-slash is just something custom the Airbus folks do internally.
But more generally the font has an empty GSUB table which would be used for such substitutions. I'm wondering if the cockpit display maybe misses support for that and that's why they tried not to use it for anything.
When alphanumeric, put the slash, when only numeric leave it out?
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’
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...
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.