DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25222>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25222

XALAN processing fails, if you want to use the "document()" function and open a xhtml 
file, that has a dtd header:

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|                            |INVALID



------- Additional Comments From [EMAIL PROTECTED]  2004-02-19 09:02 -------
Yes, you are right, we agreed, that the first problem is our environment 
problem (not to have access to the web around the proxy settings), not a XALAN 
defect. I just wanted to assemble both problems concerning DTD headers again, 
but I will follow your suggestion and raise an enhancement request for that. 
Unfortunately I can't use your workaround, as the XHTML files are generated 
automatically by a programme I can't influence (Microsoft Visio). The easier 
workaround for me is just to delete the DTD header in the resulting file (or 
just use Visio 2002 instead of Visio 2000, no DTD header is created then).

To the second problem:
I recognized, that the problem is caused by the not XML compliant DTD header in 
the HTM file exported by Visio 2000:

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">

This DTD header is a HTML Doctype defining the document as HTML 2.0 compliant. 
To make this HTM file available for XML processing (document function) I use 
HTML Tidy (JTidy) to convert the HTML to a XHTML file. Unfortunately this 
conversion does not change the DTD header, if the configuration "Output as 
XHTML" is not set in the HTML Tidy configuration (I just used "Output as XML", 
but obviously that's not enough).

For XML documents the DTD header has to follow the notation:

<!DOCTYPE name SYSTEM "URI">

So the parsing of the document causes an exception.

AND THAT IS NO XALAN OR XERCES DEFECT !!!

Thanx for your support.

Reply via email to