Transfer Encodings

From Just Solve the File Format Problem
(Difference between revisions)
Jump to: navigation, search
m (See also)
(One intermediate revision by one user not shown)
Line 14: Line 14:
 
* [[Base58]]
 
* [[Base58]]
 
* [[Base64]]
 
* [[Base64]]
 +
* [[Base-122]]
 
* [[BinHex]] (.hqx)
 
* [[BinHex]] (.hqx)
 
* [[Crockford Base32]]
 
* [[Crockford Base32]]
Line 23: Line 24:
 
* [[Xxencoding]]
 
* [[Xxencoding]]
 
* [[yEnc]]
 
* [[yEnc]]
 +
* [[Z85]]
  
 
== Related/Uncategorized ==
 
== Related/Uncategorized ==
Line 35: Line 37:
 
== See also ==
 
== See also ==
 
* [[E-Mail, newsgroups, and forums#Transfer Encodings|E-Mail, newsgroups, and forums: Transfer Encodings]]
 
* [[E-Mail, newsgroups, and forums#Transfer Encodings|E-Mail, newsgroups, and forums: Transfer Encodings]]
* [[Archiving#Transfer encodings|Archiving: Transfer encodings]]
+
* [[Archiving#Transfer formats]]
 
* [[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 16:40, 11 November 2018

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

Transfer encodings

Related/Uncategorized

See also

Links

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox