[Haskell-cafe] ANNOUNCE: Haddock version 2.8.0

Sat Sep 4 21:47:23 EDT 2010

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 9/4/10 21:27 , Jeremy Shaw wrote:
> Here is why I am dubious. Browsers that support html and xhtml have
> two different code paths for rending html vs xhtml. The *only* way to
> select which code path is taken is by specifying the mime-type when
> you serve it. Either application/xml or text/html.

XHTML starts with a <!DOCTYPE>.  You've just asserted that no browser is
capable of noticing that and responding to it even though it's right at the
start, while somehow managing to support <META HTTP-EQUIV=...> tags buried
in the <HEAD> that can force it to go back and start from scratch.  Really?
 Or have we all been imagining the latter for the past, oh, 15 or so years?
 (Mozilla had a serious bug relating to that restart for years; I assure you
it's not a fantasy.)

I wouldn't be surprised if HTML and XHTML ultimately follow different
rendering paths --- but your assertions are raising red flags and smell
suspiciously like ideology taking offense at reality not automatically
constraining itself to fit in its assigned pigeonhole.

- -- 
brandon s. allbery     [linux,solaris,freebsd,perl]      allbery at kf8nh.com
system administrator  [openafs,heimdal,too many hats]  allbery at ece.cmu.edu
electrical and computer engineering, carnegie mellon university      KF8NH
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.10 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkyC9qsACgkQIn7hlCsL25U8uACfdDA4RLUv5LedObrIaO4DpQE1
0CMAnj5ntJ6dhRju5sCw7IGfor68Aaa4
=TaCL
-----END PGP SIGNATURE-----