http://alistapart.com/blog/post/opera-moves-to-webkit 选择性的简译一些我觉得使用者会关心的问题，原文如上，有兴趣请自行阅读 ____________________________________________________________________________ We announced that Opera will switch its rendering engine to WebKit and JavaScript engine to V8 by building on top of Chromium (the open-source browser that powers Google Chrome). 透过在 Chromium（Google Chrome 的源头开放原始码专案）上的制作将成像引擎与 JavaScript 引擎转向使用 Webkit 及 V8。 Opera 向 Webkit 提供了一个微小但具有象徵意义的贡献给 Webkit——目前 Presto 引 擎已实作的 CSS multicolumn。 \___________________________________________________________________________ Opera for desktops, Opera Mobile, and Opera Mini are all moving over to [Chromium] WebKit? 桌面版 Opera、Opera Mobile、Opera Mini 全部都会转向 [Chromium] Webkit 吗？ ￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣＼／￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣ Eventually, yes. 是的，总有一天会。 \___________________________________________________________________________ The developer community seems pretty divided on this. Some say we’re moving towards an IE6-style “monoculture,” and some seem to think there’s enough diversity in WebKit implementations themselves that it’s a non-issue. What do you think? 开发社群的意见看起来很两极。有些说我们正走向 IE6 式的独占文化，然而另一些人却 认为在 Webkit 的实作上本身有足够的多样性（t7：应该意指多个组织来贡献与主导）， 所以这并非是个问题。你怎麽看？ ￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣＼／￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣ I was initially worried, but it seems to me that WebKit has excellent diversity. And, of course, there is no monolithic WebKit. 一开始我也担心过，但我觉得 Webkit 在多样性方面非常棒。而且 Webkit 不存在所谓的 的独占。 \___________________________________________________________________________ What impact will this have on web standards? Will this mean Opera has some say in Chromium’s roadmap, or are they more or less beholden to Apple/Google ’s decisions now? 这对网路的标准有甚麽影响呢？可以说 Opera 在 Chromium 的开发路线上或者说他们更 多或更少的依赖 Apple / Gooogle 的决定？ ￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣＼／￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣ We have independence to add (or remove) anything we like from WebKit or Chromium via our fork, but we aim to promote interoperability, not harm it. We have eighteen years of experience making browsers, and have participated in making many standards that are integral to the modern web (Media Queries, HTML5, native video, etc.) so we have lots of ideas to contribute. 我们有权力决定在我们的分支（t7：发行版）上对 Webkit 或 Chromium 做任何的异动 ，但我们的目的是推广相互作业能力，而非破坏他。我们具有 18 年的开发浏览器经验 ，而且参与制定过整合到现代网路的多项标准（Media Queries、HTML5、native video 等），因此我们有很多点子可以贡献。 \___________________________________________________________________________ Can we expect radical changes to Opera products within the next version or two, or will it be a more gradual process? I can’t imagine a brand new rendering engine will just drop in clean. 我们可以期待下一个或两个版本的 Opera 产品会带来崭新的变化吗？还是你们打算循序 渐进？ ￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣＼／￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣ A new version for Android is being demoed at Mobile World Congress in Barcelona at the end of the month (come and say hello—I’m the guy with the pink mohawk, stuffed into a cheap suit and uncomfortable shoes). After that I can’t really speak to timescales as I simply don’t know yet. Android 上的新版本将会在二月底的 MWC 上展示。其余的我真的不知道。 \___________________________________________________________________________ Will this free up Opera devs to work on new features, now that their primary concern isn’t just maintaining platform parity? 这是否会让 Opera 开发团队有更多时间去开发新的功能，目前他们最关心的就是是否只 是仅仅维护平台一致性？ ￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣＼／￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣ I can’t comment on individual features of future products. But you can be sure that I’ll be fighting to get accessibility improvements in there, just as I’ve fought to get them added to specifications. 我无法针对未来产品中的某个单一功能做出评论。但你可以放心的是我着力於改善存取 能力，就像我面对规格的态度一样。 \___________________________________________________________________________ --

※ 发信站: 批踢踢实业坊(ptt.cc) ◆ From: 140.113.73.123 ※ 编辑: t7yang 来自: 140.113.73.123 (02/16 00:40)