goba            Sat Nov 10 08:42:19 2001 EDT

  Modified files:              
    /phpdoc     global.ent 
    /phpdoc/en/chapters install.xml 
  Log:
  . Adding general installation instructions, talking about
    servers, the module and CGI option, command line a GTK
    setup.
  
  . Correcting problems part with the actual bug information,
    inline link to the PHP FAQ
  
  . Maybe some more small corrections
  
  
Index: phpdoc/global.ent
diff -u phpdoc/global.ent:1.122 phpdoc/global.ent:1.123
--- phpdoc/global.ent:1.122     Sat Nov 10 05:39:37 2001
+++ phpdoc/global.ent   Sat Nov 10 08:42:18 2001
@@ -1,6 +1,6 @@
 <!-- -*- SGML -*-
 
- $Id: global.ent,v 1.122 2001/11/10 10:39:37 mj Exp $
+ $Id: global.ent,v 1.123 2001/11/10 13:42:18 goba Exp $
 
  Contains global "macros" for all the XML documents.
 
@@ -117,20 +117,24 @@
 <!ENTITY url.php.faq "http://www.php.net/FAQ.php";>
 <!ENTITY url.php.changelog "http://www.php.net/ChangeLog.php";>
 <!ENTITY url.php.bugs "http://bugs.php.net/";>
+
+<!-- Not used in the english version, only here for compatibility -->
 <!ENTITY url.php.bugdosdonts "http://bugs.php.net/bugs-dos-and-donts.php";>
+
+<!ENTITY url.php.bugs.howtoreport "http://bugs.php.net/how-to-report.php";>
 <!ENTITY url.php.conf "http://conf.php.net/";>
 <!ENTITY url.php.cvs "http://cvs.php.net/";>
 <!ENTITY url.php.cvs.anonymous "http://www.php.net/anoncvs.php";>
 <!ENTITY url.php.docs "http://www.php.net/docs.php";>
 <!ENTITY url.php.gtk "http://gtk.php.net/";>
+<!ENTITY url.php.hosts "http://hosts.php.net/";>
 <!ENTITY url.php.manual "http://www.php.net/manual/";>
 <!ENTITY url.php.pear "http://pear.php.net/";>
 <!ENTITY url.php.pear.faq "http://pear.php.net/faq.php";>
-<!-- 
- the next entity is not used in the english version, we only
- keep it until the other languages update their preface.xml
--->
+
+<!-- Not used in the english version, only here for compatibility -->
 <!ENTITY url.php.snaps.manual "http://snaps.php.net/manual/";>
+
 <!ENTITY url.php.stats "../images/phpstats-200002.gif">
 <!ENTITY url.phpdoc 'http://www.phpdoc.de/'>
 <!ENTITY url.pgsql "http://www.postgresql.org/";>
Index: phpdoc/en/chapters/install.xml
diff -u phpdoc/en/chapters/install.xml:1.86 phpdoc/en/chapters/install.xml:1.87
--- phpdoc/en/chapters/install.xml:1.86 Tue Oct 16 13:42:39 2001
+++ phpdoc/en/chapters/install.xml      Sat Nov 10 08:42:19 2001
@@ -1,15 +1,84 @@
 <?xml encoding="iso-8859-1"?>
-<!-- $Revision: 1.86 $ -->
+<!-- $Revision: 1.87 $ -->
  <chapter id="installation">
   <title>Installation</title>
 
+  <sect1 id="install.general">
+   <title>General Installation Considerations</title>
+   <para>
+    Before installing first, you need to know what do you
+    want to use PHP for. There are three main fields you
+    can use PHP, as described in the
+    <link linkend="intro-whatcando">What can PHP do?</link>
+    section:
+    <itemizedlist>
+     <listitem><simpara>Server-side scripting</simpara></listitem>
+     <listitem><simpara>Command line scripting</simpara></listitem>
+     <listitem><simpara>Client-side GUI applications</simpara></listitem>
+    </itemizedlist>
+   </para>
+   <para>
+    For the first and most common form, you need three things:
+    PHP itself, a web server and a web browser. You
+    probably already have a web browser, and depending on
+    your operating system setup, you may also have a web
+    server (eg. Apache on Linux or IIS on Windows).
+    You may also rent webspace at a company. This way, you
+    don't need to set up anything on your own, only write
+    your PHP scripts, upload it to the server you rent, and
+    see the results in your browser. You can find a list of
+    hosting companies at <ulink
+    url="&url.php.hosts;">&url.php.hosts;</ulink>.
+   </para>
+   <para>
+    While setting up the server and PHP on your own, you have
+    two choices for the method of connecting PHP to the
+    server. For many servers PHP has a direct module
+    interface (also called SAPI). These servers include
+    Apache, Microsoft Internet Information Server,
+    Netscape and iPlanet servers. Many other servers
+    have support for ISAPI, the Microsoft module
+    interface (OmniHTTPd for example). If PHP has no
+    module support for your web server, you can always
+    use it as a CGI processor. This means you set up
+    your server to use the command line executable of
+    PHP (<filename>php.exe</filename> on Windows) to
+    process all PHP file requests on the server.
+   </para>
+   <para>
+    If you are also interested to use PHP for command line
+    scripting (eg. write scripts autogenerating some images
+    for you offline, or processing text files depending
+    on some arguments you pass to them), you always need
+    the command line executable. For more information, read
+    the section about <link linkend="commandline">writing
+    command line PHP applications</link>. In this case,
+    you need no server and no browser.
+   </para>
+   <para>
+    With PHP you can also write client side GUI applications
+    using the PHP-GTK extension. This is a completely
+    different approach than writing web pages, as you
+    do not output any HTML, but manage windows and objects
+    within them. For more information about PHP-GTK, please
+    <ulink url="&url.php.gtk;">visit the site dedicated to
+    this extension</ulink>. PHP-GTK is not included in the
+    official PHP distribution.
+   </para>
+   <para>
+    From now on, this section deals with setting up PHP
+    for web servers on Unix and Windows with server module
+    interfaces and CGI executables.
+   </para>
+  </sect1>
+  
   <sect1 id="install.downloading">
    <title>Downloading the latest version</title>
    <simpara>
-    The source code, and binary distributions for some platforms
-    (including Windows), can be found at <literal><ulink
-    url="&url.php;">&url.php;</ulink></literal>. We recommend
-    you to choose <ulink url="&url.mirrors;">mirror</ulink> nearest
+    The source code, and binary distributions for Windows
+    can be found at <ulink url="&url.php;">&url.php;</ulink>.
+    We recommend you to choose a
+    <ulink url="&url.mirrors;">mirror</ulink> nearest
     to you for downloading the distributions.
    </simpara>
   </sect1>
@@ -18,7 +87,7 @@
    <title>Installation on UNIX systems</title>
    <para>
     This section will guide you through the general configuration and
-    installation of PHP on unix systems. Be sure to investigate any
+    installation of PHP on Unix systems. Be sure to investigate any
     sections specific to your platform or web server before you begin
     the process.
    </para>
@@ -5024,7 +5093,7 @@
     see <link linkend="install.configure.servers">Server-related
     options</link> for a full list of server-related configure
     options. The PHP CGI binaries are compatible with almost all
-    webservers supporting the CGI interface.
+    webservers supporting the CGI standard.
    </para>
   </sect1>
 
@@ -5035,8 +5104,8 @@
     <title>Read the FAQ</title>
     <simpara>
      Some problems are more common than others. The most
-     common ones are listed in the PHP FAQ, found at <ulink
-     url="&url.php.faq;">&url.php.faq;</ulink>
+     common ones are listed in the <link linkend="faq">PHP
+     FAQ</link>, part of this manual.
     </simpara>
    </sect2>
 
@@ -5070,12 +5139,14 @@
      PHP developers probably don't know about it, and unless you
      report it, chances are it won't be fixed. You can report bugs
      using the bug-tracking system at <ulink
-     url="&url.php.bugs;">&url.php.bugs;</ulink>.
+     url="&url.php.bugs;">&url.php.bugs;</ulink>. Please do not
+     send bug reports in mailing list or personal letters. The
+     bug system is also suitable to submit feature requests.
     </simpara>
     <simpara>
      Read the <ulink 
-     url="&url.php.bugdosdonts;">Bugs-Dos-And-Donts</ulink> 
-     before submitting any bug reports!
+     url="&url.php.bugs.howtoreport;">How to report a bug</ulink> 
+     document before submitting any bug reports!
     </simpara>
    </sect2>
 


Reply via email to