leszek Mon May 27 12:52:49 2002 EDT
Modified files:
/phpdoc/en/chapters config.xml
Log:
Few corrections. Hope good ones...
Index: phpdoc/en/chapters/config.xml
diff -u phpdoc/en/chapters/config.xml:1.54 phpdoc/en/chapters/config.xml:1.55
--- phpdoc/en/chapters/config.xml:1.54 Mon May 27 07:33:48 2002
+++ phpdoc/en/chapters/config.xml Mon May 27 12:52:49 2002
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="iso-8859-1"?>
-<!-- $Revision: 1.54 $ -->
+<!-- $Revision: 1.55 $ -->
<chapter id="configuration">
<title>Configuration</title>
@@ -431,8 +431,7 @@
method variables with POST-method variables of the same name.
</para>
<para>
- See also <link
-linkend="ini.register-globals">register_globals</link>.
+ See also <link linkend="ini.register-globals">register_globals</link>.
</para>
</listitem>
</varlistentry>
@@ -440,14 +439,16 @@
<varlistentry id="ini.ignore-user-abort">
<term>
<parameter>ignore_user_abort</parameter>
- <type>string</type>
+ <type>boolean</type>
</term>
<listitem>
<para>
- On by default. If changed to Off scripts will be terminated as
- soon as they try to output something after a client has aborted
- their connection.
- <function>ignore_user_abort</function>.
+ &true; by default. If changed to &false; scripts will be terminated
+ as soon as they try to output something after a client has aborted
+ their connection.
+ </para>
+ <para>
+ See also <function>ignore_user_abort</function>.
</para>
</listitem>
</varlistentry>
@@ -667,8 +668,9 @@
<simpara>
Sets max size of post data allowed. This setting also affects
file upload. To upload large files, this value must be larger
- than <link linkend="ini.upload-max-filesize">upload_max_filesize</link>.
- </simpara>
+ than <link
+ linkend="ini.upload-max-filesize">upload_max_filesize</link>.
+ </simpara>
<simpara>
If memory limit is enabled by configure script, <link
linkend="ini.memory-limit">memory_limit</link> also affects
@@ -852,8 +854,8 @@
</term>
<listitem>
<para>
- Whether to use <literal>UID</literal> (<literal>Off</literal>) or
- <literal>GID</literal> (<literal>On</literal>) checking upon file
+ Whether to use <literal>UID</literal> (&false;) or
+ <literal>GID</literal> (&true;) checking upon file
access. See <link linkend="features.safe-mode">Safe Mode</link> for
more information.
</para>
@@ -1544,7 +1546,7 @@
<listitem>
<para>
<literal>mbstring.http_input</literal> defines default
- HTTP input character encoding.
+ <literal>HTTP</literal> input character encoding.
</para>
</listitem>
</varlistentry>
@@ -1557,7 +1559,7 @@
<listitem>
<para>
<literal>mbstring.http_output</literal> defines default
- HTTP output character encoding.
+ <literal>HTTP</literal> output character encoding.
</para>
</listitem>
</varlistentry>
@@ -1597,7 +1599,8 @@
character encodings of user comments when module mbstring
is available. This is done by first decoding the comment
using the specified characterset. The result is then encoded
- with another characterset which should match your http output.
+ with another characterset which should match your
+ <literal>HTTP</literal> output.
<variablelist>
<varlistentry id="ini.exif.encode_unicode">
@@ -1610,7 +1613,7 @@
<literal>exif.encode_unicode</literal> defines the
characterset UNICODE user comments are handled.
This defaults to ISO-8859-15 which should work for
- most non asian counties. The setting can be empty
+ most non asian countries. The setting can be empty
or must be an encoding supported by mbstring. If it
is empty the current internal encoding of mbstring is
used.