4 ms·
This is why even some of ASCII is a mistake, maybe we shouldn't even bother with case. Every time something like this comes about I just get more cynical about
by microcolonel 9y ago
This is why even some of ASCII is a mistake, maybe we shouldn't even bother with case.
Every time something like this comes about I just get more cynical about the complexity of multilingual systems, or systems with interesting typesetting routines.
- jstimpfle 9y agoASCII is very well defined. Control characters were needed at the time (and still are today, if you're using a terminal emulator). It's easy to handle, just disallow < 32 and > 127, which are invalid or non-printable chars (but think about tab/cr/lf). Basically every font you can find can display all of the ASCII printable range without room for confusion.
- colejohnson66 9y agoWhat ASCII characters are a mistake? If we required all apps to only use characters in the ASCII charset (the 127 codepoint one, not the Windows-1291 "ASCII" garbage), these tricks wouldn’t work.
- irl_zebra 9y agoThe poster said some ascii is a mistake. I’m assuming those chars that don’t translate to much/anything.
- colejohnson66 9y agoLike basically anything in the 0x1 to 0x1F range?