Re: [PHP-DOC] clearing the behaviour of unset()

[Egon Schmid]

Hi Konstantin and/or Ursula,
 
please do not write your local announcements 
to this PHPDOC list. It isn´t very interesting for agricultural students at 
the University of Hohenheim :).
 
-Egon  

  - Original Message - 
  From: 
  Konstantin 
  Schukraft 
  To: [EMAIL PROTECTED] 
  Sent: Monday, July 21, 2003 8:49 PM
  Subject: Re: [PHP-DOC] clearing the 
  behaviour of unset()
  
  Hallo liebe 
  Studierende und Fachschaftsaktive, 
  
  alle Halbjahre 
  wieder .. 
  
  Wir vom Büro 
  für Internationale Angelegenheiten planen gerade wieder die 
  Einführungsveranstaltung - genannt Orientation Seminar - für alle neuen 
  internationalen Studierenden zum Wintersemester 2003. 
  Der Termin wird 
  der 8.-10. Oktober sein. 
  
  Wie immer 
  möchten wir den Studierenden auch eine Fachstudienberatung  anbieten, 
  wofür wir Eure Hilfe brauchen. 
  Der Termin 
  wäre am Freitag, dem 10. Oktober und zwar zwischen 11:00  und 
  13:00 Uhr im K2, Keplerstraße 17, 9. und 10. Stock. 
  
  Es könnten aber 
  auch Termine in Vaihingen vereinbart werden, wenn dies sinnvoll erscheint, 
  weil man den 'Neuen' gleich das Institut/Einrichtungen etc. vor Ort zeigen 
  möchte oder wenn es für  Euch den Aufwand nicht rechtfertigt, da es sich 
  nur um 1-2  Studierende handelt. 
  Wir werden 
  sicherlich wieder jemanden brauchen für Architektur, BWL, E- technik, 
  Maschinenbau, Verfahrenstechnik. Genauere  Zahlen werde ich halt erst 
  kurz vorher haben, auch wie immer.
  
  Wer von Euch 
  Interesse und Zeit hat, einer kleinen Gruppe von Studierenden aus aller Welt 
  bei der Stundenplangestaltung und durch den Vorlesungsdschungel zu helfen, 
  sollte sich diesen Termin schon mal vormerken und möglichst bald bei mir 
  rückmelden (email). 
  
  Nähere Infos zu 
  den Studierenden und um was es bei dieser Fachstudienberatung genau gehen 
  soll, bekommt ihr auch bei mir.
  
  Herzlichen Dank 
  schon mal vorab und 
  viele Grüße aus 
  dem  
  International 
  Office 
  ---
  Ursula 
  Habel
  
  Advisor for 
  International Scholarship Holders
  Office of 
  International Affairs
  Universitaet 
  Stuttgart
  Geschwister-Scholl-Str. 24
  D-70174 
  Stuttgart
  Tel: +49 711 
  121-2793  
  Fax: +49 711 
  121-4104
  http://www.uni-stuttgart.de/ia/
  
  Office hours: 
  
  Mon  
  1:30-4 pm, Tues 9-12 am, Wedn 1:30-5 pm
  Thurs 9-12 am, 
  Frid closed
  
  
  
  

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

Re: [PHP-DOC] cvs: phpdoc-de /reference/com functions.xml

[Egon Schmid]

From: "Thomas Schoefbeck" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, May 15, 2002 10:11 PM
Subject: [PHP-DOC] cvs: phpdoc-de /reference/com functions.xml


> tom Wed May 15 16:11:47 2002 EDT
>
>   Removed files:
> /phpdoc-de/reference/com functions.xml
>   Log:
>   no need, the en-version is always up-to-date

Please stop the removal of German files. All German files are in
German language. I have removed the not translated files since we
have a automatical fallback to the English version if there is no
German translation.

-Egon

Re: [PHP-DOC] cvs: phpdoc-de / translation.xml

[Egon Schmid]

From: "Thomas Schoefbeck" <[EMAIL PROTECTED]>

> tom Thu May  9 13:34:48 2002 EDT
>
>   Modified files:
> /phpdoc-de translation.xml
>   Log:
>   deleted WIP-entries older than Nov. 2001 (nobody can seriously
work up to 2 years on one file), del. also language variables, since
it's already ready till 1.32
>
> Index: phpdoc-de/translation.xml
> diff -u phpdoc-de/translation.xml:1.29
phpdoc-de/translation.xml:1.30
> --- phpdoc-de/translation.xml:1.29 Thu Apr 18 12:08:03 2002
> +++ phpdoc-de/translation.xml Thu May  9 13:34:47 2002
> @@ -45,28 +45,11 @@
>   
>
>   
> -  
> -  
>
> -  
> -  
> -  
> -  
>
> -  
>
>
> -  
> -  
>
> -  
> -  
> -  
> -  
> -  
> -  
> -  
> -  
>   
>
>  

Please revert this patch. It is really silly to remove lines with
old dates.

-Egon

Re: [PHP-DOC] cvs: phpdoc /en/reference/pgsql reference.xml

[Egon Schmid]

From: "Anderson Fortaleza" <[EMAIL PROTECTED]>

> phaser Fri May  3 14:30:09 2002 EDT
>
>   Modified files:
> /phpdoc/en/reference/pgsql reference.xml
>   Log:
>   1st translated version

Please revert this patch. You have translated the English file into
another language.

-Egon

Re: [PHP-DOC] Indentation in mysql examples

[Egon Schmid]

From: "Simone Cortesi" <[EMAIL PROTECTED]>
> At 00.24 03/05/02 +0200, =?iso-8859-2?Q?S=B3awomir_Pucia?= wrote:
>
> >Probably you didn't get the point.
> >
> >Since 1.101 many examples look like...
> >
> > > /* Connecting, selecting database */
> > $link = mysql_connect("mysql_host", "mysql_user",
"mysql_password")
> > or die("Could not connect");
> > print "Connected successfully";
> >[...]
> >
> >Until 1.101 they looked like...
> >
> > >/* Connecting, selecting database */
> >$link = mysql_connect("mysql_host", "mysql_user",
"mysql_password")
> > or die("Could not connect");
> >print "Connected successfully";
> >[...]
> >
> >The question is whether or not to use these 4 spaces in each
line. If yes, I
> >will correct the rest of mysql related files, and use it in pl/.
>
> I've read that we should start at column 1 in examples:
>
> Take a look at: /phpdoc/RFC/coding_standards

Oh, it seems that Derick haven´t read the coding_standards :(

-Egon

Re: [PHP-DOC] Indentation in mysql examples

[Egon Schmid]

From: "Sławomir Pucia" <[EMAIL PROTECTED]>

> Could someone (maybe Derick) please explain why indentation of
many (half?)
> examples in mysql.xml (revision 1.101) have been changed? Now we
have half
> of the examples indented (4 spaces) and half not. Now I'm confused
with
> applying these changes to pl/. IMHO we should go back to
non-indented
> examples (as in the rest of chapters).

Since the beginning of the English PHP Manual, there have been 4
spaces in examples. You can correct this in en/ and use it in the
pl/ tree.

-Egon

Re: [PHP-DOC] please answer

[Egon Schmid]

From: "haha web" <[EMAIL PROTECTED]>

> Hello!
> I am Kaido from Estonia.

> I decided to translate the full PHP Manual into estonian and now I
have
> done one so far not much, about 55 functions are already
translated.

I don´t know, but I think Estonians speaks the russian language.

> But when I finish the translation, am I allowed to sale it for
money? All
> who want it in estonian here in Estonia they should pay for that
(only for
> my work on the translation). Is this allowed? If not, then I don't
sale
> it and I put it into my homepage for free and everybody can visit
this site
> and learn PHP.

Please join the russian translators or/and ask for a CVS account at
php.net, if the languages are so different.

> So, what do you think?
> It would be great if I could sale it, because I put my time into
> translating.

I have put also many hours and years into the English and German PHP
manual. If you want to sell it, you have to put the original authors
on the front page and use the current licence GPL.

-Egon


kaido

Re: [PHP-DOC] /en/appendices/reserved.xml

[Egon Schmid]

From: "Simone Cortesi" <[EMAIL PROTECTED]>

> on top of /phpdoc/en/appendices/reserved.xml I read this note.
>
> 
>
> Is it still valid? I already have an italian version of that file,
but it
> is version 1.14 while the current english one is 1.18.
>
> What should I do? sync the italian translation? wait?

I think you can ignore this comment or even better, delete it.
Haven´t found the original author in CVS. The same should we done
with the install.xml splitting by Mark.

-Egon

Re: [PHP-DOC] cvs: phpdoc /de Translators

[Egon Schmid]

From: "Simone Cortesi" <[EMAIL PROTECTED]>
> At 02.47 16/04/02 +0200, Egon Schmid wrote:
>
> >Good idea! With Cornelia I have spoken this evening and told her
> >that Catharina is back again.  I have told Conni, that she should
do
> >the same, but it seems that you knows about our speaking at
> >Stuttgart (MySQL meeting in the pub "Step In").
>
> I dunno why, but if you look at my commit it seems like I did
change
> something in the /de/Translators file, but if you look at
cvs.php.net on
> the web the change has been made by Cornelia.

I have told her to do so and it can be that I have missed the commit
message. The meeting tooks many hours :(

-Egon

Re: [PHP-DOC] cvs: phpdoc /de Translators /en/reference/mssql reference.xml /en/reference/muscat reference.xml /en/reference/mysql reference.xml /en/reference/ncurses reference.xml /en/reference/network reference.xml /en/reference/nis reference.xml

[Egon Schmid]

From: "Simone Cortesi" <[EMAIL PROTECTED]>
Sent: Monday, April 15, 2002 11:57 PM
Subject: [PHP-DOC] cvs: phpdoc /de Translators /en/reference/mssql

Good idea! With Cornelia I have spoken this evening and told her
that Catharina is back again.  I have told Conni, that she should do
the same, but it seems that you knows about our speaking at
Stuttgart (MySQL meeting in the pub "Step In").

-Egon

--- phpdoc/de/Translators:1.300 Sat Apr 13 09:03:43 2002
+++ phpdoc/de/Translators Mon Apr 15 17:57:06 2002
@@ -166,7 +166,8 @@
 pcre.xmlRichard Samar   in Arbeit
 pdf.xml Uwe Steinmann   in Arbeit
 pfpro.xml   Sebastian Nohn  fertig (bis V.
1.12)
-pgsql.xml   Cornelia Boenigkfertig (Rev.
1.78)
+pgsql.xml   Catharina Paulsen
+Cornelia Boenigkfertig (Rev.
1.78)
 posix.xml   Martin Samesch  fertig (Rev.
1.19)
 printer.xml
 pspell.xml  Martin Samesch  in Arbeit

Re: [PHP-DOC] cvs: phpdoc /de/chapters config.xml install.xml /de/functions mysql.xml

[Egon Schmid]

Hi Georg,

you have deleted my girl friends :(

-Egon

- Original Message -
From: "Georg Richter" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, April 11, 2002 5:19 PM
Subject: [PHP-DOC] cvs: phpdoc /de/chapters config.xml install.xml
/de/functions mysql.xml


> georg Thu Apr 11 11:19:41 2002 EDT
>
>   Modified files:
> /phpdoc/de/chapters install.xml config.xml
> /phpdoc/de/functions mysql.xml
>   Log:
>
>   a) moved ini-descriptions into mysql.xml
>   b) restructuring of partintro
>   c) consistent parameters in examples: localhost, mysql_user,
mysql_password
>   e) Translation for mysql_info
>
>

Re: [PHP-DOC] Bug #16530 Updated: in PHP 4.1.2, calling mysql_real_escape_string fails

[Egon Schmid]

Please don´t document new function names in the documentation. This
will be done by scripts from Hartmut Holzgraefe.

Please only document added or deleted functions "argument"s, because
they cannot detected with the above mentioned scripts.

-Egon

- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Wednesday, April 10, 2002 5:27 PM
Subject: [PHP-DOC] Bug #16530 Updated: in PHP 4.1.2, calling
mysql_real_escape_string fails


> ID:  16530
>  Updated by:  [EMAIL PROTECTED]
>  Reported By: [EMAIL PROTECTED]
> -Status:  Open
> +Status:  Closed
>  Bug Type:Documentation problem
>  PHP Version: 4.1.2
>  New Comment:
>
> This bug has been fixed in CVS.
>
>
> Previous Comments:
> --
--
>
> [2002-04-10 10:31:43] [EMAIL PROTECTED]
>
> Documentation problem. It should be stated on the manual page.
>
> --
--
>
> [2002-04-10 10:30:32] [EMAIL PROTECTED]
>
> It is added in 4.3.0 and the version info hasn't been updated on
the
> site yet.
>
> Derick
>
> --
--
>
> [2002-04-10 10:27:53] [EMAIL PROTECTED]
>
> In PHP 4.1.2 (not tested on other versions), calling
> mysql_real_escape_string fails w/ message:
>
> "Call to undefined function: mysql_real_escape_string() in ..."
>
>
>
> --
--
>
>
> --
> Edit this bug report at http://bugs.php.net/?id=16530&edit=1
>
>

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

[Egon Schmid]

From: "Friedhelm Betz" <[EMAIL PROTECTED]>
>   Modified files:
> /phpdoc/en/language variables.xml
>   Log:
>   typo fix
>
> Index: phpdoc/en/language/variables.xml
> diff -u phpdoc/en/language/variables.xml:1.42
phpdoc/en/language/variables.xml:1.43
> --- phpdoc/en/language/variables.xml:1.42 Thu Mar 28 12:16:45 2002
> +++ phpdoc/en/language/variables.xml Tue Apr  2 06:32:26 2002
> @@ -1,5 +1,5 @@
>  
> -
> +
>   
>Variables
>
> @@ -608,7 +608,7 @@
>  
>  Warthog
>  Guinness
> -Stuttgarter Schwabenbräu
> +Stuttgarter Schwabenbräu
>  
>  
>  

Please revert this patch. Our native English speakers doesnt see a
"ä". In the German PHP manual it is okay, but not in the English
manual.

-Egon

[PHP-DOC] cvs: phpdoc /de/functions math.xml

[Egon Schmid]

eschmid Sat Mar 30 23:21:13 2002 EDT

  Modified files:  
/phpdoc/de/functionsmath.xml 
  Log:
  Fixed a typo
  
Index: phpdoc/de/functions/math.xml
diff -u phpdoc/de/functions/math.xml:1.22 phpdoc/de/functions/math.xml:1.23
--- phpdoc/de/functions/math.xml:1.22   Fri Mar 22 12:31:33 2002
+++ phpdoc/de/functions/math.xmlSat Mar 30 23:21:13 2002
@@ -230,7 +230,7 @@
  Diese Funktion liefert einen String, der
  number zur Basis
  tobase enthält. Der Parameter
- frombase giebt die Basis des Eingabewertes
+ frombase gibt die Basis des Eingabewertes
  number an. tobase
  und tobase können Werte von 2 bis
  einschließlich 36 enthalten. Für die Darstellung von Werten mit

Re: [PHP-DOC] section titles to entities :)

[Egon Schmid]

From: <[EMAIL PROTECTED]>
> On Fri, 29 Mar 2002, Egon Schmid wrote:
>
> > -100 for me. It doesn´t help for translations. I know that not
every
> > translator use entities in a correct way.
>
> Then teach them to use it correctly. If used correctly, the
translations
> whould be consisntent more easier and it's less typing.

No, I don´t teach them. It is easier for me, not translating the
entities file. Have you ever used emacs?  This files are are so
wrong, that I cannot use the psgml-mode with emacs. Please look at
the double and single quotes.

-Egon

Re: [PHP-DOC] section titles to entities :)

[Egon Schmid]

- Original Message -
From: "Gabor Hojtsy" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, March 29, 2002 8:53 PM
Subject: [PHP-DOC] section titles to entities :)


> Hi!
>
> I would like to propose to put all section titles now used
> in function reference files to entities, like
> Runtime Configuration  to
> §itle.runtime; because of the ease [**and consistency**]
> of translations.

-100 for me. It doesn´t help for translations. I know that not every
translator use entities in a correct way.

-Egon

Re: [PHP-DOC] cron reference

[Egon Schmid]

From: "Andrew Lindeman" <[EMAIL PROTECTED]>

> In http://www.php.net/manual/en/intro-whatcando.php, the page
mentions cron,
> but in parans it says "task scheduler on Windows."  Now, I'm
pretty sure that
> cron runs on linux/unix (unless theres a port).  I just want to
make sure
> that linux/unix was meant there before I change it.
>
> Also, I'll ask again: what do I need to do to get my name as an
> author/editor/etc.. of the PHP manual.  I usually just edit/delete
user
> submitted notes, but I do try to regularly maintain the
documentation (like
> this).

If you do more like Hartmut Holzgraefe? He is on my list for new
authors. And there are others ...

-Egon

Re: [PHP-DOC] cvs: phpdoc /de/language oop.xml

[Egon Schmid]

From: "Gabor Hojtsy" <[EMAIL PROTECTED]>

> > Please translate the comments in exampls back into German. It
> > doesn´t make any sense to have English comments in a German PHP
> > manual.
>
> The whole file seems to be comitted in English not German.

Oops, haven´t read the huge commit not very carefull. Version 1.8 of
de/language/oop.xml is English and version 1.7 is German. Thank you
for reporting this.

-Egon

Re: [PHP-DOC] cvs: phpdoc /de/language oop.xml

[Egon Schmid]

Please translate the comments in exampls back into German. It
doesn´t make any sense to have English comments in a German PHP
manual.

-Egon

- Original Message -
From: "Thomas Schoefbeck" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, March 27, 2002 8:22 PM
Subject: [PHP-DOC] cvs: phpdoc /de/language oop.xml


> tom Wed Mar 27 14:22:06 2002 EDT
>
>   Modified files:
> /phpdoc/de/language oop.xml
>   Log:
>   file is finally complete now, translation will follow soon
>

Re: [PHP-DOC] cvs: phpdoc /de/language operators.xml

[Egon Schmid]

Oops, the entities should be written as &false; and &true; and NOT
as "&false" and "&true". Please remove the quotation and add a
semicolon at the end.

-Egon

- Original Message -
From: "Hakan Kuecuekyilmaz" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, March 27, 2002 2:47 PM
Subject: [PHP-DOC] cvs: phpdoc /de/language operators.xml


> hakan Wed Mar 27 08:47:48 2002 EDT
>
>   Modified files:
> /phpdoc/de/language operators.xml
>   Log:
>   changed TRUE and FALSE with appropriatate entities
>   thanks to Egon Schmid
>
>
> Index: phpdoc/de/language/operators.xml
> diff -u phpdoc/de/language/operators.xml:1.12
phpdoc/de/language/operators.xml:1.13
> --- phpdoc/de/language/operators.xml:1.12 Wed Mar 27 07:06:09 2002
> +++ phpdoc/de/language/operators.xml Wed Mar 27 08:47:48 2002
> @@ -190,38 +190,38 @@
> 
>  $a == $b
>  Gleich
> -Gibt "TRUE" zurück, wenn $a gleich $b ist.
> +Gibt "&true" zurück, wenn $a gleich $b
ist.
> 
> 
>  $a === $b
>  Identisch
> -Gibt "TRUE" zurück wenn $a gleich $b ist und beide
> +Gibt "&true" zurück wenn $a gleich $b ist und
beide
>  vom gleichen Typ sind(funktioniert nur in PHP4)
> 
> 
>  $a != $b
>  Ungleich
> -Gibt "TRUE" zurück, wenn $a nicht gleich $b
ist.
> +Gibt "&true" zurück, wenn $a nicht gleich $b
ist.
> 
> 
>  $a < $b
>  Kleiner Als
> -Gibt "TRUE" zurück, wenn $a kleiner als $b
ist.
> +Gibt "&true" zurück, wenn $a kleiner als $b
ist.
> 
> 
>  $a > $b
>  Größer Als
> -Gibt "TRUE" zurück, wenn $a größer als $b
ist.
> +Gibt "&true" zurück, wenn $a größer als $b
ist.
> 
> 
>  $a <= $b
>  Kleiner Gleich 
> -Gibt "TRUE" zurück, wenn $a kleiner oder gleich $b
ist.
> +Gibt "&true" zurück, wenn $a kleiner oder gleich
$b ist.
> 
> 
>  $a >= $b
>  Größer Gleich
> -Gibt "TRUE" zurück, wenn $a größer oder gleich $b
ist.
> +Gibt "&true" zurück, wenn $a größer oder gleich $b
ist.
> 
>
>   
> @@ -239,9 +239,9 @@
>
>   Dieser Ausdruch gibt
>   ausdr2 zurück, wenn
> - ausdr1 "TRUE" zurückgibt, und
> + ausdr1 "&true" zurückgibt, und
>   ausdr3, wenn
> - ausdr1 "FALSE" zurückgibt.
> + ausdr1 "&false" zurückgibt.
> 
>
>
> @@ -409,32 +409,32 @@
> 
>  $a and $b
>  Und
> -TRUE wenn sowohl $a als auch $b TRUE ist.
> +&true wenn sowohl $a als auch $b &true
ist.
> 
> 
>  $a or $b
>  Oder
> -TRUE wenn $a oder $b TRUE ist.
> +&true wenn $a oder $b &true ist.
> 
> 
>  $a xor $b
>  Entweder Oder
> -TRUE wenn entweder $a oder $b TRUE ist, aber nicht
beide.
> +&true wenn entweder $a oder $b &true ist, aber
nicht beide.
> 
> 
>  ! $a
>  Nicht
> -TRUE wenn $a nicht TRUE ist.
> +&true wenn $a nicht &true ist.
> 
> 
>  $a && $b
>  Und
> -TRUE wenn sowohl $a als auch $b TRUE ist.
> +&true wenn sowohl $a als auch $b &true
ist.
> 
> 
>  $a || $b
>  Oder
> -TRUE wenn $a oder $b TRUE ist.
> +&true wenn $a oder $b &true ist.
> 
>
>   
>
>
>

Re: [PHP-DOC] cvs: phpdoc /de/language operators.xml

[Egon Schmid]

Please use the entities &false; and &true; which you can find in
phpdoc/entities/globals.ent at the end of this file.

-Egon

- Original Message -
From: "Hakan Kuecuekyilmaz" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, March 27, 2002 1:06 PM
Subject: [PHP-DOC] cvs: phpdoc /de/language operators.xml


> hakan Wed Mar 27 07:06:16 2002 EDT
>
>   Modified files:
> /phpdoc/de/language operators.xml
>   Log:
>   replaced wahr with TRUE and falsch with FALSE
>   thanks to Friedhelm Betz
>
>
> Index: phpdoc/de/language/operators.xml
> diff -u phpdoc/de/language/operators.xml:1.11
phpdoc/de/language/operators.xml:1.12
> --- phpdoc/de/language/operators.xml:1.11 Wed Mar 27 03:20:41 2002
> +++ phpdoc/de/language/operators.xml Wed Mar 27 07:06:09 2002
> @@ -190,38 +190,38 @@
> 
>  $a == $b
>  Gleich
> -Gibt "wahr" zurück, wenn $a gleich $b ist.
> +Gibt "TRUE" zurück, wenn $a gleich $b ist.
> 
> 
>  $a === $b
>  Identisch
> -Gibt "wahr" zurück wenn $a gleich $b ist und beide
> +Gibt "TRUE" zurück wenn $a gleich $b ist und beide
>  vom gleichen Typ sind(funktioniert nur in PHP4)
> 
> 
>  $a != $b
>  Ungleich
> -Gibt "wahr" zurück, wenn $a nicht gleich $b
ist.
> +Gibt "TRUE" zurück, wenn $a nicht gleich $b
ist.
> 
> 
>  $a < $b
>  Kleiner Als
> -Gibt "wahr" zurück, wenn $a kleiner als $b
ist.
> +Gibt "TRUE" zurück, wenn $a kleiner als $b
ist.
> 
> 
>  $a > $b
>  Größer Als
> -Gibt "wahr" zurück, wenn $a größer als $b
ist.
> +Gibt "TRUE" zurück, wenn $a größer als $b
ist.
> 
> 
>  $a <= $b
>  Kleiner Gleich 
> -Gibt "wahr" zurück, wenn $a kleiner oder gleich $b
ist.
> +Gibt "TRUE" zurück, wenn $a kleiner oder gleich $b
ist.
> 
> 
>  $a >= $b
>  Größer Gleich
> -Gibt "wahr" zurück, wenn $a größer oder gleich $b
ist.
> +Gibt "TRUE" zurück, wenn $a größer oder gleich $b
ist.
> 
>
>   
> @@ -239,9 +239,9 @@
>
>   Dieser Ausdruch gibt
>   ausdr2 zurück, wenn
> - ausdr1 "wahr" zurückgibt, und
> + ausdr1 "TRUE" zurückgibt, und
>   ausdr3, wenn
> - ausdr1 "falsch" zurückgibt.
> + ausdr1 "FALSE" zurückgibt.
> 
>
>
> @@ -409,32 +409,32 @@
> 
>  $a and $b
>  Und
> -Wahr wenn sowohl $a als auch $b wahr ist.
> +TRUE wenn sowohl $a als auch $b TRUE ist.
> 
> 
>  $a or $b
>  Oder
> -Wahr wenn $a oder $b wahr ist.
> +TRUE wenn $a oder $b TRUE ist.
> 
> 
>  $a xor $b
>  Entweder Oder
> -Wahr wenn entweder $a oder $b wahr ist, aber nicht
beide.
> +TRUE wenn entweder $a oder $b TRUE ist, aber nicht
beide.
> 
> 
>  ! $a
>  Nicht
> -Wahr wenn $a nicht wahr ist.
> +TRUE wenn $a nicht TRUE ist.
> 
> 
>  $a && $b
>  Und
> -Wahr wenn sowohl $a als auch $b wahr ist.
> +TRUE wenn sowohl $a als auch $b TRUE ist.
> 
> 
>  $a || $b
>  Oder
> -Wahr wenn $a oder $b wahr ist.
> +TRUE wenn $a oder $b TRUE ist.
> 
>
>   
>
>
>

Re: [PHP-DOC] cvs: phpdoc /de/functions math.xml

[Egon Schmid]

Oh my ? It was Hartmut, who speaks sometimes in a never existing
language from a city which had never existed. If it does make you
happy, we should change the Bielefeld slang to the Swabian slang.

-Egon

- Original Message -
From: "Thomas Schoefbeck" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, March 22, 2002 6:31 PM
Subject: [PHP-DOC] cvs: phpdoc /de/functions math.xml


> tom Fri Mar 22 12:31:34 2002 EDT
>
>   Modified files:
> /phpdoc/de/functions math.xml
>   Log:
>   some typos
>
> Index: phpdoc/de/functions/math.xml
> diff -u phpdoc/de/functions/math.xml:1.21
phpdoc/de/functions/math.xml:1.22
> --- phpdoc/de/functions/math.xml:1.21 Sat Feb  2 10:34:04 2002
> +++ phpdoc/de/functions/math.xml Fri Mar 22 12:31:33 2002
> @@ -203,8 +203,8 @@
>   Diese Funktion berechnet den Arcustangens aus den Parametern
>   x und y im
Bereich
>   (-¶; ¶].  Dieser entspricht weitgehend dem
Arcustangens
> - aus x / y, allerdingskann hier das Vorzeichen beider
Parameter
> - ausgewertet und so der Quadrant des Ergebnises bestimmt
werden.
> + aus x / y, allerdings kann hier das Vorzeichen beider
Parameter
> + ausgewertet und so der Quadrant des Ergebnisses bestimmt
werden.
>  
>  
>   Siehe auch atan,
acos,
> @@ -260,7 +260,7 @@
>
stringbinary_string

>   
>  
> - Liefert die dezimale Entsprechnung der in
> + Liefert die dezimale Entsprechung der in
>   binary_string übergebenen binären
>   Zahl. Der größte konvertierbare Wert ist ein String aus 31
>   Einsen, das entspricht 2147483647 dezimal (2 hoch 32 minus
1).
> @@ -327,7 +327,7 @@
>
intnumber
>   
>  
> - Diese Funktion liefert eine binäre Representation von
> + Diese Funktion liefert eine binäre Repräsentation von
>   number als String zurück.  Der größte
>   konvertierbare Wert für number ist
dezimal
>   4294967295, dies entspricht (2 hoch 32)-1 und liefert einen
String
> @@ -352,7 +352,7 @@
>
intnumber
>   
>  
> - Diese Funktion liefert eine hexadezimale Representation von
> + Diese Funktion liefert eine hexadezimale Repräsentation von
>   number als String zurück.  Der größte
>   konvertierbare Wert für number ist
dezimal
>   2147483647, dies entspricht (2 hoch 32)-1 und liefet als
Ergebnis
> @@ -377,7 +377,7 @@
>
intnumber
>   
>  
> - Diese Funktion liefert eine oktale (zur Basis 8)
Representation
> + Diese Funktion liefert eine oktale (zur Basis 8)
Repräsentation
>   von number als String zurück.  Der
größte
>   konvertierbare Wert für number ist
dezimal
>   2147483647, dies entspricht (2 hoch 32)-1 und liefet als
Ergebnis
> @@ -488,7 +488,7 @@
>
stringhex_string
>   
>  
> - Liefert die dezimale Entsprechnung der in
> + Liefert die dezimale Entsprechung der in
>   hex_string übergebenen hexadezimalen
>   Zahl. Der größte konvertierbare Wert ist "7fff", das
>   entspricht 2147483647 dezimal (2 hoch 32 minus 1).
> @@ -561,14 +561,14 @@
>  
>  
>   Ist der erste Parameter ein Array, so wird der größte Wert
> - innerhalb dieses Array zurückgegeben. Anderenfalls müßen
> + innerhalb dieses Array zurückgegeben. Anderenfalls müssen
>   mindestens zwei Parameter übergeben werden, und
>   max liefert den Wert des größten
Parameters
> - zurück. Die Anzahl der Eingabe-Paramter ist nur durch den
> + zurück. Die Anzahl der Eingabe-Parameter ist nur durch den
>   verfügbaren Hauptspeicher begrenzt.
>  
>  
> - Ist mindestens einer der Eigabewerte vom Typ double, so
werden
> + Ist mindestens einer der Eingabewerte vom Typ double, so
werden
>   alle Werte als double behandelt und der Rückgabewert ist
>   ebenfalls vom Typ double. Anderenfalls werden alle
Eingabewerte
>   als int behandelt und auch ein int zurückgegeben.
> @@ -598,14 +598,14 @@
>  
>  
>   Ist der erste Parameter ein Array, so wird der kleinste Wert
> - innerhalb dieses Array zurückgegeben. Anderenfalls müßen
> + innerhalb dieses Array zurückgegeben. Anderenfalls müssen
>   mindestens zwei Parameter übergeben werden, und
>   min liefert den Wert des kleinsten
> - Parameters zurück. Die Anzahl der Eingabe-Paramter ist nur
durch
> + Parameters zurück. Die Anzahl der Eingabe-Parameter ist nur
durch
>   den verfügbaren Hauptspeicher begrenzt.
>  
>  
> - Ist mindestens einer der Eigabewerte vom Typ double, so
werden
> + Ist mindestens einer der Eingabewerte vom Typ double, so
werden
>   alle Werte als double behandelt und der Rückgabewert ist
>   ebenfalls vom Typ double. Anderenfalls werden alle
Eingabewerte
>   als int behandelt und auch ein int zurückgegeben.
> @@ -645,7 +645,7 @@
>   libc-Algorithmus.
>  
>  
> - Weitere Informationen zum Mersenne Twister und zur
opmimierten
> + Weitere Informationen zum Mersenne Twister und zur
optimierten
>   Imp

Re: [PHP-DOC] Fw: Bug #16206: wrong message in "./configure"

[Egon Schmid]

From: "Hartmut Holzgraefe" <[EMAIL PROTECTED]>
> Egon Schmid wrote:
> > It is not a bug from the PHP documentation team. It is the
> > generating software. Please blame Norman Walsh about this. I
have
> > seen this wrong #AEN... anchors many years ago.
>
> they are not 'wrong', they are just not static, so they might
> change with every build. within the manual they are absolutely
> valid and useable, you just can't rely on them for external
> linkage, similar to page urls generated for tags without id
> attribute
>
> would be nice if id attributes would be used here as they
> are for page urls ...

If static or dynamic, we have some AEN anchors in the PHP manual.
Please read a recent build log and add the missings IDs :)  I think
it have not to do with external linkage.

-Egon

Re: [PHP-DOC] Fw: Bug #16206: wrong message in "./configure"

[Egon Schmid]

From: "Gabor Hojtsy" <[EMAIL PROTECTED]>

> > > > There's a bug report about a broken reference to an anchor
in
> > > > faq.build. That anchor seems to me like a auto-generated
> > (semi-random)
> > > > one. Is that correct, and if so, is there any way we can
> > reliable refer
> > > > to a specific item in the FAQ?
> > >
> > > At least you can give a link to the page, and add the
> > > question / answer number. So users need to find the
> > > number manually.
> >
> > It is not a bug from the PHP documentation team. It is the
> > generating software. Please blame Norman Walsh about this. I
have
> > seen this wrong #AEN... anchors many years ago.
>
> We *can* customize the style sheets to generate some
> nice anchors. Were are these bogus links actually
> presented?

I think it cannot repaired with style sheets. If you want to see
this AEN anchors, look at the build logs at php.net.

-Egon

Re: [PHP-DOC] Fw: Bug #16206: wrong message in "./configure"

[Egon Schmid]

From: "Gabor Hojtsy" <[EMAIL PROTECTED]>

> > There's a bug report about a broken reference to an anchor in
> > faq.build. That anchor seems to me like a auto-generated
(semi-random)
> > one. Is that correct, and if so, is there any way we can
reliable refer
> > to a specific item in the FAQ?
>
> At least you can give a link to the page, and add the
> question / answer number. So users need to find the
> number manually.

It is not a bug from the PHP documentation team. It is the
generating software. Please blame Norman Walsh about this. I have
seen this wrong #AEN... anchors many years ago.

-Egon

Re: [PHP-DOC] OT question

[Egon Schmid]

From: "Gre7g Luterman" <[EMAIL PROTECTED]>

> I love how the PHP manual is displayed on the php.net web site,
and
> I'm wondering what program they used to generate those pages.  Is
the
> code publicly available?  If not, does anyone know of any publicly
> available code which does a similar thing?
>
> I've recently written a manual for djbdns and I'm looking for a
way
> to make it more "net friendly" than a single PDF file.  I'd love
to
> have it broken into sections, have prev/next capabilities, search,
> etc., but I don't want to go reinventing the wheel.

We are using only publicly available code. Look for DocBook, Jade,
Stylesheets and so ... If you want more learn about the PHP
documentation, download the howto.tar.gz

-Egon

Re: [PHP-DOC] chapters/install.*

[Egon Schmid]

From: "Mark Kronsbein" <[EMAIL PROTECTED]>

> > When will install.* files be available for translation? They
were last
> > updated 2 months ago. What's the current status of these files?
>
> We talked a bit about this at the phpdoc meeting. I hope, the
reordering
> of the files/content will start the next days.

Please remove the DO_NOT_TRANSLATE. I don´t see any argument for not
translating/splitting the install files in other languages.

-Egon

Re: [PHP-DOC] rand function definition

[Egon Schmid]

I think, all s aren´t correct rendered after Hartmut´s
conversion to PHP 4. See for example www.php.net/mt_rand

-Egon

From: "Philip Olson" <[EMAIL PROTECTED]>

> Fixed.  Also, anyone have word as to when or if
> rand functions "auto seed" if seeds don't exist?
>
> iirc, jeroen/sterling did work on that...
>
> Regards,
> Philip
>
>
> On Wed, 13 Mar 2002, Rasmus Lerdorf wrote:
>
> > Currently rand shows up as:
> >
> > int rand ( void)int rand ( int min, int max)
> >
> > at http://www.php.net/manual/en/function.rand.php
> >
> > This is extremely ugly.  Ca we not do:
> >
> > int rand([int min, int max])
> >
> > ?
> >
> > -Rasmus
> >
>
>

Re: [PHP-DOC] I'm back and things have changed!

[Egon Schmid]

From: "Daniel Beckham" <[EMAIL PROTECTED]>

> Well, after a long hiatus, I'm trying to get back involved in the
phpdoc
> community again.  After a quick cvs checkout, it seems a lot of
the phpdoc
> tree has changed. =)  Anything I should know before I start
contributing
> again?

Please read the protocol at php.net about our PHPDOC meeting last
weekend for future changes. There have been only very few changes
the last months.

-Egon

Re: [PHP-DOC] some errors in ctype.xml

[Egon Schmid]

> If you want an CVS account, please fill out the form at
> www.php.net/php-cvs.php. Please speak with Luca Perugini or Simone
> about the details. Simone Cortesi is currently moving from
Stuttgart
> (Germany) back to Italy. Simone have been at our PHP documentation
> meeting in Stuttgart.

Sorry, it is cvs-php.php :)

-Egon

Re: [PHP-DOC] some errors in ctype.xml

[Egon Schmid]

From: "Gabriele S." <[EMAIL PROTECTED]>

> I think there are some errors in ctype (Character type functions).
>
> line 40
> "this function are enabled" -> "these functions are enabled"
>
> line 135
> "special control funcion" -> "special control function"
>
> and I think too
> line 196 and 219
> "actualy" -> "actually"
>
> line 270
> "formfeed" -> "form feed" (i'm not sure)
>
> PS: how can i obtain a CVS account for the italian translation?

If you want an CVS account, please fill out the form at
www.php.net/php-cvs.php. Please speak with Luca Perugini or Simone
about the details. Simone Cortesi is currently moving from Stuttgart
(Germany) back to Italy. Simone have been at our PHP documentation
meeting in Stuttgart.

-Egon

Re: [PHP-DOC] de Translators

[Egon Schmid]

Please update Translators and translation.xml.

-Egon

From: "Thomas Schöfbeck" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, March 08, 2002 3:46 PM
Subject: Re: [PHP-DOC] de Translators


> Hi Guys,
>
> are you shure, that everybody is still working with this instead
of the
> "new" revcheck?
> (see the howto at
http://cvs.php.net/cvs.php/phpdoc/howto/howto.html.tar.gz,
> and
> http://at.php.net/manual/de/revcheck.html)
>
> Just a thought, the actual states of "my" files are all only
actual in
> revcheck.
>
> Cu,
> Thomas
>
>
> Jan Lehnardt wrote:
>
> > Hi,
> > On Thu, 7 Mar 2002 16:20:37 +0100
> > Georg Richter <[EMAIL PROTECTED]> wrote:
> >
> > > icap is deprecated, and there will be no german translation in
the
> > future.
> > > So I guess we can kick it.
> > IMHO the documentation should be nuked everywhere. Only the note
to mcal
> > should remain. What do you think?
> > Or what about a "no longer supported" appendix where such files
should
> > move to?
> >
> > Jan
> > --
> > Q: Thank Jan? A: http://geschenke.an.dasmoped.net/
>
>

Re: [PHP-DOC] cvs: phpdoc /de/chapters intro.xml

[Egon Schmid]

From: "Friedhelm Betz" <[EMAIL PROTECTED]>

>>> I've just synced to the en-tree, where this section is also
> deleted
>>> (also don't know why :)

>> Aha, it was Goba who deleted the short history in the en tree.

> As far as I know:  the contents has moved to the appendix "About
this manual".

The German manual doesn´t have a history.xml in appendices and will
replaced by the English file. This means the translation of that
part is lost.

-Egon

Re: [PHP-DOC] cvs: phpdoc /de/chapters intro.xml

[Egon Schmid]

From: "Thomas Schöfbeck" <[EMAIL PROTECTED]>

> I've just synced to the en-tree, where this section is also
deleted
> (also don't know why :)

Aha, it was Goba who deleted the short history in the en tree.

-Egon

Re: [PHP-DOC] cvs: phpdoc /de/chapters intro.xml

[Egon Schmid]

From: "Thomas Schoefbeck" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, March 06, 2002 8:11 PM
Subject: [PHP-DOC] cvs: phpdoc /de/chapters intro.xml


> tom Wed Mar  6 14:11:18 2002 EDT
>
>   Modified files:
> /phpdoc/de/chapters intro.xml
>   Log:
>   sync with en-version

If I haven´t missed some details. Why do you delete the history of
PHP in the German tree?

-Egon

Re: [PHP-DOC] pgsql.xml

[Egon Schmid]

From: "Simone Cortesi" <[EMAIL PROTECTED]>

> should I add php.ini where needed in the
'pgsql.xml' file?
>
> I see many occurrencies of 'php.ini' (without the DocBook
 tag)
> at the beginning of the file.

Yes, you can do that :)

-Egon

Re: [PHP-DOC] cvs: phpdoc /de/functions array.xml

[Egon Schmid]

Please revert this patch. We use German text in examples. BTW you
have introduced commas in enumeration before the closing "und". This
is an error in German and Hungarian but not in English.

-Egon

- Original Message -
From: "Thomas Schoefbeck" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, February 28, 2002 7:21 PM
Subject: [PHP-DOC] cvs: phpdoc /de/functions array.xml


> tom Thu Feb 28 13:21:42 2002 EDT
>
>   Modified files:
> /phpdoc/de/functions array.xml
>   Log:
>   file is actual again
>

Re: [PHP-DOC] alternative interfaces

[Egon Schmid]

From: "Hartmut Holzgraefe" <[EMAIL PROTECTED]>

> Egon Schmid wrote:
> > We doesn´t need alternative interfaces.
>
> could you elaborate on that?

If Enrico would build his own man pages he can do so, but I don´t
see that we should distribute man pages from phpweb.

-Egon

Re: [PHP-DOC] alternative interfaces

[Egon Schmid]

We doesn´t need alternative interfaces.

-Egon

- Original Message -
From: "Enrico Weigelt" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, February 28, 2002 8:46 AM
Subject: [PHP-DOC] alternative interfaces


>
> hi folks,
>
> i'm new to the php documentation stuff and i wanna write some
> alternative interfaces for the php documentation, i.e. for
> good old *nix man.
>
> where should i start looking at ?
>
> ~-n
>
> --
>  Enrico Weigelt==   meTUX IT services
>  software development, IT service, internet security solutions
>  www: http://www.metux.de/phone: +49 36207 519931
>  email:   [EMAIL PROTECTED]cellphone: +49 174 7066481
>

Re: [PHP-DOC] Bug #15592: misc - exit - missing line break

[Egon Schmid]

From: "Sebastian Nohn" <[EMAIL PROTECTED]>

> [EMAIL PROTECTED] wrote:
>
> > From: [EMAIL PROTECTED]
> > Operating system: All
> > PHP version:  4.1.1
> > PHP Bug Type: Documentation problem
> > Bug description:  misc - exit - missing line break
> >
> > -> Miscellaneous functions
> > -> exit
> >
> > missing líne break in description:
> >
> >
> > void exit ( [string status])void exit ( int status)
> > <<<
> > (http://www.php.net/manual/en/function.exit.php)
> >
>
> The source says:
>   
>voidexit
>
choice="opt">stringstatus
>   
>   
>voidexit
>
>
intstatus
>   
>
> The question is if to put there a manual break or change the
stylesheet.
> or is there any other possibility to fix this?

The current customized stylesheets doesn´t allow line breaks here.
It is possible, but the resulting output doesn´t look correct.

-Egon

Re: [PHP-DOC] cvs: phpdoc /de/functions session.xml

[Egon Schmid]

From: "Gabor Hojtsy" <[EMAIL PROTECTED]>

> > > Oops, I have looked in de/functions/session.xml at line 43 and
not
> > > in manual.xml. Please note that I have seen this error only
with
> > > openjade and not with jade. If you have time, remove the
comment and
> > > test it again.
> >
> > Still (almost) the same error message:
> >
> > /usr/bin/nsgmls:manual.xml:43:20:E: character data is not
allowed here
> >  ^^
> > was 'jade' before
>
> It was me who committed the change. That one space should not
> be treated as whitespace as of XML 1.0... I checked it with jade
> and saxon on my machine, and they had no complaints about it.
>
> Actually I built the CHMs available from
http://weblabor.hu/php-doc-chm
> and it worked quite nice without any errors...

Look at www.php.net/manual/LANG/build.log.gz and I´m sure it is
installpart.xml.in who break the build of all languages.

-Egon

Re: [PHP-DOC] cvs: phpdoc /de/functions session.xml

[Egon Schmid]

From: "Martin Samesch" <[EMAIL PROTECTED]>

> Egon Schmid wrote:
> >
> > eschmid Sun Feb 17 04:55:06 2002 EDT
> >
> >   Modified files:
> > /phpdoc/de/functionssession.xml
> >   Log:
> >   Some errors lesser. But there is one around line 43
> >
> >   /usr/local/bin/openjade:manual.xml:43:20:E: character data is
not allowed here
>
> Ooops, sorry, I forgot 'make test'
>
> session.xml seems to be fixed, thanks, but what about line 43 in
> manual.xml?
>
>   &chapters.install; 
>
> Are comment tags allowed?

Oops, I have looked in de/functions/session.xml at line 43 and not
in manual.xml. Please note that I have seen this error only with
openjade and not with jade. If you have time, remove the comment and
test it again.

-Egon

[PHP-DOC] cvs: phpdoc /de/functions session.xml

[Egon Schmid]

eschmid Sun Feb 17 04:55:06 2002 EDT

  Modified files:  
/phpdoc/de/functionssession.xml 
  Log:
  Some errors lesser. But there is one around line 43
  
  eschmid@marliesle:/usr/local/usr/phpdoc > make
  /usr/local/bin/openjade -D . -wno-idref -c /usr/share/sgml/CATALOG.docbk30 -d 
dsssl/html.dsl -V use-output-dir -t sgml ./dtds/dbxml-4.1.2/phpdocxml.dcl manual.xml
  /usr/local/bin/openjade:manual.xml:43:20:E: character data is not allowed here
  
Index: phpdoc/de/functions/session.xml
diff -u phpdoc/de/functions/session.xml:1.41 phpdoc/de/functions/session.xml:1.42
--- phpdoc/de/functions/session.xml:1.41Sat Feb 16 20:01:17 2002
+++ phpdoc/de/functions/session.xml Sun Feb 17 04:55:06 2002
@@ -54,6 +54,9 @@
  track_vars
  immer aktiviert.
 
+   
+   
+
  Seit PHP 4.1.0 steht $_SESSION genau wie
  $_POST, $_GET,
  $_REQUEST und so weiter, als globale Variable

Re: [PHP-DOC] state of install/ini/configure

[Egon Schmid]

From: "Gabor Hojtsy" <[EMAIL PROTECTED]>

> As the state of Hungarian translated files show, all the core
stuff
> in the manual are translated to Hungarian. We can manage to have
> some time from week to week to update the pages to reflect the
> new content in EN files.
>
> However this is not the case with install ini and configure
stuff..
>
> As someone exploded the install.xml file to separate pieces,
> without asking anybody, we are not able to update our huge
> install.xml copy.
>
> As the current status of install files is far from the desired
> one, anyone can understand that we would not like to spend any
> of our free time with work for nothing worth, so we are unable
> to update the install staff and it is getting older and older,
> making that part of our manual useless...
>
> As I post similar messages from week to week to this list and
would
> like to put it into the members mind, that it needs to be **high**
> priority to discuss this thing, and make the neccessary changes,
> so people out there with free time to contribute to this project
> can do any work on it.
>
> I posted several summarized messages about what are my
> recommendations for file places, and that this need to be
> done with a temporary backward compatible check in configure,
> so there are many things to change.
>
> As *very* few opinions arrived to the list about this subject,
> I would not like to get into the same error, like the person,
> who exploded install.xml.
>
> As you can see, we have a fairly ready core part (actual revcheck
> one attached, as php.net/manual/hu/revcheck.html is outdated).
> We would like to have a correct install part, but it
> is impossible in this case.
>
> Hey, I would like to give my work for you! We just need to decide
> on this thing and make the changes *A*S*A*P*.

I hope you can understand me now, that the revcheck doesn´t help if
you are some revisions behind the en tree. It is nearly impossible
to follow the CVS commits.

It is also a nightmare to move functions in other languages into
other files if the language is not uptodate with the en tree.

I hope I can speak with Mark K. tomorrow or next Saturday and will
clear the problem.

-Egon

Re: [PHP-DOC] the PHP Documentation License

[Egon Schmid]

From: "James Cox" <[EMAIL PROTECTED]>

> As far as the license clauses that Rasmus mentioned, i think these
are it:
>
> >
> > VI. ADDITIONAL LICENSE TERMS
> >
> > A. Distribution of "substantively modified" versions of this
document is
> > prohibited without the explicit permission of the copyright
holder.
> > "Substantive modification" is defined as a change to the content
of the
> > document, and excludes mere changes in format or typographical
> > corrections.
> >
> > B. Commercial distribution of the work or derivative of the work
in any
> > standard (paper) book form is prohibited unless prior permission
is
> > obtained from the copyright holder.
> >
>
> and based on that assumption, i think that they are acceptable,
but with
> modification to state "without the acknowledgement of the PHP
documentation
> team, available at [EMAIL PROTECTED]". The point being there
is that it
> wouldn't be so prohibitive, but would allow for us to know of
works that
> will use it.

With that modification it would no longer be the original Open
Publication License. And what about the PEAR documentation?

-Egon

Re: [PHP-DOC] the PHP Documentation License

[Egon Schmid]

From: "James Cox" <[EMAIL PROTECTED]>

> Egon, from ZendAPI LICENSE file:

I have read this myself. No need to post it to the mailing list. You
can read it also in Till and Tobia´s book ´Web Application
Development with PHP 4.0´.

-Egon

Re: [PHP-DOC] the PHP Documentation License

[Egon Schmid]

From: "James Cox" <[EMAIL PROTECTED]>
To: "phpdoc" <[EMAIL PROTECTED]>
Sent: Saturday, February 09, 2002 3:36 PM
Subject: RE: [PHP-DOC] the PHP Documentation License


> has anything happened with this? Egon, have you started to contact
those who
> currently hold the license?

No, I think every copyright holder reads the PHP-DOC mailing list.
As you can see, the Zend API license on zend.com use the options A
and B. Rasmus said, that this option shouldn´t be used. The special
license in the manual looks not valid, because it is only a link to
http://www.opencontent.org/openpub/ and therefor doesn´t say
something about the options to use or not to use.

-Egon

Re: [PHP-DOC] XSLT call to arms! (was Re: [PHP-DOC] revcheck.html)

[Egon Schmid]

From: "Gabor Hojtsy" <[EMAIL PROTECTED]>

> > >   a) Writing a new DSSSL customization or
> > >   b) Writing a new XSL customization
> > >
> > > because
> >
> > [...]
> >
> > XML is the way we go. If you want HTML, I want LaTeX :)
>
> Well, I cannot fully understand how this is related, or
> how this holds an opinion of yours, but HTML is the
> only format going to be supported for offline help
> on MS platforms in the following few years. They
> will release MS Help 2.0 the next year. It supports
> XML for TOC specifications, but HTML is the format
> for Help content.
>
> Or is your comment related to use XSL instead of
> DSSSL, pointing to DSSSL with the LaTeX analogy?

No, if XSLT works better as DSSSL, why not use it. HTML would be a
step in the wrong direction. XML is the future and I don´t rely on
MS. Sure you can only display HTML in most browsers, but this can
change in future.

-Egon

Re: [PHP-DOC] XSLT call to arms! (was Re: [PHP-DOC] revcheck.html)

[Egon Schmid]

From: "Gabor Hojtsy" <[EMAIL PROTECTED]>

> > > I'll check this out as soon as I have sufficient time. I am
> > > currently working on a quite ugly regular expression based
> > > implementation to generate newchm output. I am quite ready
> > > with it, only some errors are left...
> >
> > With respect, generating HTML Help by XSLT stylesheets works
like a
> > charm, no need for REs, everything is taken directly from XML
sources.
>
> Well for the first time, it seemed that producing HTML Help output
> from DSSSL generated output filtered through some formatting
regepxs
> are better then
>
>   a) Writing a new DSSSL customization or
>   b) Writing a new XSL customization
>
> because

[...]

XML is the way we go. If you want HTML, I want LaTeX :)

-Egon

Re: [PHP-DOC] the PHP Documentation License

[Egon Schmid]

From: "Georg Richter" <[EMAIL PROTECTED]>

> On Wednesday, 6. February 2002 02:26, James Cox wrote:
>
> > As far as the actual license goes, GPL is probably not where we
want to be
> > - it's something i personally shy away from due to it's
restrictiveness.
> > There are many other open source documentation licenses, and we
should
> > probably be looking at them.
> >
>
> +2
>
> Anybody else?!
>
> Where is the problem to change license to OPL or OPL related
license?
> Currently the license and politics of their holder(s) really
doesn't improve
> the Manual (and the spirit of Open Source).

Have you a problem? The copyright holders, if you mean that, doesn´t
have any problems to change the licence. I need only a acknowledgemt
from editors (including editors of other languages than English) and
authors.

-Egon

Re: [PHP-DOC] the PHP Documentation License

[Egon Schmid]

From: "Mark Kronsbein" <[EMAIL PROTECTED]>

> > - a small number of people have "acclaim" for the
documentation. And
> > whatever anyone might say, it's not edited by Stig and Egon, but
by many
>
> Yes. At http://www.php.net/manual/en/copyright.php it says "This
> manual is Copyright [...] by the PHP Documentation Group. The
members
> of this group are listed on the front page of this manual." Does
this
> mean, only _these_ are members of the doc team? I don't have a big
> problem with this sentence concerning my person, since I did not
> _that_ much, other people did. But there are some people who
definately
> deserve it, to be on the front page. I dont want to annoy Egon,
but,
> shouldn't there be at least a sentence like "...and numerous other
> helpers"?

You haven´t understood all terms. The members of this group are
members of the PHP Documentation Group and not only the doc team.
All members (except the editors of other languages) are working
since 1997 for the PHP manual.

> > more people. People like Harmut should be on the front page of
the manual,
> > and he's not - and that's a bad thing.

I have asked Hartmut to be listed on the front page as an author. He
said "No" until we haven´t changed the licence.

> > - a small number of people religiously hold control over
the Documentation.
> > This is bad, and does not help or encourage new people to take
part.
>
> ACK.

*g*

> > - If i want/see a need to make a change to the front
page, i shouldn't
> > expect to be shouted at (unless i had broken it, etc).
>
> See my try ;)

You have to respect my decision. We can not allow all people to
change the front page, to become a member of the PHP Documentation
Group.

> > As far as the actual license goes, GPL is probably not where we
want to be -
> > it's something i personally shy away from due to it's
restrictiveness. There
> > are many other open source documentation licenses, and we should
probably be
> > looking at them.
>
> Yes. I dont know that much about those differences, but GPL is
> definately not
> what we (read: I) want.

I have asked more than once and got no response.

> > Finally, yes i am aware that this is also due to be discussed at
the meeting
> > in march, however i feel it's of importance (given zendapi's
introduction to
> > PHP cvs) to start discussion now - and at least have some idea
of current
> > general thoughts.
>
> I think this was right, to start a discussion which maybe ends in
march
> ;)

I have also asked about the meeting in March. On this theme I got
also no response. I know only that this meeting will be held in
March 9 - 10, 2002 in or near Stuttgart.

-Egon

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

[Egon Schmid]

From: "Jan Lehnardt" <[EMAIL PROTECTED]>

> On Wed, 6 Feb 2002 19:39:58 +0100
> "Egon Schmid" <[EMAIL PROTECTED]> wrote:
>
> > Use what you want. It is not critical.
> to gain consistency, we agreed on following the RFC in phpdoc,
when this
> was discussed the last time.

There are some other problems with consistency. I haven´t and will
probably not read this RFC.

-Egon

Re: [PHP-DOC] revcheck.html

[Egon Schmid]

From: "Mark Kronsbein" <[EMAIL PROTECTED]>

> Hi guys!

and gals!

> I have some questions about thos revcheck.html files.
>
> - How often are the build?
> - http://www.php.net/manual/de/revcheck.html is nice, but
>   http://www.php.net/manual/it/revcheck.html is way cooler.
>   Is this because the german file is build earlier?
>
> I used the file very often the last days and think this is _very_
> helpful for translating stuff. AFAIK I only need a php cgi to
> build it locally, is this true?

If you look at the line after "Status of the translated PHP Manual"
you can see the date it was generated.

-Egon

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

[Egon Schmid]

From: "Simone Cortesi" <[EMAIL PROTECTED]>
> At 17.22 06/02/02 +, Andrew Lindeman wrote:
>
> >+   will include path information if present
> >+   (e.g. $PHP_SELF on this address:
> >+   "http://test.com/test.php/foo.bar"; would be
> >+   "/test.php/foo.bar")
>
> As of RFC 2606  shouldn't we use
"example.com"
> for all example URLs in the manual?

Use what you want. It is not critical.

-Egon

[PHP-DOC] Re: [PHP-DEV] Tabs Vs Spaces (and other coding styles)

[Egon Schmid]

From: "James Cox" <[EMAIL PROTECTED]>

> have we ever decided on this? in our code do we go for tabs or
spaces? Is
> there a style guide anywhere on this?

If you use 3 spaces for the comments in the function folding hooks,
you can get a correct funcsummary.txt. See CODING_STANDARDS.

-Egon

Re: [PHP-DOC] Re: [PHP-DEV] Re: ZE repositories

[Egon Schmid]

From: "Hartmut Holzgraefe" <[EMAIL PROTECTED]>

> Zeev Suraski wrote:
> > At 10:23 AM 2/5/2002, Derick Rethans wrote:
> >
> >> On Tue, 5 Feb 2002, Zeev Suraski wrote:
> >>
> >> > That may be trickier.  License wise, it's under a different
license
> >> (we're
> >> > not in a position to change it, New Riders, Till and Tobias
are).  I
> >> also
> >> > think it makes sense to keep it in a different module (like
the ZE/ZE2
> >> > will, even though they'll be in the php.net CVS).  The build
can
> >> probably
> >> > change to automatically include this into the manual, and it
should be
> >> > possible to note that this part is under a different OS
license.
> >>
> >> The build process already works that way, but otherwise I think
we just
> >> should ask New Riders if the licence can be changed is needed.
> >
> >
> > It should be noted that I believe it'll be better for the manual
to lose
> > the ugly license it's under and move to the openbook license,
than the
> > other way around.  But I've already done my share of license
wars in my
> > life - if you want to talk to New Riders, go ahead.
>
> agreement has been reached a long time ago that the GPL is not the
> right license for documentation anyway (although maybe for
different
> reasons then what you refered to as 'ugly' ;)
>
> i hope that we be able to finaly decide on which license to switch
> to in march, and yes, the "Open Publication License" the API doc
> is now under is one of the few that had been suggested ...

What should happen in March? I have heard of a PHPDOC meeting early
March at or near Stuttgart in Germany. Why doesn´t appear some more
information on this mailing list or is it a conspiratorial meeting?

-Egon

[PHP-DOC] cvs: phpdoc /de/appendices about.xml

[Egon Schmid]

eschmid Sun Feb  3 05:47:13 2002 EDT

  Modified files:  
/phpdoc/de/appendices   about.xml 
  Log:
  Only whitespace and 'mißbrauchen' should be 'missbrauchen'.
  

Index: phpdoc/de/appendices/about.xml
diff -u phpdoc/de/appendices/about.xml:1.8 phpdoc/de/appendices/about.xml:1.9
--- phpdoc/de/appendices/about.xml:1.8  Sun Feb  3 05:27:17 2002
+++ phpdoc/de/appendices/about.xml  Sun Feb  3 05:47:13 2002
@@ -1,5 +1,5 @@
 
-
+
 
 
 
-
- Über das Handbuch
+ 
+  Über das Handbuch
 
- 
-  Formate
-  
-   Das PHP Handbuch wird in diversen Formaten zur Verfügung gestellt. 
-   Diese Formate lassen sich in zwei Gruppen aufteilen: Formate, die online 
-   lesbar sind und solche, die zum Download bereit stehen.
-  
-  
-   
-Einige Verlage haben gedruckte Versionen dieses Handbuchs veröffentlicht. 
-Wir können diese Bücher nicht empfehlen, da sie relativ schnell 
-veraltet sind.
-   
-  
-  
-   Sie können das Handbuch unter  &url.php;
-   und zahllosen Mirrors online lesen. Sie sollten generell immer einen Mirror in
-   Ihrer Nähe verwenden. Sie können sich das Handbuch entweder in purem 
-   (druckfreundlichen) HTML Format oder in einem HTML Format im Design der PHP 
-   Website ansehen.
-  
-  
-   Der Vorteil des Onlinehandbuchs gegenüber den meisten Offlineformaten ist
-   die Integration von Kommentaren (User Notes), 
die von Usern
-   eingetragen werden. Ein offensichtlicher Nachteil ist, daß Sie online sein müssen,
-   um das Onlinehandbuch anzusehen.
-  
-  
-   Es stehen diverse Offlineformate des Handbuchs zur Verfügung. Welches Format 
-   das Beste für Sie ist hängt davon ab, welches Betriebssystem Sie verwenden
-   und welches Sie am liebsten lesen. Wenn Sie Informationen darüber suchen, wie das 
-   Handbuch in so vielen verschiedenen Formaten generiert wird, lesen Sie bitte den 
-   Abschnitt 'Wir wir die Formate generieren' 
-   in diesem Anhang.
-  
-  
-   Die plattformunabhängigsten Formate des Handbuchs sind die HTML- und 
-   Textversionen. Das HTML Format steht sowohl als einzelne HTML-Datei, als auch als
-   Paket von mehren einzelnen Dateien für jedes Kapitel (welches mehrere tausend 
-   Dateien ergibt) zur Verfügung. Die HTML- und Textformate können als
-   komprimierte tar-Dateien (sowohl gzip als auch bzip2) und zip-Archive 
heruntergeladen werden.
-  
-  
-   Ein anderes geläufiges Format, welches plattformunabhängig ist, und 
-   das Format, was sich am besten zum drucken eignet, ist PDF (auch als Adobe Acrobat 
-   bekannt). Bevor Sie jetzt dieses Format downloaden und auf den Druckbutton drücken:
-   Seien Sie gewarnt, dieses Handbuch umfaßt fast 2000 Seiten und wird ständig
-   erweitert.
-  
-  
-   
-Wenn Sie noch kein Programm installiert haben, über das Sie PDFs ansehen
-können, laden Sie sich den Adobe
-Acrobat Reader herunter.
-   
-  
-  
-   Für Besitzer von Palm kompatiblen Handhelds gibt es das Handbuch als
-   Palm Document und im iSilo Format. Beide Formate sind ideal für diese Plattform. 
-   Sie können Ihren Handheld dazu verwenden, auf Ihrem täglichen Weg zur Arbeit 
-   mit der DOC oder 
-   iSilo Software Ihre PHP-Kenntnisse 
aufzubessern, 
-   oder einfach nur, um schnell etwas nachzuschlagen.
-  
-  
-   Unter Windows gibt es ein HTML-Handbuch zur Verwendung mit der Windows HTML Hilfe. 
-   Diese Version beinhaltet eine Volltextsuche, einen kompletten Index und 
Lesezeichen. 
-   Viele bekannte PHP Entwicklungsumgebungen haben diese Version der Dokumentation
-   für schnelleren Zugriff integriert.
-  
-  
-   
-Es gibt ein Visual Basic für Linux Projekt, welches u.A. Software zum Erstellen 
-und Ansehen von CHM Dateien unter Linux entwickelt. Wenn Sie am Fortschreiten der 
Entwicklung
-interessiert sind, dann werfen Sie einen Blick auf die Website bei
-SourceForge.net.
+  
+   Formate
+   
+Das PHP Handbuch wird in diversen Formaten zur Verfügung gestellt.
+Diese Formate lassen sich in zwei Gruppen aufteilen: Formate, die
+online lesbar sind und solche, die zum Download bereit stehen.
+   
+   
+
+ Einige Verlage haben gedruckte Versionen dieses Handbuchs
+ veröffentlicht.  Wir können diese Bücher nicht empfehlen, da sie
+ relativ schnell veraltet sind.
+
+   
+   
+Sie können das Handbuch unter 
+&url.php; und zahllosen Mirrors online lesen. Sie sollten
+generell immer einen Mirror in Ihrer Nähe verwenden. Sie können
+sich das Handbuch entweder in purem (druckfreundlichen) HTML
+Format oder in einem HTML Format im Design der PHP Website
+ansehen.

-  
- 
- 
- 
-  Über die Kommentare (User Notes)
-  
-   Die Kommentare der Benutzer spielen eine wichtige Rolle in der Entwicklung des 
Handbuchs.
-   Dadurch, dass Benutzern erlaubt wird, Beispiele, Warnungen und weitere Klärungen 
-   über ihren Browser beizusteuern, ist es uns möglich, diese Rückmeldungen
-   in den Text des Handbuchs einzuarbeiten. Und bis die Kommentare eingearbeite

[PHP-DOC] cvs: phpdoc /de/appendices about.xml

[Egon Schmid]

eschmid Sun Feb  3 05:22:20 2002 EDT

  Modified files:  
/phpdoc/de/appendices   about.xml 
  Log:
  Fixed some typos.
  
Index: phpdoc/de/appendices/about.xml
diff -u phpdoc/de/appendices/about.xml:1.6 phpdoc/de/appendices/about.xml:1.7
--- phpdoc/de/appendices/about.xml:1.6  Sat Feb  2 17:09:47 2002
+++ phpdoc/de/appendices/about.xml  Sun Feb  3 05:22:19 2002
@@ -1,5 +1,5 @@
 
-
+
 
 
 

Re: [PHP-DOC] FW: [PHP-NOTES] note 18678 added to index

[Egon Schmid]

From: "Mark Kronsbein" <[EMAIL PROTECTED]>

> James Cox wrote:
> >
> > docbook4, which we're converting to, right?
>
> right.

Right. I am waiting for Hartmut who have more experience with
DocBook 4 than I. The HowTo would IMHO be a good place to publish
all steps for the the change from DocBook 3 to 4.

-Egon

Re: [PHP-DOC] FW: [PHP-NOTES] note 18678 added to index

[Egon Schmid]

From: "James Cox" <[EMAIL PROTECTED]>

> I have deleted this note, but it may be worth discussing...
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, January 31, 2002 10:10 AM
> To: [EMAIL PROTECTED]
> Subject: [PHP-NOTES] note 18678 added to index
>
>
> A suggestion for the manual pages:
> It's time to categorize them into higher-level sections, e.g.
built-in
> modules, communication modules, db modules, security modules,
graphics
> modules etc. Even as an experienced user, I find it difficult to
locate the
> right section now. New users must be totally confused. Thank you.
> --
> http://www.php.net/manual/en/index.php
> http://master.php.net/manage/user-notes.php?action=edit+18678
> http://master.php.net/manage/user-notes.php?action=delete+18678
> http://master.php.net/manage/user-notes.php?action=reject+18678

This was discussed several times. It is easier to categorize the
modules with DocBook 4.

-Egon

Re: [PHP-DOC] document generated HTML

[Egon Schmid]

From: "James Cox" <[EMAIL PROTECTED]>

> yeah, but for some clients, i guess adding new lines etc may
confuse them.
>
> if it works, it works.

I haven´t got your point here. How are clients confused by new
lines?

-Egon

> > -Original Message-
> > From: Egon Schmid [mailto:[EMAIL PROTECTED]]
> > Sent: Tuesday, January 29, 2002 9:08 PM
> > To: James Cox; phpdoc
> > Subject: Re: [PHP-DOC] document generated HTML
> >
> >
> > From: "James Cox" <[EMAIL PROTECTED]>
> >
> > > oh well, lets hope that no-one inspects our html :)
> >
> > There are also some working DocBook stylesheets in the
background.
> > The transformation from XML to HTML is valid. I know the HTML
code
> > is looking strange and ugly, but the HTML code is correct
(almost
> > all time, if someone doesn´t correct the errors in the XML
source :)
> >
> > -Egon
> >
> > > > -Original Message-
> > > > From: Egon Schmid [mailto:[EMAIL PROTECTED]]
> > > > Sent: Tuesday, January 29, 2002 8:38 PM
> > > > To: James Cox; phpdoc
> > > > Subject: Re: [PHP-DOC] document generated HTML
> > > >
> > > >
> > > > From: "James Cox" <[EMAIL PROTECTED]>
> > > >
> > > > > has anyone else noticed that the generated HTML sucks, and
is
> > > > there a way to
> > > > > fix this?
> > > >
> > > > No, if we use Jade.
> > > >
> > > > -Egon
> > > >
> > > >
> > >
> >
> >
>
>

Re: [PHP-DOC] document generated HTML

[Egon Schmid]

From: "James Cox" <[EMAIL PROTECTED]>

> oh well, lets hope that no-one inspects our html :)

There are also some working DocBook stylesheets in the background.
The transformation from XML to HTML is valid. I know the HTML code
is looking strange and ugly, but the HTML code is correct (almost
all time, if someone doesn´t correct the errors in the XML source :)

-Egon

> > -Original Message-----
> > From: Egon Schmid [mailto:[EMAIL PROTECTED]]
> > Sent: Tuesday, January 29, 2002 8:38 PM
> > To: James Cox; phpdoc
> > Subject: Re: [PHP-DOC] document generated HTML
> >
> >
> > From: "James Cox" <[EMAIL PROTECTED]>
> >
> > > has anyone else noticed that the generated HTML sucks, and is
> > there a way to
> > > fix this?
> >
> > No, if we use Jade.
> >
> > -Egon
> >
> >
>

Re: [PHP-DOC] document generated HTML

[Egon Schmid]

From: "James Cox" <[EMAIL PROTECTED]>

> has anyone else noticed that the generated HTML sucks, and is
there a way to
> fix this?

No, if we use Jade.

-Egon

[PHP-DOC] cvs: phpdoc / funclist.txt funcsummary.txt

[Egon Schmid]

eschmid Sun Jan 27 10:39:38 2002 EDT

  Modified files:  
/phpdoc funclist.txt funcsummary.txt 
  Log:
  Updated funclist.txt and funcsummary.txt.
  

Index: phpdoc/funclist.txt
diff -u phpdoc/funclist.txt:1.18 phpdoc/funclist.txt:1.19
--- phpdoc/funclist.txt:1.18Sat Jan 12 15:09:32 2002
+++ phpdoc/funclist.txt Sun Jan 27 10:39:37 2002
@@ -232,6 +232,9 @@
 domxml_add_root
 domxml_attributes
 domxml_children
+domxml_dump_mem
+domxml_dump_mem_file
+domxml_dump_node
 domxml_dumpmem
 domxml_elem_get_attribute
 domxml_elem_set_attribute
@@ -243,15 +246,21 @@
 domxml_node
 domxml_node_attributes
 domxml_node_children
+domxml_node_get_content
+domxml_node_has_attributes
 domxml_node_new_child
 domxml_node_set_content
 domxml_node_unlink_node
 domxml_root
 domxml_set_attribute
 domxml_setattr
+domxml_substitute_entities_default
 domxml_unlink_node
 domxml_version
 domxml_xslt_process
+domxml_xslt_stylesheet
+domxml_xslt_stylesheet_doc
+domxml_xslt_stylesheet_file
 domxml_xslt_version
 html_doc
 html_doc_file
@@ -263,6 +272,7 @@
 xpath_eval
 xpath_eval_expression
 xpath_new_context
+xpath_register_ns
 xptr_eval
 xptr_new_context
 # ../php4/ext/exif/exif.c
@@ -2437,6 +2447,7 @@
 yaz_element
 yaz_errno
 yaz_error
+yaz_es_result
 yaz_hits
 yaz_itemorder
 yaz_present
Index: phpdoc/funcsummary.txt
diff -u phpdoc/funcsummary.txt:1.16 phpdoc/funcsummary.txt:1.17
--- phpdoc/funcsummary.txt:1.16 Sat Jan 12 15:09:32 2002
+++ phpdoc/funcsummary.txt  Sun Jan 27 10:39:38 2002
@@ -27,25 +27,25 @@
 string bcsub(string left_operand, string right_operand [, int scale]) 
  Returns the difference between two arbitrary precision numbers  
 # ../php4/ext/bz2/bz2.c
-int bzclose(resouce bzp) 
+int bzclose(int bz) 
  Closes a BZip2 stream  
 string bzcompress(string source [, int blocksize100k [, int workfactor]]) 
  Compresses a string into BZip2 encoded data  
 string bzdecompress(string source [, int small]) 
  Decompresses BZip2 compressed data  
-int bzerrno(resouce bzp) 
+int bzerrno(int bz) 
  Returns the error number  
-array bzerror(resouce bzp) 
+array bzerror(int bz) 
  Returns the error number and error string in an associative array  
-string bzerrstr(resouce bzp) 
+string bzerrstr(int bz) 
  Returns the error string  
-int bzflush(resouce bzp) 
+int bzflush(int bz) 
  Flushes a BZip2 stream  
-resource bzopen(string fn|resource fp, string mode) 
+int bzopen(string|int file|fp, string mode) 
  Opens a new BZip2 stream  
-string bzread(resouce bzp [, int len]) 
+string bzread(int bz [, int len]) 
  Reads len bytes from the BZip2 stream given by bz  
-int bzwrite(resouce bzp, string data [, int len]) 
+int bzwrite(int bz, string data [, int len]) 
  Writes data to the BZip2 stream given by bz  
 # ../php4/ext/calendar/cal_unix.c
 int jdtounix(int jday) 
@@ -447,8 +447,12 @@
  Returns name of DocumentType  
 object domxml_dtd(void) 
  Returns DTD of document  
-string domxml_dumpmem([object doc_handle]) 
+string domxml_dump_mem([object doc_handle]) 
  Dumps document into string  
+int domxml_dump_mem_file([object doc_handle],filename,compressmode) 
+ Dumps document into file and uses compression if specified Returns false on 
+error, otherwise the length of the xml-document (uncompressed)  
+string domxml_dump_node([object doc_handle],object node_handle[,int format[,int 
+level]]) 
+ Dumps node into string  
 string domxml_elem_get_attribute(string attrname) 
  Returns value of given attribute  
 string domxml_elem_get_attribute_node(string attrname) 
@@ -483,6 +487,8 @@
  Returns list of children nodes  
 object domxml_node_first_child(void) 
  Returns first child from list of children  
+string domxml_node_get_content() 
+ Gets content of a node.  "Read the value of a node, this can be either 
+the text carried directly by  this node if it's a TEXT node or the aggregate string 
+of the values carried by  this node child's (TEXT and ENTITY_REF). Entity references 
+are substituted."  
 object domxml_node_has_attributes(void) 
  Returns true if node has attributes  
 object domxml_node_has_child_nodes(void) 
@@ -527,15 +533,23 @@
  Returns data of pi  
 array domxml_pi_target(void) 
  Returns target of pi  
+bool domxml_substitute_entities_default(bool enable) 
+ Set and return the previous value for default entity support  
 int domxml_test(int id) 
  Unity function for testing  
 string domxml_version(void) 
  Get XML library version  
-object domxml_xslt_process(int xsldoc_handle, int xmldoc_handle, [array 
xslt_parameters]) 
+object domxml_xslt_process(object xslstylesheet, object xmldoc [, array 
+xslt_parameters [, bool xpath_parameters]]) 
  Perform an XSLT transformation  
-string domxslt_version(void) 
+object domxml_xslt_stylesheet(string xsltstylesheet) 
+ Creates XSLT Stylesheet object from string  
+object domxml_xslt_stylesheet_doc(object xmldoc) 
+

Re: [PHP-DOC] PHP manual in an XML format?

[Egon Schmid]

From: "Hartmut Holzgraefe" <[EMAIL PROTECTED]>

> > I wonder where you can find the PHP manual in one single XML
file?
> >
> > Anyone who wants to enlight me on this one? =)
>
> we are talking about eventualy splitting it even more
> as some of the files are getting big enough so that
> you get lost when trying to edit them or when you
> attempt to track the changelog for these,
> and you want all the 5+MB in a single file?
>
> why?

Please don´t make such megapatches. If you split the languages into
different repositories, do it in single steps.

-Egon

Re: [PHP-DOC] cvs: phpdoc /de bookinfo.xml

[Egon Schmid]

From: "Hakan Kuecuekyilmaz" <[EMAIL PROTECTED]>

> hakan Mon Jan 21 11:49:35 2002 EDT
>
>   Modified files:
> /phpdoc/de bookinfo.xml
>   Log:
>   added my name
>
>
> Index: phpdoc/de/bookinfo.xml
> diff -u phpdoc/de/bookinfo.xml:1.29 phpdoc/de/bookinfo.xml:1.30
> --- phpdoc/de/bookinfo.xml:1.29 Sat Jan  5 21:09:08 2002
> +++ phpdoc/de/bookinfo.xml Mon Jan 21 11:49:35 2002
> @@ -128,6 +128,9 @@
> 
>  Christian Ullrich
> 
> +   
> +Hakan Kücükyilmaz
> +   
>

The list of translator names follows an alphabetical order.  So
place it between J and L. The entry in de/Translators was placed at
the correct position. Translators with the oldest CVS account are
listed first and the new translators are listed at the end.

-Egon

Re: [PHP-DOC] How to prevent undocumented function to be documented?

[Egon Schmid]

From: "Egon Schmid" <[EMAIL PROTECTED]>
> From: "Yasuo Ohgaki" <[EMAIL PROTECTED]>
>
> > I'm a maintainer of PostgreSQL module and I was about to
> > document new functions.
> >
> > I saw some of new functions are documented with no
> > documentation warning. I guess these are generated
> > automatically.
> >
> > How do I prevent it?
> >
> > I don't want half done(alpha) functions to be
> > documented :)
>
> The place you can look up changes is http//cvs.php.net ->
 phpdoc ->
> en -> functions -> pgsql.

Shouldn´t read my inbox Sunday morning. This was an answer that
doesn´t make any sense.

-Egon

Re: [PHP-DOC] How to prevent undocumented function to be documented?

[Egon Schmid]

From: "Yasuo Ohgaki" <[EMAIL PROTECTED]>

> I'm a maintainer of PostgreSQL module and I was about to
> document new functions.
>
> I saw some of new functions are documented with no
> documentation warning. I guess these are generated
> automatically.
>
> How do I prevent it?
>
> I don't want half done(alpha) functions to be
> documented :)

The place you can look up changes is http//cvs.php.net ->  phpdoc ->
en -> functions -> pgsql.

-Egon

Re: [PHP-DOC] Bug #15093 Updated: $_FILES and other global array are not documented

[Egon Schmid]

From: "Hartmut Holzgraefe" <[EMAIL PROTECTED]>
To: "Philip Olson" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, January 18, 2002 7:53 PM
Subject: Re: [PHP-DOC] Bug #15093 Updated: $_FILES and other global
array are not documented


> Philip Olson wrote:
>
> >>looks like i finaly succeeded with my last changes from
yesterday
> >>
> >>http://www.php.net/manual/de/ is already up to date :)
> >>http://www.php.net/manual/en/ should be building right now
> >>
> >
> > Woohoo! And fwiw, my problems with building locally have been
solved too.
> > Happy day :)
>
> so i can go on with adding xslt support to configure and make
> and can break it all over again ;)

I hope you know the game: gun, foot, bang :)

-Egon

Re: [PHP-DOC] cvs: phpdoc /de/language operators.xml

[Egon Schmid]

From: "Hakan Kuecuekyilmaz" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, January 18, 2002 6:58 PM
Subject: [PHP-DOC] cvs: phpdoc /de/language operators.xml


> hakan Fri Jan 18 12:58:49 2002 EDT
>
>   Modified files:
> /phpdoc/de/language operators.xml
>   Log:
>   typos

I hope you haven´t forgotten our monthly PHP user meeting tomorrow.
Add your name in the Translators file and in de/bookinfo.xml. I have
some problems with the dotless "i".

-Egon

Re: [PHP-DOC] cvs: phpdoc /scripts/apply func2methodsyn.php

[Egon Schmid]

From: "Hartmut Holzgraefe" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, January 17, 2002 2:07 PM
Subject: [PHP-DOC] cvs: phpdoc /scripts/apply func2methodsyn.php


> hholzgra Thu Jan 17 08:07:49 2002 EDT
>
>   Modified files:
> /phpdoc/scripts/apply func2methodsyn.php
>   Log:
>   create xslt processor only once
>   return output only if changes were applied
>   pass xml header to xslt processor

Haven´t tried your last patches, but

[...]

> + return fasle;

[...]

doesn´t look very good.

-Egon

PS: Have you seen the error message "g++ -o scripts/makedoc
scripts/makedoc.cc
g++: scripts/makedoc.cc: No such file or directory g++: No input
files make: *** [scripts/makedoc] Error 1 rm php_manual_en.xml

Re: Re: [PHP-DOC] Re: INSTALL PARTS (was: ugly cvs subject)

[Egon Schmid]

From: "Mark Kronsbein" <[EMAIL PROTECTED]>

> > manual.xml is needed. I say do not hurry with this, as it makes
> > all translations translated install parts be replaced with
> > English, as long as they do not start translation of files.
>
> Yes. And the translation of the files should not start until we/I
are
> finished with splitting and know, how and where the files are
placed
> in the future.
>
> > And IMHO they should only be adviced to translate, if the
> > "final" paths and file names are found...
>
> ACK.

If you are not sure, how you can break the automatic manual build
and all translations, so don´t introduce new folders.

-Egon

Re: [PHP-DOC] See also

[Egon Schmid]

From: "Philip Olson" <[EMAIL PROTECTED]>

> > See also: func1 and func2.
> > See also: func1, func2, and func3.
> >
> > and for German or Hungarian:
> >
> > Siehe auch: func1 und func2.
> > Siehe auch: func1, func2 und func3.
>
> Btw, it's okay english (perfectly acceptable) to not put a comma
before
> the and here, so:
>
>   See also: func1, func2 and func3
>
> Is fine.  That is, iirc.

We use since 1997 The Chicago Manual of Style and now EOD.

-Egon

Re: [PHP-DOC] See also

[Egon Schmid]

From: "Jirka Kosek" <[EMAIL PROTECTED]>

Egon Schmid wrote:

> > I don´t have something against a rendering a "see also" block.
But
> > rendering the content with a list would be a nightmare. We had a
> > discussion at which place should be comma in this list. This
depends
> > on the language and I can guess it will be look very funny in
> > Arabic.

> DocBook stylesheets contain code for inserting puncation between
list
> items -- for example between authors in bibliography. This code is
> localized. Porting this code for our purposes shouldn't be hard.

Oh, haven´t known that. Can it do the following in English:

See also: func1 and func2.
See also: func1, func2, and func3.

and for German or Hungarian:

Siehe auch: func1 und func2.
Siehe auch: func1, func2 und func3.

Look at the commas.

-Egon

Re: [PHP-DOC] See also

[Egon Schmid]

From: "Jirka Kosek" <[EMAIL PROTECTED]>

> I finished modification of DSSSL stylesheets. They are 100%
backward
> compatible -- rendering is changed only on notes with
role="seealso". If
> you decide not to use it, you can always delete this rule in
future.
> Egon, can I commit it before I forget that I had this code on my
> machine.

Commit it and I hope Goba and Hartmut will not missuse it.

-Egon

Re: [PHP-DOC] See also

[Egon Schmid]

From: "Jirka Kosek" <[EMAIL PROTECTED]>

Egon Schmid wrote:

> > Jirka, please don´t make changes for the rendering of the "see
also"
> > notes until there is a solution for the incomplete PDF manuals.
IMHO
> > it is an overkill.

> You mean: overkill = too much markup?

Yes.

> In general you are right, but marking some block as "seealso" can
be
> very usefull when rendering and converting to other formars (e.g.
HTML
> Help). Handling role="seealso" on para will be possible but much
more
> harder then on note. Using note as a container allows you to use
> simplelist if you want some longer list of functions or whatever
else be
> seealso-ed.

I don´t have something against a rendering a "see also" block. But
rendering the content with a list would be a nightmare. We had a
discussion at which place should be comma in this list. This depends
on the language and I can guess it will be look very funny in
Arabic.

> Ultimately, you guys (Egon, Goba, Harmut) should agree on correct
markup
> pattern. I just offered my opinion from DocBook markup point of
view.

If Goba and Hartmut ignores me, so we will have never a agreement.

> > It is much better to write the "see also" notes
> > as before. Indeed it will be too complex if you consider the
other
> > languages with different rules for rendering.

> I see no problem here, if you are afraid of localizations of "see
also"
> this is not problem as there is localization for this string
already
> present in stylesheets.

You can do so, but don´t make a list.

-Egon

Re: [PHP-DOC] See also

[Egon Schmid]

From: "Jirka Kosek" <[EMAIL PROTECTED]>

> Gabor Hojtsy wrote:
>
> > > What is the exact syntax, will we still be defining commas and
'and'
> > > within the blocks?
> >
> > Yes. It seems that using lists is much more complex for the
rendering,
> > as it involves adding commas and and words only where needed
> > programatically.
> >
> > 
> >  print, and
> >  echo
> > 
>
> You can't put mixed content directly into note in DocBook. You
must wrap
> it with para:
>
> 
>  print, and
>   echo
> 
>
> > 
> >  print
> >  echo
> > 
>
> This will require change in DocBook, you can use simplelist
instead:
>
> 
> 
> print
> echo
> 
> 
>
> > but the note form allows us to do things like this:
> >
> > 
> >  print, and
> >  the notes on the CGI
> >  security page
> > 
>
> Once again, you must wrap it inside para:
>
> 
>  
>   print, and
>   the notes on the CGI
>   security page
>  
> 
>
> > Either we choose "note" or "somelisttag", it is better
> > than the current style. I have not seen too many
> > comments about this on the list so far...
>
> IMHO  is on semantic level very close to seealso. Using role
is
> standard DocBook way to make it different from standard note.

Jirka, please don´t make changes for the rendering of the "see also"
notes until there is a solution for the incomplete PDF manuals. IMHO
it is an overkill. It is much better to write the "see also" notes
as before. Indeed it will be too complex if you consider the other
languages with different rules for rendering.

-Egon

Re: [PHP-DOC] manual build issues

[Egon Schmid]

From: "Philip Olson" <[EMAIL PROTECTED]>

> > BTW which problems do you have building the HTM manual locally?
>
> In doing this:
>
>   make clean; autoconf; ./configure; make html > junk 2>&1
>
> The first few lines of 'junk' is as follows.  I used to have this
> problem with 'make test' until jim's patch 1.99 on Makefile.ini
> titled "don't make test targets depend on funcindex.xml, since
that
> depends on quickref.txt, and generation of that is forced."  Looks
> related.

I have now made a test myself with my old system. If you have a
correct DocBook installation, you should see no errors.

I have done it with:

cd phpdoc
cvs -z3 update -dP
autoconf
./configure
make

I gets only one warning: recreating the function index needs php
which was not found by configure - reusing old file.

Indeed I have no php executable on that system. It could be, that
"make clean" removes a needed old file. I don´t know which file is
missing because I never use "make clean" :)

-Egon

Re: [PHP-DOC] Obsolete modules in php4?

[Egon Schmid]

From: "Edin Kadribasic" <[EMAIL PROTECTED]>

> > > > > Modules like iisfunc are moved to pear/PECL.
> > > > > Documents for them should be moved to pear.
> > > > >
> > > > > Or am I wrong?
> > > >
> > > > Yes.
> > >
> > > It would be nice if the documentation is kept in one place so
> > people don't
> > > have to remember where the function came from.
> >
> > Do you mean with "one place" peardoc or phpdoc?
>
> I meant phpdoc. People are used to www.php.net/funcname. The
documentation
> should have some standard note that this module is part of PECL
and how you
> can install it (which is hard to tell right now :).

Cool! I have heared that peardoc is a programing language for
documentation. So it is the best to leave the docs in its old
location and make a notice in the partintro for the new location for
the source files.

-Egon

Re: [PHP-DOC] Obsolete modules in php4?

[Egon Schmid]

From: "Edin Kadribasic" <[EMAIL PROTECTED]>

> > > Modules like iisfunc are moved to pear/PECL.
> > > Documents for them should be moved to pear.
> > >
> > > Or am I wrong?
> >
> > Yes.
>
> It would be nice if the documentation is kept in one place so
people don't
> have to remember where the function came from.

Do you mean with "one place" peardoc or phpdoc?

-Egon

Re: [PHP-DOC] Obsolete modules in php4?

[Egon Schmid]

From: "Yasuo Ohgaki" <[EMAIL PROTECTED]>

> Hi all,
> 
> Modules like iisfunc are moved to pear/PECL.
> Documents for them should be moved to pear.
> 
> Or am I wrong?

Yes.

-Egon

Re: [PHP-DOC] cvs: phpdoc / funclist.txt funcsummary.txt

[Egon Schmid]

From: "Hartmut Holzgraefe" <[EMAIL PROTECTED]>

> > eschmid Sat Jan 12 15:09:32 2002 EDT
> >
> >   Modified files:
> > /phpdoc funclist.txt funcsummary.txt
> >   Log:
> >   Update of funclist.txt and funcsummary.txt
>
> do we realy need these auto generated files in CVS,

These files are not auto generated and yes we need them.

> or are they just left over from the time when php
> source and documentation were in the same repository?

No, the scripts was written by Rasmus between PHP 3.0.6 and 3.0.7.

> don't think they make much sense in CVS any longer
> as everyone checking out the manual now should be
> able to generate them himself

Please don´t touch them. They are needed for editors (programs and
humans) and translators. I don´t see that everyone checkout the
manual and PHP 3 or 4.

> same for quickref.txt

The same goes here, your auto-generate rules doesn´t help because
the automatic build system is broken.

-Egon

Re: [PHP-DOC] manual build issues

[Egon Schmid]

From: "Philip Olson" <[EMAIL PROTECTED]>

> Seems still problems exist, latest builds are January 5.  I am
unable to
> build the html manual locally, anyone else have this problem?  If
not,
> I'll expand on it.  'make test' works fine.

This is one of the reasons.

BTW which problems do you have building the HTM manual locally? I
don´t use "make test", I use "make" and wait if there are errors.
The last time I have checked the manual I got no errors.

-Egon

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

[Egon Schmid]

From: "Gabor Hojtsy" <[EMAIL PROTECTED]>

> > > Only an editor can make such additions [to bookinfo.xml].
> >
> > This info should be mentioned in phpdoc howto.  May also want to
define
> > what it means to be an author and/or editor.
>
> I thought it is obvious, that noone can invent author names,
> just the editors. Well, I would like to say +1 for including
> Hartmut in the author list, I am not against it.
>
> Quote from Egon:
>
> | > and, er, who class as editors now?
> | This is the job for Stig Bakken.
>
> Some background info: Jouni was added by Egon AFAIK, atfer
> he asked on the list and we agreed on that.

This is correct. I thought also to put Hartmut on the author list.
But ... I have some reasons.

-Egon

Re: [PHP-DOC] cvs: phpdoc /de/functions strings.xml

[Egon Schmid]

From: "Jan Lehnardt" <[EMAIL PROTECTED]>

> jan Sat Jan 12 10:22:13 2002 EDT
>
>   Modified files:
> /phpdoc/de/functions strings.xml
>   Log:
>   added note about optional parameter of parse_str()

Please sync strings.xml with the English strings.xml and update the
version information in de/Translators.

-Egon

Re: [PHP-DOC] cvs: phpdoc /de/functions classobj.xml

[Egon Schmid]

From: "Markus Fischer" <[EMAIL PROTECTED]>

> mfischer Sat Jan 12 09:03:20 2002 EDT
>
>   Modified files:
> /phpdoc/de/functions classobj.xml
>   Log:
>   - get_declared_classes(): Added note about additional classes
depending on
> the PHP compile options.

Please sync the German classobj.xml with the English file and update
the Translators file.

-Egon

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

[Egon Schmid]

From: "Simone Cortesi" <[EMAIL PROTECTED]>

At 03.38 12/01/02 +0100, Egon Schmid wrote:

> > >   mail restituisce &true; se la mail
è
> >stata spedita con
> >
> >The URLs for http://www.zend.com ... and http://pear.php.net ...
> >should be in global.ent. If you want to change the English
manual,
> >don´t forget to add the missing comma in front of the "and" in
the
> >enumeration of RFCs.

> Will commit them in 1/2 hour.

Forget it, I have done this myself.

-Egon

[PHP-DOC] cvs: phpdoc /en/functions mail.xml /entities global.ent /it/functions mail.xml

[Egon Schmid]

eschmid Sat Jan 12 04:16:12 2002 EDT

  Modified files:  
/phpdoc/entitiesglobal.ent 
/phpdoc/en/functionsmail.xml 
/phpdoc/it/functionsmail.xml 
  Log:
  URLs should be in entities/global.ent. Changed only the en and it tree.
  
Index: phpdoc/entities/global.ent
diff -u phpdoc/entities/global.ent:1.2 phpdoc/entities/global.ent:1.3
--- phpdoc/entities/global.ent:1.2  Fri Jan 11 13:05:35 2002
+++ phpdoc/entities/global.ent  Sat Jan 12 04:16:11 2002
@@ -1,6 +1,6 @@
 
+
  
   Mail functions
   Mail
@@ -90,8 +90,8 @@
  to.  Email with attachments and special
  types of content can be sent using this function. This is
  accomplished via MIME-encoding - for more information, see this
- http://www.zend.com/zend/spotlight/sendmimeemailpart1.php";>
- Zend article or the http://pear.php.net/get/Mail_Mime";>
+ 
+ Zend article or the 
  PEAR Mime Classes.
   
  
@@ -100,7 +100,7 @@
  RFC 2045,
  RFC 2046,
  RFC 2047,
- RFC 2048 and 
+ RFC 2048, and 
  RFC 2049.
 
 
Index: phpdoc/it/functions/mail.xml
diff -u phpdoc/it/functions/mail.xml:1.10 phpdoc/it/functions/mail.xml:1.11
--- phpdoc/it/functions/mail.xml:1.10   Fri Jan 11 20:50:43 2002
+++ phpdoc/it/functions/mail.xmlSat Jan 12 04:16:12 2002
@@ -90,8 +90,8 @@
  mettendo una virgola tra ogni indirizzo in a. Email con 
allegati e tipi speciali di
  contenuto possono essere spedite usando questa funzione. Questo è
  possibile tramite la codifica MIME. Per maggiori informazioni, fare riferimento a
- http://www.zend.com/zend/spotlight/sendmimeemailpart1.php";>
- un articolo Zend o alle http://pear.php.net/get/Mail_Mime";>
+ 
+ un articolo Zend o alle 
  Classi Mime del PEAR.
 
  

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

[Egon Schmid]

From: "Simone Cortesi" <[EMAIL PROTECTED]>

> cortesi Fri Jan 11 20:50:44 2002 EDT
>
>   Modified files:
> /phpdoc/it/functions mail.xml
>   Log:
>   adding RFC to be in sync with EN
>
>
> Index: phpdoc/it/functions/mail.xml
> diff -u phpdoc/it/functions/mail.xml:1.9
phpdoc/it/functions/mail.xml:1.10
> --- phpdoc/it/functions/mail.xml:1.9 Fri Dec 21 06:40:08 2001
> +++ phpdoc/it/functions/mail.xml Fri Jan 11 20:50:43 2002
> @@ -1,5 +1,5 @@
>  
> -
> +
>  
>  
>Funzioni di Mail
> @@ -90,9 +90,18 @@
>   mettendo una virgola tra ogni indirizzo in
a. Email con allegati e tipi speciali di
>   contenuto possono essere spedite usando questa funzione.
Questo è
>   possibile tramite la codifica MIME. Per maggiori
informazioni, fare riferimento a
> - http://www.zend.com/zend/spotlight/sendmimeemailpart1.php";
> -
>http://www.zend.com/zend/spotlight/sendmimeemailpart1.php o
> - RFC 1896).
> + http://www.zend.com/zend/spotlight/sendmimeemailpart1.php";>
> + un articolo Zend o alle http://pear.php.net/get/Mail_Mime";>
> + Classi Mime del PEAR.
> +
> + 
> + Le seguenti RFC possono essere di aiuto:
> + RFC 1896,
> + RFC 2045,
> + RFC 2046,
> + RFC 2047,
> + RFC 2048 e
> + RFC 2049.
>  
>  
>   mail restituisce &true; se la mail è
stata spedita con

The URLs for http://www.zend.com ... and http://pear.php.net ...
should be in global.ent. If you want to change the English manual,
don´t forget to add the missing comma in front of the "and" in the
enumeration of RFCs.

-Egon

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

[Egon Schmid]

From: "Mark Kronsbein" <[EMAIL PROTECTED]>

> mk Fri Jan 11 19:34:08 2002 EDT
>
>   Modified files:
> /phpdoc/en bookinfo.xml
>   Log:
>   I didn't (and don't) know, who is editor and who not.

The names of editors and authors are on the title page. Translations
can have other editor names on the title page. I´m also an editor
for the German PHP manual and the German word for editor is
"Herausgeber".

-Egon

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

[Egon Schmid]

From: "James Cox" <[EMAIL PROTECTED]>

> and, er, who class as editors now?

This is the job for Stig Bakken.

-Egon

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

[Egon Schmid]

From: "Mark Kronsbein" <[EMAIL PROTECTED]>

> mk Fri Jan 11 18:40:00 2002 EDT
> 
>   Modified files:  
> /phpdoc/en bookinfo.xml 
>   Log:
>   Hartmut should be there too (IMHO)
>   
> Index: phpdoc/en/bookinfo.xml
> diff -u phpdoc/en/bookinfo.xml:1.23 phpdoc/en/bookinfo.xml:1.24
> --- phpdoc/en/bookinfo.xml:1.23 Thu Jan  3 03:04:54 2002
> +++ phpdoc/en/bookinfo.xml Fri Jan 11 18:40:00 2002
> @@ -1,5 +1,5 @@
>  
> -
> +
>  
>   
>
> @@ -34,6 +34,10 @@
>  
> 
>  JouniAhto
> +   
> +
> +   
> +HartnutHolzgraefe
> 
>  
>

Please revert your patch. Only an editor can make such additions.

-Egon

[PHP-DOC] Building errors

[Egon Schmid]

Hello all,

can someone explain the error messages at
http://php.net/manual/it/build.log ? The error messages aren´t in a
local build with the current Italian manual.

-Egon

[PHP-DOC] cvs: phpdoc /es/chapters install.xml

[Egon Schmid]

eschmid Fri Jan 11 03:14:48 2002 EDT

  Modified files:  
/phpdoc/es/chapters install.xml 
  Log:
  There are more missing links to IDs.
  
Index: phpdoc/es/chapters/install.xml
diff -u phpdoc/es/chapters/install.xml:1.8 phpdoc/es/chapters/install.xml:1.9
--- phpdoc/es/chapters/install.xml:1.8  Wed Dec 12 15:47:50 2001
+++ phpdoc/es/chapters/install.xml  Fri Jan 11 03:14:48 2002
@@ -664,7 +664,7 @@
   Si está habilitado, el ejecutable CGI del PHP se puede situar
   tranquilamente fuera del árbol de la web y la gente no podrá
   saltarse la seguridad del .htaccess. Lea la sección en el capítulo de
+  linkend="security.cgi-bin.shell">sección en el capítulo de
   seguridad sobre esta opción.
  
 
@@ -714,7 +714,7 @@
   directorios de los usuarios pueden ser accedidos por cualquiera.
  
  
-  Lea la sección en
+  Lea la sección en
   el capítulo de seguridad acerca de esta opción.
  
 

[PHP-DOC] cvs: phpdoc /it/functions array.xml

[Egon Schmid]

eschmid Fri Jan 11 02:37:03 2002 EDT

  Modified files:  
/phpdoc/it/functionsarray.xml 
  Log:
  'it' can now build without errors.
  
Index: phpdoc/it/functions/array.xml
diff -u phpdoc/it/functions/array.xml:1.40 phpdoc/it/functions/array.xml:1.41
--- phpdoc/it/functions/array.xml:1.40  Wed Jan  9 07:05:57 2002
+++ phpdoc/it/functions/array.xml   Fri Jan 11 02:37:03 2002
@@ -569,7 +569,7 @@
 ]]>
   
   
-   $a ora ha i seguenti elementi (usando la funzione print_r):
+   $a ora ha i seguenti elementi (usando la funzione 
+print_r):

 
   
   
Il risultato di questo programma sarà (PHP 4.0.6):
-   
+   
 

Re: [PHP-DOC] Build system is broken

[Egon Schmid]

From: "Hartmut Holzgraefe" <[EMAIL PROTECTED]>

> >>most likely we have hit a TeX buffer limit once again
> >>
> >
> > If you compare the translated PDF manuals you will see that:
> >
> > en:Chapter 46Database issues
> > de:Kapitel 46Database issues
> >
> > stops at the same page content on different pages (1896 vs.
1611).
>
> yes, the limiting factor are labels generated for tag ids,
> not the content itself, so a buffer limit overflow will most
> likely occur at the same logical place in the content

I can´t believe it. You know, most of the translated files are not
in sync with the English files.

If the build doesn´t stop with "sed: can't read confdefs.h: No such
file or directory" grep through php.net/manual/en/build.log and look
for a "Sorry, TeX capacity exceeded".

-Egon

Re: [PHP-DOC] Build system is broken

[Egon Schmid]

From: "Hartmut Holzgraefe" <[EMAIL PROTECTED]>

> > Ok, but there is another error in the build system or the manual
> > itself. Look at the PDF manuals and you will see a incomplete
table
> > of content (?? as page numbers at the end) and this pages aren´t
> > shown.
>
> most likely we have hit a TeX buffer limit once again

If you compare the translated PDF manuals you will see that:

en:Chapter 46Database issues
de:Kapitel 46Database issues

stops at the same page content on different pages (1896 vs. 1611).

-Egon

Re: [PHP-DOC] Build system is broken

[Egon Schmid]

From: "Jim Winstead" <[EMAIL PROTECTED]>

> it is broken because the system builds the manual outside of the
phpdoc
> tree. that means when $(srcdir) isn't properly used, the build
breaks.

Ok, but there is another error in the build system or the manual
itself. Look at the PDF manuals and you will see a incomplete table
of content (?? as page numbers at the end) and this pages aren´t
shown.

-Egon

[PHP-DOC] cvs: phpdoc /de/functions dio.xml

[Egon Schmid]

eschmid Tue Jan  8 18:05:37 2002 EDT

  Modified files:  
/phpdoc/de/functionsdio.xml 
  Log:
  Whitespace only. Please use emacs psgml-mode.
  

Index: phpdoc/de/functions/dio.xml
diff -u phpdoc/de/functions/dio.xml:1.2 phpdoc/de/functions/dio.xml:1.3
--- phpdoc/de/functions/dio.xml:1.2 Mon Jan  7 07:11:52 2002
+++ phpdoc/de/functions/dio.xml Tue Jan  8 18:05:36 2002
@@ -8,17 +8,18 @@

 Direkte Ein-/Ausgabe Funktionen
 
-  PHP unterstützt die direkte Ein-/Ausgabe-Funktionen, beschrieben
-  im Posix Standard (Kapitel 6) für die Ein- und Ausgabe auf einer
-  niederen Ebene als die standardmässig verwendeten C-Funktionen
-  (fopen, fread,...).
+ PHP unterstützt die direkte Ein-/Ausgabe-Funktionen, beschrieben
+ im Posix Standard (Kapitel 6) für die Ein- und Ausgabe auf einer
+ niederen Ebene als die standardmässig verwendeten C-Funktionen
+ (fopen, fread, ...).
 


 Installation
 
  Um die DIO Funktionen benutzen zu können, muss PHP mit der Option
- --enable-dio konfiguriert werden.
+ --enable-dio konfiguriert
+ werden.
 

   
@@ -26,53 +27,79 @@
   

 dio_open
-öffnet eine Datei mit den angegebenen Rechten
+
+ Öffnet eine Datei mit den angegebenen Rechten
+


 Beschreibung
 
  
   resource dio_open
-   string filename
-   int flags
-   int
-mode
-   
+  string filename
+  int flags
+  int mode
  
 
 
-  dio_open öffnet eine Datei und liefert
-  einen Dateizeiger zurück. Im Fehlerfall liefert
-  dio_open -1 zurück.
-  Ist der Parameter flags O_CREAT, 
-  so gibt der optionale Parameter mode die
-  Dateirechte an.
-  Der Parameter flags kann eine der
-  folgenden Zugriffsmethoden sein:
-  
-O_RDONLY - öffnet die Datei für
-Lesezugriff
-O_WRONLY - öffnet die Datei für
-Schreibzugriff
-O_RDWR - öffnet die Datei für Schreib- und
-Lesezugriff
-  
-  Diese Zugriffsmethoden können mit folgenden Attributen
-  kombiniert werden:
-  
-O_CREAT - erzeugt die Datei, falls diese nicht
- existiert.
-O_EXCL - in Kombination mit O_CREAT wird ein
- Fehler (-1) zurückgegeben, wenn die Datei bereits 
existiert.
-O_TRUNC - falls die Datei bereits existiert,
- und sie für Schreibzugriff geöffnet wird, wird diese auf die
- Grösse 0 zurückgesetzt.
-O_APPEND - setzt den Zeiger für
- Schreiboperationen an das Ende der Datei.
-
-O_NONBLOCK - Setzt den Modus auf
- "nonblocking" 
-  
+ dio_open öffnet eine Datei und liefert einen
+ Dateizeiger zurück. Im Fehlerfall liefert
+ dio_open -1 zurück.  Ist der Parameter
+ flags O_CREAT, so gibt der optionale
+ Parameter mode die Dateirechte an.  Der
+ Parameter flags kann eine der folgenden
+ Zugriffsmethoden sein:
+ 
+  
+   
+O_RDONLY - öffnet die Datei für Lesezugriff
+   
+  
+  
+   
+O_WRONLY - öffnet die Datei für
+Schreibzugriff
+   
+  
+  
+   
+O_RDWR - öffnet die Datei für Schreib- und Lesezugriff
+   
+  
+ 
+ Diese Zugriffsmethoden können mit folgenden Attributen kombiniert
+ werden:
+ 
+  
+   
+O_CREAT - erzeugt die Datei, falls diese nicht existiert
+   
+  
+  
+   
+O_EXCL - in Kombination mit O_CREAT wird ein Fehler (-1)
+zurückgegeben, wenn die Datei bereits existiert
+   
+  
+  
+   
+O_TRUNC - falls die Datei bereits existiert, und sie für
+Schreibzugriff geöffnet wird, wird diese auf die Grösse 0
+zurückgesetzt
+   
+  
+  
+   
+O_APPEND - setzt den Zeiger für Schreiboperationen an das Ende
+der Datei
+   
+  
+  
+   
+O_NONBLOCK - Setzt den Modus auf "nonblocking"
+   
+   
+ 
 

   
@@ -80,18 +107,18 @@
   

 dio_read
-Liest n Bytes und gibt sie zurück, ist n nicht
-angegeben wird ein 1K Block gelesen.
+
+ Liest n Bytes und gibt sie zurück, ist n nicht angegeben wird ein
+ 1K Block gelesen
+


 Beschreibung
 
  
   string dio_read
-   resource fd
-   int
-n
-   
+  resource fd
+  int n
  
 
 
@@ -114,21 +141,18 @@
 
  
   int dio_write
-   resource fd
-   string data
-   int
-len
- 
+  resource fd
+  string data
+  int len
  
 
 
  Die Funktion dio_write schreibt bis zu
  len Bytes an Daten
  data

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

[Egon Schmid]

eschmid Tue Jan  8 17:39:37 2002 EDT

  Modified files:  
/phpdoc/en/functionsdio.xml 
  Log:
  Only whitespace.
  

Index: phpdoc/en/functions/dio.xml
diff -u phpdoc/en/functions/dio.xml:1.6 phpdoc/en/functions/dio.xml:1.7
--- phpdoc/en/functions/dio.xml:1.6 Sat Jan  5 15:35:25 2002
+++ phpdoc/en/functions/dio.xml Tue Jan  8 17:39:37 2002
@@ -1,5 +1,5 @@
 
-
+
  
   Direct IO functions
   DIO functions
@@ -8,9 +8,9 @@

 Direct I/O Functions
 
-  PHP supports the direct io functions as described in the Posix
-  Standard (Section 6) for performing I/O functions at a lower
-  level than the C-Language stream I/O functions (fopen, fread,..).
+ PHP supports the direct io functions as described in the Posix
+ Standard (Section 6) for performing I/O functions at a lower
+ level than the C-Language stream I/O functions (fopen, fread,..).
 


@@ -25,47 +25,70 @@
   

 dio_open
-Opens a new filename with specified permissions of flags and creation 
permissions of mode 
+
+ Opens a new filename with specified permissions of flags and
+ creation permissions of mode
+


 Description
 
  
   resource dio_open
-   string filename
-   int flags
-   int
-mode
-   
+  string filename
+  int flags
+  int mode
  
 
 
-  dio_open opens a file and returns a new
-  file descriptor for it, or -1 if any error occured.
-  If flags is O_CREAT, optional third parameter
-  mode will set the mode of the file
-  (creation permissions). 
-  The flags parameter can be one of the
-  following options:
-  
-O_RDONLY - opens the file for read access
-O_WRONLY - opens the file for write access
-O_RDWR - opens the file for both reading and
-writing
-  
+ dio_open opens a file and returns a new file
+ descriptor for it, or -1 if any error occured.  If
+ flags is O_CREAT, optional third parameter
+ mode will set the mode of the file
+ (creation permissions).  The flags
+ parameter can be one of the following options:
+ 
+  
+   O_RDONLY - opens the file for read access
+  
+  
+   O_WRONLY - opens the file for write access
+  
+  
+   
+O_RDWR - opens the file for both reading and
+writing
+   
+  
+ 
   The flags parameter can also include any
-combination of the following flags:
-  
-O_CREAT - creates the file, if it doesn't
-already exist
-O_EXCL - if both, O_CREAT and O_EXCL are set,
-dio_open fails, if file already exists.
-O_TRUNC - if file exists, and its opened
-for write access, file will be truncated to zero length.
-O_APPEND - write operations write data at the
-end of file
-O_NONBLOCK - sets non blocking mode
-  
+  combination of the following flags:
+ 
+  
+   
+O_CREAT - creates the file, if it doesn't already exist
+   
+   
+  
+   
+O_EXCL - if both, O_CREAT and O_EXCL are set,
+dio_open fails, if file already exists
+   
+   
+  
+   
+O_TRUNC - if file exists, and its opened for write access,
+file will be truncated to zero length.
+   
+  
+  
+   
+O_APPEND - write operations write data at the
+end of file O_NONBLOCK -
+sets non blocking mode
+   
+  
+ 
 

   
@@ -73,25 +96,26 @@
   

 dio_read
-Reads n bytes from fd and returns them, if n is not specified, reads 
1k block
+
+ Reads n bytes from fd and returns them, if n is not specified,
+ reads 1k block
+


 Description
 
  
   string dio_read
-   resource fd
-   int
-n
-   
+  resource fd
+  int n
  
 
 
- The function dio_read reads and returns 
+ The function dio_read reads and returns
  n bytes from file with descriptor
  resource. If n is
- not specified, dio_read reads 1K sized block and
- returns them. 
+ not specified, dio_read reads 1K sized block
+ and returns them.
 

   
@@ -99,26 +123,26 @@
   

 dio_write
-Writes data to fd with optional truncation at length 
+
+ Writes data to fd with optional truncation at length 
+


 Description
 
  
   int dio_write
-   resource fd
-   string data
-   int
-len
+  resource fd
+  string data
+  int len
  
  
 
 
- The function dio_write
- writes up to len bytes from
- data to file fd. If
- len is not specif