damsWed Jan 22 07:06:29 2003 EDT
Modified files:
/phpdoc/en/reference/image/functionsimagettftext.xml
Log:
die, GIF, die!
Index: phpdoc/en/reference/image/functions/imagettftext.xml
diff -u phpdoc/en/reference/image/functions/imagettftext.xml:1.3
ph
damsWed Jan 22 07:11:52 2003 EDT
Modified files:
/phpdoc/en/reference/image/functionsimagettftext.xml
Log:
black is black!
Index: phpdoc/en/reference/image/functions/imagettftext.xml
diff -u phpdoc/en/reference/image/functions/imagettftext.xml:1.4
p
Hi,
I was reading the manual of session_start() at
http://www.php.net/manual/en/function.session-start.php
But there's something strange to me. I find the following text in the
first paragraph:
session_start() creates a session (or resumes the current one based on
the session id being passed v
philip Wed Jan 22 13:34:59 2003 EDT
Modified files:
/phpdoc/en/reference/session/functions session-start.xml
Log:
Closing concern brought up by Oliver Hinckel. session gets id from request
data, not just get or cookie.
Index: phpdoc/en/reference/ses
derick Wed Jan 22 13:37:34 2003 EDT
Modified files:
/phpdoc/en/chapters install.solaris.xml
Log:
- Add GNU sed as requirement
Index: phpdoc/en/chapters/install.solaris.xml
diff -u phpdoc/en/chapters/install.solaris.xml:1.1
phpdoc/en/chapters/install.solaris
>Hi
>
> I was reading the manual of session_start() at
> http://www.php.net/manual/en/function.session-start.php
>
> But there's something strange to me. I find the following text in the
> first paragraph:
>
> session_start() creates a session (or resumes the current one based on
> the session
ID: 21816
Updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
-Status: Bogus
+Status: Assigned
-Bug Type: *Regular Expressions
+Bug Type: Documentation problem
Operating System: Windows XP
PHP Version: 4.3.0
-Assigned T
tom Wed Jan 22 16:37:34 2003 EDT
Modified files:
/phpdoc/en/reference/strings/functions sscanf.xml
Log:
typo
Index: phpdoc/en/reference/strings/functions/sscanf.xml
diff -u phpdoc/en/reference/strings/functions/sscanf.xml:1.4
phpdoc/en/reference/string
tom Wed Jan 22 16:38:26 2003 EDT
Modified files:
/phpdoc/en/reference/strings/functions substr.xml
Log:
closed open bracket
Index: phpdoc/en/reference/strings/functions/substr.xml
diff -u phpdoc/en/reference/strings/functions/substr.xml:1.5
phpdoc/en/r
tom Wed Jan 22 16:42:05 2003 EDT
Modified files:
/phpdoc/en/reference/strings/functions wordwrap.xml
Log:
corr. example
Index: phpdoc/en/reference/strings/functions/wordwrap.xml
diff -u phpdoc/en/reference/strings/functions/wordwrap.xml:1.2
phpdoc/en/r
Hi there,
looking at the current - esp. for newbies sometimes confusing - manual,
where several old info and even functions simply disappeared, but
several exlanations and even whole chapters (like 'Migrating from PHP/FI
2 to PHP 3') for PHP 3 still exist, etc., one thought came into my mind:
A quick question why can't we build a PDF version I could put some
resources into this if needed and I agree with a branch for a PHP5
clean manual for the future.
Timothy Hitchens (HiTCHO)
Open Source Consulting
e-mail: [EMAIL PROTECTED]
> -Original Message-
> From: Thomas Schöfbeck [mai
betzWed Jan 22 18:07:55 2003 EDT
Modified files:
/phpdoc .cvsignore
Log:
version independant exclusion of autoconfs cache
Index: phpdoc/.cvsignore
diff -u phpdoc/.cvsignore:1.35 phpdoc/.cvsignore:1.36
--- phpdoc/.cvsignore:1.35 Wed Jul 17 11:59:35 2
On Wed, 22 Jan 2003, [ISO-8859-1] Thomas Schöfbeck wrote:
> Hi there,
>
> looking at the current - esp. for newbies sometimes confusing - manual,
> where several old info and even functions simply disappeared, but
> several exlanations and even whole chapters (like 'Migrating from PHP/FI
> 2 to
On Thu, 23 Jan 2003, Timothy Hitchens (HiTCHO) wrote:
> A quick question why can't we build a PDF version I could put some
> resources into this if needed and I agree with a branch for a PHP5
> clean manual for the future.
Okay, spend time on an automated build of a full PHP manual
built into PDF
philip Wed Jan 22 18:55:57 2003 EDT
Modified files:
/phpdoc/en/language types.xml
Log:
Expanded string and array information including many example updates, many
more manual links, and a little cleanup. Added a decent amount of information
on using arrays wi
ID: 20601
Updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
-Status: Open
+Status: Closed
Bug Type: Documentation problem
Operating System: Windows ME
PHP Version: 4.3.0RC1
Assigned To: philip
New Comment:
Thanks for
Hi Thomas,
>
> P.S. Other questions like this will follow, like:
>
> Since we aren't able to build a pdf-version due to a lack of resources:
> Why don't we make the FAQ an extra document (esp. for 'bundled' builds
> like chm, pdf, bightml, ... - I've never read a book where chap. 43
> describes the
> Regarding PHP 3 specific information, this indeed should be
> moved but not simply deleted. History is good. Another idea
> would be to move all PHP 3 specific information into a PHP 3
> section and where the information was, point to it instead. So
> something like:
>
> php3 note
>
> This w
(Crossposting to pear-doc)
-1 on forking to a PHP5 only manual. As Philip already
mentioned is not a good idea, whereas the User -
Developer separation does make sense.
--- Friedhelm Betz <[EMAIL PROTECTED]> wrote:
[...snip...]
> - removal of outdated extensions
If the extension has been complet
(Crossposting to pear-doc)
-1 on forking to a PHP5 only manual. As Philip already
mentioned is not a good idea, whereas the User -
Developer separation does make sense.
--- Friedhelm Betz <[EMAIL PROTECTED]> wrote:
[...snip...]
> - removal of outdated extensions
If the extension has been complet
> > - removal of outdated extensions
>
> If the extension has been completely removed from the
> source tree, then yes it should be gone from the
> manual. Not sure if someone is keeping an archive of
> old manuals, just in case.
I partially disagree with this. Simply removing
them is not the a
Just a suggestion.. but what if we look at a way for the viewer of the
manual to choose their version of PHP and then see it as it related to
that version then the issue of PHP3 etc and removed extensions etc is
not
an issue anymore and the manual can grow without confusion for the
viewer.
Timoth
On Thu, 23 Jan 2003, Timothy Hitchens (HiTCHO) wrote:
> Just a suggestion.. but what if we look at a way for the viewer of the
> manual to choose their version of PHP and then see it as it related to
> that version then the issue of PHP3 etc and removed extensions etc is
> not
> an issue anymore an
ID: 21816
Updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
-Status: Assigned
+Status: Closed
Bug Type: Documentation problem
Operating System: Windows XP
PHP Version: 4.3.0
Assigned To: pollita
New Comment:
This bug
pollita Wed Jan 22 23:06:26 2003 EDT
Modified files:
/phpdoc/en/reference/pcre/functions preg-replace.xml
Log:
Typo fixes
Index: phpdoc/en/reference/pcre/functions/preg-replace.xml
diff -u phpdoc/en/reference/pcre/functions/preg-replace.xml:1.5
phpdoc/en/ref
From: [EMAIL PROTECTED]
Operating system: Windows 2000 Server
PHP version: 4.3.0
PHP Bug Type: Documentation problem
Bug description: IIS 5.0 requires additional parameters on Add Mappings Tab
This line produced the "No input file" output
after I configured PHP on IIS 5.
ID: 21833
User updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
Status: Open
Bug Type: Documentation problem
Operating System: Windows 2000 Server
PHP Version: 4.3.0
New Comment:
Sorry, I forgot to include URL:
http://aspn.activesta
ID: 21833
Updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
-Status: Open
+Status: Feedback
Bug Type: Documentation problem
Operating System: Windows 2000 Server
PHP Version: 4.3.0
New Comment:
Is this modification specifi
ID: 21833
Updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
Status: Feedback
Bug Type: Documentation problem
Operating System: Windows 2000 Server
PHP Version: 4.3.0
New Comment:
I have *NOT* experienced this requirement with PHP i
From: [EMAIL PROTECTED]
Operating system: Win2k
PHP version: 4.3.0
PHP Bug Type: Documentation problem
Bug description: First call to imagecolorallocate() assigns background
I discovered from experimentation that the first call to
imagecolorallocate() for a given image, sets
ID: 21834
Updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
Status: Open
Bug Type: Documentation problem
Operating System: Win2k
PHP Version: 4.3.0
New Comment:
This will need some study and confirmation. For example here is one
u
ID: 21834
Comment by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
Status: Open
Bug Type: Documentation problem
Operating System: Win2k
PHP Version: 4.3.0
New Comment:
Sure thing. Later today I'll investigate different image types, and
p
33 matches
Mail list logo