It looks like you've got a bone to pick with them not having agreed with you. I had a look at your Github issue and I agree that this is down to your _system_ not the application; your screenshots don't demonstrate the problem either.
It’s not a bug with the app, but the OP’s is a reasonable feature request.
The ability to specify an unambiguous font for password fields, for example, makes absolute sense.
And the app defaulting to the monospace font is not an appropriate solution, because a user may pick a monospace default which isn’t unambiguous. Not every app requires unambiguity the way a password field might, so to require the user to change their default font is not a great solution.
There’s a reason emacs, vim, etc allow you to set your own fonts specific to the app that’s different from your DE defaults. That’s because they have very specific requirements that may be different from what you’re looking for in a general default font for your DE. The same is true for something like the password field of a password manager app.
Honestly, certain devs in this case started insulting the OP well before the OP said anything unreasonable, probably because for some reason they came up with the idea that the OP thought this was a heinous bug when, as they clarified, that was an invention on the reader’s part with no grounding in anything the OP said, who was not calling it a bug, nor by any means calling it heinous. Of course the discussion went off the rails after that with the OP unnecessarily getting personal, but I can see where their frustration came from even if they shouldn’t really have acted on it.
It's very rare that you need to disambiguate letters. My handwriting only disambiguates words of you accept contextual clues, and even then ...
Stylistic considerations, some of which ride on centuries of history, overriding information transfer is extremely common (that's not an excuse, more an observation). Just look at how this site [HN] uses gradual desaturation to convey downvotes, abysmal UX, but the designer clearly felt it was fit for purpose.
Comments
It looks like you've got a bone to pick with them not having agreed with you. I had a look at your Github issue and I agree that this is down to your _system_ not the application; your screenshots don't demonstrate the problem either.
It’s not a bug with the app, but the OP’s is a reasonable feature request.
The ability to specify an unambiguous font for password fields, for example, makes absolute sense.
And the app defaulting to the monospace font is not an appropriate solution, because a user may pick a monospace default which isn’t unambiguous. Not every app requires unambiguity the way a password field might, so to require the user to change their default font is not a great solution.
There’s a reason emacs, vim, etc allow you to set your own fonts specific to the app that’s different from your DE defaults. That’s because they have very specific requirements that may be different from what you’re looking for in a general default font for your DE. The same is true for something like the password field of a password manager app.
Honestly, certain devs in this case started insulting the OP well before the OP said anything unreasonable, probably because for some reason they came up with the idea that the OP thought this was a heinous bug when, as they clarified, that was an invention on the reader’s part with no grounding in anything the OP said, who was not calling it a bug, nor by any means calling it heinous. Of course the discussion went off the rails after that with the OP unnecessarily getting personal, but I can see where their frustration came from even if they shouldn’t really have acted on it.
What is the point of ambiguous fonts anyways? I never had a use for them.
It's very rare that you need to disambiguate letters. My handwriting only disambiguates words of you accept contextual clues, and even then ...
Stylistic considerations, some of which ride on centuries of history, overriding information transfer is extremely common (that's not an excuse, more an observation). Just look at how this site [HN] uses gradual desaturation to convey downvotes, abysmal UX, but the designer clearly felt it was fit for purpose.
If your are typing a password manually, it's helpful if the font you're using makes it very clear when the character is 0 vs O, or l vs I vs 1
What I was asking is why would you design a font that makes it easy to confuse iIl|1O0, etc... we need to get rid of those fonts.
Oh, yep, I misread your question as asking about the need for "unambiguous" fonts.