Re: [PHP-DOC] Zend API documentation to be moved to the phpdoc repository

2005-04-08 Thread Philip Olson

 Continuing on this long on-hold thread, it would be nice to come up with 
 a structure to move the files into. phpdoc/en/zendapi might not be a 
 good idea after all, since this is supposed to be a start of a 
 developers manual (which will hopefully get updated eventually :). So 
 the streams docs should also go in here.
 
 What about:
 
phpdoc/en/internals/zendapi
 
 and
 
phpdoc/en/internals/streams
 
 for now :) And still bundling the ZendAPI docs and the Streams docs with 
 the manual, but in the same part (until something better comes 
 around). The ZendAPI XML files, figures and the streams XML files should 
 be easy to relocate. Systems people hinted that we should just do cvs 
 remove and cvs add since these files have nearly no practical 
 history. But the hanging question remains. What to do with the code 
 examples in ZendAPI? I mean:
 
http://cvs.php.net/ZendAPI/source/
 
 Any ideas? After these are handled, the remaing files (DTD, build 
 system) in ZendAPI are just old crap, so if we have the content in 
 phpdoc, the ZendAPI module can be removed entirely.

I don't know the internals of PHP very well but we should
plan for future versions. How will internals/zendapi evolve
for PHP 5,6...? Meaning, will this name remain appropriate?
How will PHP 5 changes be handled?

Regardless, this move is much needed. The phpdevel
(Extending PHP 3) section would need a new name too,
something involving the number 3 :)

I don't know the value of ZendAPI/source/ examples or how
fully applicatable they are today but they can be updated
and folded into the manual in screen or CDATA. New
examples, IMHO, should involve PECL_Gen. One interesting
point. PECL_Gen is a PECL extension so I assume will be
documented like any other extension or perhaps it should
simply be documented in the internals section. Hmm...
Maybe include a download of all examples somewhere too.

As long as we're at it, the README files that live in
php-src also need to find a place in the manual. And maybe,
just maybe, these README files can be generated much like
INSTALL/install.txt are today. This would also encourage
internals folk to keep this information up-to-date.

I know of two (current) article series that involve PHP
internals. Maybe these kind souls can head up this internals
documentation effort! :) One is our very own Sara[1] and
another by Nick Loeve[2]. That would be nice! :)

Regards,
Philip

Both part one of a series:
[1] http://www.zend.com/php/internals/extension-writing1.php
[2] http://www.trickie.org/code/zend_engine_one/


[PHP-DOC] Contributo alla traduzione del Manuale PHP in italiano

2005-04-08 Thread Soldatini Salvatore



Vorrei avvicinarmi 
anch'io al mondo PHP, quindi ho cominciatodal manuale in italiano 
scaricato dal sito.
Ho notato però che 
diversi parti del manuale sono ancora in inglese.
Volevo chiedere se 
potevo dare il mio contributo alla traduzione di queste 
parti.
In particolare 
vorrei tradurre in italiano (le parti ancora in lingua inglese) della terza 
parte (III struttura del linguaggio).

Rimango in attesa 
di un vostro riscontro.
Saluti
salvatore 
soldatini



 

  
  
Salvatore Soldatini -Software 
Engineer
  
Design, Build  Integrations Test IA
  
Phone : +390817564899
  
Mobile : +393351386894 
  
E-mail : [EMAIL PROTECTED] 

CONFIDENTIALITY 
NOTICEThis message and its attachments are addressed solely to the 
personsabove and may contain confidential information. If you have 
receivedthe message in error, be informed that any use of the content 
hereofis prohibited. Please return it immediately to the sender and 
deletethe message. Should you have any questions, please contact us 
byreplying to [EMAIL PROTECTED]. Thank 
you 
www.telecomitalia.it
logotelecom.bmp

[PHP-DOC] cvs: phpdoc /en/reference/apache/functions apache-setenv.xml

2005-04-08 Thread Matthew Li
mazzanetFri Apr  8 07:11:38 2005 EDT

  Modified files:  
/phpdoc/en/reference/apache/functions   apache-setenv.xml 
  Log:
  Function only available in Apache 2
  
http://cvs.php.net/diff.php/phpdoc/en/reference/apache/functions/apache-setenv.xml?r1=1.6r2=1.7ty=u
Index: phpdoc/en/reference/apache/functions/apache-setenv.xml
diff -u phpdoc/en/reference/apache/functions/apache-setenv.xml:1.6 
phpdoc/en/reference/apache/functions/apache-setenv.xml:1.7
--- phpdoc/en/reference/apache/functions/apache-setenv.xml:1.6  Fri Apr  1 
21:18:32 2005
+++ phpdoc/en/reference/apache/functions/apache-setenv.xml  Fri Apr  8 
07:11:36 2005
@@ -1,5 +1,5 @@
 ?xml version=1.0 encoding=iso-8859-1?
-!-- $Revision: 1.6 $ --
+!-- $Revision: 1.7 $ --
 !-- splitted from ./en/functions/apache.xml, last change in rev 1.7 --
 refentry id=function.apache-setenv
  refnamediv
@@ -20,6 +20,9 @@
environment variable specified by
parametervariable/parameter.
   /para
+  para
+   This function requires Apache 2 otherwise it's undefined.
+  /para
   note
para
 When setting an Apache environment variable, the corresponding 


Re: [PHP-DOC] cvs: phpdoc /en/reference/apache/functions apache-setenv.xml

2005-04-08 Thread Jakub Vrana
Matthew Li wrote:
 /phpdoc/en/reference/apache/functions apache-setenv.xml
   Function only available in Apache 2
  
Are you sure?

http://cvs.php.net/co.php/php-src/sapi/apache/php_apache.c#390

Jakub Vrana


Re: [PHP-DOC] cvs: phpdoc /dsssl html-common.dsl

2005-04-08 Thread Jakub Vrana
Jakub Vrana wrote:
   # Side effects detected in function.main, function.die, pcre.pattern.* - 
 will be fixed
  
 Patch for function.die sent, function.main is not a big deal (it's a
 dummy entry anyway), pcre.pattern.* remain. My idea is to move them to
 appendix and provide a link from ref.pcre. Any objections, Goba and
 others?

Another side effects detected in Streams API (e.g.
http://php.net/streams.php-stream-closedir ) - not a big deal IMHO as
no version information, might be only in CVS is currently displayed
too.

Another in reserved.constants.* - I will change refentry to sect2
if there are no objections. It will put these two pages on one page,
which is a plus IMHO.

Jakub Vrana


[PHP-DOC] cvs: phpdoc /en/appendices reserved.constants.core.xml reserved.constants.standard.xml

2005-04-08 Thread Jakub Vrana
vrana   Fri Apr  8 07:53:13 2005 EDT

  Modified files:  
/phpdoc/en/appendices   reserved.constants.core.xml 
reserved.constants.standard.xml 
  Log:
  Put standard and core constants on one page, fix 'no version information' on 
these two pages
  
http://cvs.php.net/diff.php/phpdoc/en/appendices/reserved.constants.core.xml?r1=1.14r2=1.15ty=u
Index: phpdoc/en/appendices/reserved.constants.core.xml
diff -u phpdoc/en/appendices/reserved.constants.core.xml:1.14 
phpdoc/en/appendices/reserved.constants.core.xml:1.15
--- phpdoc/en/appendices/reserved.constants.core.xml:1.14   Tue Dec 21 
08:27:41 2004
+++ phpdoc/en/appendices/reserved.constants.core.xmlFri Apr  8 07:53:12 2005
@@ -1,12 +1,7 @@
 ?xml version=1.0 encoding=iso-8859-1?
-!-- $Revision: 1.14 $ --
- refentry id=reserved.constants.core
-  refnamediv
-   refnameCore Predefined Constants/refname
-   refpurposeConstants defined in the PHP core, Zend, and SAPI 
modules/refpurpose
-  /refnamediv
-  refsect1
-   titleDescription/title
+!-- $Revision: 1.15 $ --
+ sect2 id=reserved.constants.core
+   titleCore Predefined Constants/title
simpara
 These constants are defined by the PHP core. This includes PHP,
 the Zend engine, and SAPI modules.
@@ -336,8 +331,7 @@
 See also: link linkend=language.constants.predefinedMagic
 constants/link.
/para
-  /refsect1
- /refentry
+ /sect2
 
 !-- Keep this comment at the end of the file
 Local variables:
http://cvs.php.net/diff.php/phpdoc/en/appendices/reserved.constants.standard.xml?r1=1.10r2=1.11ty=u
Index: phpdoc/en/appendices/reserved.constants.standard.xml
diff -u phpdoc/en/appendices/reserved.constants.standard.xml:1.10 
phpdoc/en/appendices/reserved.constants.standard.xml:1.11
--- phpdoc/en/appendices/reserved.constants.standard.xml:1.10   Thu Sep  2 
17:20:26 2004
+++ phpdoc/en/appendices/reserved.constants.standard.xmlFri Apr  8 
07:53:12 2005
@@ -1,18 +1,13 @@
 ?xml version=1.0 encoding=iso-8859-1?
-!-- $Revision: 1.10 $ --
+!-- $Revision: 1.11 $ --
 
 !-- DOCNOTE: some constants listed here are also there at
  reference/info/constants.xml. Further decision is needed
  about the place where general constants need to be put,
  and how they should be presented. Info constants are not
  deleted from here to have a consistent standard constants list. --
- refentry id=reserved.constants.standard
-  refnamediv
-   refnameStandard Predefined Constants/refname
-   refpurposeConstants defined in PHP by default/refpurpose
-  /refnamediv
-  refsect1
-   titleDescription/title
+ sect2 id=reserved.constants.standard
+   titleStandard Predefined Constants/title
simpara
 These constants are defined in PHP by default.
/simpara
@@ -2207,8 +2202,7 @@
  /listitem
 /varlistentry
/variablelist
-  /refsect1
- /refentry
+ /sect2
 
 !-- Keep this comment at the end of the file
 Local variables:


Re: [PHP-DOC] cvs: phpdoc /en/reference/apache/functions apache-setenv.xml

2005-04-08 Thread mazzanet
That's really weird.
Why is apache-getenv only in Apache 2 and apache-setenv in 1 and 2?

Jakub Vrana wrote:
Matthew Li wrote:
   /phpdoc/en/reference/apache/functionsapache-setenv.xml
 Function only available in Apache 2
  
Are you sure?

http://cvs.php.net/co.php/php-src/sapi/apache/php_apache.c#390
Jakub Vrana



Re: [PHP-DOC] cvs: phpdoc /en/reference/apache/functions apache-setenv.xml

2005-04-08 Thread Jakub Vrana
 That's really weird.
 Why is apache-getenv only in Apache 2 and apache-setenv in 1 and 2?

I don't know. I tested it under Apache 2 and get this:

apache_setenv(X, a) affects getenv(X) but putenv(X=a) doesn't
affect apache_getenv(X)

Purpose of this is maybe the same as why apache_getenv isn't in
Apache 1 :-).

Jakub Vrána


Re: [PHP-DOC] cvs: phpdoc /dsssl html-common.dsl

2005-04-08 Thread Jakub Vrana
Jakub Vrana wrote:
   # Side effects detected in function.main, function.die, pcre.pattern.* - 
 will be fixed
 Patch for function.die sent, function.main is not a big deal (it's a
 dummy entry anyway), pcre.pattern.* remain. My idea is to move them to
 appendix and provide a link from ref.pcre. Any objections, Goba and
 others?

What about moving pcre.pattern.* to ref.pcre page? It will be long but
still shorter than ref.mbstring :-). It consists of changing
refentry to section and moving links to these two files to
partintro (I already tested it).

Jakub Vrana


[PHP-DOC] cvs: phpdoc /en/reference/apache/functions apache-setenv.xml

2005-04-08 Thread Matthew Li
mazzanetFri Apr  8 08:31:30 2005 EDT

  Modified files:  
/phpdoc/en/reference/apache/functions   apache-setenv.xml 
  Log:
  Reverting...
  
http://cvs.php.net/diff.php/phpdoc/en/reference/apache/functions/apache-setenv.xml?r1=1.7r2=1.8ty=u
Index: phpdoc/en/reference/apache/functions/apache-setenv.xml
diff -u phpdoc/en/reference/apache/functions/apache-setenv.xml:1.7 
phpdoc/en/reference/apache/functions/apache-setenv.xml:1.8
--- phpdoc/en/reference/apache/functions/apache-setenv.xml:1.7  Fri Apr  8 
07:11:36 2005
+++ phpdoc/en/reference/apache/functions/apache-setenv.xml  Fri Apr  8 
08:31:26 2005
@@ -1,5 +1,5 @@
 ?xml version=1.0 encoding=iso-8859-1?
-!-- $Revision: 1.7 $ --
+!-- $Revision: 1.8 $ --
 !-- splitted from ./en/functions/apache.xml, last change in rev 1.7 --
 refentry id=function.apache-setenv
  refnamediv
@@ -20,9 +20,6 @@
environment variable specified by
parametervariable/parameter.
   /para
-  para
-   This function requires Apache 2 otherwise it's undefined.
-  /para
   note
para
 When setting an Apache environment variable, the corresponding 


[PHP-DOC] [webmaster] deadlink

2005-04-08 Thread colder.ch
Hi.
There is deadlink on the mailing list page 
(http://www.php.net/mailing-lists.php) under the section Local mailing 
lists and newsgroup :

The French Mailing List link is dead.
regards
--
colder
http://www.colder.ch/v2
[EMAIL PROTECTED]


Re: [PHP-DOC] [webmaster] deadlink

2005-04-08 Thread David Mytton
I think the best option is to report this as a bug to the PHP Website
team via http://bugs.php.net/report.php

On Apr 8, 2005 4:01 PM, colder.ch [EMAIL PROTECTED] wrote:
 Hi.
 
 There is deadlink on the mailing list page
 (http://www.php.net/mailing-lists.php) under the section Local mailing
 lists and newsgroup :
 
 The French Mailing List link is dead.
 
 regards
 
 --
 colder
 
 http://www.colder.ch/v2
 [EMAIL PROTECTED]
 


-- 
Regards,

David Mytton
http://www.olate.co.uk


Re: [PHP-DOC] [webmaster] deadlink

2005-04-08 Thread Sean Coates
David Mytton wrote:
I think the best option is to report this as a bug to the PHP Website
team via http://bugs.php.net/report.php
Definitely the best approach.
Most of the phpdoc'ers don't have php-web karma.
S


Re: [PHP-DOC] cvs: phpdoc /dsssl html-common.dsl

2005-04-08 Thread Gabor Hojtsy
I agree with Nuno here! They should stay where they are, the script
should get fixed.
I simple don't know how to fix the script. Docbook requires
refentry in reference, refnamediv in refentry, etc. I don't
know where to put the logic to disable versioning on these two pages
because they look like any other page. Maybe something ugly as
refentry role=noversion can work but I'm not sure how implement it
in DSSSL anyway.
Another option is to move these two pages to partintro (thus they
will display directly on ref.pcre.php) but they are quite long to put
here IMHO. There are other long pages (DOM, mbstring) but not so long
:-).
What if we use PHP: Hypertext Postprocessor :) I know it is hackish, I 
know. Anyway, I will first look into how this can be done in DSSSL (with 
a role=noversion).

Goba


Re: [PHP-DOC] Contributo alla traduzione del Manuale PHP in italiano

2005-04-08 Thread Gabor Hojtsy
Hi Salvatore,
Write english here, or to the italian team in italian to 
[EMAIL PROTECTED]

Regards,
Gabor Hojtsy
Soldatini Salvatore wrote:
Vorrei avvicinarmi anch'io al mondo PHP, quindi ho cominciato dal 
manuale in italiano scaricato dal sito.
Ho notato però che diversi parti del manuale sono ancora in inglese.
Volevo chiedere se potevo dare il mio contributo alla traduzione di 
queste parti.
In particolare vorrei tradurre in italiano (le parti ancora in lingua 
inglese) della terza parte (III struttura del linguaggio).
 
Rimango in attesa di un vostro riscontro.
Saluti
salvatore soldatini
 
Salvatore Soldatini - Software Engineer 
Design, Build  Integrations Test IA 
Phone : +390817564899
Mobile : +393351386894
E-mail : [EMAIL PROTECTED] 
mailto:[EMAIL PROTECTED]

 

CONFIDENTIALITY NOTICE
This message and its attachments are addressed solely to the persons
above and may contain confidential information. If you have received
the message in error, be informed that any use of the content hereof
is prohibited. Please return it immediately to the sender and delete
the message. Should you have any questions, please contact us by
replying to [EMAIL PROTECTED] mailto:[EMAIL PROTECTED].
Thank you
www.telecomitalia.it 
http://www.telecomitalia.it



Re: [PHP-DOC] cvs: phpdoc /dsssl html-common.dsl

2005-04-08 Thread Gabor Hojtsy
 # Side effects detected in function.main, function.die, pcre.pattern.* - will be fixed
Patch for function.die sent, function.main is not a big deal (it's a
dummy entry anyway), pcre.pattern.* remain. My idea is to move them to
appendix and provide a link from ref.pcre. Any objections, Goba and
others?
What about moving pcre.pattern.* to ref.pcre page? It will be long but
still shorter than ref.mbstring :-). It consists of changing
refentry to section and moving links to these two files to
partintro (I already tested it).
No, please don't do that long pages. I will look into the DSSSL way of 
getting the version info off the pcre pages.

Goba


Re: [PHP-DOC] Keeping translated methodsynopsis up-to-date

2005-04-08 Thread Gabor Hojtsy
yep. If the script could detect that the only changes were proto 
related, it could also update that tag (to try to reduce the revcheck 
outdated files).
And generalizing the script, it could also update the tag when there 
are no changes between two revisions (like when a translator 
overwrites the english files) or when there are other trivial changes 
(here the translators should help us and say which changes are these).

Well, this script seems to be a bit difficult to write, but if 
translators say its worth..
Keep it simple for the first time :)
+1 (cf. docweb :p)
A question regarding methodsynopsis, should the translators keep
the english parameter names? Let say they do. In this case, instead
of writing the script to check the differences, why don't we simply
use the english methodsynposis when generating the manual? too hackish ?
They do translate it. The problem is that the text will not correspond 
to the parameter list, and it will get confusing. Ie. when you rename a 
parameter in the English docs to fix the naming and the translation 
synopsis will also change, but the references in the text itself will not.

Goba


[PHP-DOC] cvs: phpdoc /en/reference/exec/functions escapeshellarg.xml escapeshellcmd.xml exec.xml passthru.xml proc-close.xml proc-get-status.xml proc-nice.xml proc-terminate.xml shell-exec.xml system

2005-04-08 Thread Philip Olson
philip  Fri Apr  8 16:14:53 2005 EDT

  Modified files:  
/phpdoc/en/reference/exec/functions escapeshellarg.xml 
escapeshellcmd.xml exec.xml 
passthru.xml proc-close.xml 
proc-get-status.xml 
proc-nice.xml 
proc-terminate.xml 
shell-exec.xml system.xml 
  Log:
  WS, preparation for the new doc style
  
  http://cvs.php.net/diff.php/phpdoc/en/reference/exec/functions/escapeshellarg.xml?r1=1.7r2=1.8ty=u
Index: phpdoc/en/reference/exec/functions/escapeshellarg.xml
diff -u phpdoc/en/reference/exec/functions/escapeshellarg.xml:1.7 
phpdoc/en/reference/exec/functions/escapeshellarg.xml:1.8
--- phpdoc/en/reference/exec/functions/escapeshellarg.xml:1.7   Mon Nov  1 
11:31:24 2004
+++ phpdoc/en/reference/exec/functions/escapeshellarg.xml   Fri Apr  8 
16:14:52 2005
@@ -1,45 +1,44 @@
 ?xml version=1.0 encoding=iso-8859-1?
-!-- $Revision: 1.7 $ --
+!-- $Revision: 1.8 $ --
 !-- splitted from ./en/functions/exec.xml, last change in rev 1.8 --
-  refentry id=function.escapeshellarg
-   refnamediv
-refnameescapeshellarg/refname
-refpurposeEscape a string to be used as a shell argument/refpurpose
-   /refnamediv
-   refsect1
-reftitle.description;
- methodsynopsis
-  typestring/typemethodnameescapeshellarg/methodname
-  methodparamtypestring/typeparameterarg/parameter/methodparam
- /methodsynopsis
-para
- functionescapeshellarg/function adds single quotes around a string
- and quotes/escapes any existing single quotes allowing you to pass a
- string directly to a shell function and having it be treated as a single
- safe argument.  This function should be used to escape individual
- arguments to shell functions coming from user input.  The shell functions
- include functionexec/function, functionsystem/function and the 
- link linkend=language.operators.executionbacktick operator/link. 
- A standard use would be:/para
-para
- informalexample
-  programlisting role=php
+refentry id=function.escapeshellarg
+ refnamediv
+  refnameescapeshellarg/refname
+  refpurposeEscape a string to be used as a shell argument/refpurpose
+ /refnamediv
+ refsect1
+  reftitle.description;
+  methodsynopsis
+   typestring/typemethodnameescapeshellarg/methodname
+   methodparamtypestring/typeparameterarg/parameter/methodparam
+  /methodsynopsis
+  para
+   functionescapeshellarg/function adds single quotes around a string
+   and quotes/escapes any existing single quotes allowing you to pass a
+   string directly to a shell function and having it be treated as a single
+   safe argument.  This function should be used to escape individual
+   arguments to shell functions coming from user input.  The shell functions
+   include functionexec/function, functionsystem/function and the
+   link linkend=language.operators.executionbacktick operator/link.
+   A standard use would be:/para
+  para
+   informalexample
+programlisting role=php
 ![CDATA[
 ?php
 system('ls '.escapeshellarg($dir));
 ?
 ]]
-  /programlisting
- /informalexample
-/para
-para
- See also functionescapeshellcmd/function, functionexec/function,
- functionpopen/function, functionsystem/function, and the link
- linkend=language.operators.executionbacktick operator/link.
-/para
-
-   /refsect1
-  /refentry
+/programlisting
+   /informalexample
+  /para
+  para
+   See also functionescapeshellcmd/function, functionexec/function,
+   functionpopen/function, functionsystem/function, and the link
+   linkend=language.operators.executionbacktick operator/link.
+  /para
+ /refsect1
+/refentry
 
 !-- Keep this comment at the end of the file
 Local variables:
http://cvs.php.net/diff.php/phpdoc/en/reference/exec/functions/escapeshellcmd.xml?r1=1.5r2=1.6ty=u
Index: phpdoc/en/reference/exec/functions/escapeshellcmd.xml
diff -u phpdoc/en/reference/exec/functions/escapeshellcmd.xml:1.5 
phpdoc/en/reference/exec/functions/escapeshellcmd.xml:1.6
--- phpdoc/en/reference/exec/functions/escapeshellcmd.xml:1.5   Mon Nov  1 
11:31:24 2004
+++ phpdoc/en/reference/exec/functions/escapeshellcmd.xml   Fri Apr  8 
16:14:52 2005
@@ -1,29 +1,29 @@
 ?xml version=1.0 encoding=iso-8859-1?
-!-- $Revision: 1.5 $ --
+!-- $Revision: 1.6 $ --
 !-- splitted from ./en/functions/exec.xml, last change in rev 1.2 --
-  refentry id=function.escapeshellcmd
-   refnamediv
-refnameescapeshellcmd/refname
-refpurposeEscape shell metacharacters/refpurpose
-   /refnamediv
-   refsect1
-reftitle.description;
- methodsynopsis
-  typestring/typemethodnameescapeshellcmd/methodname
-  
methodparamtypestring/typeparametercommand/parameter/methodparam
- /methodsynopsis
-para
- functionescapeshellcmd/function escapes any 

[PHP-DOC] cvs: phpdoc /en/reference/exec/functions escapeshellarg.xml escapeshellcmd.xml exec.xml passthru.xml proc-close.xml proc-get-status.xml proc-nice.xml proc-terminate.xml shell-exec.xml system

2005-04-08 Thread Philip Olson
philip  Fri Apr  8 19:18:40 2005 EDT

  Modified files:  
/phpdoc/en/reference/exec/functions escapeshellarg.xml 
escapeshellcmd.xml exec.xml 
passthru.xml proc-close.xml 
proc-get-status.xml 
proc-nice.xml 
proc-terminate.xml 
shell-exec.xml system.xml 
  Log:
  Moved to new doc style
  
  http://cvs.php.net/diff.php/phpdoc/en/reference/exec/functions/escapeshellarg.xml?r1=1.8r2=1.9ty=u
Index: phpdoc/en/reference/exec/functions/escapeshellarg.xml
diff -u phpdoc/en/reference/exec/functions/escapeshellarg.xml:1.8 
phpdoc/en/reference/exec/functions/escapeshellarg.xml:1.9
--- phpdoc/en/reference/exec/functions/escapeshellarg.xml:1.8   Fri Apr  8 
16:14:52 2005
+++ phpdoc/en/reference/exec/functions/escapeshellarg.xml   Fri Apr  8 
19:18:40 2005
@@ -1,12 +1,13 @@
 ?xml version=1.0 encoding=iso-8859-1?
-!-- $Revision: 1.8 $ --
+!-- $Revision: 1.9 $ --
 !-- splitted from ./en/functions/exec.xml, last change in rev 1.8 --
 refentry id=function.escapeshellarg
  refnamediv
   refnameescapeshellarg/refname
   refpurposeEscape a string to be used as a shell argument/refpurpose
  /refnamediv
- refsect1
+
+ refsect1 role=description
   reftitle.description;
   methodsynopsis
typestring/typemethodnameescapeshellarg/methodname
@@ -20,9 +21,37 @@
arguments to shell functions coming from user input.  The shell functions
include functionexec/function, functionsystem/function and the
link linkend=language.operators.executionbacktick operator/link.
-   A standard use would be:/para
+  /para
+ /refsect1
+
+ refsect1 role=parameters
+  reftitle.parameters;
+  para
+   variablelist
+varlistentry
+ termparameterarg/parameter/term
+ listitem
+  para
+   The argument that will be escaped.
+  /para
+ /listitem
+/varlistentry
+   /variablelist
+  /para
+ /refsect1
+
+ refsect1 role=returnvalues
+  reftitle.returnvalues;
   para
-   informalexample
+   The escaped string.
+  /para
+ /refsect1
+
+ refsect1 role=examples
+  reftitle.examples;
+  para
+   example
+titlefunctionescapeshellarg/function example/title
 programlisting role=php
 ![CDATA[
 ?php
@@ -30,12 +59,20 @@
 ?
 ]]
 /programlisting
-   /informalexample
+   /example
   /para
+ /refsect1
+
+ refsect1 role=seealso
+  reftitle.seealso;
   para
-   See also functionescapeshellcmd/function, functionexec/function,
-   functionpopen/function, functionsystem/function, and the link
-   linkend=language.operators.executionbacktick operator/link.
+   simplelist
+memberfunctionescapeshellcmd/function/member
+memberfunctionexec/function/member
+memberfunctionpopen/function/member
+memberfunctionsystem/function/member
+memberlink linkend=language.operators.executionbacktick 
operator/link/member
+   /simplelist
   /para
  /refsect1
 /refentry
http://cvs.php.net/diff.php/phpdoc/en/reference/exec/functions/escapeshellcmd.xml?r1=1.6r2=1.7ty=u
Index: phpdoc/en/reference/exec/functions/escapeshellcmd.xml
diff -u phpdoc/en/reference/exec/functions/escapeshellcmd.xml:1.6 
phpdoc/en/reference/exec/functions/escapeshellcmd.xml:1.7
--- phpdoc/en/reference/exec/functions/escapeshellcmd.xml:1.6   Fri Apr  8 
16:14:52 2005
+++ phpdoc/en/reference/exec/functions/escapeshellcmd.xml   Fri Apr  8 
19:18:40 2005
@@ -1,12 +1,13 @@
 ?xml version=1.0 encoding=iso-8859-1?
-!-- $Revision: 1.6 $ --
+!-- $Revision: 1.7 $ --
 !-- splitted from ./en/functions/exec.xml, last change in rev 1.2 --
 refentry id=function.escapeshellcmd
  refnamediv
   refnameescapeshellcmd/refname
   refpurposeEscape shell metacharacters/refpurpose
  /refnamediv
- refsect1
+
+ refsect1 role=description
   reftitle.description;
   methodsynopsis
typestring/typemethodnameescapeshellcmd/methodname
@@ -20,9 +21,38 @@
is passed to the functionexec/function or
functionsystem/function functions, or to the link
linkend=language.operators.executionbacktick
-   operator/link. A standard use would be:/para
+   operator/link.
+  /para
+ /refsect1
+
+ refsect1 role=parameters
+  reftitle.parameters;
+  para
+   variablelist
+varlistentry
+ termparametercommand/parameter/term
+ listitem
+  para
+   The command that will be escaped.
+  /para
+ /listitem
+/varlistentry
+   /variablelist
+  /para
+ /refsect1
+
+ refsect1 role=returnvalues
+  reftitle.returnvalues;
   para
-   informalexample
+   The escaped string.
+  /para
+ /refsect1
+
+ refsect1 role=examples
+  reftitle.examples;
+  para
+   example
+titlefunctionescapeshellcmd/function example/title
 programlisting role=php
 ![CDATA[
 ?php
@@ -37,12 +67,20 @@
 ?
 ]]
 /programlisting
-   /informalexample
+   /example
   /para
+ /refsect1
+
+ refsect1 role=seealso
+  reftitle.seealso;
   para

[PHP-DOC] cvs: phpdoc /en/reference/apache/functions apache-getenv.xml

2005-04-08 Thread Philip Olson
philip  Fri Apr  8 19:19:54 2005 EDT

  Modified files:  
/phpdoc/en/reference/apache/functions   apache-getenv.xml 
  Log:
  Typo
  
  
http://cvs.php.net/diff.php/phpdoc/en/reference/apache/functions/apache-getenv.xml?r1=1.6r2=1.7ty=u
Index: phpdoc/en/reference/apache/functions/apache-getenv.xml
diff -u phpdoc/en/reference/apache/functions/apache-getenv.xml:1.6 
phpdoc/en/reference/apache/functions/apache-getenv.xml:1.7
--- phpdoc/en/reference/apache/functions/apache-getenv.xml:1.6  Fri Apr  1 
21:18:32 2005
+++ phpdoc/en/reference/apache/functions/apache-getenv.xml  Fri Apr  8 
19:19:53 2005
@@ -1,5 +1,5 @@
 ?xml version=1.0 encoding=iso-8859-1?
-!-- $Revision: 1.6 $ --
+!-- $Revision: 1.7 $ --
 refentry id=function.apache-getenv
  refnamediv
   refnameapache_getenv/refname
@@ -58,7 +58,7 @@
   reftitle.examples;
   para
example
-titlefunctionfunctionname/function example/title
+titlefunctionapache_getenv/function example/title
 para
  The example above shows how to retrieve the value of the Apache
  environment variable varnameSERVER_ADDR/varname.