Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: Well-formedness and undeclared general entity references

From: Stanimir Stamenkov <s7an10@--------.--->
To: NULL
Date: 4/10/2009 5:51:00 PM
10 Apr 2009 14:26:52 GMT, /Richard Tobin/:
> In article <grnc77$r5e$1@n...>, 
> Stanimir Stamenkov  <s7an10@n...> wrote:
>
>> <!DOCTYPE test SYSTEM "empty.dtd">
>> <test>
>>   foo
>>   &bar;
>> </test>
>>
>> Where "empty.dtd" is really an empty file.
> 
> A non-validating processor isn't required to read empty.dtd, so it may 
> not be able to tell that it doesn't contain any declarations.  The 
> idea is that an error that can only be detected by reading the 
> external DTD is a validity error, rather than a well-formedness error.

So I may address this issue further on the Xerces mailing list as I 
can see the "empty.dtd" gets read, first by registering a SAX 
LexicalHandler and observing the start/endEntity events, then by 
declaring:

<!ENTITY fu "foo">

And replacing "foo" with "&fu;" (w/o the quotes) in the original 
example.

-- 
Stanimir


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent