News for hackers. Stuff that matters.
Re:Strings – Dive Into Python 3 by Roboprog on Friday May 10, 2013 @12:15PM (#5687022)
And, he didn't even touch on the horror that is EBCDIC. Once you've had to touch that, the idea of "code point" for a character is something you can't ignore, hoping that things just work "most of the time" -- ASCII A != EBCDIC A.
Re:Strings – Dive Into Python 3 by reeses on Tuesday May 14, 2013 @05:31PM (#5708378)
EBCDIC A != EBCDIC A :-)

It's easier to read text on punchcards in EBCDIC of whatever variation, though.

Re:Strings – Dive Into Python 3 by sluu99 on Friday May 10, 2013 @12:24PM (#5687077)
Are there still (many) of people using EBCDIC?
Re:Strings – Dive Into Python 3 by Roboprog on Friday May 10, 2013 @12:27PM (#5687097)
Yes. High volume printing is often done using IBM's AFP/MODCA print language, which typically has the text in IBM's EBCDIC encoding.

(disclosure: I once worked at a company that made tools to port code and data from IBM minicomputers to Unix & MS platforms, and also at the largest [format,] print & mail shop in the US)

Re:Strings – Dive Into Python 3 by Roboprog on Friday May 10, 2013 @12:25PM (#5687085)
Or the 6 bit funky set that the old CDC Cyber mainframes used to use! ("What is this lower case 'a' you speak of???")