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 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.
Still a worthy bug to be submitted.
Re:B612 Font Family
by throw0101b on Friday September 15, 2023 @07:06AM
(#37521223)
The workflow to fix things doesn't seem clear - are people supposed to work on the .glif files?
The hero we need but don't deserve.
does it have to do with "knowing" whether the data being displayed is numeric vs alphanumeric?
When alphanumeric, put the slash, when only numeric leave it out?
Re:B612 Font Family
by ungamedplayer on Saturday September 16, 2023 @02:23AM
(#37532475)
Can't wait for a font renderer to get this smart. Any day now...
> 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.
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’
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.