|
|
Posted by Neo Geshel on 04/20/07 22:04
NOTE: PAST EXPERIENCE HAS SHOWN ME THAT MANY ON USENET FAIL TO READ
ARTICLES PROPERLY PRIOR TO ANSWERING. I AM LOOKING FOR VERY SPECIFIC
INFORMATION, THEREFORE PLEASE READ AND UNDERSTAND THOROUGHLY BEFORE
RESPONDING; OR ASK QUESTIONS TO CLARIFY. I *WILL* APPRECIATE ANY
CONSTRUCTIVE REPLY.
Greetings!
I am in the process of creating a template for a site. The site will be
*true* XHTML 1.1. That is, it will validate as XHTML 1.1 on all pages,
it will make use of the UTF-8 character set, and it will (whenever
possible) be sent out with a mime-type of application/xhtml+xml. To
force standards-compliant mode in Internet Explorer, I am also making
use of the JavaScript IE7 compliance patch (http://dean.edwards.name/IE7/).
The problem that I am experiencing is with Internet Explorer. As anyone
with any serious Borg-like tendencies (i.e., the “pursuit of
perfection”) will tell you, Internet Explorer is incapable of handling
application/xhtml+xml; treating it instead as a downloadable file. There
is a workaround, however. XHTML pages *can* be treated as
application/xml in a pinch (it is not *dis*allowed, just discouraged;
unlike text/html which is disallowed for XHTML), and IE *does* recognize
this format. However, to prevent IE from either downloading it or
displaying the XML tree, one has to apply a very small XSLT transformation.
The problem that I have run across is that IE (with the version in
question depending on the machine) will throw an XML parsing error due
to the standard XHTML 1.1 DOCTYPE:
<output>
The XML page cannot be displayed
Cannot view XML input using XSL style sheet. Please correct the error
and then click the Refresh button, or try again later.
--------------------------------------------------------------------------------
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;
-^
</output>
Now, on *my* machine, I have reworked the resulting output so that IE 6
and lower does not throw this error, despite being fed a normal DOCTYPE.
However, IE7 *does* have to be fed a *non-standard* DOCTYPE to avoid
throwing this error.
Since IE 6 and lower is being fed a normal XHTML 1.1 DOCTYPE, I would
like to know if this error appears on any other person’s machine, when
they are using a version of IE less than 7. If you get this error with
your version of IE, I would like to know the following:
• Your version of IE
• Your OS (32-bit/64-bit), including service packs
• Your version of MSXMLS installed
• And the error message, if it differs significantly from above
Any and all comments about the *design* would also be appreciated.
The template can be found at http://www.bannerswarm.net/template.php
Please also note that the template is still under construction. While
the DOCTYPE in question will not change, the content and layout may
change suddenly and without warning.
TIA
...Geshel
--
*********************************************************************
My return e-mail address is an automatically monitored spam honeypot.
Do not send e-mail there unless you wish to be reported as a spammer.
Please send all e-mail to my first name at my last name dot org, with
a subject-line of “NEWSGROUP REPLY FOR NEO GESHEL” (all uppercase).
*********************************************************************
Navigation:
[Reply to this message]
|