Web标准符合开源？ [英] Web Standards Meets Open Source?

问题描述

我几年来一直在创作网站，最近

重视网络标准（由Zeldman和其他许多网站吹捧

（利用浏览器越野车的技巧）和特殊规则要记住
才能确保任何一个页面都会在许多流行的浏览器中正确显示

。


这导致我...


由于许多程序员编写自己的浏览器（IE，Firefox，

Mozilla，Opera，Safari等）最终必须实现相同的

W3C规格，为什么要'他们共同开发一个引擎/ DOM

用于呈现网页内容并分享它？


浏览器可以简单地通过

它们提供的功能/接口。这个共同的努力不会导致

使网络成为每个人更好的地方 - 用户和

设计师？


我错过了什么吗？


此致，

Mario T. Lanza

Clarity Information Architecture，Inc。

2004.09

I have been authoring web sites for several years now and recently
come to value web standards (as touted by Zeldman and many other web
gurus). I have noticed with frustration that there are so many hacks
(tricks to take advantage of browser buggy-ness) and special rules to
be remembered in order to make sure that any one page displays
properly in the many popular browsers.

This leads me to...

Since the many programmers authoring their own browsers (IE, Firefox,
Mozilla, Opera, Safari, etc.) ultimately have to implement the same
W3C specs, why don''t they all work together to develop one engine/DOM
for rendering web content and share it?

The browsers, could simply be differentiated by the
features/interfaces they offer. Wouldn''t this shared effort result in
making the web a better place for every one -- both the users and
designers?

Am I missing something?

Sincerely,
Mario T. Lanza
Clarity Information Architecture, Inc.
2004.09

推荐答案

Mario T. Lanza写道：

Mario T. Lanza wrote:

由于很多编写自己的浏览器（IE，Firefox，Mozilla，Opera，Safari等）的程序员最终必须实现相同的W3C规范，为什么他们不能共同开发一个引擎/ DOM
用于渲染网页内容并分享它？

Since the many programmers authoring their own browsers (IE, Firefox,
Mozilla, Opera, Safari, etc.) ultimately have to implement the same
W3C specs, why don''t they all work together to develop one engine/DOM
for rendering web content and share it?

Firefox，Netscape，Mozilla，Galeon，Epiphany，K-Meleon，IBM Web浏览器
OS / 2的
，Beonex，Camino，DocZilla，Skipstone和Thunderbird（电子邮件


Safari和Konq ueror共享另一个名为KHTML的渲染引擎。


和Nautilus，Encompass和Evolution（电子邮件）共享另一个HTML

渲染引擎GtkHTML。 />

-

Toby A Inkster BSc（荣誉）ARCS

联系我〜 http://tobyinkster.co.uk/contact

Firefox, Netscape, Mozilla, Galeon, Epiphany, K-Meleon, IBM Web Browser
for OS/2, Beonex, Camino, DocZilla, Skipstone and Thunderbird (e-mail
client) all share the same open source HTML rendering engine called Gecko.

Safari and Konqueror share another one rendering engine called KHTML.

And Nautilus, Encompass and Evolution (e-mail) share another HTML
rendering engine, GtkHTML.

--
Toby A Inkster BSc (Hons) ARCS
Contact Me ~ http://tobyinkster.co.uk/contact

Mario T. Lanza写道：

Mario T. Lanza wrote:

由于许多程序员创作自己的浏览器（IE，Firefox，
Mozilla，Opera，Safari等）最终都要实现相同的
W3C规格，


但是有很多不在规格中。

为什么他们都不工作一起开发一个引擎/ DOM来呈现网页内容并分享它？

Since the many programmers authoring their own browsers (IE, Firefox,
Mozilla, Opera, Safari, etc.) ultimately have to implement the same
W3C specs,
But there''s so much that is not in the spec.
why don''t they all work together to develop one engine/DOM for
rendering web content and share it?

这就是Mozilla的意思，不是吗？ ？一群人，很多b
志愿者，分享他们的工作。由于这样的项目没有明显的收入来源

，我相信你可以看到为什么MS，Opera和其他人都不是那么热衷于这个想法。


-

Brian（删除无效给我发电子邮件）
http://www.tsmchughs.com/

Mario T. Lanza写道：

Mario T. Lanza wrote:

由于许多编写自己的浏览器（IE，Firefox，
Mozilla，Opera，Safari等）的程序员最终都必须实现相同的W3C规范，为什么要'他们共同开发一个引擎/ DOM来渲染网页内容并分享它吗？

Since the many programmers authoring their own browsers (IE, Firefox,
Mozilla, Opera, Safari, etc.) ultimately have to implement the same
W3C specs, why don''t they all work together to develop one engine/DOM
for rendering web content and share it?

所有今天的渲染引擎 - Gecko，KHTML，Presto，MSIE，Tasman，

等 - 是为了当时完全理智的原因而创建的。

你是对的，它会现在合并它们可能有意义，但

那个将意味着放弃了许多人们努力工作的代码，而不是提及为使其全部正常工作所需的努力。并且

甚至假设它可以让所有的浏览器项目一起工作，这看起来有点牵强。


然而，一些合并确实发生了：Safari使用KHTML，一个由KDE项目创建的开源

渲染引擎; Mozilla和Firefox共享

Gecko渲染引擎;和WYSIWYG编辑一样，GoLive和

Dreamweaver许可Opera'的Presto渲染引擎，用于预览网页
页面。甚至IE的专有渲染引擎也可以嵌入带有ActiveX的其他

浏览器而无需付费。

All of today''s rendering engines -- Gecko, KHTML, Presto, MSIE, Tasman,
etc. -- were created for what were perfectly sane reasons at the time.
You''re right that it would probably make sense to merge them now, but
that would mean abandoning lots of code people have worked hard on, not
to mention the effort it would take to get it all working right. And
that''s even assuming it''s possible to get all of the browser projects to
work together, which seems a little far-fetched.

However, some merging does happen: Safari uses KHTML, an open-source
rendering engine created by the KDE project; Mozilla and Firefox share
the Gecko rendering engine; and WYSIWYG editors like GoLive and
Dreamweaver license Opera''s Presto rendering engine for previewing web
pages. Even IE''s proprietary rendering engine can be embedded in other
browsers with ActiveX without paying.

这篇关于Web标准符合开源？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！