←back to thread

181 points Bogdanp | 1 comments | | HN request time: 0.001s | source
Show context
java-man ◴[] No.45116823[source]
I don't understand why 0 and O look nearly identical.
replies(6): >>45116919 #>>45116926 #>>45116930 #>>45116937 #>>45117008 #>>45117796 #
ilc ◴[] No.45116930[source]
Aviation use. They won't allow O and 0 to be valid for the same data.

So there is no need to disambiguate them.

replies(1): >>45117076 #
illamint ◴[] No.45117076[source]
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...

replies(3): >>45118095 #>>45118253 #>>45119274 #
1. ilc ◴[] No.45118095{3}[source]
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.