> > OK. Please do not only ACK my folder ideas, but please also
> > give your opinion. For example whether it would be better
> > to put condigure things into install/configure or configure/.
> 
> Installation -> install/ Configure Options -> install/configure
> php.ini Stuff/configuration directives  -> install/settings
>  
> my 2 cents

Settings were never part of the installation section. But as
the configure part is somewhat integral in installation
(especially on non-Windows systems), your idea might be
better than mine. But then if we have confgure options under
installation, we can have settings under it too to be more
clear.

OK, so what needs to be done to these files before they are
ready for translation:

 - Split config.xml to parts :)
 - Support translation (make "static" indexes, with no parts
   to translate [cuurently install.xml is an example of such file])
 - Introduce DocBook XML level grouping 

   Installation             <part>
     + General              <chapter>
     + Unix                 <chapter>
     + Windows              <chapter>
     + Servers              <chapter>
     + Problems             <chapter>
     + Configure options    <chapter>
     + PHP.ini settings     <chapter>

   This is a "move one up" of the elemts in the doc, with including
   the config options and settings in installation. Then the master
   parts would be:

    Getting Started
    Installation
    Language Reference
    Features
    Security
    Function reference
    Extending PHP 4 ??? => put into developers manual??
    FAQ
    Appendixes

I have already contacted Rasmus about expanding the Getting Started
section with inclusion of php.net/tut.php, and addig more newcomers
info stuff... This would make Getting Started to legally be a standalone
master part.

NOTE: All things in this letter needs more discussions!

Goba


Reply via email to