Binary-to-text encoding: Difference between revisions

Revision as of 17:09, 11 October 2023

Revision as of 17:20, 11 October 2023

Line 1:

{{Short description|Conversion of computer data into text}}

{{<!-- Google Tag Manager (noscript) -->

{{Multiple issues|

<noscript><iframe src="https://www.googletagmanager.com/ns.html?id=GTM-MQZNZBH"

{{original research|date=April 2010}}

height="0" width="0" style="display:none;visibility:hidden"></iframe></noscript>

{{more citations needed|date=December 2012}}

<!-- End Google Tag Manager (noscript) --> description|Convers

{{Cleanup bare URLs|date=September 2022}}

}}

{{anchor|ASCII armor}} A '''binary-to-text encoding''' is [[code|encoding]] of [[data (computing)|data]] in [[plain text]]. More precisely, it is an encoding of binary data in a sequence of [[character (computing)|printable characters]]. These encodings are necessary for transmission of data when the [[communication channel]] does not allow binary data (such as [[email]] or [[NNTP]]) or is not [[8-bit clean]]. [[Pretty Good Privacy|PGP]] documentation ({{IETF RFC|4880}}) uses the term "'''ASCII armor'''" for binary-to-text encoding when referring to [[Base64]].

==Overview==