I can never decide what browser to use. And that's mostly because they all use different rendering engines, each with their own pros and cons. WebKitis blazing fast, but often renders pages incorrectly. Gecko (Firefox's engine) renders everything except ActiveX, but is fairly slow. That's where Kazehakase comes in. Unlike most browsers (which only have one engine), Kazenhakase has support for both Gecko and WebKit, with more engines like GkHTML, Dillo, and w3m to come. It also includes a very powerful GTK interface, complete with different levels of complexity (Beginner, Medium, and Expert), bookmarks, and much more.
To install Kazenhakase, use the *kazenhakase* package in the *universe*repository. In Intrepid, you'll also have to choose between *kazenhakase-webkit* and * kazenhakase-gecko*, since the Hardy version supports only Gecko.
On Sat, 2008-07-19 at 18:15 +0800, Derek Wu wrote: > 大家好，我是Derek，我正在翻译15期的Top5这篇文章，但是有一个 > 词"intrepid"不知翻译成什么才合适点，请大家给给意见。谢谢！ > 原文如下： > Kazehakase > Homepage: http://kazehakase.sourceforge.jp/
> I can never decide what browser to use. And that's mostly because they > all use different rendering engines, each with their own pros and > cons. WebKit is blazing fast, but often renders pages incorrectly. > Gecko (Firefox's engine) renders everything except ActiveX, but is > fairly slow. That's where Kazehakase comes in. Unlike most browsers > (which only have one engine), Kazenhakase has support for both Gecko > and WebKit, with more engines like GkHTML, Dillo, and w3m to come. It > also includes a very powerful GTK interface, complete with different > levels of complexity (Beginner, Medium, and Expert), bookmarks, and > much more.
> To install Kazenhakase, use the kazenhakase package in the universe > repository. In Intrepid, you'll also have to choose between > kazenhakase-webkit and kazenhakase-gecko, since the Hardy version > supports only Gecko.
> > I can never decide what browser to use. And that's mostly because they > > all use different rendering engines, each with their own pros and > > cons. WebKit is blazing fast, but often renders pages incorrectly. > > Gecko (Firefox's engine) renders everything except ActiveX, but is > > fairly slow. That's where Kazehakase comes in. Unlike most browsers > > (which only have one engine), Kazenhakase has support for both Gecko > > and WebKit, with more engines like GkHTML, Dillo, and w3m to come. It > > also includes a very powerful GTK interface, complete with different > > levels of complexity (Beginner, Medium, and Expert), bookmarks, and > > much more.
> > To install Kazenhakase, use the kazenhakase package in the universe > > repository. In Intrepid, you'll also have to choose between > > kazenhakase-webkit and kazenhakase-gecko, since the Hardy version > > supports only Gecko.
I can never decide what browser to use. And that's mostly because they all use different rendering engines, each with their own pros and cons. WebKit is blazing fast, but often renders pages incorrectly. Gecko (Firefox's engine) renders everything except ActiveX, but is fairly slow. That's where Kazehakase comes in. Unlike most browsers (which only have one engine), Kazenhakase has support for both Gecko and WebKit, with more engines like GkHTML, Dillo, and w3m to come. It also includes a very powerful GTK interface, complete with different levels of complexity (Beginner, Medium, and Expert), bookmarks, and much more.
To install Kazenhakase, use the kazenhakase package in the universe repository. In Intrepid, you'll also have to choose between kazenhakase-webkit and kazenhakase-gecko, since the Hardy version supports only Gecko.
