[PHP-DOC] ��Ң�¶١ Licensed Windows XP Pro, win 98, 98 se, Office XP Small, Office

2006-06-26 Thread paisarn
àÃÒ¢Ò¶١ Licensed Windows XP Pro, win 98, 98 se, Office XP Small, Office XP Professional, Office Pro 2003 ¶Ù¡ÁÒ¡ ¢Í§á·éá¹è¹Í¹ 100 % µÔ´µèÍ Paisarn 06-5881135 - Windows 95 ẺÁÕ CD ¤ÃºªØ´ 200 bath - Windows 98 book+COA only 800 bath - Windows 98 boo

Re: [PHP-DOC] cvs: phpdoc /en/reference/simplexml/functions simplexml-element-getDocNamespaces.xml simplexml-element-getNamespaces.xml simplexml-element-registerXPathNamespace.xml simplexml-load-file.

2006-06-26 Thread Sean Coates
> So it's not clear to me that Ben is in the wrong here. In any case, I un-volunteer to mess with >300 files on the CVS server. S

Re: [PHP-DOC] cvs: phpdoc /en/reference/simplexml/functions simplexml-element-getDocNamespaces.xml simplexml-element-getNamespaces.xml simplexml-element-registerXPathNamespace.xml simplexml-load-file.

2006-06-26 Thread Dan Scott
On 22/06/06, Philip Olson <[EMAIL PROTECTED]> wrote: > On 6/22/06, Ben Ramsey <[EMAIL PROTECTED]> wrote: >> ramsey Thu Jun 22 03:04:36 2006 UTC >> >> Added files: >> /phpdoc/en/reference/simplexml/functions >> simplexml-element- >> r

Re: [PHP-DOC] cvs: phpdoc /en/reference/simplexml/functions simplexml-element-getDocNamespaces.xmlsimplexml-element-getNamespaces.xml simplexml-element-registerXPathNamespace.xmlsimplexml-load-file.xm

2006-06-26 Thread Gabor Hojtsy
On Mon, 26 Jun 2006, Philip Olson wrote: There appears to be 356 (ignoring ZEND and internals) that need changed (in en/), but that number also looks too high! I think it's fine to pick on ben and simplexml here :), this is a newish extension that should adhere to our guidelines despite a hist

Re: [PHP-DOC] cvs: phpdoc /en/reference/simplexml/functions simplexml-element-getDocNamespaces.xmlsimplexml-element-getNamespaces.xml simplexml-element-registerXPathNamespace.xmlsimplexml-load-file.xm

2006-06-26 Thread Philip Olson
On Jun 26, 2006, at 8:39 AM, Sean Coates wrote: I can just cvs remove the existing files and re-add them with their lowercase names, but this will lose the history information attached to the files? Is there another way you recommend I handle this? This will upset translators. (-: I can mo

Re: [PHP-DOC] cvs: phpdoc /en/reference/simplexml/functions simplexml-element-getDocNamespaces.xmlsimplexml-element-getNamespaces.xml simplexml-element-registerXPathNamespace.xmlsimplexml-load-file.xm

2006-06-26 Thread Sean Coates
>> I can just cvs remove the existing files and re-add them with their >> lowercase names, but this will lose the history information attached to >> the files? Is there another way you recommend I handle this? > > This will upset translators. (-: > > I can move the files in CVS. > > Translators:

[PHP-DOC] #37913 [Opn->Bgs]: preg_match_all typo

2006-06-26 Thread nlopess
ID: 37913 Updated by: [EMAIL PROTECTED] Reported By: tom at foreignproperty dot com -Status: Open +Status: Bogus Bug Type:Documentation problem PHP Version: Irrelevant New Comment: No. The example is correct. It shows how to use nested parenteses and backreferences.

[PHP-DOC] #37913 [Bgs->Opn]: preg_match_all typo

2006-06-26 Thread tom at foreignproperty dot com
ID: 37913 User updated by: tom at foreignproperty dot com Reported By: tom at foreignproperty dot com -Status: Bogus +Status: Open Bug Type:Documentation problem PHP Version: Irrelevant New Comment: look at the array keys. it goes $matches[0], $

[PHP-DOC] #37913 [Opn->Bgs]: preg_match_all typo

2006-06-26 Thread takagi
ID: 37913 Updated by: [EMAIL PROTECTED] Reported By: tom at foreignproperty dot com -Status: Open +Status: Bogus Bug Type:Documentation problem PHP Version: Irrelevant New Comment: No, that's perfectly correct. The regx is "/(<([\w]+)[^>]*>)(.*)(<\/\\2>)/". So, [1]

[PHP-DOC] #37913 [NEW]: preg_match_all typo

2006-06-26 Thread tom at foreignproperty dot com
From: tom at foreignproperty dot com Operating system: PHP version: Irrelevant PHP Bug Type: Documentation problem Bug description: preg_match_all typo Description: In the description for preg_match_all, in the 2nd example, Find matching HTML tags (greedy), the