derick Mon Jan 3 07:51:36 2005 EDT
Modified files: /phpdoc/en/reference/http/functions setcookie.xml Log: - Unbreak build http://cvs.php.net/diff.php/phpdoc/en/reference/http/functions/setcookie.xml?r1=1.35&r2=1.36&ty=u Index: phpdoc/en/reference/http/functions/setcookie.xml diff -u phpdoc/en/reference/http/functions/setcookie.xml:1.35 phpdoc/en/reference/http/functions/setcookie.xml:1.36 --- phpdoc/en/reference/http/functions/setcookie.xml:1.35 Sun Jan 2 15:36:02 2005 +++ phpdoc/en/reference/http/functions/setcookie.xml Mon Jan 3 07:51:36 2005 @@ -1,5 +1,5 @@ <?xml version="1.0" encoding="iso-8859-1"?> -<!-- $Revision: 1.35 $ --> +<!-- $Revision: 1.36 $ --> <!-- splitted from ./en/functions/http.xml, last change in rev 1.2 --> <refentry id="function.setcookie"> <refnamediv> @@ -317,15 +317,16 @@ The following RFC's may also be useful: <ulink url="&url.rfc;2109">RFC 2109</ulink> and <ulink url="&url.rfc;2965">RFC 2695</ulink> - <para> - You may notice the <parameter>expire</parameter> parameter takes on a - Unix timestamp, as opposed to the date format <literal>Wdy, DD-Mon-YYYY - HH:MM:SS GMT</literal>, this is because PHP does this conversion - internally. - </para> - <para> - <parameter>expire</parameter> is compared to the client's time which can - differ from server's time. + </para> + <para> + You may notice the <parameter>expire</parameter> parameter takes on a + Unix timestamp, as opposed to the date format <literal>Wdy, DD-Mon-YYYY + HH:MM:SS GMT</literal>, this is because PHP does this conversion + internally. + </para> + <para> + <parameter>expire</parameter> is compared to the client's time which can + differ from server's time. </para> </note> <note>