Category:LSL Base64 - Revision history

Strife Onizuka at 06:12, 25 June 2013

2013-06-25T06:12:51Z

← Older revision		Revision as of 23:12, 24 June 2013
Line 22:		Line 22:
	\|AAAwOQ==		\|AAAwOQ==
	\|}		\|}

			== Deprecated Functions ==
			There are several Base64 XOR functions in LSL. [[llXorBase64]] is the latest. Deprecated implementations include [[llXorBase64Strings]] and [[llXorBase64StringsCorrect]]. The big difference between the various versions is how they handle NULL characters.

Strife Onizuka: /* Examples */ link ^_^

2012-10-22T21:10:47Z

Examples: link ^_^

← Older revision		Revision as of 14:10, 22 October 2012
Line 19:		Line 19:
	\|4pOQ4pOR4pOS4pOT4pOU		\|4pOQ4pOR4pOS4pOT4pOU
	\|-		\|-
	\|12345 (as an integer)		\|12345 (as an [[llIntegerToBase64\|integer]])
	\|AAAwOQ==		\|AAAwOQ==
	\|}		\|}

Ibrew Meads: Added a description of Base64.

2012-10-22T01:55:58Z

Added a description of Base64.

← Older revision		Revision as of 18:55, 21 October 2012
Line 1:		Line 1:
	{{LSL Header\|ml=*}}{{LSLC\|}}{{LSLC\|Encoding}}		{{LSL Header\|ml=*}}{{LSLC\|}}{{LSLC\|Encoding}}
			== About Base64 encoding ==
			Base64 conversion expands three bytes of arbitrary binary data into four bytes of common ASCII characters in a completely reversible algorithm. It is generally used to convert binary data to strings so they can be sent across a text interface where ASCII control characters might be misinterpreted as end of string (\0) newline (\n) or otherwise not be transferred properly to the receiving process. In LSL this might be used to store binary data in an object's description, break data into bytes for cryptographic processing, or send data from one process to another using chat or linked messages.

			Base64 input can be any sequence of bytes, the output consists exclusively of uppercase and lowercase letters, digits and the plus (+), slash (/) and equals (=) characters. Conversion to Base64 is done in blocks of three bytes (24 bits), padded if needed. These twenty-four bits are split into four six bit numbers which become an index to the conversion key ("ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/") and written out as the eight bit ASCII character. Since the data is converted three bytes at a time, zero one or two equals characters are added to indicate how much padding was done in the last block. See [http://en.wikipedia.org/wiki/Base64 the Wikipedia article] for more information.

			== Examples ==
			String and integer data in Base64.
			<div align="left">
			{\| style="border:1px solid #A3B1BF; text-align:left; background:#f5faff"
			\|-
			\| width="50%" style="background: #cee0f2; padding: 0.3em; text-align:center;"\|'''Text'''
			\| style="background: #cee0f2; padding: 0.3em; text-align:center;"\|'''Base64'''
			\|-
			\|Abcde
			\|QWJjZGU=
			\|-
			\|ⓐⓑⓒⓓⓔ
			\|4pOQ4pOR4pOS4pOT4pOU
			\|-
			\|12345 (as an integer)
			\|AAAwOQ==
			\|}

Strife Onizuka at 22:06, 24 October 2008

2008-10-24T22:06:43Z

← Older revision		Revision as of 15:06, 24 October 2008
Line 1:		Line 1:
	{{LSL Header}}{{LSLC\|}}{{LSLC\|Encoding}}		{{LSL Header\|ml=*}}{{LSLC\|}}{{LSLC\|Encoding}}

Strife Onizuka: New page: {{LSL Header}}{{LSLC|}}{{LSLC|Encoding}}

2007-06-08T15:11:43Z

New page: {{LSL Header}}{{LSLC|}}{{LSLC|Encoding}}

New page