Transfer Encodings
From Just Solve the File Format Problem
(Difference between revisions)
(→Transfer encodings) |
(→Transfer encodings) |
||
| Line 23: | Line 23: | ||
* [[BOO (binary-to-text encoding)|BOO]] | * [[BOO (binary-to-text encoding)|BOO]] | ||
* [[BWTC32Key]] | * [[BWTC32Key]] | ||
| + | * [[BXP]] | ||
* [[Code91]] | * [[Code91]] | ||
* [[Crockford Base32]] | * [[Crockford Base32]] | ||
Revision as of 17:26, 1 September 2022
A transfer encoding is a method of reversibly transforming data so that it uses a reduced set of bytes (or other symbols), to make it compatible with a protocol or format that does not allow all possible byte values.
It's not clear how common the term transfer encoding is. Web searches for it are useless, due to noise from the HTTP Transfer-Encoding and MIME Content-Transfer-Encoding headers.
Contents |
Transfer encodings
- 2ASCII
- ASCII Encoded HP 48 Object (ASC)
- Ascii85 (Base85)
- Asteroid
- Base32
- Base45 [1]
- Base58
- Base64
- Base-122
- Base2048 [2]
- Base65536 [3]
- BinHex (.hqx)
- BOO
- BWTC32Key
- BXP
- Code91
- Crockford Base32
- crzy64 [4]
- Hex encoding (Base16)
- Percent-encoding
- Quoted-printable
- ship
- TTCODE
- UTF-7
- Uuencoding
- XX34
- XXBUG
- Xxencoding
- yEnc
- Z85
Related/Uncategorized
- AR7
- Binary II (.bny) (for Apple II series) (often squeezed as .bqy)
- MacBinary
- MIME
- PEM
- Punycode
- Transport Neutral Encapsulation Format (TNEF; winmail.dat)
- URL encoding
See also
- Archiving#Transfer formats
- E-Mail, newsgroups, and forums#Transfer Encodings
- Executable envelopes#Transfer-encoded executables
- Serialization
