Re: [PHP-DOC] New CHM manual opinions

2001-10-31 Thread Hojtsy Gabor

 And one feature I would l really love to see is a link to the online
 equivilant of the each help page to see what new coments have been
 posted

This is part of the online functions section right now :)

 and drop down menus (they could just be combo boxes) to
 related help documents.

This was also planned, although it turned out, that there is
no easy way to extract a related page list from the pages.
There are see also sections, but they are not clearly separated
(this build process tries to identify and mark them, but it is
not 100%, as it won't recognize any see also notes in the text
flow... So it seemed for now, the see also boxing is the only
thing we can do... There is a movement to include some see also
tags in the xml sources, but this is not used yet...

Goba



[PHP-DOC] cvs: phpdoc /en/language types.xml

2001-10-31 Thread Jeroen van Wolffelaar

jeroen  Wed Oct 31 09:21:23 2001 EDT

  Modified files:  
/phpdoc/en/language types.xml 
  Log:
  Revert accidentel error.
  
  
Index: phpdoc/en/language/types.xml
diff -u phpdoc/en/language/types.xml:1.58 phpdoc/en/language/types.xml:1.59
--- phpdoc/en/language/types.xml:1.58   Tue Oct 30 21:02:20 2001
+++ phpdoc/en/language/types.xmlWed Oct 31 09:21:23 2001
@@ -1,5 +1,5 @@
 ?xml encoding=iso-8859-1?
-!-- $Revision: 1.58 $ --
+!-- $Revision: 1.59 $ --
  chapter id=language.types
   titleTypes/title
 
@@ -232,7 +232,7 @@
  with zero elements/simpara
 /listitem
 listitem
- simparathe special value link linkend=language.types.null
+ simparathe special type link linkend=language.types.null
 NULL/link 
  /simpara
 /listitem





[PHP-DOC] New CHM manual opinions

2001-10-31 Thread Rick Morris

The new CHM manual design (from http://weblabor.hu/php/newchm.html) looks
nice overall, and I love the new features. There are just a couple of
things:

1. It loads slowly. I really like the speed I get with the last version of
the manual. I think this is partly because of the heavy graphics, and partly
from the Javascript loading of header and footer.

2. I can deal with the orange bar and icons at the top, but the multicolored
orange user notes has GOT to be changed.

3. The faded background graphic behind the text is pretty, but distracting.

4. The code examples need some sort of background or outline to
differentiate them.

5. I think it is only right to have the PHP logo somewhere on the page. (at
least the lettering)

I grabbed a couple HTML pages out of the manual and made the above changes,
including a few other stylistic changes. I believe the changes make the
manual a little more ergononic and should make it load a little faster, too.
Please take a look at http://64.34.228.37/php_manual/

I will be working on a nice design for the manual start page. I would be
happy to provide any other help desired in CSS, Javascript, etc... I also
have some other ideas on how to reduce the graphics without sacrificing the
design.

Rick Morris




[PHP-DOC] New CHM manual opinions

2001-10-31 Thread Hari ramamurthy

Dear Sir,
I am a freelance web developer from India and would
like to submit a few samples.How do I do so?Can I mail
them to this email address or link it to my homepage.
Thanks and regards,
Hari


Nokia Game is on again. 
Go to http://uk.yahoo.com/nokiagame/ and join the new
all media adventure before November 3rd.



Re[2]: [PHP-DOC] Don't forget about old chm

2001-10-31 Thread Olexandr Vynnychenko


DR Thas last time I uploaded was 25 October, but it seems it's not correctly
DR distributed anymore.

And what does it mean?

-- 
Best regards,
 Olexandrmailto:[EMAIL PROTECTED]





[PHP-DOC] cvs: phpdoc /en/functions filesystem.xml url.xml

2001-10-31 Thread jim winstead

jimwWed Oct 31 13:19:29 2001 EDT

  Modified files:  
/phpdoc/en/functionsfilesystem.xml url.xml 
  Log:
  cross reference parse_url() and pathinfo()
  
Index: phpdoc/en/functions/filesystem.xml
diff -u phpdoc/en/functions/filesystem.xml:1.83 phpdoc/en/functions/filesystem.xml:1.84
--- phpdoc/en/functions/filesystem.xml:1.83 Wed Oct 17 12:24:00 2001
+++ phpdoc/en/functions/filesystem.xml  Wed Oct 31 13:19:29 2001
@@ -1,5 +1,5 @@
 ?xml encoding=iso-8859-1?
-!-- $Revision: 1.83 $ --
+!-- $Revision: 1.84 $ --
  reference id=ref.filesystem
   titleFilesystem functions/title
   titleabbrevFilesystem/titleabbrev
@@ -2201,7 +2201,8 @@
 /para
 para
  See also functiondirname/function,
- functionbasename/function and functionrealpath/function.
+ functionbasename/function, functionparse_url/function
+ and functionrealpath/function.
 /para
/refsect1
   /refentry
Index: phpdoc/en/functions/url.xml
diff -u phpdoc/en/functions/url.xml:1.17 phpdoc/en/functions/url.xml:1.18
--- phpdoc/en/functions/url.xml:1.17Fri Sep 21 18:47:48 2001
+++ phpdoc/en/functions/url.xml Wed Oct 31 13:19:29 2001
@@ -1,5 +1,5 @@
 ?xml encoding=iso-8859-1?
-!-- $Revision: 1.17 $ --
+!-- $Revision: 1.18 $ --
  reference id=ref.url
   titleURL Functions/title
   titleabbrevURLs/titleabbrev
@@ -78,6 +78,9 @@
  various components of the URL that are present. This includes the
  scheme, host, port, user, pass, path, query, and
  fragment.
+/para
+para
+ See also functionpathinfo/function.
 /para
/refsect1
   /refentry





[PHP-DOC] cvs: phpdoc /en/language variables.xml

2001-10-31 Thread Philip Olson

philip  Wed Oct 31 14:24:18 2001 EDT

  Modified files:  
/phpdoc/en/language variables.xml 
  Log:
  Added note about magic_quotes_gpc and slashes under 'variables from outside php'
  A link to html faq was also added.
  
  
Index: phpdoc/en/language/variables.xml
diff -u phpdoc/en/language/variables.xml:1.20 phpdoc/en/language/variables.xml:1.21
--- phpdoc/en/language/variables.xml:1.20   Fri Sep 21 18:47:49 2001
+++ phpdoc/en/language/variables.xmlWed Oct 31 14:24:18 2001
@@ -1,5 +1,5 @@
 ?xml encoding=iso-8859-1?
-!-- $Revision: 1.20 $ --
+!-- $Revision: 1.21 $ --
  chapter id=language.variables
   titleVariables/title
   
@@ -860,11 +860,22 @@
  be available as varname$username/varname in the global scope.
 /para
 
+note
+ para
+  The link linkend=ini.magic-quotes-gpcmagic_quotes_gpc/link 
+  configuration directive affects Get, Post and Cookie values.  If 
+  turned on, value (It's PHP!) will automagically become (It\'s \PHP!\).
+  Escaping is needed for DB insertion.  Also see
+  functionaddslashes/function, functionstripslashes/function and 
+  link linkend=ini.magic-quotes-sybasemagic_quotes_sybase/link.
+ /para
+/note
+
 simpara
- PHP also understands arrays in the context of form variables. You
- may, for example, group related variables together, or use this
- feature to retrieve values from a multiple select
- input:
+ PHP also understands arrays in the context of form variables 
+ (see the link linkend=faq.htmlrelated faq/link).  You may, 
+ for example, group related variables together, or use this 
+ feature to retrieve values from a multiple select input:
 /simpara
 
 para





[PHP-DOC] New CHM manual opinions

2001-10-31 Thread Elizabeth Fulghum



Nice design on the new manual, I am one of those 
looking forward to the inclusion of the user comments. As I was trying it out, I 
noticed a couple of issues. 

While it looks great on screen, the layout is not 
very scalable. When I browse through the help files, I like to keep the 
contents/index/search/etc window open for easy navigation and searching. In the 
old manual, the content would "flex" depending on the width of the window - not 
so in this new version.

See: http://home.dal.net/rabbitdog/screenshot.png

I can see this as being one of the big "this annoys 
the heck out of me" issues with the new manual.


Just my two cents, 

Liz Fulghum
--
http://www.lipstickalley.com/ - Be 
Popular!
Want to learn PHP? http://webdeveloper.earthweb.com/scripting/article/0,,12014_900521,00.html
--


[PHP-DOC] ai traduttori italiani

2001-10-31 Thread alan

Ciao a tutti,
da oggi faccio parte anche io del gruppo di lavoro
per la manutenzione e la traduzione del manuale PHP
in Italiano.

Sono felicissimo di iniziare quest'esperienza,
e sono assolutamente daterminato a fare un buon lavoro,
è n onore lavorare in un gruppo (il PHP development team)
a cui ho sempre aspirato e guardato com ammirazione :)

Solo alcune domande mi sovvengono ...

1)
devo aspettare qualche segnale dai curatori,
o posso iniziare a lavorare su una sezione del
manuale non ancora assegnata a nessuno (in
relazione al file it/Translators)?

2)
c'è qualcosa che non dice l'HowTo sul lavoro
da svolgere che dovrei sapere?
(per esempio ... questo è un formalismo a cui è
bene attenersi suppongo)
commento che informa della revisione del file array.xml in en:
!-- $Revision: 1.108 $ --
commento che informa aquale revisione si riferisce la traduzione del file
array.xml in it:
!-- EN-Revision: 1.108 Maintainer: cucinato  Status: ready --

Se c'è poi qualche informazione che dovrei sapere,
o avete qualche consiglio da darmi, sarebbe assolutamente gradito :)

Un grazie a tutti, e buon lavoro :)

Spero che il sig. Luca Perugini non si sia adirato con
me per le troppe domande :)

Ciao ... Alan





[PHP-DOC] configuration directives

2001-10-31 Thread jimw

right now, we have configuration directives that are extension-specific
in one of two places -- in the extension documentation (like for
sessions), or in the configuration section (like for mysql). i think it
would make sense to move the extension-specific stuff into the extension
documentation.  any objections?

(in fact, i'd love to do this for compile-time configuration, too. i
don't think the long 'list of all configure --options' section is all
that easy to use. an up-to-date listing of all of the options is easy
enough to get from the command line.)

and, just because i have the data at hand, here's the list of the top
ten most-commented manual pages. i'm going to start working on rewriting
these pages to address all of the notes.

113 | function.header
104 | function.mail
 91 | ref.session
 87 | function.setcookie
 76 | function.date
 76 | features.file-upload
 68 | language.oop
 63 | install.windows
 61 | function.ereg
 53 | function.ereg-replace
 51 | function.include
 49 | function.session-start

(there's 6270 notes across 990 different sections.)

jim



[PHP-DOC] ai traduttori italiani

2001-10-31 Thread Alan D'Angelo [php-power.it]



Ciao a tutti,da oggi faccio parte anche io del gruppo di lavoroper 
la manutenzione e la traduzione del manuale PHPin Italiano.Sono 
felicissimo di iniziare quest'esperienza,e sono assolutamente daterminato a 
fare un buon lavoro,è n onore lavorare in un gruppo (il PHP development 
team)a cui ho sempre aspirato e guardato com ammirazione :)Solo 
alcune domande mi sovvengono ...1)devo aspettare qualche segnale dai 
curatori,o posso iniziare a lavorare su una sezione delmanuale non 
ancora assegnata a nessuno (inrelazione al file 
it/Translators)?2)c'è qualcosa che non dice l'HowTo sul lavoroda 
svolgere che dovrei sapere?(per esempio ... questo è un formalismo a cui 
èbene attenersi suppongo)commento che informa della revisione del file 
array.xml in en:!-- $Revision: 1.108 $ --commento che informa 
aquale revisione si riferisce la traduzione del filearray.xml in 
it:!-- EN-Revision: 1.108 Maintainer: cucinato Status: ready 
--Se c'è poi qualche informazione che dovrei sapere,o avete 
qualche consiglio da darmi, sarebbe assolutamente gradito :)Un grazie a 
tutti, e buon lavoro :)Spero che il sig. Luca Perugini non si sia 
adirato conme per le troppe domande :)Ciao ... 
Alan


Re: [PHP-DOC] ai traduttori italiani

2001-10-31 Thread Sander Roobol

 Ciao a tutti,
 da oggi faccio parte anche io del gruppo di lavoro
 per la manutenzione e la traduzione del manuale PHP
 in Italiano.
 [snip]
Can you please post in English? Most people don't understand Italian (nor do
I).

Sander




[PHP-DOC] cvs: phpdoc / global.ent

2001-10-31 Thread jim winstead

jimwWed Oct 31 17:35:12 2001 EDT

  Modified files:  
/phpdoc global.ent 
  Log:
  update rfc entries in global.ent
  
Index: phpdoc/global.ent
diff -u phpdoc/global.ent:1.116 phpdoc/global.ent:1.117
--- phpdoc/global.ent:1.116 Sun Oct 28 13:32:15 2001
+++ phpdoc/global.ent   Wed Oct 31 17:35:12 2001
@@ -1,6 +1,6 @@
 !-- -*- SGML -*-
 
- $Id: global.ent,v 1.116 2001/10/28 18:32:15 jeroen Exp $
+ $Id: global.ent,v 1.117 2001/10/31 22:35:12 jimw Exp $
 
  Contains global macros for all the XML documents.
 
@@ -139,9 +139,11 @@
 !ENTITY url.redhat.support 
http://www.redhat.com/products/ccvs/support/CCVS3.3docs/ProgPHP.html;
 !ENTITY url.rfc  'http://www.faqs.org/rfcs/'
 !ENTITY url.rfc.editor  'http://www.rfc-editor.org/'
-!ENTITY url.rfc1950  'ftp://ftp.uu.net/pub/archiving/zip/doc/rfc1950.txt'
-!ENTITY url.rfc1951  'ftp://ftp.uu.net/pub/archiving/zip/doc/rfc1951.txt'
-!ENTITY url.rfc1952  'ftp://ftp.uu.net/pub/archiving/zip/doc/rfc1952.txt'
+!ENTITY url.rfc1806  'http://www.ietf.org/rfc/rfc1806.txt'
+!ENTITY url.rfc1896  'http://www.ietf.org/rfc/rfc1896.txt'
+!ENTITY url.rfc1950  'http://www.ietf.org/rfc/rfc1950.txt'
+!ENTITY url.rfc1951  'http://www.ietf.org/rfc/rfc1951.txt'
+!ENTITY url.rfc1952  'http://www.ietf.org/rfc/rfc1952.txt'
 !ENTITY url.sablotron http://www.gingerall.com/;
 !ENTITY url.sesam.de 
http://its.siemens.de/lobs/its/techinf/oltp/sesam/manuals/index_gr.htm;
 !ENTITY url.sesam.en 
http://its.siemens.de/lobs/its/techinf/oltp/sesam/manuals/index_en.htm;





[PHP-DOC] cvs: phpdoc /en/functions mail.xml

2001-10-31 Thread jim winstead

jimwWed Oct 31 17:45:44 2001 EDT

  Modified files:  
/phpdoc/en/functionsmail.xml 
  Log:
  some reformatting, use example.com for example email addresses. (now i know where 
all those stupid messages bouncing off [EMAIL PROTECTED] came from.)
  
Index: phpdoc/en/functions/mail.xml
diff -u phpdoc/en/functions/mail.xml:1.29 phpdoc/en/functions/mail.xml:1.30
--- phpdoc/en/functions/mail.xml:1.29   Wed Oct 10 16:58:09 2001
+++ phpdoc/en/functions/mail.xmlWed Oct 31 17:45:43 2001
@@ -1,5 +1,5 @@
 ?xml encoding=iso-8859-1?
-!-- $Revision: 1.29 $ --
+!-- $Revision: 1.30 $ --
  reference id=ref.mail
   titleMail functions/title
   titleabbrevMail/titleabbrev
@@ -41,18 +41,17 @@
  accomplished via MIME-encoding - for more information, see
  ulink url=http://www.zend.com/zend/spotlight/sendmimeemailpart1.php;
  http://www.zend.com/zend/spotlight/sendmimeemailpart1.php/ulink or
- RFC 1896 (Visit ulink url=http://www.rfc-editor.org/;
- http://www.rfc-editor.org//ulink).
+ ulink url=url.rfc1896;RFC 1896/ulink).
 /simpara
 para
  functionmail/function returns true; if the mail
- is sucessfully sent, false; otherwise.
+ is successfully sent, false; otherwise.
 /para
 para
  example
   titleSending mail./title
   programlisting
-mail([EMAIL PROTECTED], My Subject, Line 1\nLine 2\nLine 3);
+mail([EMAIL PROTECTED], My Subject, Line 1\nLine 2\nLine 3);
   /programlisting
  /example/para
 simpara
@@ -77,16 +76,17 @@
  example
   titleSending mail with extra headers./title
   programlisting
-mail([EMAIL PROTECTED], the subject, $message,
+mail([EMAIL PROTECTED], the subject, $message,
  From: webmaster@$SERVER_NAME\nReply-To: webmaster@$SERVER_NAME\nX-Mailer: PHP/ 
. phpversion());
   /programlisting
  /example
- With the fifth parameter you can set additional command line parameters to
- the actual mailer. In the example below we set the correct Return-Path
- header for sendmail. Normally sendmail will add the X-Authentication-Warning
- header when using the -f parameter, because the webserver user is probably
- not a member of the trusted users. To suppress this warning, you should add
- the web server user to the trusted users in your sendmail config file.
+ With the fifth parameter you can set additional command line
+ parameters to the mail program. In the example below we set the
+ correct Return-Path header when using sendmail. Normally sendmail
+ will add the X-Authentication-Warning header when using the -f
+ parameter, because the webserver user is probably not a member of
+ the trusted users. To suppress this warning, you should add the web
+ server user to the trusted users in your sendmail configuration file.
 /para
 note
  para
@@ -97,7 +97,7 @@
  example
   titleSending mail with extra headers and setting an additional command line 
parameter./title
   programlisting
-mail([EMAIL PROTECTED], the subject, $message,
+mail([EMAIL PROTECTED], the subject, $message,
  From: webmaster@$SERVER_NAME, -fwebmaster@$SERVER_NAME);
   /programlisting
  /example
@@ -107,9 +107,8 @@
   titleSending complex email./title
   programlisting
 /* recipients */
-$recipient .= Mary lt;[EMAIL PROTECTED] . ,  ; //note the comma
-$recipient .= Kelly lt;[EMAIL PROTECTED] . , ;
-$recipient .= [EMAIL PROTECTED];
+$recipient .= Mary lt;[EMAIL PROTECTED]gt; . ,  ; //note the comma
+$recipient .= Kelly lt;[EMAIL PROTECTED]gt;;
 
 /* subject */
 $subject = Birthday Reminders for August;
@@ -121,22 +120,22 @@
 $message .= 17rd\t\tAug \t\t1973\n;
 
 /* you can add a stock signature */
-$message .= --\r\n; //Signature delimiter
-$message .= Birthday reminder copylefted by public domain;
+$message .= -- \r\n; //Signature delimiter
+$message .= Birthday reminder;
 
 /* additional header pieces for errors, From cc's, bcc's, etc */
 
-$headers .= From: Birthday Reminder lt;[EMAIL PROTECTED]\n;
-$headers .= X-Sender: lt;[EMAIL PROTECTED]\n;
+$headers .= From: Birthday Reminder lt;[EMAIL PROTECTED]gt;\n;
+$headers .= X-Sender: lt;[EMAIL PROTECTED]gt;\n;
 $headers .= X-Mailer: PHP\n; // mailer
 $headers .= X-Priority: 1\n; // Urgent message!
-$headers .= Return-Path: lt;[EMAIL PROTECTED]\n;  // Return path for errors
+$headers .= Return-Path: lt;[EMAIL PROTECTED]gt;\n;  // Return path for errors
 
-/* If you want to send html mail, uncomment the following line */
-// $headers .= Content-Type: text/html; charset=iso-8859-1\n; // Mime type
+/* To send HTML mail, you can set the Content-type header. */
+// $headers .= Content-type: text/html; charset=iso-8859-1\n;
 
-$headers .= cc: [EMAIL PROTECTED]\n; // CC to
-$headers .= bcc: [EMAIL PROTECTED], [EMAIL PROTECTED]; // BCCs to
+$headers .= Cc: [EMAIL PROTECTED]\n;
+$headers .= Bcc: [EMAIL PROTECTED]\n;
 
 /* and now mail it */
 mail($recipient, $subject, $message, 

[PHP-DOC] cvs: phpdoc / global.ent /en/functions http.xml

2001-10-31 Thread jim winstead

jimwWed Oct 31 20:58:12 2001 EDT

  Modified files:  
/phpdoc global.ent 
/phpdoc/en/functionshttp.xml 
  Log:
  rfc2183 supercedes rfc1806
  
Index: phpdoc/global.ent
diff -u phpdoc/global.ent:1.117 phpdoc/global.ent:1.118
--- phpdoc/global.ent:1.117 Wed Oct 31 17:35:12 2001
+++ phpdoc/global.ent   Wed Oct 31 20:58:11 2001
@@ -1,6 +1,6 @@
 !-- -*- SGML -*-
 
- $Id: global.ent,v 1.117 2001/10/31 22:35:12 jimw Exp $
+ $Id: global.ent,v 1.118 2001/11/01 01:58:11 jimw Exp $
 
  Contains global macros for all the XML documents.
 
@@ -139,7 +139,7 @@
 !ENTITY url.redhat.support 
http://www.redhat.com/products/ccvs/support/CCVS3.3docs/ProgPHP.html;
 !ENTITY url.rfc  'http://www.faqs.org/rfcs/'
 !ENTITY url.rfc.editor  'http://www.rfc-editor.org/'
-!ENTITY url.rfc1806  'http://www.ietf.org/rfc/rfc1806.txt'
+!ENTITY url.rfc2183  'http://www.ietf.org/rfc/rfc2183.txt'
 !ENTITY url.rfc1896  'http://www.ietf.org/rfc/rfc1896.txt'
 !ENTITY url.rfc1950  'http://www.ietf.org/rfc/rfc1950.txt'
 !ENTITY url.rfc1951  'http://www.ietf.org/rfc/rfc1951.txt'
Index: phpdoc/en/functions/http.xml
diff -u phpdoc/en/functions/http.xml:1.30 phpdoc/en/functions/http.xml:1.31
--- phpdoc/en/functions/http.xml:1.30   Wed Oct 31 17:27:31 2001
+++ phpdoc/en/functions/http.xmlWed Oct 31 20:58:12 2001
@@ -1,5 +1,5 @@
 ?xml encoding=iso-8859-1?
-!-- $Revision: 1.30 $ --
+!-- $Revision: 1.31 $ --
  reference id=ref.http
   titleHTTP functions/title
   titleabbrevHTTP/titleabbrev
@@ -167,7 +167,7 @@
 para
  If you want the user to be prompted to save the data you are
  sending, such as a generated PDF file, you can use the ulink
- url=url.rfc1806;Content-Disposition/ulink header to
+ url=url.rfc2183;Content-Disposition/ulink header to
  supply a recommended filename and force the browser to display the
  save dialog.
  informalexample





[PHP-DOC] Bug #13890: Docu-Error at opendir()

2001-10-31 Thread hannes . dorn

From: [EMAIL PROTECTED]
Operating system: Windows 2000
PHP version:  4.0.6
PHP Bug Type: Documentation problem
Bug description:  Docu-Error at opendir()

Related File: chm
This file was generated: Thu Jul 26 22:28:30 2001

In opendir() docu, it says:

if ($dir = @opendir(/tmp)) {
  while($file = readdir($dir)) {
echo $file\n;
  }  
  closedir($dir);
}

The while statement stops wenn a filename contains only of a 0. In
readdir() the docu is correct.

$handle=opendir('.');
echo Directory handle: $handle\n;
echo Files:\n;
while (($file = readdir($handle))!==false) {
echo $file\n;
}
closedir($handle); 
Note the !== false in the while statement.

Rasty
-- 
Edit bug report at: http://bugs.php.net/?id=13890edit=1