- From: Laurent Carcone <Laurent.Carcone@inrialpes.fr>
- Date: Fri, 10 Jan 2003 12:11:29 +0100
- To: Brant Langer Gurganus <brantgurganus2001@cherokeescouting.org>
- Cc: www-amaya@w3.org
Hello Brant, This bug is now fixed. Actually, it was due to a modification I made before the last release to manage the BOM issue. > Amaya has an XML parsing issue that causes it to not report an error > that should be reported in order to be conformant > > From XML spec: > [Definition: *Validating processors* must, at user option, report > violations of the constraints expressed by the declarations in the DTD > <http://www.w3.org/TR/REC-xml#dt-doctype>, and failures to fulfill the > validity constraints given in this specification.] To accomplish this, > validating XML processors must read and process the entire DTD and all > external parsed entities referenced in the document.. > > By that definition (if Amaya uses a validating XML processor), it must > report if whitespace appears before the XML declaration. > Amaya 'only' uses a well-formedness processor for XML documents and checks validity for some known formats like XHTML, SVG and MathML. > Expected Results: > A message similar to the following should be given: > XML Parsing Error: xml processing instruction not at start of external entity > Location: file:///F:/Documents%20and%20Settings/Brant%20Gurganus/My%20Documents/Personal/brant.xhtml > Line Number 1, Column 2: <?xml version="1.0" encoding="UTF-8"?> > -^ > > Please not that the above sample is from Mozilla which is not a validating processor and by the definition of such is not required to check for this. Regards, Laurent Carcone
Received on Friday, 10 January 2003 06:12:35 UTC