站点模板 - 任何Internet Explorer XML Parser错误？ [英] Site Template - Any Internet Explorer XML Parser errors?
问题描述
注意：过去的体验让我觉得USENET上的许多事情无法阅读
文章在回答之前是正确的。我正在寻找非常具体的信息
信息，因此请完全阅读并理解之前
响应;或者提出澄清问题。我*会*感激任何
建设性回复。
问候！
我正在创建网站的模板。该网站将是
* true * XHTML 1.1。也就是说，它将在所有页面上验证为XHTML 1.1，
它将使用UTF-8字符集，它将（每当
可能）被发送使用mime类型的application / xhtml + xml。为了在Internet Explorer中强制符合标准的模式，我也在使用JavaScript IE7兼容性补丁（ http://dean.edwards.name/IE7/) 。
问题我遇到的是Internet Explorer。任何人都有任何严重的博格式倾向（即，追求完美的价值）会告诉你，Internet Explorer无法处理
/>
application / xhtml + xml;将其视为可下载文件。然而，
是一种解决方法。 XHTML页面*可以被视为
application / xml（它不是* dis *允许，只是气馁;
不同于text / html，不允许使用XHTML）和IE *确实*识别
这种格式。但是，为了防止IE下载它或显示XML树的
，必须应用一个非常小的XSLT转换。
我有的问题运行的是IE（具有取决于机器的
问题中的版本）将抛出XML解析错误，因为
到标准XHTML 1.1 DOCTYPE：
< output>
无法显示XML页面
无法使用XSL样式表查看XML输入。请更正错误
，然后单击刷新按钮，或稍后再试。
------------------ -------------------------------------------------- ------------
参数实体必须在使用前定义。处理错误
资源''http：//www.w3.org/TR/xhtml11/DTD/xhtml11.dtd ...
％xhtml- prefw-redecl.mod;
- ^
< / output>
现在，在* my * machine上，我已经重新设计了结果输出，以便IE 6
和更低版本不会抛出此错误，尽管被送入正常的DOCTYPE。
但是，IE7 *必须* *非标准* DOCTYPE以避免
抛出此错误。
由于IE 6及更低版本正在使用普通的XHTML 1.1 DOCTYPE，我想
想知道这个错误是否出现在任何其他角色的机器上，当
他们使用的IE版本低于7.如果你的IE版本为
，我想知道以下内容：
a ？你的IE版本
a？¢你的操作系统（32位/ 64位），包括服务包
a？¢你安装的MSXMLS版本
a？¢和错误信息，如果它与上面显着不同
任何和所有关于* design *的评论也将不胜感激。
该模板可在 http://www.bannerswarm.net找到/template.php
请注意，模板仍在施工。虽然
有问题的DOCTYPE不会改变，但内容和布局可能会突然发生变化而且没有任何警告。
TIA
... Geshel
-
********************* ***************************** ******************* />
我的回复电子邮件地址是一个自动监控的垃圾邮件蜜罐。
除非您希望被报告为垃圾邮件发送者，否则不要在那里发送电子邮件。
请将所有电子邮件发送到我姓氏dot org的第一个名字，然后使用
a主题内容为NEO GESHELA提供新闻报道？ （全部大写）。
************************************* ************* *******************
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 a??pursuit of
perfectiona??) 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 persona??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:
a?￠ Your version of IE
a?￠ Your OS (32-bit/64-bit), including service packs
a?￠ Your version of MSXMLS installed
a?￠ 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 a??NEWSGROUP REPLY FOR NEO GESHELa?? (all uppercase).
************************************************** *******************
推荐答案
Neo Geshel< go **** @ geshel.orgwrites：
Neo Geshel <go****@geshel.orgwrites:
注意：过去的经验告诉我，USENET上有很多事情无法阅读
文章在回答之前正确。我正在寻找非常具体的信息
信息，因此请完全阅读并理解之前
响应;或者提出澄清问题。我*会*感激任何
建设性回复。
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.
你首先通过交叉发布，大喊大叫，然后告诉我们我们应该
读一篇文章正确，即使你不能费心去发布
那样。
你认真期待那之后的建设性回复吗？
我的建议是，由于使用XHTML导致问题，请改用HTML。
问题解决了。
或者，如果你坚持使用XHTML尽管有许多众所周知的问题，但是不要再回到这里，要求解决你坚持要解决的问题
为自己创造的问题，以及侮辱那些试图告诉你的人如何在第一时间避免这些问题。
sherm--
-
西弗吉尼亚人为西弗吉尼亚人提供的虚拟主机服务： http://wv-www.net
Perl中的Cocoa编程： http://camelbones.sourceforge.net
Sherm Pendley写道：
Sherm Pendley wrote:
Neo Geshel< go **** @ geshel.orgwrites：
Neo Geshel <go****@geshel.orgwrites:
>注意：过去的经验告诉我，USENET上的许多人都无法在回答之前正确阅读文章。我正在寻找非常具体的信息，因此请在回复之前仔细阅读和理解;或者提出澄清问题。我*会*感谢任何建设性回复。
>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.
你首先通过交叉发布，大喊大叫，然后告诉我们我们应该
读一篇文章正确，即使你不能打扰它发布
那样。
You begin by cross-posting, shouting, and then telling us that we should
read an article "properly", even though you can''t be bothered to post it
that way.
你想我多发帖吗？我已经使用互联网16 +
年，我的理解是，交叉发布比多发帖更好*更多
。
你知道，将来我总是可以发帖多篇文章，如果那个
会让你开心。这样，在一个NG中阅读的人将无法在另一个NG中看到同一帖子的答案。
Would you rather I multi-post? Having been using the Internet for 16+
years, it is my understanding that cross-posting is *far* more
preferable than multi-posting.
You know, in the future I could always multi-post articles, if that
would make you happy. That way, people reading in one NG would be unable
to see answers to the same post in another NG.
你真的期待吗？之后的建设性回复？
Do you seriously expect constructive replies after that?
Ita ??总是一个foola ??希望期待Usenet的建设性回复，
特别是更复杂或更详细的帖子。 Thata ??为什么我要求b $ b试图淘汰那些只会鹦鹉学舌的人，我明确表示我很感兴趣，或者已经打了折扣。
是的，我发布的文章越精确或越具技术性，回复的答案就越多，我已经明确表示我
打折，或明确表示我没兴趣。因此，我试图
a ?? focusa ??人们。
Ita??s always a foola??s hope to expect constructive replies from Usenet,
especially with more complicated or more detailed posts. Thata??s why I
tried to weed out those who would just parrot back that which I clearly
stated I wasna??t interested in, or had already discounted.
And yes, the more precise or more technical an article I post, the more
people that reply with an answer I had already clearly stated that I
discounted, or clearly stated I had no interest in. Hence, my attempt to
a??focusa?? people.
我的建议是，由于使用XHTML导致问题，请改用HTML。
问题解决了。
My advice is, since using XHTML is causing problems, use HTML instead.
Problem solved.
我有更多的HTML问题和一个奇怪的模式？渲染
我用过XHTML的HTML浏览器之间的差异。
I have far more problems with HTML and a??quirks modea?? rendering
differences between browsers with HTML that I have ever had with XHTML.
或者，如果你坚持使用XHTML而不是许多众所周知的问题，
Or, if you insist on using XHTML in spite of its many well-known problems,
它的*众多*众所周知的问题？我只知道两个问题 - 互联网
Explorera无法处理application / xhtml + xml，以及（通过代理）
IEa ?? sa ?? quirks modea ?? XML Prologue的问题（可以通过
修复它来对文档进行XSLT转换，并提供
application / xml）。
否则，XHTML 1.1对我来说效果很好。
Its *many* well-know problems? I know of only two problems - Internet
Explorera??s inability to handle application/xhtml+xml, and (by proxy)
IEa??s a??quirks modea?? problems with the XML Prologue(which can be fixed by
getting it to conduct an XSLT transformation on a document served up as
application/xml).
Otherwise, XHTML 1.1 works just fine for me.
不要回到这里，要求解决你遇到的问题坚持为自己创造
，并侮辱那些试图告诉你的人如何避免这些问题。
don''t come back here asking for solutions to the problems you''ve insisted
on creating for yourself, and insulting the very people who tried to tell
you how to avoid those problems in the first place.
令人困惑的原因和结果，是吗？有时间
效果的问题？亲爱的，你是第一个回复这篇文章的人。没有人
已经*试过*来帮助我*这个*帖子和*这个*问题。尝试
避免将来的时间旅行，k？原谅双关语。
干杯。
... Geshel
-
** ************************************************ ** *****************
我的回复电子邮件地址是一个自动监控的垃圾邮件蜜罐。
不发送电子邮件 - 除非您希望被报告为垃圾邮件发送者，否则邮件会在那里发送。
请将所有电子邮件发送到我的姓氏dot org，用
a主题行一个??新闻报道对于NEO GESHELa？ （全部大写）。
************************************* ************* *******************
Confusing cause and effect, are we? Having trouble with temporal
effects? You are the first person to reply to this post, dearie. No-one
has *tried* to help me with *this* post and *this* issue yet. Try to
avoid time-travel in the future, k? Pardon the pun.
Cheers.
...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 a??NEWSGROUP REPLY FOR NEO GESHELa?? (all uppercase).
************************************************** *******************
Neo Geshel写道：
Neo Geshel wrote:
Sherm Pendley写道：
Sherm Pendley wrote:
> Neo Geshel< go **** @ geshel .orgwrites：
>Neo Geshel <go****@geshel.orgwrites:
>>注意：过去的经验告诉我，USENET上的许多人都没有读过
>>NOTE: PAST EXPERIENCE HAS SHOWN ME THAT MANY ON USENET FAIL TO READ
傲慢的混蛋认为他们比单纯的人更好。
posts by arrogant bastards who think they''re better than mere humans.
>>
你首先交叉发帖，大喊大叫，然后告诉我们，我们应该正确地阅读一篇文章，即使你不能打扰发布它那样。
>>
You begin by cross-posting, shouting, and then telling us that we should
read an article "properly", even though you can''t be bothered to post it
that way.
你想我多发帖吗？我已经使用互联网16 +
年，我的理解是，交叉发布比多发帖更好*更多
。
Would you rather I multi-post? Having been using the Internet for 16+
years, it is my understanding that cross-posting is *far* more
preferable than multi-posting.
你没有理由做一些愚蠢和粗鲁的事情威胁要做一些更愚蠢和粗鲁的事情。如果你真的有16年的使用互联网经验，也许你会知道如何缩小适当的NG的价值。或者16年的互联网体验包括
只有16分钟的USENET体验？
You are not excused to do something stupid and rude by threatening to do
something even more stupid and rude. And if you''ve really got 16 years
of experience of using the Internet, maybe you''d know how to narrow down
appropriate NGs. Or maybe that 16 years of Internet experience includes
only 16 minutes of USENET experience?
>
你知道，将来我总是可以多篇文章，如果那个
会让你开心。这样，在一个NG中阅读的人将无法在另一个NG中查看同一帖子的答案。
>
You know, in the future I could always multi-post articles, if that
would make you happy. That way, people reading in one NG would be unable
to see answers to the same post in another NG.
嗯，谢谢，但我们已经知道多次发布有什么问题了。你做了什么？b $ b你在过去的半小时内把它搞砸了吗？
Um, thanks, but we already know what''s wrong with multi-posting. What''d
you do, just Google this up in the last half-hour?
>之后你真的期待建设性的回复吗？
>Do you seriously expect constructive replies after that?
Ita ??总是一个foola ??希望期待Usenet的建设性回复，
Ita??s always a foola??s hope to expect constructive replies from Usenet,
....然而，你来到这里;对你有什么看法？
....and yet, you came here; what''s that say about you?
特别是更复杂或更详细的帖子。 Thata ??为什么我要求b $ b试图淘汰那些只会鹦鹉学舌的人，我明确表示我很感兴趣，或者已经打了折扣。
是的，我发布的文章越精确或越具技术性，回复的答案就越多，我已经明确表示我
打折，或明确表示我没兴趣。因此，我试图
a ?? focusa ??人。
especially with more complicated or more detailed posts. Thata??s why I
tried to weed out those who would just parrot back that which I clearly
stated I wasna??t interested in, or had already discounted.
And yes, the more precise or more technical an article I post, the more
people that reply with an answer I had already clearly stated that I
discounted, or clearly stated I had no interest in. Hence, my attempt to
a??focusa?? people.
太糟糕了，你没有一个二乘四你可以打我们，或者一个
泰瑟;那会引起我们的注意。可惜你必须求助于这样的原油
意味着使用单词和所有大写。
Too bad you don''t have a two-by-four you can whack us with, or maybe a
Taser; that''d get our attention. Pity you have to resort to such crude
means as using words and ALL CAPS.
>
>
>我的建议是，由于使用XHTML会导致问题，请改用HTML。
问题解决了。
>My advice is, since using XHTML is causing problems, use HTML instead.
Problem solved.
我有更多的HTML问题和一个怪癖模式？渲染
我用过XHTML的HTML浏览器之间的差异。
I have far more problems with HTML and a??quirks modea?? rendering
differences between browsers with HTML that I have ever had with XHTML.
然后诱导*标准*模式。结合Sherm的建议和
（请注意这里;我想要*聚焦*）你在
标准模式下获得HTML。
Then induce *standards* mode. Combine this with Sherm''s suggestion and
(Please pay attention here; I WANT YOU TO *FOCUS*) you get HTML in
standards mode.
>
你是第一个回复这篇文章的人，亲爱的。没有人
已经*试过*来帮助我*这个*帖子和*这个*问题。
>
You are the first person to reply to this post, dearie. No-one
has *tried* to help me with *this* post and *this* issue yet.
我建议你不要期待一大堆乐于助人的人。亲爱的。
-
John
I suggest you not expect a long line of helpful folks. Dearie.
--
John
这篇关于站点模板 - 任何Internet Explorer XML Parser错误？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
