betz Thu Sep 12 16:28:37 2002 EDT
Modified files:
/phpdoc/en/chapters config.xml
Log:
remove integrated part
Index: phpdoc/en/chapters/config.xml
diff -u phpdoc/en/chapters/config.xml:1.73 phpdoc/en/chapters/config.xml:1.74
--- phpdoc/en/chapters/config.xml:1.73 Tue Sep 3 15:49:16 2002
+++ phpdoc/en/chapters/config.xml Thu Sep 12 16:28:36 2002
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="iso-8859-1"?>
-<!-- $Revision: 1.73 $ -->
+<!-- $Revision: 1.74 $ -->
<chapter id="configuration">
<title>Configuration</title>
@@ -1433,170 +1433,6 @@
</variablelist>
</sect2>
- <sect2 id="ini.sect.informix">
- <title>Informix Configuration Directives</title>
- <variablelist>
-
- <varlistentry id="ini.ifx.allow-persistent">
- <term>
- <parameter>ifx.allow_persistent</parameter>
- <type>boolean</type>
- </term>
- <listitem>
- <para>
- Whether to allow persistent Informix connections.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry id="ini.ifx.max-persistent">
- <term>
- <parameter>ifx.max_persistent</parameter>
- <type>integer</type>
- </term>
- <listitem>
- <para>
- The maximum number of persistent Informix connections per
- process.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry id="ini.ifx.max-links">
- <term>
- <parameter>ifx.max_links</parameter>
- <type>integer</type>
- </term>
- <listitem>
- <para>
- The maximum number of Informix connections per process, including
- persistent connections.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry id="ini.ifx.default-host">
- <term>
- <parameter>ifx.default_host</parameter>
- <type>string</type>
- </term>
- <listitem>
- <para>
- The default host to connect to when no host is specified
- in <function>ifx_connect</function> or
- <function>ifx_pconnect</function>.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry id="ini.ifx.default-user">
- <term>
- <parameter>ifx.default_user</parameter>
- <type>string</type>
- </term>
- <listitem>
- <para>
- The default user id to use when none is specified
- in <function>ifx_connect</function> or
- <function>ifx_pconnect</function>.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry id="ini.ifx.default-password">
- <term>
- <parameter>ifx.default_password</parameter>
- <type>string</type>
- </term>
- <listitem>
- <para>
- The default password to use when none is specified
- in <function>ifx_connect</function> or
- <function>ifx_pconnect</function>.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry id="ini.ifx.blobinfile">
- <term>
- <parameter>ifx.blobinfile</parameter>
- <type>boolean</type>
- </term>
- <listitem>
- <para>
- Set to &true; if you want to return blob columns
- in a file, &false; if you want them in memory. You can
- override the setting at runtime
- with <function>ifx_blobinfile_mode</function>.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry id="ini.ifx.textasvarchar">
- <term>
- <parameter>ifx.textasvarchar</parameter>
- <type>boolean</type>
- </term>
- <listitem>
- <para>
- Set to &true; if you want to return TEXT columns
- as normal strings in select statements,
- &false; if you want to use blob id parameters. You can
- override the setting at runtime with
- <function>ifx_textasvarchar</function>.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry id="ini.ifx.byteasvarchar">
- <term>
- <parameter>ifx.byteasvarchar</parameter>
- <type>boolean</type>
- </term>
- <listitem>
- <para>
- Set to &true; if you want to return BYTE columns
- as normal strings in select queries,
- &false; if you want to use blob id parameters. You can
- override the setting at runtime with
- <function>ifx_textasvarchar</function>.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry id="ini.ifx.charasvarchar">
- <term>
- <parameter>ifx.charasvarchar</parameter>
- <type>boolean</type>
- </term>
- <listitem>
- <para>
- Set to &true; if you want to trim trailing spaces
- from CHAR columns when fetching them.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry id="ini.ifx.nullformat">
- <term>
- <parameter>ifx.nullformat</parameter>
- <type>boolean</type>
- </term>
- <listitem>
- <para>
- Set to &true; if you want to return &null; columns
- as the literal string "&null;", &false; if you want
- them returned as the empty string "". You can
- override this setting at runtime with
- <function>ifx_nullformat</function>.
- </para>
- </listitem>
- </varlistentry>
-
-
- </variablelist>
- </sect2>
-
<sect2 id="ini.sect.bcmath">
<title>BC Math Configuration Directives</title>
<variablelist>
@@ -1707,118 +1543,7 @@
</variablelist>
</sect2>
- <sect2 id="ini.sect.exif">
- <title>Exif Configuration Directives</title>
- <para>
- Exif supports automatically conversion for Unicode and JIS
- 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
- <literal>HTTP</literal> output.
- <variablelist>
-
- <varlistentry id="ini.exif.encode_unicode">
- <term>
- <parameter>exif.encode_unicode</parameter>
- <type>string</type>
- </term>
- <listitem>
- <para>
- <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 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.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry id="ini.exif.decode_unicode_motorola">
- <term>
- <parameter>exif.decode_unicode_motorola</parameter>
- <type>string</type>
- </term>
- <listitem>
- <para>
- <literal>exif.decode_unicode_motorola</literal> defines
- the image internal characterset for Unicode encoded user
- comments if image is in motorola byte order (big-endian).
- This setting cannot be empty but you can specify a list
- of encodings supported by mbstring. The default is UCS-2BE.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry id="ini.exif.decode_unicode_intel">
- <term>
- <parameter>exif.decode_unicode_intel</parameter>
- <type>string</type>
- </term>
- <listitem>
- <para>
- <literal>exif.decode_unicode_intel</literal> defines
- the image internal characterset for Unicode encoded user
- comments if image is in intel byte order (little-endian).
- This setting cannot be empty but you can specify a list
- of encodings supported by mbstring. The default is UCS-2LE.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry id="ini.exif.encode_jis">
- <term>
- <parameter>exif.encode_jis</parameter>
- <type>string</type>
- </term>
- <listitem>
- <para>
- <literal>exif.encode_jis</literal> defines the
- characterset JIS user comments are handled.
- This defaults to an empty value which forces
- the functions to use the current internal encoding
- of mbstring.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry id="ini.exif.decode_jis_motorola">
- <term>
- <parameter>exif.decode_jis_motorola</parameter>
- <type>string</type>
- </term>
- <listitem>
- <para>
- <literal>exif.decode_jis_motorola</literal> defines
- the image internal characterset for JIS encoded user
- comments if image is in motorola byte order (big-endian).
- This setting cannot be empty but you can specify a list
- of encodings supported by mbstring. The default is JIS.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry id="ini.exif.decode_jis_intel">
- <term>
- <parameter>exif.decode_jis_intel</parameter>
- <type>string</type>
- </term>
- <listitem>
- <para>
- <literal>exif.decode_jis_intel</literal> defines
- the image internal characterset for JIS encoded user
- comments if image is in intel byte order (little-endian).
- This setting cannot be empty but you can specify a list
- of encodings supported by mbstring. The default is JIS.
- </para>
- </listitem>
- </varlistentry>
-
- </variablelist>
- </para>
- </sect2>
</sect1>
--
PHP Documentation Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
