beta2 XHTML合规性？这是必要的。或愚蠢...读取MICROSOFT [英] beta2 XHTML compliance? is this necessary. OR STUPID...read UP MICROSOFT

问题描述

我听说beta 2现在使ASP.NET xhtml兼容。


任何人都可以了解一下这会改变什么，它会打破东西

将HTML转换为XHTML页面会破坏事物。请参阅，
http://www.alistapart.com/articles/betterliving /


我读了
http://msdn.microsoft.com/netframewo...etfxcompat.asp


它说他们改变了这样的东西


"符合标准：ASP.NET中的HTML呈现更新为

XHTML 1.0 Transitional，符合标准


这又是另一个STUPID标准合规mindnumb机器人类型

思考。标准合规性是并且永远不会是重要的，因为它可以在多个浏览器上工作。如果应用程序

甚至不起作用，标准有什么用呢？新标准怎么样？它被称为让它工作

而不是听一些愚蠢的委员会，他们整天坐在会议中互相交谈但对现实世界一无所知在

让事情真正发挥作用。

I heard that beta 2 now makes ASP.NET xhtml compliant.

Can anyone shed some light on what this will change and it will break stuff
as converting HTML to XHTML pages DO break things. see,
http://www.alistapart.com/articles/betterliving/

I read on
http://msdn.microsoft.com/netframewo...etfxcompat.asp

It said they changed stuff like this

" Standards Compliance: The HTML rendering in ASP.NET was updated to be
XHTML 1.0 Transitional, which is standards compliant "

which is again another STUPID standard compliance mindnumb robot type of
thinking. Standard compliance is and will NEVER be important as getting it
to work on multiple browsers, period. What good is standards if the app
doesn''t even work? How about a new standard? It''s called getting it to work
instead of listening to some stupid committee who sits around all day in
conference talking to each other but know nothing of the real world in
getting things to actually work.

推荐答案

您好，


如果我没记错的话，这是

ASP.NET 2.0最受欢迎的功能之一。标准也是让它适用于所有浏览器的方式，因为大多数浏览器都支持XHTML，当然更多和

更多的浏览器会在开始时这样做成为它的需求。主要

网络技术非常接近仅仅是因为这个原因。

另一方面，ASP.NET 2.0中的渲染也可以很好地配置

所以我想你可以使用几乎任何你喜欢的浏览器。你是否因为某种原因而某些特定情况因ASP.NET 2.0而失败？

另一个？也许我们可以提供帮助？


-

Teemu Keiski

ASP.NET MVP，AspInsider

芬兰，欧盟

Hello,

If I recall correctly this has been one of the most requested features to
ASP.NET 2.0. Standards are also the way to get it work with all browsers as
the majority browsers all somewhat support XHTML, and of course more and
more browsers will do that when there begins to be the demand for it. Major
web technique is quite close being a reason for that alone.

On the other hand, rendering in ASP.NET 2.0 is also pretty well configurable
so I suppose you can get it to work with almost any browser you like. Do you
have some specific scenario that fails with ASP.NET 2.0 for a reason or
another? Maybe we can help?

--
Teemu Keiski
ASP.NET MVP, AspInsider
Finland, EU

你如何停止抱怨并接受标准和改变...数千人

的人们要求它和MS给了他们......你应该很高兴MS

正在创造标准的兼容性。你仍然可以选择使用

HTML标准，如果你想通过改变渲染文档类型...没有人

强迫你使用XHTML 1.0


" rhat" <无*** @ hotmail.com>在消息中写道

新闻：％2 **************** @ TK2MSFTNGP10.phx.gbl ...

how about you stop complaining and accept standards and change... Thousands
of people asked for it and MS gave it to them... you should be happy that MS
is creating something standard complient. You still have the option to use
HTML standard if you want to by changing the rendering doc type... no one is
forceing you to use XHTML 1.0

"rhat" <no***@hotmail.com> wrote in message
news:%2****************@TK2MSFTNGP10.phx.gbl...

我听说beta 2现在使ASP.NET xhtml兼容。

任何人都可以了解这将改变什么，它将打破
将HTML转换为XHTML页面的内容的东西。请参阅，
http://www.alistapart.com/articles/betterliving /

我读了
http://msdn.microsoft.com/netframewo...etfxcompat.asp

它说他们改变了这样的东西

标准合规性：ASP.NET中的HTML呈现更新为XHTML 1.0 Transitional，符合标准的

这又是另一个STUPID标准合规性思维机器人类型思考。标准合规性是并且永远不会是重要的，因为它可以在多个浏览器上工作。如果应用程序甚至不工作，标准有什么用呢？新标准怎么样？它被称为让它工作
而不是听一些愚蠢的委员会，他们整天坐在会议中相互交谈但却对现实世界一无所知。 >让事情真正发挥作用。

I heard that beta 2 now makes ASP.NET xhtml compliant.

Can anyone shed some light on what this will change and it will break
stuff
as converting HTML to XHTML pages DO break things. see,
http://www.alistapart.com/articles/betterliving/

I read on
http://msdn.microsoft.com/netframewo...etfxcompat.asp

It said they changed stuff like this

" Standards Compliance: The HTML rendering in ASP.NET was updated to be
XHTML 1.0 Transitional, which is standards compliant "

which is again another STUPID standard compliance mindnumb robot type of
thinking. Standard compliance is and will NEVER be important as getting
it
to work on multiple browsers, period. What good is standards if the app
doesn''t even work? How about a new standard? It''s called getting it to
work
instead of listening to some stupid committee who sits around all day in
conference talking to each other but know nothing of the real world in
getting things to actually work.

这个beta 2白皮书说他们默认使用XHTML，我想想


这些所谓的人，有实际测试那里的应用程序，看他们是否b $ b不要打破而不是让我们符合标准只是为了符合
符合b b标准的标准。


这就是那种认识某些知识分子的黑棒机器人的类型来自

触摸现实。


现实是＃1让'确保它适用于所有浏览器而不是

让'标准'符合标准'只是为了满足一些委员会的要求并且这样说

我们打了贴纸，如果它实际上没有任何意义在这个浏览器上没有工作和打破

应用程序。


在你张开嘴之前和那些微软的机器人之前，

LET跳转到XHTML之前的实际测试......大部分是你所谓的标准

拥护者甚至没有开始的WEB应用程序......所以请保持安静如果你没有b
$ b生产中的东西。

" Brian Henry" <无**** @ newsgroups.com>在消息中写道

新闻：eL ************** @ TK2MSFTNGP15.phx.gbl ...

This beta 2 white paper says they are going to XHTML as a default, I think

These so-called people, have the ACTUALLY TESTED there apps to see if they
DON''T break as opposed to "Let''s be standards compliant just for the sake of
standards compliant".

That''s the type of nim rod robot thinking of some intellectual who''s out of
touch of reality.

The reality is #1 let''s make sure it works across all browsers as opposed to
let''s make be standard''s compliant just to satisfy some committee and say so
we slap a sticker that means nothing if it ACTUALLY doesn''t work and breaks
an app on this browser.

Before you open your mouth and for Microsoft bunch of robots out there,
LET"S ACTUALLY TEST before jumpt to XHTML....MOST OF YOU so-called standard
advocates DO NOT even HAVE a WEB APP to begin with...so be quiet if you
don''t something in production.
"Brian Henry" <no****@newsgroups.com> wrote in message
news:eL**************@TK2MSFTNGP15.phx.gbl...

你怎么停止抱怨接受标准和改变...
成千上万的人要求它，MS给了他们......你应该感到高兴的是，
MS正在创造标准的兼容性。如果你想改变渲染文档类型，你仍然可以选择使用
HTML标准......没有人
强迫你使用XHTML 1.0

rhat ; <无*** @ hotmail.com>在消息中写道
新闻：％2 **************** @ TK2MSFTNGP10.phx.gbl ...

how about you stop complaining and accept standards and change... Thousands of people asked for it and MS gave it to them... you should be happy that MS is creating something standard complient. You still have the option to use
HTML standard if you want to by changing the rendering doc type... no one is forceing you to use XHTML 1.0

"rhat" <no***@hotmail.com> wrote in message
news:%2****************@TK2MSFTNGP10.phx.gbl...

我现在听说测试版2使ASP.NET xhtml兼容。

任何人都可以了解这将会发生什么变化，它会破坏
将HTML转换为XHTML页面会破坏事物。请参阅，
http://www.alistapart.com/articles/betterliving /

我读了
http://msdn.microsoft.com/netframewo...etfxcompat.asp
它说他们改变了像这个

"标准合规性：ASP.NET中的HTML呈现更新为XHTML 1.0 Transitional，符合标准的

这又是另一个STUPID标准合规性思维机器人类型思考。标准合规性是并且永远不会是重要的，因为它可以在多个浏览器上工作。如果应用程序甚至不工作，标准有什么用呢？新标准怎么样？它被称为让它工作
而不是听一些愚蠢的委员会，他们整天坐在会议中相互交谈但却对现实世界一无所知。 >让事情真正发挥作用。

I heard that beta 2 now makes ASP.NET xhtml compliant.

Can anyone shed some light on what this will change and it will break
stuff
as converting HTML to XHTML pages DO break things. see,
http://www.alistapart.com/articles/betterliving/

I read on
http://msdn.microsoft.com/netframewo...etfxcompat.asp
It said they changed stuff like this

" Standards Compliance: The HTML rendering in ASP.NET was updated to be
XHTML 1.0 Transitional, which is standards compliant "

which is again another STUPID standard compliance mindnumb robot type of
thinking. Standard compliance is and will NEVER be important as getting
it
to work on multiple browsers, period. What good is standards if the app
doesn''t even work? How about a new standard? It''s called getting it to
work
instead of listening to some stupid committee who sits around all day in
conference talking to each other but know nothing of the real world in
getting things to actually work.

这篇关于beta2 XHTML合规性？这是必要的。或愚蠢...读取MICROSOFT的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！