Re: [PHP-DOC] Typo encountered!

2010-05-22 Thread Braian Iván Monnier
Ok Daniel, thanks. I'll read the tips soon. Excuse me, but I've just realized (when I saw the DIFF) that on line 267, it says "[mybox:user /src/php4]". I'm not sure (that's the reason why I don't report it as a bug) if it should be "[mybox:user /src/php*5*]" or both of them. If not, I apologize for

Re: [PHP-DOC] Typo encountered!

2010-05-22 Thread Daniel Egeberg
On Sat, May 22, 2010 at 20:32, Braian Iván Monnier wrote: > I've found a typo in faq/installation.xml, in line 287, where "but when I to > access" should be replaced with "but when I try to access". > On the other hand, on the same file, in line 265, Apache appears with the > first "a" in lowercas

Re: [PHP-DOC] Typo in localtime() example

2006-04-12 Thread Jakub Vrana
Hannes Magnusson wrote: > Theres a silly typo in "expected output" for localtime(), the last > array entry has the key 8, not 9 Fixed, thanks. Jakub Vrana

Re: [PHP-DOC] Typo

2005-11-12 Thread Nuno Lopes
It was already fixed. Thanks, Nuno - Original Message - Dear Sir or Madam, yesterday I submitted a note via http://php.benscom.com/manual/add- note.php?sect=ref.spl I just saw that I mada a typo but i have no possibility to change my mistake... could you please change "array($t

Re: [PHP-DOC] Typo in en/reference/maxdb/reference.xml

2005-04-19 Thread Nuno Lopes
Commited! thanks, Nuno - Original Message -- Hi, there's a typo in en/reference/maxdb/reference.xml. The property insert-id should read insert_id (minus and underscore mixed up). Sorry, can't commit it, I'm lacking privileges. Thanks! Ulf [EMAIL PROTECTED]:~/src/phpdoc/en/reference/maxdb

Re: [PHP-DOC] Typo in htmlspecialchars

2004-11-27 Thread Friedhelm Betz
Hi Ted, http://www.php.net/manual/en/function.htmlspecialchars.php Bullet two, which currently reads: '"' (double quote) becomes '"' when ENT_NOQUOTES is not set. should probably read: '"' (double quote) becomes '"' when ENT_COMPAT (the default) or ENT_QUOTES is set. or maybe (but leaves room

Re: [PHP-DOC] Typo Report

2004-07-28 Thread Nuno Lopes
Hello Steven, This error was already corrected in CVS. The correct version will avaliable in the mirrors in the next manual build, which can take up to two weeks. Thanks for your report, Nuno Lopes - Original Message - > Dear PHP Documentation Team, > > I'd like to report what seems to

Re: [PHP-DOC] Typo Report

2004-07-28 Thread Jakub Vrana
[EMAIL PROTECTED] wrote: > I'd like to report what seems to be a typo. > To be found here: > PHP Manual > Classes and Objects > Visibility > 2nd Paragraph: > "Class members must be defined with public, private, or private." > (Maybe: "Class members must be defined with public, protected or private

Re: [PHP-DOC] Typo dans la doc

2004-04-21 Thread Derick Rethans
On Wed, 21 Apr 2004, [iso-8859-1] Benoît Bournac wrote: > > Bonjour et merci pour la doc PHP > > une petite erreur s'est glissée dans la page > > http://fr3.php.net/manual/fr/print/language.types.array.php Fixed! merci! Derick

Re: [PHP-DOC] typo..

2003-08-14 Thread Gabor Hojtsy
http://www.php.net/manual/en/function.pspell-new-personal.php there is $pspell_link = pspell_new_personal ("/var/dictionaries/custom.pws", "en", "", "", "", PSPELL_FAST|PSPELL_RUN_TOGETHER)); which is wrong, should be: $pspell_link = pspell_new_personal ("/var/dictionaries/custom.pws",

Re: [PHP-DOC] typo in the docs

2003-03-21 Thread Steph
Nope, deprecate is the right one -- it has been used for many years in many standards documents (ANSI, ISO, and others). It indicates that a certain usage is now disapproved of (see meaning 2 of deprecate, below), not that its value has in any way changed. +1! - Steph -- PHP Documentation Mai

RE: [PHP-DOC] typo in the docs

2003-03-21 Thread Ford, Mike [LSS]
> -Original Message- > From: Gabor Hojtsy [mailto:[EMAIL PROTECTED] > Sent: 21 March 2003 16:38 > To: [EMAIL PROTECTED] > Subject: [PHP-DOC] typo in the docs > > > An excerpt from a mail we received at [EMAIL PROTECTED] As > you can see, > Thomas spent significant time researching what