3 ms·
Well, I would say that some types like "eight-bit character in ISO-8859-1 encoding" is a monumentally stupid idea in this day and age (and yes, I live in 8859-2
by mcepl 10y ago
Well, I would say that some types like "eight-bit character in ISO-8859-1 encoding" is a monumentally stupid idea in this day and age (and yes, I live in 8859-2 area, but that isn't the point … http://www.joelonsoftware.com/articles/Unicode.html http://www.joelonsoftware.com/articles/Unicode.html).
- Someone 10y agoI would have written PETSCII, EBCDIC or shift-JIS instead, but feared few users would understand it. Not everybody writes new stuff; some software has to interface with stuff written decades ago. Also, even for software 100% written today it often is impossible to stay in a world where all strings use compatible encodings. Examples where you need conversions: when connecting systems that support different Unicode versions or when generating http headers, windows file names, or QR codes. I guess many 'older' systems will not handle ZIP or tar files that use UTF-8 for file names in the archive, either.