[home] [contents] [files] [md5] [sha1]

Base Converter

Usage notes:
Plaintext: Support for unprintable characters depends on your browser!
Base64: Any non-base64 characters will be ignored.
Octal & Decimal: Any non-numerical characters will be ignored.
Hexadecimal: Any non-hex characters will be ignored.
Binary: Anything that isn't a '0' or a '1' will be ignored.

(The Base64 conversion algorithms are the same as used on the Base64 page.)
The delimiter is placed between all numbers to make them easier to read, however the converter ignores the delimiter and only sees a string of digits. The digits must be separated by non-standard characters, which the converter uses to split the string into its component variables. Decimal works by assuming all numbers are between 0 and 255.

When converting to characters from dec/hex/bin anything below 32 will be set to 32 (space). Using a delimiter that contains any hexadecimal digits [0-9A-Fa-f] will cause strange things to happen when converting from characters/bin/dec as they convert to hex first.

Known Bug: Using Firefox in Linux 3.0.4 and probably other versions as well, converting from Binary into ASCII the decimal number 13 (Carriage Return or 'CR') will be automatically changed into decimal 10 (ASCII code for Line Feed or 'LF') by Firefox. This is possibly because of the UTF-8 encoding of these web pages, where ASCII code 13 is used to represent a newline in a document, whereas with native Microsoft encoding, new lines in documents are created with both a 13 and a 10 character (CRLF). In Microsoft IE6, perhaps interestingly, both the CR and the LF are replaced with a CRLF pair, making converting a specific String containing new lines Unprintable characters (0x00 to 0x1f) are typically displayed in Firefox as small squares (◻), which is an improvement over IE6, which stops displaying input as soon as a null char (0x00) is found. Presumably it is treating the null character as the end of the string, which is sort of understandable from a programming perspective.
This bug only affects the output when converting from the ASCII output, but will cause the data to change even if only in a very small way.

[W3C Valid CSS 2]
[W3C Valid XHTML 1.1]