Add links to RFCs

git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@219871 c90b9560-bf6c-de11-be94-00142212c4b1
This commit is contained in:
Hannes Magnusson 2006-09-12 21:43:35 +00:00
parent 7f43ab8137
commit 9a5cf31818
5 changed files with 11 additions and 11 deletions

View file

@ -1,5 +1,5 @@
<?xml version="1.0" encoding="iso-8859-1"?>
<!-- $Revision: 1.6 $ -->
<!-- $Revision: 1.7 $ -->
<!-- splitted from ./en/functions/imap.xml, last change in rev 1.33 -->
<refentry id="function.imap-clearflag-full">
<refnamediv>
@ -21,7 +21,7 @@
messages in the specified <parameter>sequence</parameter>.
The flags which you can unset are "\\Seen", "\\Answered",
"\\Flagged", "\\Deleted", and "\\Draft" (as defined
by RFC2060). &return.success;.
by <ulink url="&url.rfc;2060">RFC2060</ulink>). &return.success;.
</para>
<para>
<parameter>options</parameter> are a bit mask and may contain

View file

@ -1,5 +1,5 @@
<?xml version="1.0" encoding="iso-8859-1"?>
<!-- $Revision: 1.14 $ -->
<!-- $Revision: 1.15 $ -->
<!-- splitted from ./en/functions/imap.xml, last change in rev 1.2 -->
<refentry id="function.imap-get-quota">
<refnamediv>
@ -61,8 +61,8 @@ imap_close($mbox);
</para>
<para>
As of PHP 4.3, the function more properly reflects the
functionality as dictated by the RFC 2087. The array return value has
changed to support an unlimited number of returned resources (i.e.
functionality as dictated by the <ulink url="&url.rfc;2087">RFC2087</ulink>.
The array return value has changed to support an unlimited number of returned resources (i.e.
messages, or sub-folders) with each named resource receiving an individual
array key. Each key value then contains an another array with the usage
and limit values within it. The example below shows the updated returned

View file

@ -1,5 +1,5 @@
<?xml version="1.0" encoding="iso-8859-1"?>
<!-- $Revision: 1.5 $ -->
<!-- $Revision: 1.6 $ -->
<!-- splitted from ./en/functions/imap.xml, last change in rev 1.33 -->
<refentry id="function.imap-mail">
<refnamediv>
@ -27,7 +27,7 @@
<para>
The parameters <parameter>to</parameter>, <parameter>cc</parameter>
and <parameter>bcc</parameter> are all strings and are all parsed
as rfc822 address lists.
as <ulink url="&url.rfc;822">RFC822</ulink> address lists.
</para>
<para>
The receivers specified in <parameter>bcc</parameter> will get the

View file

@ -1,5 +1,5 @@
<?xml version="1.0" encoding="iso-8859-1"?>
<!-- $Revision: 1.6 $ -->
<!-- $Revision: 1.7 $ -->
<!-- splitted from ./en/functions/imap.xml, last change in rev 1.2 -->
<refentry id="function.imap-search">
<refnamediv>
@ -154,7 +154,7 @@
use: "UNANSWERED FROM mom". Searches appear to be case
insensitive. This list of criteria is from a reading of the UW
c-client source code and may be incomplete or
inaccurate (see also RFC2060, section 6.4.4).
inaccurate (see also <ulink url="&url.rfc;2060">RFC2060</ulink>, section 6.4.4).
</para>
<para>
Valid values for flags are SE_UID, which causes the returned

View file

@ -1,5 +1,5 @@
<?xml version="1.0" encoding="iso-8859-1"?>
<!-- $Revision: 1.10 $ -->
<!-- $Revision: 1.11 $ -->
<!-- splitted from ./en/functions/imap.xml, last change in rev 1.2 -->
<refentry id="function.imap-setflag-full">
<refnamediv>
@ -23,7 +23,7 @@
<para>
The flags which you can set are "\\Seen", "\\Answered",
"\\Flagged", "\\Deleted", and "\\Draft" (as defined
by RFC2060).
by <ulink url="&url.rfc;2060">RFC2060</ulink>).
</para>
<para>
<parameter>options</parameter> are a bit mask and may contain