Re: [PHP-DOC] cvs: phpdoc /en/chapters config.xml install.configure.misc.xml install.iis.xml install.iplanet.xml install.xitami.xml /en/features commandline.xml /en/language expressions.xml /en/reference/com/functions class.com.xml /en/reference/cpdf/functions cpdf-place-inline-image.xml /en/reference/dba reference.xml /en/reference/http/functions headers-sent.xml /en/reference/imap/functions imap-mail.xml /en/reference/info constants.xml /en/reference/info/functions phpinfo.xml /en/reference/ming configure.xml /en/reference/ming/functions swfdisplayitem.rotateto.xml /en/reference/mnogosearch/functions udm-set-agent-param.xml /en/reference/printer/functions printer-open.xml /en/reference/pspell/functions pspell-config-personal.xml pspell-config-repl.xml /en/reference/sesam reference.xml /en/reference/sesam/functions sesam-fetch-row.xml sesam-field-array.xml sesam-settransaction.xml /en/security index.xml

2003-12-21 Thread Gabor Hojtsy
  Log:
  - php - PHP where appropriate.
Also if you find PHP3, PHP4, PHP5 (PHP written without a space with the 
version number), then it shuold be written with a space :)

Goba


Re: [PHP-DOC] cvs: phpdoc /en/chapters config.xml install.configure.misc.xml install.iis.xml install.iplanet.xml install.xitami.xml /en/features commandline.xml /en/language expressions.xml /en/reference/com/functions class.com.xml /en/reference/cpdf/functions cpdf-place-inline-image.xml /en/reference/dba reference.xml /en/reference/http/functions headers-sent.xml /en/reference/imap/functions imap-mail.xml /en/reference/info constants.xml /en/reference/info/functions phpinfo.xml /en/reference/ming configure.xml /en/reference/ming/functions swfdisplayitem.rotateto.xml /en/reference/mnogosearch/functions udm-set-agent-param.xml /en/reference/printer/functions printer-open.xml /en/reference/pspell/functions pspell-config-personal.xml pspell-config-repl.xml /en/reference/sesam reference.xml /en/reference/sesam/functions sesam-fetch-row.xml sesam-field-array.xml sesam-settransaction.xml /en/security index.xml

2003-12-21 Thread Dave
On Sunday, December 21, 2003, 9:22:59 PM, Gabor wrote:

   Log:
   - php - PHP where appropriate.

 Also if you find PHP3, PHP4, PHP5 (PHP written without a space with the
 version number), then it shuold be written with a space :)

 Goba

Thanks, done!

Dave


Re: [PHP-DOC] cvs: phpdoc /en/chapters config.xml install.hpux.xmltutorial.xml

2003-06-22 Thread Philip Olson

Hello Derick-

What do you have against this note title?  I find
it fully appropriate as it's indeed a note about
Autoglobals.

-titlePHP Autoglobals Note/title

Regards,
Philip



On Sun, 22 Jun 2003, Derick Rethans wrote:

 derickSun Jun 22 11:09:22 2003 EDT
 
   Modified files:  
 /phpdoc/en/chapters   config.xml install.hpux.xml tutorial.xml 
   Log:
   - Summer cleaning time!
   
   


-- 
PHP Documentation Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php



Re: [PHP-DOC] cvs: phpdoc /en/chapters config.xml install.hpux.xmltutorial.xml

2003-06-22 Thread Derick Rethans
On Sun, 22 Jun 2003, Philip Olson wrote:

 What do you have against this note title?  I find
 it fully appropriate as it's indeed a note about
 Autoglobals.

Sometimes those titles are just too obvious and don't really add any 
information, just like in this case.

regards,
Derick

-- 
Interpreting what the GPL actually means is a job best left to those
that read the future by examining animal entrails.
-
 Derick Rethans http://derickrethans.nl/ 
 International PHP Magazine  http://php-mag.net/
-

-- 
PHP Documentation Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php



Re: [PHP-DOC] cvs: phpdoc /en/chapters config.xml install.hpux.xmltutorial.xml

2003-06-22 Thread Philip Olson
On Sun, 22 Jun 2003, Derick Rethans wrote:

 On Sun, 22 Jun 2003, Philip Olson wrote:
 
  What do you have against this note title?  I find
  it fully appropriate as it's indeed a note about
  Autoglobals.
 
 Sometimes those titles are just too obvious and don't really add any 
 information, just like in this case.

Exactly.  Many people already know about autoglobals and don't
need to read about them so they see the title and skip the
paragraph.  Or for those that don't know, the title will
intrigue them.  Not everyone knows the art of skimming nor
is having a title hurting anything.  Personally, I think most
every note could use a title.

Regards,
Philip


-- 
PHP Documentation Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php



Re: [PHP-DOC] cvs: phpdoc /en/chapters config.xml

2002-09-03 Thread Friedhelm Betz


 hakan   Tue Sep  3 15:49:16 2002 EDT

   Modified files:  
 /phpdoc/en/chapters config.xml 
   Log:
   closing bug #19214
  
you can set more than _one_ path with PHPRC
and the first one, where a config file is found, this one is taken.

 Friedhelm   


-- 
PHP Documentation Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php




Re: [PHP-DOC] cvs: phpdoc /en/chapters config.xml

2002-07-11 Thread Gabor Hojtsy

 Why doesn't 'make test' pick up on these entity  
 errors?

Because NSGMLS cannot find these errors. It's not a problem
for Jade, so the manual can still build. But it's not valid
XML, and it's a problem for any XSLT processor.

 Also, I notice you turned the two spaces after the 
 period into one.  I've always used two after a 
 period, we use just one here?  Afaik both ways 
 are accepted although I was always tought two.

AFAIK American guys use two spaces. I was always told that
one space should be between two sentences. We have no
standard for this in phpdoc. But browser rendering also
resembles this, as there any number of repetitive spaces
are turned into one (incl. the spaces between sentences).
So at the end both the two space and one space ones display
the same way...

Goba



-- 
PHP Documentation Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php




Re: [PHP-DOC] cvs: phpdoc /en/chapters config.xml

2002-07-11 Thread Jim Winstead

Philip Olson [EMAIL PROTECTED] wrote:
 Also, I notice you turned the two spaces after the 
 period into one.  I've always used two after a 
 period, we use just one here?  Afaik both ways 
 are accepted although I was always tought two.

it probably doesn't matter. the processing tools will almost certainly
collapse all whitespace to a single space.

(for what it is worth, the two-spaces-after-period rule comes from the
days of typewriters with monospace fonts, a la courier. it is completely
unnecessary with proportional fonts, and of debatable merit with
monospace fonts.)

jim

-- 
PHP Documentation Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php




Re: [PHP-DOC] cvs: phpdoc /en/chapters config.xml

2002-04-01 Thread Friedhelm Betz


Hi Mark,



 If someone wants to take a look, my proposal for layout:
 http://mysql.holliwell.de/ref.mysql.html, including the infos from
 config.xml. I don't just want to commit, maybe one of the more experienced

 Looks great. This is what I have in mind, too. Perhaps you should add
 a short installation instruction for MySQL, so all information you need
 to 
 use MySQL with PHP will be on one page.

 Mark

back from the family meeting for the easter days :-)
What Installation instructions do you have in mind (Complete list of configure options
?)
The part under Installation seems to be enough for me? Is
there/should there be more stuff?
Will the section  Complete list of configure options stay at the place
its now? Or should this be deleted too? The contents are under the
Installation part of the intro to mysql.xml.
Let me know. Thanks !

 Friedhelm




Re: [PHP-DOC] cvs: phpdoc /en/chapters config.xml

2002-04-01 Thread Mark Kronsbein


 What Installation instructions do you have in mind (Complete list of configure 
options
 ?)

I have in mind that someone whos reading the manual finds everything 
he needs to install and use i.e. MySQL on one place.

- MySQL quick install
- Configuring PHP for MySQL
- Normal manual pages for functions etc.

 Will the section  Complete list of configure options stay at the place
 its now? Or should this be deleted too? The contents are under the
 Installation part of the intro to mysql.xml.

Hartmut is planning something with the options ;)

Mark

-- 
German Gabber Network  http://www.gabber.de
Infos und Tips zu PHP http://www.php-homepage.de



Re: [PHP-DOC] cvs: phpdoc /en/chapters config.xml

2002-04-01 Thread Gabor Hojtsy

  If someone wants to take a look, my proposal for layout:
  http://mysql.holliwell.de/ref.mysql.html, including the infos from
  config.xml. I don't just want to commit, maybe one of the more
experienced

  Looks great. This is what I have in mind, too. Perhaps you should add
  a short installation instruction for MySQL, so all information you need
  to
  use MySQL with PHP will be on one page.

 back from the family meeting for the easter days :-)
 What Installation instructions do you have in mind (Complete list of
configure options
 ?)
 The part under Installation seems to be enough for me? Is
 there/should there be more stuff?
 Will the section  Complete list of configure options stay at the place
 its now? Or should this be deleted too? The contents are under the
 Installation part of the intro to mysql.xml.
 Let me know. Thanks !

Two points from me:

a) All info related to one extension at one place
b) No duplicated documentation, link when duplications needed

Goba





Re: [PHP-DOC] cvs: phpdoc /en/chapters config.xml

2002-04-01 Thread Mark Kronsbein



 a) All info related to one extension at one place
 b) No duplicated documentation, link when duplications needed

Thats what I meant. If the installation of a lib is only
configure, make, make install, its okay, to write it in the 
PHP manual. If its more, link to an installation faq or something.

Mark

-- 
German Gabber Network  http://www.gabber.de
Infos und Tips zu PHP http://www.php-homepage.de



Re: [PHP-DOC] cvs: phpdoc /en/chapters config.xml

2002-04-01 Thread Friedhelm Betz


Hallo Mark,

Monday, April 01, 2002, 9:40:19 PM, you wrote:

 a) All info related to one extension at one place
 b) No duplicated documentation, link when duplications needed

+1

 Thats what I meant. If the installation of a lib is only
 configure, make, make install,
 its okay, to write it in the
 PHP manual. If its more, link to an installation faq or something.

also +1, this could also include the chance to give the win-users the
proper info, e.g. which dll to enable for that extension and also if
this extension _is_ available on win


 Friedhelm   




Re: [PHP-DOC] cvs: phpdoc /en/chapters config.xml

2002-04-01 Thread Friedhelm Betz


 What Installation instructions do you have in mind (Complete list of configure 
options
 ?)

 I have in mind that someone whos reading the manual finds everything 
 he needs to install and use i.e. MySQL on one place.

 - MySQL quick install

Really?? For most extensions this is not as easy :-). In this case
your other proposal (linking to external infos) seems to be more handy
to me.

 - Configuring PHP for MySQL
 - Normal manual pages for functions etc.

 Will the section  Complete list of configure options stay at the place
 its now? Or should this be deleted too? The contents are under the
 Installation part of the intro to mysql.xml.

 Hartmut is planning something with the options ;)

So for now, I'll leave that section untouched :-) Untill Hartmut has
worked out, there are two sections with nearly the same contents, but
in this case it seems to be ok for me.

  Friedhelm




Re: [PHP-DOC] cvs: phpdoc /en/chapters config.xml

2002-03-30 Thread Mark Kronsbein

 If someone wants to take a look, my proposal for layout:
 http://mysql.holliwell.de/ref.mysql.html, including the infos from
 config.xml. I don't just want to commit, maybe one of the more experienced

Looks great. This is what I have in mind, too. Perhaps you should add
a short installation instruction for MySQL, so all information you need
to 
use MySQL with PHP will be on one page.

Mark

-- 
German Gabber Network  http://www.gabber.de
Infos und Tips zu PHP http://www.php-homepage.de




Re: [PHP-DOC] cvs: phpdoc /en/chapters config.xml

2002-03-29 Thread Gabor Hojtsy

 betz Fri Mar 29 10:31:37 2002 EDT
 
   Modified files:  
 /phpdoc/en/chapters config.xml 
   Log:
   correcting uodbc directives. changed uodbc.* to odbc.* 
   minor changes to MySQL directives

IMHO if you add directives to the functions directory to
the appropriate file, it would be the best to *remove* them
from here.

Having options listed in two places would only make
confusion, more time to update, etc.

We already discussed moving the configure and ini options
to the function reference part.

Goba





Re: [PHP-DOC] cvs: phpdoc /en/chapters config.xml

2002-03-29 Thread Friedhelm Betz


Hallo Gabor,

Friday, March 29, 2002, 6:16:43 PM, you wrote:

 betz Fri Mar 29 10:31:37 2002 EDT
 
   Modified files:  
 /phpdoc/en/chapters config.xml 
   Log:
   correcting uodbc directives. changed uodbc.* to odbc.* 
   minor changes to MySQL directives

 IMHO if you add directives to the functions directory to
 the appropriate file, it would be the best to *remove* them
from here.

OK, couldn't remember, sorry! I guess therefore is the runtime
configuration section in the func references :-)
Which layout to choose? The same  as in config.xml?
Asking this stupid question because of the runtime configs in
mysql.xml and uodbc.xml (The later I just added today, mysql few weeks
ago). Is there an example?

 Having options listed in two places would only make
 confusion, more time to update, etc.

right :-)

 We already discussed moving the configure and ini options
 to the function reference part.

Is this definitley decided? :-)

 Friedhelm   




Re: [PHP-DOC] cvs: phpdoc /en/chapters config.xml

2002-03-29 Thread Gabor Hojtsy

 OK, couldn't remember, sorry! I guess therefore is the runtime
 configuration section in the func references :-)
 Which layout to choose? The same  as in config.xml?
 Asking this stupid question because of the runtime configs in
 mysql.xml and uodbc.xml (The later I just added today, mysql few weeks
 ago). Is there an example?

I cannot give you an example. You have just started to volunteer
on providing an example with mysql.xml and uodbc.xml for the
other guys ;)

  We already discussed moving the configure and ini options
  to the function reference part.
 
 Is this definitley decided? :-)

Not officialy. We discussed it, but not decided.
Though noone had any objections against it AFAIK.

Goba





Re: [PHP-DOC] cvs: phpdoc /en/chapters config.xml

2002-03-29 Thread Friedhelm Betz


Hi,


 Jep, but I did this with the often asked question in mind, which and
 how php.ini-seetings could be altered (with no access to php.ini).
 And not to forget: just deleting the entries from config.xml would be a
 loss on information. I'll think about and provide an improved example
 in mysql.xml.

 As discussed, we will move the ini and configure options to the
 extensions information in the future. It makes all info concentrated
 in one place. I have not compared the information contained in
 the configure part and in mysql.xml though, so that may be a
 stupid thing now just to blindly remove the info from the 
 configure part.

If someone wants to take a look, my proposal for layout:
http://mysql.holliwell.de/ref.mysql.html, including the infos from
config.xml. I don't just want to commit, maybe one of the more experienced
on docbook finds a better solution. And maybe the moving will be done
automagically?

 Friedhelm   




Re: [PHP-DOC] cvs: phpdoc /en/chapters config.xml

2002-02-07 Thread Gabor Hojtsy

 Index: phpdoc/en/chapters/config.xml
 diff -u phpdoc/en/chapters/config.xml:1.36
phpdoc/en/chapters/config.xml:1.37
 --- phpdoc/en/chapters/config.xml:1.36 Wed Feb  6 17:30:51 2002
 +++ phpdoc/en/chapters/config.xml Wed Feb  6 21:26:36 2002
 @@ -1,5 +1,5 @@
  ?xml version=1.0 encoding=iso-8859-1?
 -!-- $Revision: 1.36 $ --
 +!-- $Revision: 1.37 $ --
   chapter id=configuration
titleConfiguration/title

 @@ -368,6 +368,14 @@
   module, open_basedir paths from parent directories are now
   automatically inherited.
  /para
 + para
 + The restriction specified with open_basedir is actually a
 + prefix, not a directory name.  This means that open_basedir =
 + /dir/incl also allows access to /dir/include and
 + /dir/incls if they exist.  When you want to restrict access to
 + only the specified directory, end with a slash.  For example:
 + open_basedir = /dir/incl/
 + /para

Please use spaces for indentation. Please indent this para to
the column where the other para ends.

Thanks,
Goba





Re: [PHP-DOC] cvs: phpdoc /en/chapters config.xml

2001-11-09 Thread Markus Fischer

On Fri, Nov 09, 2001 at 02:29:29PM -, Derick Rethans wrote : 
 derickFri Nov  9 09:29:29 2001 EDT

 + Please not that this can not be set in a .htaccess file.
   

Yo!

- Markus