Binary-to-text encoding: Difference between revisions

Revision as of 07:14, 5 June 2024

Revision as of 20:57, 10 June 2024

Line 3:

{{original research|date=April 2010}}

{{more citations needed|date=December 2012}}

{{Cleanup bare URLs|date=September 2022}}

}}

Line 113 ⟶ 112:

Some encodings (the original version of BinHex and the recommended encoding for [[CipherSaber]]) use four bits instead of six, mapping all possible sequences of 4 bits onto the 16 standard [[hexadecimal]] digits. Using 4 bits per encoded character leads to a 50% longer output than base64, but simplifies encoding and decoding—expanding each byte in the source independently to two encoded bytes is simpler than base64's expanding 3 source bytes to 4 encoded bytes.

Out of [[PETSCII]]'s first 192 codes, 164 have visible representations when quoted: 5 (white), 17–20 and 28–31 (colors and cursor controls), 32–90 (ascii equivalent), 91–127 (graphics), 129 (orange), 133–140 (function keys), 144–159 (colors and cursor controls), and 160–192 (graphics).<ref>http{{Cite web |title=Commodore 64 PETSCII codes |url=https://sta.c64.org/cbm64pet.html et al|website=sta.c64.org}}</ref> This theoretically permits encodings, such as base128, between PETSCII-speaking machines.

== See also ==