Base32 is a derivation of Base64 with the following additional properties: In computing, base64 is a data encoding scheme whereby binary-encoded data is converted to printable ASCII characters. ...
The resulting character set is all uppercase, which can often be beneficial when using a case-sensitive filesystem.
The result can be included in a URL without escaping any characters.
It is a notation for expressing large numbers in a form that can be conveniently and accurately transmitted between humans and computer systems. A character encoding is a code that pairs a set of characters (such as an alphabet or syllabary) with a set of something else, such as numbers or electrical pulses. ... See Filing system for this term as it is used in libraries and offices In computing, a file system is a method for storing and organizing computer files and the data they contain to make it easy to find and access them. ... A Uniform Resource Locator, URL (either pronounced as earl (IPA: [ɜː˞l]; SAMPA: [3:`l]) or spelled out), or Web address, is a standardized address for some resource (such as a document or image) on the Internet (or elsewhere). ...
Base32 (http://www.crockford.com/wrmg/base32.html) NOTE: this is an alternate Base32 encoding scheme. The alphabet found at this link does NOT match RFC3548!
Similar to Base64, Base32 encodes arbitrary (binary) data in ASCII text.
The difference to Base64 is that Base32 encoding is case insensitive.
Base32 is defined in rfc3548 using the characters [A-Z2-7], but this module by default uses [0-9A-V] for compatibility with older versions of MIME::Base32.
In the base32 alphabet below, where 0 (zero) and 1 (one) are not present, a decoder may interpret 0 as O, and 1 as I or L depending on case.
This encoding should not be regarded as the same as the "base32" encoding and should not be referred to as only "base32".
One property with this alphabet, which the base64 and base32 alphabets lack, is that encoded data maintains its sort order when the encoded data is compared bit-wise.