Transfer Encodings

From Just Solve the File Format Problem
(Difference between revisions)
Jump to: navigation, search
(See also)
(Transfer encodings)
 
(One intermediate revision by one user not shown)
Line 16: Line 16:
 
* [[Base64]]
 
* [[Base64]]
 
* [[Base-122]]
 
* [[Base-122]]
 +
* [[Base2048]] [https://github.com/qntm/base2048]
 
* [[Base65536]] [https://github.com/qntm/base65536]
 
* [[Base65536]] [https://github.com/qntm/base65536]
 
* [[BinHex]] (.hqx)
 
* [[BinHex]] (.hqx)
Line 21: Line 22:
 
* [[BWTC32Key]]
 
* [[BWTC32Key]]
 
* [[Crockford Base32]]
 
* [[Crockford Base32]]
 +
* [[crzy64]] [https://github.com/ilyakurdyukov/crzy64]
 
* [[Hex encoding]] (Base16)
 
* [[Hex encoding]] (Base16)
 
* [[Percent-encoding]]
 
* [[Percent-encoding]]

Latest revision as of 18:18, 10 May 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