XHTML严格与基本疯狂 [英] XHTML Strict vs Basic Madness
问题描述
我测试了一些新的诺基亚6600功能。它配备了
WAP2和XHTML支持（它说）。它的作用是检查Doctype -
，如果它不是XHTML Mobile Profile Doctype，而是XHTML1.0 Strict
one，media-handheld CSS是_ignored_。只有使用诺基亚Doctype，
才能使用CSS。我发现这真的很烦人，因为它违背了与媒体无关的XHTML Strict以及样式表的整个想法。
好的一面，WML似乎正在运行但仅限于
向后兼容性，几乎任何HTML都可以呈现 -
和XHTML1严格使用CSS2自然比大多数人好得多
页面这里。
不过，如果我想设计我已经工作的页面，我需要制作一个
冗余副本，或者更改为XHTML Basic Doctype，可能会在桌面平台上混淆半打Doctype-sniffer。这是
Netscape 4再次烧毁。
我使用的样品：
Mobile DTD（使用手持设备）与诺基亚的CSS）：
< http://outer-court.com/mobile/index.html>
1.0严格的DTD（缺乏CSS支持）与诺基亚合作）
< http://outer-court.com/mobile/test.html>
Philipp Lenssen写道：我测试了一些新的诺基亚6600功能。它配备了
WAP2和XHTML支持（它说）。它的作用是检查Doctype -
如果它不是XHTML Mobile Profile Doctype，而是XHTML1.0 Strict
，那么媒体手持CSS就是_ignored_。仅使用诺基亚Doctype，
使用CSS。我发现这真的很烦人，因为它违背了与媒体无关的XHTML Strict和样式表的整个想法。
另一个DOCTYPE，意思是其他元素。对于诺基亚的行为，有一些话可以说。
好的一面，WML似乎正在运行，但只是为了向后兼容，几乎任何HTML都可以呈现 -
和XHTML1严格使用CSS2自然比这里的大多数页面都要好得多。
如果我想设计我已经工作过的页面，我需要制作一个
冗余副本，或者更改为XHTML Basic Doctype，这可能会混淆桌面平台上的六十个Doctype-sniffer。这是Netscape 4再次发生的灾难。
XHTML Basic不支持编写脚本并从XHTML派生（sp？）
模块化，这意味着它的内容类型应该是
application / xhtml + xml，也是Internet Explorer的灾难;-)。
我使用的样品：
Mobile DTD（使用手持设备）与诺基亚的CSS）：
< http://outer-court.com/mobile/index.html>
1.0严格的DTD（诺基亚缺乏CSS支持）
< ; http：//outer-court.com/mobile/test.html>
-
Anne van Kesteren
< http://www.annevankesteren.nl/>
Anne van Kesteren写道：
Philipp Lenssen写道：我测试了一些新的诺基亚6600功能。它配备了
WAP2和XHTML支持（它说）。它的作用是检查Doctype
- 如果它不是XHTML Mobile Profile Doctype，而是XHTML1.0严格的，那么媒体手持式CSS将被忽略。只有诺基亚
Doctype，才使用CSS。我发现这真的很烦人，因为它与媒体无关的XHTML Strict和
样式表的整个想法相对立。
另一个DOCTYPE，意味着其他元素。对于诺基亚的行为有一些话要说。
但是XHTML Basic只是XHTML Strict的一个子集......
他们应该只渲染Strict并忽略他们想要忽略的内容......
XHTML Basic不支持编写脚本并从
XHTML模块化中派生（sp？）它的内容类型应该是
application / xhtml + xml，也是Internet Explorer的灾难; - ）。
理论上是的，虽然实际上诺基亚似乎并不关心
内容类型。我提供HTML。 （我想知道这与
的情况有什么关系。）
实际上，我应该检查它是否适用于Basic Doctype -
我第一次测试的是诺基亚移动配置文件
Doctype。
我想知道是否有人知道XHTML的问题基本Doctype和
流行的doctype-sniffing？
Philipp Lenssen写道：
但是XHTML Basic只是XHTML Strict的一个子集...
他们应该只渲染严格并忽略他们想要忽略的东西...
我不确定是否是浏览器应该这样做。但是如果你不是以bb格式提供它，那么浏览器可能就是。
理论上是的，虽然实际上诺基亚似乎并不关心
内容类型。我提供HTML。 （我想知道这与
情况有什么关系。）
实际上，我应该检查它是否适用于Basic Doctype -
我服务的第一个测试的时间是诺基亚移动配置文件
Doctype。
这确实会派上用场。
我想知道有没有人知道XHTML Basic Doctype和
流行的doctype-sniffing的问题？
Mozilla将保持标准模式，我认为Internet Explorer 6也将支持
（旧的IE'没有检查doctype） 。不确定Opera和
Mac浏览器。
-
Anne van Kesteren
< http： //www.annevankesteren.nl/>
I''ve tested some of the new Nokia 6600 functionality. It ships with
WAP2 and XHTML Support (it says). What it does is check the Doctype --
if it''s not the XHTML Mobile Profile Doctype, but a XHTML1.0 Strict
one, the media-handheld CSS is _ignored_. Only with the Nokia Doctype,
the CSS is used. I find this really annoying as it goes against the
whole idea of media-independent XHTML Strict along with stylesheets.
On the good side, WML seems to be running but only for
backwards-compatibility, and pretty much any HTML can be rendered --
and XHTML1 Strict using CSS2 naturally fares much better than most
pages here.
Still, if I want to style my already working pages, I need to make a
redundant copy, or change to XHTML Basic Doctype, which would probably
confuse half dozen Doctype-sniffers on the desktop-platform. It''s the
Netscape 4 desaster all over again.
Samples I used:
Mobile DTD (uses handheld-CSS with Nokia):
<http://outer-court.com/mobile/index.html>
1.0 Strict DTD (lacks CSS support with Nokia)
<http://outer-court.com/mobile/test.html>
Philipp Lenssen wrote:I''ve tested some of the new Nokia 6600 functionality. It ships with
WAP2 and XHTML Support (it says). What it does is check the Doctype --
if it''s not the XHTML Mobile Profile Doctype, but a XHTML1.0 Strict
one, the media-handheld CSS is _ignored_. Only with the Nokia Doctype,
the CSS is used. I find this really annoying as it goes against the
whole idea of media-independent XHTML Strict along with stylesheets.
Another DOCTYPE, means other elements. There is something to say for
Nokia''s behavior.
On the good side, WML seems to be running but only for
backwards-compatibility, and pretty much any HTML can be rendered --
and XHTML1 Strict using CSS2 naturally fares much better than most
pages here.
Still, if I want to style my already working pages, I need to make a
redundant copy, or change to XHTML Basic Doctype, which would probably
confuse half dozen Doctype-sniffers on the desktop-platform. It''s the
Netscape 4 desaster all over again.
XHTML Basic doesn''t support scripting and derives (sp?) from the XHTML
modularization which means that it''s content-type should be
application/xhtml+xml, a Internet Explorer disaster as well ;-).
Samples I used:
Mobile DTD (uses handheld-CSS with Nokia):
<http://outer-court.com/mobile/index.html>
1.0 Strict DTD (lacks CSS support with Nokia)
<http://outer-court.com/mobile/test.html>
--
Anne van Kesteren
<http://www.annevankesteren.nl/>
Anne van Kesteren wrote:
Philipp Lenssen wrote:I''ve tested some of the new Nokia 6600 functionality. It ships with
WAP2 and XHTML Support (it says). What it does is check the Doctype
-- if it''s not the XHTML Mobile Profile Doctype, but a XHTML1.0
Strict one, the media-handheld CSS is ignored. Only with the Nokia
Doctype, the CSS is used. I find this really annoying as it goes
against the whole idea of media-independent XHTML Strict along with
stylesheets.
Another DOCTYPE, means other elements. There is something to say for
Nokia''s behavior.
But XHTML Basic is just a Subset of XHTML Strict...
They should just render Strict and ignore what they want to ignore...
XHTML Basic doesn''t support scripting and derives (sp?) from the
XHTML modularization which means that it''s content-type should be
application/xhtml+xml, a Internet Explorer disaster as well ;-).
Theoretically yes, though actually Nokia doesn''t seem to care about the
content-type. I serve HTML. (I wonder how that is connected to the
situation.)
Actually, I should check if it works with the Basic Doctype at all --
what I was serving the first time to test was the Nokia Mobile Profile
Doctype.
I wonder does anybody know problems with XHTML Basic Doctype and
popular doctype-sniffing?
Philipp Lenssen wrote:
But XHTML Basic is just a Subset of XHTML Strict...
They should just render Strict and ignore what they want to ignore...
I''m not sure if a browser is supposed to do that. But if you are not
serving it as XML, the browser probably is.
Theoretically yes, though actually Nokia doesn''t seem to care about the
content-type. I serve HTML. (I wonder how that is connected to the
situation.)
Actually, I should check if it works with the Basic Doctype at all --
what I was serving the first time to test was the Nokia Mobile Profile
Doctype.
That would indeed come in handy.
I wonder does anybody know problems with XHTML Basic Doctype and
popular doctype-sniffing?
Mozilla will stay in standard mode and I think Internet Explorer 6 will
as well (older IE''s didn''t check the doctype). Not sure about Opera and
Mac browsers though.
--
Anne van Kesteren
<http://www.annevankesteren.nl/>
这篇关于XHTML严格与基本疯狂的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
