Binary-to-text encoding: Difference between revisions

Revision as of 14:48, 9 March 2023

Revision as of 17:25, 9 March 2023

Line 1:

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

��NrٰB)SS��@�����cG)D�v�x�\��.����4���۔�n`������k�����ɇ�6U��ä�P���P/�

{{Multiple issues|

��*]�掾/~y��%ᄽ/ �"Ť��h�Ү��Moi�Ē��,� o���3�������ٞ�)#��tG�Y�m���.J���x�nj��u���4������]5n.B����_l�����ɇ�8U���u,P���&���-�k]�ꎾ�~y��%儽/ � %eM�)��\1Z:o�U���ȏ����Џ�R��N�ΰ��S�G\����m�G>��v�x�

{{original research|date=April 2010}}

{{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 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==