3 ms·
Didn’t extended ASCII cover that and make text terminals usable with non-English character sets? Genuinely curious.
by geenew 5y ago
Didn’t extended ASCII cover that and make text terminals usable with non-English character sets? Genuinely curious.
- skrebbel 5y agoHow would you use extended-ascii to write Arabic?
- superjan 5y agoThe following was actually used: https://www.charset.org/charsets/iso-8859-6 https://www.charset.org/charsets/iso-8859-6 There’s no single byte encoding for Chinese, Japanese, or Korean though.
- enqk 5y agoIn practice, young folks write arabic with roman script when they chat. (with numbers to supplement the missing letters)
- qsort 5y agoExtended ASCII was actually several different and incompatible encoding, "codepages". It was kind of a solution, but there were major issues that made it much worse than Unicode/utf8: - Asian languages needed special encodings, 256 characters weren't sufficient. - It was impossible to work with different languages in the same document, each codepage only covered some character/alphabet. - There was no 'safe subset': Unicode codepoints 0-127 are exactly ASCII, which means that ASCII is compliant utf8. The same wasn't true at the time.