cvs: phpdoc /en/install pecl.xml
| From: | Kalle Sommer Nielsen | Date: | Sun, 31 Aug 2008 23:00:38 +0000 |
| Subject: | cvs: phpdoc /en/install pecl.xml | ||
| Groups: | php.doc.cvs | ||
| Request: | Send a blank email to doc-cvs+get-2126@lists.php.net to get a copy of this message | ||
kalle Sun Aug 31 23:00:38 2008 UTC
Modified files:
/phpdoc/en/install pecl.xml
Log:
Some markup fixes
http://cvs.php.net/viewvc.cgi/phpdoc/en/install/pecl.xml?r1=1.18&r2=1.19&diff_format=u
Index: phpdoc/en/install/pecl.xml
diff -u phpdoc/en/install/pecl.xml:1.18 phpdoc/en/install/pecl.xml:1.19
--- phpdoc/en/install/pecl.xml:1.18 Sun Aug 31 00:58:16 2008
+++ phpdoc/en/install/pecl.xml Sun Aug 31 23:00:38 2008
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="iso-8859-1"?>
-<!-- $Revision: 1.18 $ -->
+<!-- $Revision: 1.19 $ -->
<chapter xml:id="install.pecl" xmlns="http://docbook.org/ns/docbook"
xmlns:xlink="http://www.w3.org/1999/xlink">
<title>Installation of PECL extensions</title>
@@ -120,32 +120,32 @@
PHP distribution nor in PECL, you may have to compile it before you can start using the
extension.
</para>
+ </sect1>
- <sect2 xml:id="install.pecl.windows.locate">
- <title>Where to find an extension?</title>
- <para>
- PHP extensions are usually called "php_*.dll" (where the star represents the name of
- the extension) and they are located under the "PHP\ext" ("PHP\extensions"
in PHP4)
- folder.
- </para>
- <para>
- PHP ships with the extensions most useful to the majority of developers. They are
- called "core" extensions.
- </para>
- <para>
- However, if you need functionnality not provided by any core extension, you may still be
- able to find one in PECL. The PHP Extension Community Library (PECL) is a repository for
- PHP Extensions, providing a directory of all known extensions and hosting facilities for
- downloading and development of PHP extensions.
- </para>
- <para>
- If you have developped an extension for your own uses, you might want to think about hosting
- it on PECL so that others with the same needs can benefit from your time. A nice side effect
- is that you give them a good chance to give you feedback, (hopefully) thanks, bug reports
- and even fixes/patches. Before you submit your extension for hosting on PECL, please read
- &url.pecl.submit.
- </para>
- </sect2>
+ <sect1 xml:id="install.pecl.windows.find">
+ <title>Where to find an extension?</title>
+ <para>
+ PHP extensions are usually called "php_*.dll" (where the star represents the name of
+ the extension) and they are located under the "PHP\ext" ("PHP\extensions"
in PHP4)
+ folder.
+ </para>
+ <para>
+ PHP ships with the extensions most useful to the majority of developers. They are
+ called "core" extensions.
+ </para>
+ <para>
+ However, if you need functionnality not provided by any core extension, you may still be
+ able to find one in PECL. The PHP Extension Community Library (PECL) is a repository for
+ PHP Extensions, providing a directory of all known extensions and hosting facilities for
+ downloading and development of PHP extensions.
+ </para>
+ <para>
+ If you have developped an extension for your own uses, you might want to think about hosting
+ it on PECL so that others with the same needs can benefit from your time. A nice side effect
+ is that you give them a good chance to give you feedback, (hopefully) thanks, bug reports
+ and even fixes/patches. Before you submit your extension for hosting on PECL, please read
+ &url.pecl.submit.
+ </para>
<sect2 xml:id="install.pecl.windows.which">
<title>Which extension to download?</title>
@@ -162,19 +162,16 @@
Different thread safety settings
</simpara>
</listitem>
- </itemizedlist>
<listitem>
<simpara>
Different processor settings (x86, 64 bits...)
</simpara>
</listitem>
- </itemizedlist>
<listitem>
<simpara>
Different debugging settings
</simpara>
</listitem>
- </itemizedlist>
<listitem>
<simpara>
<literal>ect.</literal>
@@ -186,27 +183,21 @@
You should keep in mind that your extension settings should match all the
settings of the PHP executable you are using. The following PHP script will
tell you <emphasis>all</emphasis> about your PHP settings:
- <example>
- <info><title>Getting your php information using
<function>phpinfo</function></title></info>
- <programlisting role="php">
+ <screen>
<![CDATA[
<?php
phpinfo();
?>
]]>
- </programlisting>
- </example>
+ </screen>
</para>
<para>
Or from the command line, run:
- <example>
- <info><title>Getting your php information using the command line
interface</title></info>
- <programlisting role="cmd">
+ <screen>
<![CDATA[
drive:\\path\to\php\executable\php.exe -i
]]>
- </programlisting>
- </example>
+ </screen>
</para>
</sect2>
@@ -216,43 +207,31 @@
The most common way to load a PHP extension is to include it in your
<filename>php.ini</filename>
configuration file. Please note that many extensions are already present in your
<filename>php.ini</filename> and that you only need to remove the semicolon to
activate them.
- <example>
- <info><title>Inactive extension</title></info>
- <programlisting role="ini">
+ <screen>
<![CDATA[
;extension=php_extname.dll
]]>
- </programlisting>
- </example>
- <example>
- <info><title>Active extension</title></info>
- <programlisting role="ini">
+ </screen>
+ <screen>
<![CDATA[
extension=php_extname.dll
]]>
- </programlisting>
- </example>
+ </screen>
</para>
<para>
However, some webservers are confusing because they do not use the php.ini located alongside
your PHP executable. To find out where your actual <filename>php.ini</filename>
resides, look
for its path in <function>phpinfo</function>:
- <example>
- <info><title>Not the info we want</title></info>
- <programlisting role="text">
+ <screen>
<![CDATA[
Configuration File (php.ini) Path C:\WINDOWS
]]>
- </programlisting>
- </example>
- <example>
- <info><title>This is what we need</title></info>
- <programlisting role="text">
+ </screen>
+ <screen>
<![CDATA[
Loaded Configuration File C:\Program Files\PHP\5.2\php.ini
]]>
- </programlisting>
- </example>
+ </screen>
</para>
<para>
After activating an extension, save <filename>php.ini</filename>, restart the
webserver and check