Timeline for Why do some fonts make I, l, 1 look the same?
Current License: CC BY-SA 3.0
15 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 9, 2022 at 1:15 | comment | added | MicroMachine | @Vikki but how does one know which one is which if the glyphs are identical? Even if there’s just one? You can still confuse l0BJ632 and 1OBJ632… | |
| Feb 9, 2022 at 0:56 | comment | added | Vikki | @MicroMachine: Don't license plates (for instance) only allow 1 xor I and 0 xor O, not both members of either pair? | |
| Dec 3, 2019 at 4:04 | comment | added | MicroMachine | The real question would be, why is it legal to use homoglyphs on the numbers of important printed documents (such as ID) - which invariably make people input the wrong codes? A good rule would be to generate codes that rule out 1, I and l and 0/O... | |
| Oct 12, 2019 at 14:46 | review | Suggested edits | |||
| Oct 12, 2019 at 19:27 | |||||
| May 29, 2016 at 1:30 | history | protected | user9447 | ||
| Aug 17, 2014 at 17:38 | comment | added | supercat |
Some of the worst offenders historically were the Monaco bitmap fonts which shipped with the Macintosh. Curiously, the fonts were included in the System file, but the Macintosh would use fonts stored in ROM instead of those in System unless the file also contained a rOvr resource. Monaco was on many machines the only monospaced font, and it used identical glyphs for I and l, as well as for O and 0.
|
|
| Jul 8, 2013 at 3:50 | vote | accept | Frames Catherine White | ||
| May 2, 2012 at 23:10 | vote | accept | Frames Catherine White | ||
| Nov 19, 2012 at 11:23 | |||||
| Apr 27, 2012 at 20:14 | comment | added | Lauren-Clear-Monica-Ipsum | I always thought they just hated the abbreviation for Illinois (Ill). | |
| Apr 27, 2012 at 20:12 | history | tweeted | twitter.com/#!/StackDesign/status/195968632478633984 | ||
| Apr 27, 2012 at 20:07 | answer | added | DA01 | timeline score: 19 | |
| Apr 27, 2012 at 18:46 | history | edited | Farray |
edited tags
|
|
| Apr 27, 2012 at 18:16 | history | migrated | from ux.stackexchange.com (revisions) | ||
| Apr 27, 2012 at 16:16 | comment | added | Myrddin Emrys | Arial, one of the most common current culprits, was designed for a computer, so it can't be explained with printing-press explanations. It's incredibly frustrating to deal with logins that contain ambiguous characters. I'm just glad when I have control of the font used to display vital information. | |
| Apr 27, 2012 at 16:08 | history | asked | Frames Catherine White | CC BY-SA 3.0 |