No, please, tell me it's all a bad dream...
Doesn't that workaround mean that all browsers, even ones that support XHTML 1.1 (such as Firefox), will suddenly start applying an XSL transformation to the entire web page?
Wouldn't it be a much less nasty hack just to tell Tomcat to serve these pages as text/html? How can I do that?
Garret
Mark Eggers wrote:
On Fri, 2004-09-17 at 17:55, Garret Wilson wrote:
With Tomcat 5.5.2, JSF, and JSP, I'm serving up pure, standards-compliant XHTML 1.1 that starts out with:
<?xml version="1.0">
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd";>
<html xmlns="http://www.w3.org/1999/xhtml";>
That works just fine with FireFox, but with IE (the very latest and greatest available), I get:
Parameter entity must be defined before it is used. Error processing resource 'http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd...
%xhtml-prefw-redecl.mod; -^
Yep - known bug that IE cannot handle this. Apparently there is a work-around detailed at:
http://www.w3.org/MarkUp/2004/xhtml-faq#texthtml
I haven't tried it yet.
/mde/ just my two cents . . . .
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
