Binary-to-text encoding: Difference between revisions

Content deleted Content added
hmmm just noticed they're red ... red links help Wikipedia grow but if we don't have an article about a computing topic by now, maybe we won't ever have one
No edit summary
Tags: Reverted Mobile edit Mobile web edit
Line 1:
{{<!-- Google Tag Manager (noscript) -->
{{Short description|Conversion of computer data into text}}
<noscript><iframe src="https://www.googletagmanager.com/ns.html?id=GTM-MQZNZBH"
{{Multiple issues|
height="0" width="0" style="display:none;visibility:hidden"></iframe></noscript>
{{original research|date=April 2010}}
<!-- End Google Tag Manager (noscript) --> description|Convers
{{more citations needed|date=December 2012}}
{{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==