Transfer Encodings
From Just Solve the File Format Problem
(Difference between revisions)
(→Transfer encodings) |
(→Transfer encodings) |
||
| (One intermediate revision by one user not shown) | |||
| Line 15: | Line 15: | ||
* [[Base64]] | * [[Base64]] | ||
* [[Base-122]] | * [[Base-122]] | ||
| + | * [[Base65536]] [https://github.com/qntm/base65536] | ||
* [[BinHex]] (.hqx) | * [[BinHex]] (.hqx) | ||
* [[BWTC32Key]] | * [[BWTC32Key]] | ||
| Line 28: | Line 29: | ||
== Related/Uncategorized == | == Related/Uncategorized == | ||
| + | * [[AR7]] | ||
* [[Binary II]] (.bny) (for Apple II series) (often [[squeeze]]d as .bqy) | * [[Binary II]] (.bny) (for Apple II series) (often [[squeeze]]d as .bqy) | ||
* [[MacBinary]] | * [[MacBinary]] | ||
Revision as of 14:49, 12 October 2020
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
- ASCII Encoded HP 48 Object (ASC)
- Ascii85 (Base85)
- Base32
- Base58
- Base64
- Base-122
- Base65536 [1]
- BinHex (.hqx)
- BWTC32Key
- Crockford Base32
- Hex encoding (Base16)
- Percent-encoding
- Quoted-printable
- UTF-7
- Uuencoding
- 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
