Transfer Encodings

From Just Solve the File Format Problem
(Difference between revisions)
Jump to: navigation, search
(Transfer encodings)
 
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 57: Line 59:
 
* [[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]]

Latest revision as of 15:43, 18 September 2022

File Format
Name Transfer Encodings
Ontology

{{{caption}}}

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

[edit] Transfer encodings

[edit] Related/Uncategorized

[edit] See also

[edit] Links

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox