UrlDecodeUnicode and FormUrlDecodeUnicode (String functions) - Revision history

JAL at 23:05, 5 November 2012

2012-11-05T23:05:35Z

← Older revision		Revision as of 23:05, 5 November 2012
Line 5:		Line 5:
	{{Template:String:UrlDecodeUnicode syntax}}		{{Template:String:UrlDecodeUnicode syntax}}
	{{Template:String:FormUrlDecodeUnicode syntax}}		{{Template:String:FormUrlDecodeUnicode syntax}}

	===Syntax terms===		===Syntax terms===
	<table class="syntaxTable">		<table class="syntaxTable">
	<tr><th>%unicode</th><td>The <var>Unicode</var> variable that results when <var class="term">string</var> is decoded.</td></tr>		<tr><th>%unicode</th><td>The <var>Unicode</var> variable that results when <var class="term">string</var> is decoded.</td></tr>
	<tr><th>string</th><td>The [http://en.wikipedia.org/wiki/Utf-8 UTF-8 encoded] string that contains a URL encoded representation of a ~~unicode~~ string.</td></tr>
	<tr><th>~~boolean~~</th>		<tr><th>string</th>
	<td>~~Indicates~~ whether ~~unicode~~ characters that cannot be translated back to EBCDIC are to be allowed. If <var class="term">boolean</var> is set to <code>False</code> a ~~unicode~~ character that cannot be translated back to EBCDIC results in request cancellation.</td></tr>		<td>The [http://en.wikipedia.org/wiki/Utf-8 UTF-8 encoded] string that contains a URL-encoded representation of a Unicode string.</td></tr>

			<tr><th><var>AllowUntranslatable</var></th>
			<td>This optional, [[Notation conventions for methods#Named parameters\|name required]], argument indicates whether Unicode characters that cannot be translated back to EBCDIC are to be allowed. If <var class="term">boolean</var> is set to <code>False</code>, a Unicode character that cannot be translated back to EBCDIC results in request cancellation.</td></tr>
	</table>		</table>

	==Exceptions==		==Exceptions==

	<var>UrlDecodeUnicode</var> and <var>FormUrlDecodeUnicode</var> can throw the following exception:		<var>UrlDecodeUnicode</var> and <var>FormUrlDecodeUnicode</var> can throw the following exception:
	<dl>		<dl>
Line 21:		Line 25:

	==Usage notes==		==Usage notes==
			<ul>
			<li>If an EBCDIC version of URL-encoded data needs to be converted to Unicode, the EBCDIC string must be:
			<ol>
			<li>Assigned to a Unicode variable (using either implicit EBCDIC-to-Unicode translation or doing it explicitly with <var>[[EbcdicToUnicode (String function)\|EbcdicToUnicode]]</var>)
			<li>Converted to UTF-8 using <var>[[UnicodeToUtf8 (Unicode function)\|UnicodeToUtf8]]</var>
			<li>Translated to Unicode using <var>UrlDecodeUnicode</var>
			</ol>
			An example below illustrates this process.

			<li>The difference between <var>FormUrlDecodeUnicode</var> and <var>UrlDecodeUnicode</var> is that <var>FormUrlDecodeUnicode</var> converts pluses (<tt>+</tt>) to spaces, while <var>UrlDecodeUnicode</var> expects spaces to be percent encoded as <code>%20</code>. <var>UrlDecodeUnicode</var> will throw a <var>[[CharacterTranslationException class\|CharacterTranslationException]]</var> exception if it encounters a plus character. Typically form URL encoding is only used in HTML form posts when the form is posted using the <code>x-www-form-urlencoded</code> content type.

	~~<ul>~~
	<li>If an EBCDIC version of URL encoded data needs to be converted to unicode, the EBCDIC string must first be assigned to a unicode variable using either implicit EBCDIC to Unicode translation or doing it explicitly with <var>[[EbcdicToUnicode (String function)\|EbcdicToUnicode]]</var>, converted to UTF-8 using <var>[[UnicodeToUtf8 (Unicode function)\|UnicodeToUtf8]]</var>, and finally translated to unicode using <var>UrlDecodeUnicode. And example below illustrates this process.<li>The difference between <var>FormUrlDecodeUnicode</var> and <var>UrlDecodeUnicode</var> is that<var>FormUrlDecodeUnicode</var> converts pluses (<code>+</code>) to spaces while <var>UrlDecodeUnicode</var> expects spaces to be percent encoded as <code>%20</code>. <var>UrlDecodeUnicode</var> will throw a <var>[[CharacterTranslationException class\|CharacterTranslationException]]</var> exception if it encounters a plus (<code>+</code>). Typically form URL encoding is only used in HTML form posts when the form is posted using the x-www-form-urlencoded content type.
	<li>URL encoding is mostly used in web applications or for encoding a URI, possibly in an XML namespace declaration.		<li>URL encoding is mostly used in web applications or for encoding a URI, possibly in an XML namespace declaration.
	<li>The ~~inverse~~ of <var>UrlDecodeUnicode</var> and <var>FormUrlDecodeUnicode</var> are <var>[[UnicodeUrlEncode (Unicode function)\|UnicodeUrlEncode]]</var> and <var>[[UnicodeFormUrlEncode (Unicode function)\|UnicodeFormUrlEncode]]</var>, respectively.</ul>
			<li>The inverses of <var>UrlDecodeUnicode</var> and <var>FormUrlDecodeUnicode</var> are <var>[[UnicodeUrlEncode (Unicode function)\|UnicodeUrlEncode]]</var> and <var>[[UnicodeFormUrlEncode (Unicode function)\|UnicodeFormUrlEncode]]</var>, respectively.
			</ul>

	==Examples==		==Examples==

	===URL decoding an EBCDIC string===		====URL decoding an EBCDIC string====
	The following example URL decodes a URL encoded EBCDIC string to ~~unicode~~:		The following example URL decodes a URL encoded EBCDIC string to <var>Unicode</var>:
	<p class="code">b		<p class="code">b
	%ebcdic is longstring		%ebcdic is longstring
Line 43:		Line 57:
	end		end
	</p>		</p>
	and outputs		and outputs:
	<p class="output">%unicode = I like apple &#x03C0; and eat it 4 × a day.		<p class="output">%unicode = I like apple &#x03C0; and eat it 4 × a day.
	</p>		</p>
	===Catching an exception when URL decoding===
	The following is an example of catching a URL decoding exception. In the ~~following~~ example, the supposedly URL encoded string contains a %2x which is not a valid percent ~~encode~~ hexadecimal value. This results in an exception:		====Catching an exception when URL decoding====
			The following is an example of catching a URL decoding exception. In the example, the supposedly URL encoded string contains a <code>%2x</code>, which is not a valid percent encoded hexadecimal value. This results in an exception:
	<p class="code">begin		<p class="code">begin

JAL2: /* Usage notes */

2011-08-22T19:39:29Z

Usage notes

← Older revision		Revision as of 19:39, 22 August 2011
Line 23:		Line 23:

	<ul>		<ul>
	<li>If an EBCDIC version of URL encoded data needs to be converted to unicode, the EBCDIC string must first be assigned to a unicode variable using either implicit EBCDIC to Unicode translation or doing it explicitly with <var>[[EbcdicToUnicode (String function)\|EbcdicToUnicode]]</var>, converted to UTF-8 using <var>[[UnicodeToUtf8 (Unicode function)\|UnicodeToUtf8]]</var>, and finally translated to unicode using <var>UrlDecodeUnicode. And example below illustrates this process.<li>The difference between <var>FormUrlDecodeUnicode</var> and <var>UrlDecodeUnicode</var> is that<var>FormUrlDecodeUnicode</var> converts pluses (<code>+</code>) to spaces while <var>UrlDecodeUnicode</var> expects spaces to be percent encoded as <code>%20</code>. <var>UrlDecodeUnicode</var> will throw a [[CharacterTranslationException]] exception if it encounters a plus (<code>+</code>). Typically form URL encoding is only used in HTML form posts when the form is posted using the x-www-form-urlencoded content type.		<li>If an EBCDIC version of URL encoded data needs to be converted to unicode, the EBCDIC string must first be assigned to a unicode variable using either implicit EBCDIC to Unicode translation or doing it explicitly with <var>[[EbcdicToUnicode (String function)\|EbcdicToUnicode]]</var>, converted to UTF-8 using <var>[[UnicodeToUtf8 (Unicode function)\|UnicodeToUtf8]]</var>, and finally translated to unicode using <var>UrlDecodeUnicode. And example below illustrates this process.<li>The difference between <var>FormUrlDecodeUnicode</var> and <var>UrlDecodeUnicode</var> is that<var>FormUrlDecodeUnicode</var> converts pluses (<code>+</code>) to spaces while <var>UrlDecodeUnicode</var> expects spaces to be percent encoded as <code>%20</code>. <var>UrlDecodeUnicode</var> will throw a <var>[[CharacterTranslationException class\|CharacterTranslationException]]</var> exception if it encounters a plus (<code>+</code>). Typically form URL encoding is only used in HTML form posts when the form is posted using the x-www-form-urlencoded content type.
	<li>URL encoding is mostly used in web applications or for encoding a URI, possibly in an XML namespace declaration.		<li>URL encoding is mostly used in web applications or for encoding a URI, possibly in an XML namespace declaration.
	<li>The inverse of <var>UrlDecodeUnicode</var> and <var>FormUrlDecodeUnicode</var> are <var>[[UnicodeUrlEncode (Unicode function)\|UnicodeUrlEncode]]</var> and <var>[[UnicodeFormUrlEncode (Unicode function)\|~~UnicodeUrlEncode~~]]</var>, respectively.</ul>		<li>The inverse of <var>UrlDecodeUnicode</var> and <var>FormUrlDecodeUnicode</var> are <var>[[UnicodeUrlEncode (Unicode function)\|UnicodeUrlEncode]]</var> and <var>[[UnicodeFormUrlEncode (Unicode function)\|UnicodeFormUrlEncode]]</var>, respectively.</ul>

	==Examples==		==Examples==

Alex: /* URL decoding an EBCDIC string */

2011-03-11T02:54:24Z

URL decoding an EBCDIC string

@@ Line 30: / Line 30: @@
 ===URL decoding an EBCDIC string===
 The following example URL decodes a URL encoded EBCDIC string to unicode:
 <p class="code">b
@@ Line 44: / Line 43: @@
 end
 </p>
-and outputs
+%url   is longstring
-<p class="output">%unicode = I like apple &amp;#x03C0; and eat it 4 × a day.
+end
 </p>
 ==See also==
 {{Template:Unicode:UnicodeUrlEncode and UnicodeFormUrlEncode footer}}

Alex: Created page with "{{Template:String:UrlDecodeUnicode and FormUrlDecodeUnicode subtitle}} `UrlDecodeUnicode` and `FormUrlDecodeUnicode` decode data that's been [http://en.wikipedi..."

2011-03-11T02:46:23Z

Created page with "{{Template:String:UrlDecodeUnicode and FormUrlDecodeUnicode subtitle}} <var>UrlDecodeUnicode</var> and <var>FormUrlDecodeUnicode</var> decode data that's been [http://en.wikipedi..."

New page

{{Template:String:UrlDecodeUnicode and FormUrlDecodeUnicode subtitle}}
<var>UrlDecodeUnicode</var> and <var>FormUrlDecodeUnicode</var> decode data that's been [http://en.wikipedia.org/wiki/Percent-encoding URL encoded or percent-encoded] to a unicode string.

==Syntax==
{{Template:String:UrlDecodeUnicode syntax}}
{{Template:String:FormUrlDecodeUnicode syntax}}
===Syntax terms===
<table class="syntaxTable">
<tr><th>%unicode</th><td>The <var>Unicode</var> variable that results when <var class="term">string</var> is decoded.</td></tr>
<tr><th>string</th><td>The [http://en.wikipedia.org/wiki/Utf-8 UTF-8 encoded] string that contains a URL encoded representation of a unicode string.</td></tr>
<tr><th>boolean</th>
<td>Indicates whether unicode characters that cannot be translated back to EBCDIC are to be allowed. If <var class="term">boolean</var> is set to <code>False</code> a unicode character that cannot be translated back to EBCDIC results in request cancellation.</td></tr>
</table>
==Exceptions==

<var>UrlDecodeUnicode</var> and <var>FormUrlDecodeUnicode</var> can throw the following exception:
<dl>
<dt><var>[[CharacterTranslationException_class|CharacterTranslationException]]</var>
<dd>If the method encounters a translation problem, properties of the exception object may indicate the location and type of problem.
</dl>

==Usage notes==

<ul>
<li>If an EBCDIC version of URL encoded data needs to be converted to unicode, the EBCDIC string must first be assigned to a unicode variable using either implicit EBCDIC to Unicode translation or doing it explicitly with <var>[[EbcdicToUnicode (String function)|EbcdicToUnicode]]</var>, converted to UTF-8 using <var>[[UnicodeToUtf8 (Unicode function)|UnicodeToUtf8]]</var>, and finally translated to unicode using <var>UrlDecodeUnicode. And example below illustrates this process.<li>The difference between <var>FormUrlDecodeUnicode</var> and <var>UrlDecodeUnicode</var> is that<var>FormUrlDecodeUnicode</var> converts pluses (<code>+</code>) to spaces while <var>UrlDecodeUnicode</var> expects spaces to be percent encoded as <code>%20</code>. <var>UrlDecodeUnicode</var> will throw a [[CharacterTranslationException]] exception if it encounters a plus (<code>+</code>). Typically form URL encoding is only used in HTML form posts when the form is posted using the x-www-form-urlencoded content type.
<li>URL encoding is mostly used in web applications or for encoding a URI, possibly in an XML namespace declaration.
<li>The inverse of <var>UrlDecodeUnicode</var> and <var>FormUrlDecodeUnicode</var> are <var>[[UnicodeUrlEncode (Unicode function)|UnicodeUrlEncode]]</var> and <var>[[UnicodeFormUrlEncode (Unicode function)|UnicodeUrlEncode]]</var>, respectively.</ul>

==Examples==

===URL decoding an EBCDIC string===

The following example URL decodes a URL encoded EBCDIC string to unicode:
<p class="code">b
%ebcdic is longstring
%unicode is unicode

%ebcdic = 'I%20like%20apple%20%CF%80%20and%20eat%20it%204%20%C3%97%20a%20day.'

%unicode = %ebcdic:ebcdicToUnicode:unicodeToUtf8:urlDecodeUnicode

printText {~} = {%unicode}

end
</p>

and outputs

<p class="output">%unicode = I like apple &#x03C0; and eat it 4 × a day.
</p>

==See also==
{{Template:Unicode:UnicodeUrlEncode and UnicodeFormUrlEncode footer}}

UrlDecodeUnicode and FormUrlDecodeUnicode (String functions) - Revision history

JAL at 23:05, 5 November 2012

JAL2: /* Usage notes */

Alex: /* URL decoding an EBCDIC string */

Alex: Created page with "{{Template:String:UrlDecodeUnicode and FormUrlDecodeUnicode subtitle}} UrlDecodeUnicode and FormUrlDecodeUnicode decode data that's been [http://en.wikipedi..."

Alex: Created page with "{{Template:String:UrlDecodeUnicode and FormUrlDecodeUnicode subtitle}} `UrlDecodeUnicode` and `FormUrlDecodeUnicode` decode data that's been [http://en.wikipedi..."