Transfer Encodings

From Just Solve the File Format Problem
(Difference between revisions)
Jump to: navigation, search
(Transfer encodings)
(Transfer encodings)
Line 9: Line 9:
  
 
== Transfer encodings ==
 
== Transfer encodings ==
 +
* [[2ASCII]]
 
* [[ASCII Encoded HP 48 Object]] (ASC)
 
* [[ASCII Encoded HP 48 Object]] (ASC)
 
* [[Ascii85]] (Base85)
 
* [[Ascii85]] (Base85)
 +
* [[Asteroid]]
 
* [[Base32]]
 
* [[Base32]]
 
* [[Base45]] [https://datatracker.ietf.org/doc/draft-faltstrom-base45/]
 
* [[Base45]] [https://datatracker.ietf.org/doc/draft-faltstrom-base45/]
Line 21: Line 23:
 
* [[BOO (binary-to-text encoding)|BOO]]
 
* [[BOO (binary-to-text encoding)|BOO]]
 
* [[BWTC32Key]]
 
* [[BWTC32Key]]
 +
* [[Code91]]
 
* [[Crockford Base32]]
 
* [[Crockford Base32]]
 
* [[crzy64]] [https://github.com/ilyakurdyukov/crzy64]
 
* [[crzy64]] [https://github.com/ilyakurdyukov/crzy64]
Line 26: Line 29:
 
* [[Percent-encoding]]
 
* [[Percent-encoding]]
 
* [[Quoted-printable]]
 
* [[Quoted-printable]]
 +
* [[Ship (encoding)|ship]]
 +
* [[TTCODE]]
 
* [[UTF-7]]
 
* [[UTF-7]]
 
* [[Uuencoding]]
 
* [[Uuencoding]]
 +
* [[XX34]]
 +
* [[XXBUG]]
 
* [[Xxencoding]]
 
* [[Xxencoding]]
 
* [[yEnc]]
 
* [[yEnc]]

Revision as of 15:32, 29 August 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

Transfer encodings

Related/Uncategorized

See also

Links

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox