EBCDIC

[4][failed verification] While IBM was a chief proponent of the ASCII standardization committee,[5] the company did not have time to prepare ASCII peripherals (such as card punch machines) to ship with its System/360 computers, so the company settled on EBCDIC.

[3] The System/360 became wildly successful, together with clones such as RCA Spectra 70, ICL System 4, and Fujitsu FACOM, thus so did EBCDIC.

All IBM's mainframe operating systems, and its IBM i operating system for midrange computers, use EBCDIC as their inherent encoding[6] (with toleration for ASCII, for example, ISPF in z/OS can browse and edit both EBCDIC and ASCII encoded files).

It exists in at least six mutually incompatible versions, all featuring such delights as non-contiguous letter sequences and the absence of several ASCII punctuation characters fairly important for modern computer languages (exactly which characters are absent varies according to which version of EBCDIC you're looking at).

IBM adapted EBCDIC from punched card code in the early 1960s and promulgated it as a customer-control tactic (see connector conspiracy), spurning the already established ASCII standard.

One such joke, found in the Unix fortune file of 4.3BSD Reno (1990)[24] went: Professor: "So the American government went to IBM to come up with an encryption standard, and they came up with—"Student: "EBCDIC!

"References to the EBCDIC character set are made in the 1979 computer game series Zork.

A customer insisted that the correct spelling of his surname included an umlaut, which the bank omitted, and the customer filed a complaint citing the guarantee in the General Data Protection Regulation of the right to timely "rectification of inaccurate personal data."

The bank's argument included the fact that their system used EBCDIC, as well as that it did not support letters with diacritics (or lower case, for that matter).