Base32
From Just Solve the File Format Problem
(Difference between revisions)
(Created page with "{{FormatInfo |formattype=electronic |subcat=Transfer Encodings }} Base32 is a family of binary-to-text encodings which use an alphabet of 32 symbols. Such encodings usuall...") |
Dan Tobias (Talk | contribs) |
||
| Line 6: | Line 6: | ||
In particular, it usually refers to the Base32 encoding defined in RFC 4648, which uses the following symbols (along with <code>=</code>, for padding): | In particular, it usually refers to the Base32 encoding defined in RFC 4648, which uses the following symbols (along with <code>=</code>, for padding): | ||
| − | ABCDEFGHIJKLMNOPQRSTUVWXYZ234567 | + | <code>ABCDEFGHIJKLMNOPQRSTUVWXYZ234567</code> (although other alphabets have also been used for similar encodings). People deciding on alphabets for such encodings often skip letters and numbers that are easily confused, such as number 1, letter I, and lowercase letter l. |
== See also == | == See also == | ||
Revision as of 16:05, 28 May 2019
Base32 is a family of binary-to-text encodings which use an alphabet of 32 symbols. Such encodings usually use ASCII letters and digits, and are case-insensitive.In particular, it usually refers to the Base32 encoding defined in RFC 4648, which uses the following symbols (along with =, for padding):
ABCDEFGHIJKLMNOPQRSTUVWXYZ234567 (although other alphabets have also been used for similar encodings). People deciding on alphabets for such encodings often skip letters and numbers that are easily confused, such as number 1, letter I, and lowercase letter l.
See also
Links
- Wikipedia: Base32
- RFC 3548: The Base16, Base32, and Base64 Data Encodings (obsolete)
- RFC 4648: The Base16, Base32, and Base64 Data Encodings
