Re: [PHP-DOC] Could somebody pls. correct a typo?

2001-04-20 Thread Damien Seguy

Hi,

- would somebody pls. correct br/ to br in both lagunages?
   That's not a typo.  nl2br() uses XHTML br / tags since PHP-4.0.4
 Thats the correct syntax nowadays.
Are you sure of this? I just tested it on a 4.0.4pl1 version, and it still
gives me br. 
Or this may be browser dependent?  Or am I missing something?

Best regards,
Damien Seguy




[PHP-DOC] getimagesize extra informations

2001-04-20 Thread Damien Seguy

Hi,

Lately, I used getimageisize on a JPEG picture, and I got extra index in the
returned array.

 [bits] = 8
 [channels] = 3
 index 0 through 3 are documented but not "bits" and "channels".

I talked with Wez, and here is his conclusion :

'channels' is the number of channels;
most likely 3 for RGB images, 4 for CMYK images.

'bits' is the number of bits of information per channel.

So bits = 8 and channels = 3 implies that you have an RGB image, with 8 bits
per pixel; 8 * 3 = 24 bits per pixel (or true colour) image.

This sounds sensible, but can anyone with greater experience validate this?
If anyone disagree, I'll add it in the docs.

Best regards,
Damien Seguy




Re: [PHP-DOC] Could somebody pls. correct a typo?

2001-04-20 Thread Rasmus Lerdorf

This was changed by Jon on Dec.28, 2000.

http://cvsweb.php.net/viewcvs.cgi/php4/ext/standard/string.c.diff?r1=1.176r2=1.177

PHP 4.0.4 was released before then.

-Rasmus

On Fri, 20 Apr 2001, Damien Seguy wrote:

 Hi,

 - would somebody pls. correct br/ to br in both lagunages?
That's not a typo.  nl2br() uses XHTML br / tags since PHP-4.0.4
  Thats the correct syntax nowadays.
 Are you sure of this? I just tested it on a 4.0.4pl1 version, and it still
 gives me br.
 Or this may be browser dependent?  Or am I missing something?

 Best regards,
 Damien Seguy





[PHP-DOC] cvs: phpdoc / global.ent /en/chapters install.xml

2001-04-20 Thread Egon Schmid

eschmid Fri Apr 20 00:44:51 2001 EDT

  Modified files:  
/phpdoc global.ent 
/phpdoc/en/chapters install.xml 
  Log:
  This generated some errors.
  
Index: phpdoc/global.ent
diff -u phpdoc/global.ent:1.86 phpdoc/global.ent:1.87
--- phpdoc/global.ent:1.86  Wed Apr 11 07:01:17 2001
+++ phpdoc/global.ent   Fri Apr 20 00:44:50 2001
@@ -1,6 +1,6 @@
 !-- -*- SGML -*-
 
- $Id: global.ent,v 1.86 2001/04/11 14:01:17 mboeren Exp $
+ $Id: global.ent,v 1.87 2001/04/20 07:44:50 eschmid Exp $
 
  Contains global "macros" for all the SGML documents.
 
@@ -65,6 +65,7 @@
 !ENTITY url.ldap.openldap-c-api 
"http://www.openldap.org/devel/cvsweb.cgi/~checkout~/doc/drafts/draft-ietf-ldapext-ldap-c-api-xx.txt"
 !ENTITY url.levenshtein.demo "http://odur.let.rug.nl/~kleiweg/lev/"
 !ENTITY url.lightyear "http://homepage.mac.com/LightyearDesign/MacOSX/Packages/"
+!ENTITY url.macosx "http://www.entropy.ch/software/macosx"
 !ENTITY url.macromedia "http://www.macromedia.com/"
 !ENTITY url.malinimg "http://www.pvv.org/~ssb/malin/bilder/mi/twain001.jpg"
 !ENTITY url.mcal "http://mcal.chek.com/"
Index: phpdoc/en/chapters/install.xml
diff -u phpdoc/en/chapters/install.xml:1.52 phpdoc/en/chapters/install.xml:1.53
--- phpdoc/en/chapters/install.xml:1.52 Thu Apr 19 23:50:19 2001
+++ phpdoc/en/chapters/install.xml  Fri Apr 20 00:44:51 2001
@@ -481,9 +481,8 @@
  sect2 id="install.macosx.client"
   titleCompiling for MacOS X client/title
   simpara
-   Those tips are graciously provided by Marc Liyanage :
-   link ulink"http://www.entropy.ch/software/macosx"future site/link
-   (link ulink=""old site/link).
+   Those tips are graciously provided by Marc Liyanage : ulink
+   url="url.macosx;"future site/ulink.
   /simpara
   simpara
The PHP module for the Apache web server included in Mac OS X.
@@ -516,7 +515,6 @@
   4.   type "sudo apxs -i -a -n php4 libphp4.so" 
  /simpara
 /listitem
-listitem
/itemizedlist
Now type "literalsudo open -a TextEdit /etc/httpd/httpd.conf/literal"
TextEdit will open with the web server configuration file. Locate these 





Re: [PHP-DOC] nl2br and br / (was : could someone correct atypo...?

2001-04-20 Thread Damien Seguy

on 20/04/01 9:27, Rasmus Lerdorf at [EMAIL PROTECTED] wrote:

 This was changed by Jon on Dec.28, 2000.
 
 http://cvsweb.php.net/viewcvs.cgi/php4/ext/standard/string.c.diff?r1=1.176r2=
 1.177
 
 PHP 4.0.4 was released before then.
This is true, as show in cvs.php.net.

However, the ext/standard/string.c bundled in the source distribution of PHP
dates back to december 14th. My installation is Linux Debian Apache, from
sources (I don't have a clue for other distributions).

I've just been browsing a freshly downloaded source distribution, and the
string.c file dates also from december 14th.

So, the br / approach should appear when version = 4.04pl1, but for
source distribution, this will be a version = 4.05 availability.

I suggest to add this version availability information added in the doc.
If anyone is using win32 binaries, it would be nice to test it too.

I'm also interested in knowing how such an old version of string.c is
bundled? Is this done on purpose, using CVS tags? Or some automated tags
misundertanding? 

Best regards,
Damien Seguy 




[PHP-DOC] cvs: phpdoc /fr/pear standards.xml

2001-04-20 Thread Damien Seguy

damsFri Apr 20 01:19:14 2001 EDT

  Modified files:  
/phpdoc/fr/pear standards.xml 
  Log:
  Added latest corrections
  
Index: phpdoc/fr/pear/standards.xml
diff -u phpdoc/fr/pear/standards.xml:1.2 phpdoc/fr/pear/standards.xml:1.3
--- phpdoc/fr/pear/standards.xml:1.2Tue Apr  3 06:22:26 2001
+++ phpdoc/fr/pear/standards.xmlFri Apr 20 01:19:14 2001
@@ -87,12 +87,14 @@
para
 Comme illustreacute; ci-dessus, il faut un espace autour des signes
 eacute;gal lorsqu'il est utiliseacute; dans une assignation de variable.
-Dans le cas d'assignement en bloc, plusieurs espaces peuvent ecirc;tre
+Dans le cas d'assignation en bloc, plusieurs espaces peuvent ecirc;tre
 introduit pour ameacute;liorer la lisibiliteacute;.
 programlisting role="php"
+lt;?php
 $short = foo($bar);
 $long_variable = foo($baz);
-/programlisting
+gt;
+/programlisting
/para
   /sect1
   sect1 id="pear.standards.funcdef"
@@ -101,6 +103,7 @@
 Les deacute;clarations de fonction suivent la convention 
 "one TRUE brace" (une seule accolade veacute;ritable) : 
 programlisting role="php"
+lt;?php
 function fooFunction($arg1, $arg2 = '')
 {
 if (condition) {
@@ -108,7 +111,8 @@
 }
 return $val;
 }
-/programlisting
+?gt;
+/programlisting
/para
para
 Les arguments ayant une valeur par deacute;faut doivent aller
@@ -116,7 +120,8 @@
 une valeur utile de vos fonctions, degrave;s que c'est le cas.
 Voici un exemple : 
 programlisting role="php"
-function connect(amp;$dsn, $persistent = false)
+lt;?php
+function connect(amp;$dsn, $persistent = FALSE)
 {
 if (is_array($dsn)) {
 $dsninfo = amp;$dsn;
@@ -128,8 +133,9 @@
 return $this-raiseError();
 }
 
-return true;
+return TRUE;
 }
+?gt;
 /programlisting
/para
   /sect1





Re: [PHP-DOC] nl2br and br / (was : could someone correct atypo...?

2001-04-20 Thread Thomas

Hi all!

Damien Seguy wrote:

 So, the br / approach should appear when version = 4.04pl1, but for
 source distribution, this will be a version = 4.05 availability.

 I suggest to add this version availability information added in the doc.
 If anyone is using win32 binaries, it would be nice to test it too.


Many thanks for that suggestion!
I'll install and test it on Win32 at home during the weekend and come to you again.


 I'm also interested in knowing how such an old version of string.c is
 bundled? Is this done on purpose, using CVS tags? Or some automated tags
 misundertanding?

Hm... Don't know about the "branch-" and "bundling-" process. It was also with the
mssql.c which returned the wrong value in 4.04, and even Frank fixed this bug on
Jan.4, the 4.04PL1 released on Jan.11 still had the buggy version.
= is there somewhere a doc which descibes this process?

Best regards,
Thomas




Re: [PHP-DOC] Could somebody pls. correct a typo?

2001-04-20 Thread Daniel Beckham

Are you positive that Netscape 4.x will not see a br / as a line break?
This is perfectly formed sgml or xml as far as I know.

Daniel

- Original Message -
From: "Thomas" [EMAIL PROTECTED]
Newsgroups: php.doc
To: [EMAIL PROTECTED]
Sent: Thursday, April 19, 2001 5:05 PM
Subject: Re: [PHP-DOC] Could somebody pls. correct a typo?


 But shouldn't that be worth a short comment in the doc (like "inserts
XHTML breaks..." instead of "HTML breaks", and
 when the change (from what) happened?) , since Browsers like Netscape 4.x
don't react on br/?
 Or have I missed a section with all these things one has to consider
(know) before - or at least after upgrading - (like
 $array[myfield] and the backward-compatible nl2br "doesn't work anymore")?




Re: [PHP-DOC] Could somebody pls. correct a typo?

2001-04-20 Thread Daniel Beckham

Don't know about version 4.0.4, but I'm testing 4.0.5-dev now and it's
outputting br /.

Daniel

- Original Message -
From: "Damien Seguy" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, April 20, 2001 2:23 AM
Subject: Re: [PHP-DOC] Could somebody pls. correct a typo?


 Hi,

 - would somebody pls. correct br/ to br in both lagunages?
That's not a typo.  nl2br() uses XHTML br / tags since PHP-4.0.4
  Thats the correct syntax nowadays.
 Are you sure of this? I just tested it on a 4.0.4pl1 version, and it still
 gives me br.
 Or this may be browser dependent?  Or am I missing something?

 Best regards,
 Damien Seguy






Re: [PHP-DOC] Could somebody pls. correct a typo?

2001-04-20 Thread Daniel Beckham

No, it's not difficult, but why should it really matter?  br / or p / or
hr /, et. al. should all be compatible with older browsers.  Like I said,
it's perfectly valid SGML/XML.

The following html works flawlessly in NS 4.72:

html
headtitle/title/head
body
This is a test.
p /
This is another test.br /br /br /
This is a final test.
hr /
/body
/html

Regards,

Daniel Beckham


- Original Message -
From: "Thomas" [EMAIL PROTECTED]
Newsgroups: php.doc
To: [EMAIL PROTECTED]
Sent: Friday, April 20, 2001 3:32 AM
Subject: Re: [PHP-DOC] Could somebody pls. correct a typo?



 What I meant: Shouldn't HTML be changed to XHTML?
 And is it really that bad to write also a note like "Note: In versions
older than PHP 4.04 nl2br() returned a string with
 'br' inserted before all newlines." ?

 For behavior-changes like this: Please have in mind, that there are
millions scripts running out there, and not all of them
 running on the last PHP-version.

   Is there a consideration for eventually occuring "traps" for the
change to 4.05?
   I assume that it's not really funny if a user - or worse - ISP
upgrades, and than can't defend against complaints
   because of "buggy" scripts (which worked before).
 
   Anil Madhavapeddy wrote:
  
 - would somebody pls. correct br/ to br in both lagunages?
   
That's not a typo.  nl2br() uses XHTML br / tags since PHP-4.0.4
 
  Thats the correct syntax nowadays.

 Agreed.

 Regards,
 Thomas







[PHP-DOC] cvs: phpdoc /nl/language control-structures.xml

2001-04-20 Thread Egon Schmid

eschmid Fri Apr 20 07:58:49 2001 EDT

  Modified files:  
/phpdoc/nl/language control-structures.xml 
  Log:
  Fixed some elements.
  
Index: phpdoc/nl/language/control-structures.xml
diff -u phpdoc/nl/language/control-structures.xml:1.10 
phpdoc/nl/language/control-structures.xml:1.11
--- phpdoc/nl/language/control-structures.xml:1.10  Fri Apr  6 08:53:52 2001
+++ phpdoc/nl/language/control-structures.xml   Fri Apr 20 07:58:49 2001
@@ -866,7 +866,7 @@
 zijn de in aangeroepen file. Als de functionrequire/function
 optreed in een functie in de aanroepende file, dan zal de code
 die zich in het bestand dat ge-required wordt zich gedragen alsof
-deze in de functie waarin functionrequire/functie wordt
+deze in de functie waarin functionrequire/function wordt
 aangeroepen.
/simpara
para
@@ -961,7 +961,7 @@
para
 functioninclude/function verschilt van het 
 functionrequire/function statement op eacute;eacute; punt.
-Een functioninclude/include statement wordt elke keer
+Een functioninclude/function statement wordt elke keer
 ge-evalueerd als deze wordt tegengekomen (en ook alleen maar tijdens
 de uitvoering van een script). Dit in tegenstelling tot het
 functionrequire/function statement, welke wordt vervangen door





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

2001-04-20 Thread Damien Seguy

damsFri Apr 20 10:01:09 2001 EDT

  Modified files:  
/phpdoc/en/chapters install.xml 
  Log:
  Added macos client.
  
Index: phpdoc/en/chapters/install.xml
diff -u phpdoc/en/chapters/install.xml:1.53 phpdoc/en/chapters/install.xml:1.54
--- phpdoc/en/chapters/install.xml:1.53 Fri Apr 20 00:44:51 2001
+++ phpdoc/en/chapters/install.xml  Fri Apr 20 10:01:09 2001
@@ -481,8 +481,9 @@
  sect2 id="install.macosx.client"
   titleCompiling for MacOS X client/title
   simpara
-   Those tips are graciously provided by Marc Liyanage : ulink
-   url="url.macosx;"future site/ulink.
+   Those tips are graciously provided by Marc Liyanage : 
+   ulink url="url.macosx2;"April 2001's site/ulink and 
+   ulink url="url.macosx;"future site/ulink.
   /simpara
   simpara
The PHP module for the Apache web server included in Mac OS X.





Re: [PHP-DOC] Translations to Brazilian Portuguese

2001-04-20 Thread Joao Prado Maia


On Fri, 20 Apr 2001, Renato Arruda wrote:

 I am new to the effort to translate the php manual. I would like to help
 w/ the translation to Brazilian Portuguese, I know that the files are on
 CVS now, can I commit on CVS, don't I need an account to check documents
 back in?

 A little help on getting started would be greatly appreciated.

 Thanks,
 []'s
 Renato


Hi Renato,

Yes you will need a CVS account to do that. You can see a rather sketchy
document on how to get started with CVS for the translation efforts (and
how to get a php.net CVS account) on this URL:

http://phpbrasil.com/traducao.php

We have also setup a separate mailing list for the translation team, so we
can talk in portuguese about problems or small issues with the tasks. If
you are interested in joining it, the address also goes below:

http://groups.yahoo.com/group/traducao-php

If you have any questions, please post them to that mailing list or even
send it directly to me.

Thanks!
Joao

--
Joo Prado Maia [EMAIL PROTECTED]
http://phpbrasil.com - php com um jeitinho brasileiro




Re: [PHP-DOC] getimagesize extra informations

2001-04-20 Thread Jani Taskinen

On Fri, 20 Apr 2001, Damien Seguy wrote:

Hi,

Lately, I used getimageisize on a JPEG picture, and I got extra index in the
returned array.

 [bits] = 8
 [channels] = 3
 index 0 through 3 are documented but not bits and channels.

I talked with Wez, and here is his conclusion :

'channels' is the number of channels;
most likely 3 for RGB images, 4 for CMYK images.

'bits' is the number of bits of information per channel.

So bits = 8 and channels = 3 implies that you have an RGB image, with 8 bits
per pixel; 8 * 3 = 24 bits per pixel (or true colour) image.

This sounds sensible, but can anyone with greater experience validate this?
If anyone disagree, I'll add it in the docs.


According to the image.c the bits / channels are set only for JPEGs.

--Jani