[PHP-DOC] Re: [PHP-DEV] Re: Modules/Extensions not in 4.3

On Fri, 2002-11-29 at 18:20, Philip Olson wrote: > > On Fri, 29 Nov 2002, Wez Furlong wrote: > > IMO, the manual should include all of the "maintstream" PHP extensions. > > The reasoning is that if someone downloads the PHP manual, they expect > > to get the PHP manual and not have to hunt around f

[PHP-DOC] Re: [PEAR-CVS] cvs: php4 /pear/PEAR/Command Registry.php phpdoc/es/reference/apache reference.xml phpdoc/es/reference/arrayreference.xml phpdoc/es/reference/aspell reference.xml phpdoc/es/reference/bc reference.xml phpdoc/es/reference/calendarreference.xml phpdoc/es/reference/classobj reference.xml phpdoc/es/reference/com reference.xml phpdoc/es/reference/cpdfreference.xml phpdoc/es/reference/curl reference.xml phpdoc/es/reference/cybercash reference.xml phpdoc/es/reference/datetimereference.xml phpdoc/es/reference/dba reference.xml phpdoc/es/reference/dbase reference.xml phpdoc/es/reference/dbmreference.xml phpdoc/es/reference/dir reference.xml phpdoc/es/reference/domxml reference.xml phpdoc/es/reference/errorfuncreference.xml phpdoc/es/reference/exec reference.xml phpdoc/es/reference/fdf reference.xml phpdoc/es/reference/fileproreference.xml phpdoc/es/reference/filesystem reference.xml phpdoc/es/reference/ftp reference.xml phpdoc/es/r! eference/funchandreference.xml phpdoc/es

On Tue, 2002-04-16 at 11:46, Tomas V.V.Cox wrote: > El mar, 16-04-2002 a las 11:29, Stig S. Bakken escribió: > > On Tue, 2002-04-16 at 09:54, [EMAIL PROTECTED] wrote: > > > Something was messed here. I have *only* commited a simple patch for > > > /php4/pear/PEAR/Co

[PHP-DOC] Re: [PEAR-CVS] cvs: php4 /pear/PEAR/Command Registry.php phpdoc/es/reference/apache reference.xml phpdoc/es/reference/arrayreference.xml phpdoc/es/reference/aspell reference.xml phpdoc/es/reference/bc reference.xml phpdoc/es/reference/calendarreference.xml phpdoc/es/reference/classobj reference.xml phpdoc/es/reference/com reference.xml phpdoc/es/reference/cpdfreference.xml phpdoc/es/reference/curl reference.xml phpdoc/es/reference/cybercash reference.xml phpdoc/es/reference/datetimereference.xml phpdoc/es/reference/dba reference.xml phpdoc/es/reference/dbase reference.xml phpdoc/es/reference/dbmreference.xml phpdoc/es/reference/dir reference.xml phpdoc/es/reference/domxml reference.xml phpdoc/es/reference/errorfuncreference.xml phpdoc/es/reference/exec reference.xml phpdoc/es/reference/fdf reference.xml phpdoc/es/reference/fileproreference.xml phpdoc/es/reference/filesystem reference.xml phpdoc/es/reference/ftp reference.xml phpdoc/es/r! eference/funchandreference.xml phpdoc/es

On Tue, 2002-04-16 at 09:54, [EMAIL PROTECTED] wrote: > Something was messed here. I have *only* commited a simple patch for > /php4/pear/PEAR/Command > Registry.php. I even dubt to have write access to the phpdoc module :-? "Pear karma" means access to pearweb, php4/pear, pear and peardoc right

RE: [PHP-DOC] Bug #16476 Updated: unpacking

Btw, if we care about download size, we should at least not use zip. Check this out: 13400 php_manual_en.tar 4128php_manual_en.zip 1300php_manual_en.tar.gz 912 php_manual_en.tar.bz2 - Stig On Mon, 2002-04-08 at 12:14, Stig S. Bakken wrote: > It's been tar.gz for a l

RE: [PHP-DOC] Bug #16476 Updated: unpacking

It's been tar.gz for a long time before, I don't see why we can't keep providing it in that format? Download size? - Stig On Mon, 2002-04-08 at 07:38, Andi Gutmans wrote: > I definitely would go for either .zip or .tar.gz. I think .zip on Windows > is preferable but as .tar.gz is supported by

[PHP-DOC] [Fwd: CHM lib]

--- Begin Message --- You are probably not the correct person to send this to but I am hoping you can foward this email to the correct person. There was mention in the Documentation Team Meeting notes that there was need for a CHM generator for non-Win32 systems. I found this

Re: [PHP-DOC] make dynamic module

On Fri, 2002-03-01 at 09:57, Lars Gunder Knudsen wrote: > Hello > > I'm under pressure to make a PHP extension (for mobile phones) finishing the > end of March. I read the documentation on 'Creating Extensions' - no real > help found (maybe it's too easy a process to document :-) ) on making > d

Re: [PHP-DOC] the PHP Documentation License

On Wed, 2002-02-06 at 21:55, Georg Richter wrote: > 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 so

Re: [PHP-DOC] the PHP Documentation License

On Wed, 2002-02-06 at 02:26, James Cox wrote: > > - 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 > more people. People like Harmut should be on the front page of the manual, > and he's not - and

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

On Tue, 2002-02-05 at 20:41, Andi Gutmans wrote: > At 05:19 PM 2/5/2002 +, James Cox wrote: > >Guys, > > > >have we ever decided on this? in our code do we go for tabs or spaces? Is > >there a style guide anywhere on this? > > [4] When indenting, use the tab character. A tab is expected to r

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

But historically, tabs were are also rendered on screen as 8 spaces. This is no longer true, since tabs are often 4 spaces by default. And for this very reason, today it is better to use spaces because that is the _only_ way to format code so it looks the same in less, Emacs, joe, vi, MSVC, Zend

RE: [PHP-DOC] document generated HTML

Actually, the generated HTML is like this exactly because it is the only format where you can be sure that whitespace does not get messed up, while still being able to insert a newline here and there. (If this didn't work, XHTML wouldn't work either.) - Stig On Tue, 2002-01-29 at 22:12, James