#23676 [Bgs]: error on processing instructions that begin with xml
ID: 23676
User updated by: brandon dot whitehead at orst dot edu
Reported By: brandon dot whitehead at orst dot edu
Status: Bogus
Bug Type: DOM XML related
Operating System: Win32 (XP)
PHP Version: 4.3.1
Assigned To: edink
New Comment:
It is a bit of a confusing definition, because the defintion of a PI
excludes instances of "XML" explicitly, yet it is already accounted for
in the "Name" definition upon which it is based. I therefore find
fault with the W3's recommendation.
Unfortunately, the bug must therefore be in XML Spy which is the
program that is generating the violating xml pi.
Previous Comments:
------------------------------------------------------------------------
[2003-05-18 10:23:14] rrichards@php.net
Thank you for taking the time to write to us, but this is not
a bug. Please double-check the documentation available at
http://www.php.net/manual/ and the instructions on how to
report
a bug at http://bugs.php.net/how-to-report.php
first 3 characters "xml" are reserved for any future standard PIs.
Currently "xml-stylesheet" is also support.
Upgrading libxml will not change this as there have been no changes to
this rule in their library.
------------------------------------------------------------------------
[2003-05-18 08:42:11] sniper@php.net
Edin, update your libxml for the win32 build..
------------------------------------------------------------------------
[2003-05-17 20:49:01] brandon dot whitehead at orst dot edu
The DOMXML processor fails if it runs into processing instructions that
BEGIN with any case composition of "XML". See the rules here:
http://www.w3.org/TR/REC-xml#sec-pi
For example "<?xmltarget ?>" would cause a failure.
Admittedly its a bit of a tricky definition, but basically, anything is
valid except the following targets: "XML", "XMl", "XmL",
"Xml", "xML",
"xMl", "xmL", and "xml"
"xmltarget" is valid because there is not whitespace folliwng the "l"
Since LibXML appears to now be built into php_domxml.dll, I can not
upgrade from the built in version of 2.04.30 to the current version of
2.05.07. Therefore I am reporting it as a bug in PHP.
I sincerely appologize if this is in some way bogus.
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=23676&edit=1
Thread (5 messages)