Transfer Encodings
From Just Solve the File Format Problem
(Difference between revisions)
(→Transfer encodings) |
Dan Tobias (Talk | contribs) (→Related/Uncategorized) |
||
| (One intermediate revision by one user not shown) | |||
| Line 22: | Line 22: | ||
* [[Base2048]] [https://github.com/qntm/base2048] | * [[Base2048]] [https://github.com/qntm/base2048] | ||
* [[Base65536]] [https://github.com/qntm/base65536] | * [[Base65536]] [https://github.com/qntm/base65536] | ||
| + | * [[Bencode (Quinton/Lalonde)]] | ||
* [[BinHex]] (.hqx) | * [[BinHex]] (.hqx) | ||
* [[BOO (binary-to-text encoding)|BOO]] | * [[BOO (binary-to-text encoding)|BOO]] | ||
* [[BWTC32Key]] | * [[BWTC32Key]] | ||
* [[BXP]] | * [[BXP]] | ||
| + | * [[c7encode]] | ||
* [[Code91]] | * [[Code91]] | ||
* [[Crockford Base32]] | * [[Crockford Base32]] | ||
| Line 52: | Line 54: | ||
* [[Transport Neutral Encapsulation Format]] (TNEF; winmail.dat) | * [[Transport Neutral Encapsulation Format]] (TNEF; winmail.dat) | ||
* [[URL encoding]] | * [[URL encoding]] | ||
| + | * [[XX]] (format for representing binary data in text form) | ||
== See also == | == See also == | ||
| Line 57: | Line 60: | ||
* [[E-Mail, newsgroups, and forums#Transfer Encodings]] | * [[E-Mail, newsgroups, and forums#Transfer Encodings]] | ||
* [[Executable envelopes#Transfer-encoded executables]] | * [[Executable envelopes#Transfer-encoded executables]] | ||
| + | * [[File transfer]] | ||
* [[Serialization]] | * [[Serialization]] | ||
== Links == | == Links == | ||
* [[Wikipedia:Binary-to-text encoding|Wikipedia: Binary-to-text encoding]] | * [[Wikipedia:Binary-to-text encoding|Wikipedia: Binary-to-text encoding]] | ||
Revision as of 15:57, 27 December 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
- ABE
- ASCIFY
- ASCII Encoded HP 48 Object (ASC)
- Ascii85 (Base85)
- Asteroid
- Base32
- Base45 [1]
- Base58
- Base64
- Base-122
- Base2048 [2]
- Base65536 [3]
- Bencode (Quinton/Lalonde)
- BinHex (.hqx)
- BOO
- BWTC32Key
- BXP
- c7encode
- Code91
- Crockford Base32
- crzy64 [4]
- Hex encoding (Base16)
- Percent-encoding
- Quoted-printable
- Ship
- TTCODE
- UBX
- 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
- XX (format for representing binary data in text form)
See also
- Archiving#Transfer formats
- E-Mail, newsgroups, and forums#Transfer Encodings
- Executable envelopes#Transfer-encoded executables
- File transfer
- Serialization
