betz Tue Jul 30 05:25:35 2002 EDT Modified files: /phpdoc/en/reference/url/functions rawurlencode.xml base64-encode.xml base64-decode.xml Log: make RFC's as link Index: phpdoc/en/reference/url/functions/rawurlencode.xml diff -u phpdoc/en/reference/url/functions/rawurlencode.xml:1.2 phpdoc/en/reference/url/functions/rawurlencode.xml:1.3 --- phpdoc/en/reference/url/functions/rawurlencode.xml:1.2 Wed Apr 17 02:44:55 2002 +++ phpdoc/en/reference/url/functions/rawurlencode.xml Tue Jul 30 05:25:35 2002 @@ -1,10 +1,10 @@ <?xml version="1.0" encoding="iso-8859-1"?> -<!-- $Revision: 1.2 $ --> +<!-- $Revision: 1.3 $ --> <!-- splitted from ./en/functions/url.xml, last change in rev 1.6 --> <refentry id="function.rawurlencode"> <refnamediv> <refname>rawurlencode</refname> - <refpurpose>URL-encode according to RFC1738</refpurpose> + <refpurpose>URL-encode according to RFC 1738</refpurpose> </refnamediv> <refsect1> <title>Description</title> @@ -16,10 +16,10 @@ Returns a string in which all non-alphanumeric characters except <screen>-_.</screen> have been replaced with a percent (<literal>%</literal>) sign followed by two hex digits. This is - the encoding described in RFC1738 for protecting literal + the encoding described in RFC 1738 for protecting literal characters from being interpreted as special URL delimiters, and for protecting URL's from being mangled by transmission media - with character conversions (like some email systems). For + with character conversions (like some email systems). For example, if you want to include a password in an FTP URL: </para> <example> @@ -46,7 +46,8 @@ <simpara> See also <function>rawurldecode</function>, <function>urldecode</function>, - <function>urlencode</function>. + <function>urlencode</function> and + <ulink url="&url.rfc;rfc1738.html">RFC 1738</ulink> </simpara> </refsect1> </refentry> Index: phpdoc/en/reference/url/functions/base64-encode.xml diff -u phpdoc/en/reference/url/functions/base64-encode.xml:1.2 phpdoc/en/reference/url/functions/base64-encode.xml:1.3 --- phpdoc/en/reference/url/functions/base64-encode.xml:1.2 Wed Apr 17 02:44:54 2002 +++ phpdoc/en/reference/url/functions/base64-encode.xml Tue Jul 30 05:25:35 2002 @@ -1,5 +1,5 @@ <?xml version="1.0" encoding="iso-8859-1"?> -<!-- $Revision: 1.2 $ --> +<!-- $Revision: 1.3 $ --> <!-- splitted from ./en/functions/url.xml, last change in rev 1.2 --> <refentry id="function.base64-encode"> <refnamediv> @@ -25,7 +25,7 @@ See also: <function>base64_decode</function>, <function>chunk_split</function>, - RFC2045 section 6.8. + <ulink url="&url.rfc;rfc2045.html">RFC 2045</ulink> section 6.8. </para> </refsect1> </refentry> Index: phpdoc/en/reference/url/functions/base64-decode.xml diff -u phpdoc/en/reference/url/functions/base64-decode.xml:1.2 phpdoc/en/reference/url/functions/base64-decode.xml:1.3 --- phpdoc/en/reference/url/functions/base64-decode.xml:1.2 Wed Apr 17 02:44:54 2002 +++ phpdoc/en/reference/url/functions/base64-decode.xml Tue Jul 30 05:25:35 2002 @@ -1,5 +1,5 @@ <?xml version="1.0" encoding="iso-8859-1"?> -<!-- $Revision: 1.2 $ --> +<!-- $Revision: 1.3 $ --> <!-- splitted from ./en/functions/url.xml, last change in rev 1.2 --> <refentry id="function.base64-decode"> <refnamediv> @@ -15,11 +15,11 @@ <para> <function>base64_decode</function> decodes <parameter>encoded_data</parameter> and returns the original - data. The returned data may be binary. + data. The returned data may be binary. </para> <para> - See also: <function>base64_encode</function>, RFC2045 section - 6.8. + See also: <function>base64_encode</function>, + <ulink url="&url.rfc;rfc2045.html">RFC 2045</ulink> section 6.8. </para> </refsect1> </refentry>
-- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php