[ilc]

Aviation use. They won't allow O and 0 to be valid for the same data.

So there is no need to disambiguate them.

[illamint]

It's funny, though, there's literally an example of this in the picture located on the ENAC project page for this font in the flight plan screen:

https://lii.enac.fr/projects/definition-and-validation-of-an...

Also seems to be more discussion of this point the last time this was posted:

https://news.ycombinator.com/item?id=37519166

It also seems like there's a "slashed zero" glyph in the font, though I don't know how to actually type it:

https://github.com/polarsys/b612/blob/master/sources/ufo/B61...

[cge]

It's confusing and certainly non-standard, but rather than using a variant for this, the slashed zero is U+E007, in a private use area.

There seems to be an unofficial variant here that might be more useful for coding: https://github.com/carlosedp/b612

[masfuerte]

I don't know how this font is encoded, but it's often the case in modern fonts that variant glyphs are mapped to the same code point (i.e. U+0030 in this case) so you can't directly type the variants. If you want to use them then your software needs to understand how to select font features.

In CSS you can use font-feature-settings.

https://developer.mozilla.org/en-US/docs/Web/CSS/@font-face/...

[ilc]

The first pic shows the slashed 0, which is what I'd expect if there's any chance of confusion.

But in general, aviation is pretty paranoid over this stuff.