--PNTmBPCT7hxwcZjr
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Well... the idea behind xhtml is to have a structured page, so
it is easier for browsers to parse it, and there is nothing that
it can make other browsers to understand it... and about css, if
a thing is not implemented, then it is not drawn! Well... then,
there is xhtml transitional, which is simply a strict html, so
it allows font's and the like...


On Mon, May 13, 2002 at 08:47:26PM +0200, Martin Weber wrote:
> On Mon, May 13, 2002 at 08:36:07PM +0200, Julio Merino wrote:
> > [use css & xhtml ?]
>=20
> Well, none of our supported browsers supports those fully :)
>=20
> I dislike writing documentation which has to be viewed by
> microsoft products :> And yes, there might be browsers supporting
> this stuff, but if you use a combination of dillo, links and
> (sometimes) netscape (4.7) because you have the "typical"
> netbsd machine (i.e. not more horsepower than the combined
> formula one cars) and don't want to wait half a minute for
> even plainest pages to appear and render, then you shouldn't
> be locked out from our documentation either!
>=20
> You might call "legacy, legacy" now, "get rid of the old junk",
> but hey, after all we don't need many of the new features of
> css etc. We need a structured hypertext collection of documentation,
> and for the style, we use the .list files which work very fine
> in ensuring a central style :)
>=20
> I am strictly against using those newer features unless they are
> supported by my "legacy" applications (and face it, there's only
> shit as browsers under unix, pervert enough), because I really
> dislike to lock myself out of my work.
>=20
> But well, I'm just one, and not even a commiter (though working
> on translation/documentation), and this is just mnsho :)
>=20
> -Martin

--=20
Of course it runs NetBSD - http://www.netbsd.org
HispaBSD member - http://www.hispabsd.org
Julio Merino <jmmv@hispabsd.org>

--PNTmBPCT7hxwcZjr
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (NetBSD)
Comment: For info see http://www.gnupg.org

iD8DBQE84A4uzz00ZOPKycwRAh09AKCc4x4uTrIAulbXyMao0L43aIjJnACeN7KF
QtwbqMm5ALtSWKiLRZOCgWQ=
=/2o4
-----END PGP SIGNATURE-----

--PNTmBPCT7hxwcZjr--