From: "H. Peter Anvin" <hpa@zytor.com>
To: "J.H." <warthog19@eaglescrag.net>
Cc: Nicolas Pitre <nico@cam.org>, git@vger.kernel.org
Subject: Re: bug with gitweb on kernel.org
Date: Mon, 23 Apr 2007 17:18:52 -0700 [thread overview]
Message-ID: <462D4CEC.6010204@zytor.com> (raw)
In-Reply-To: <1177294925.24896.48.camel@localhost.localdomain>
J.H. wrote:
>
> Well the only difference in the pages being served is the mime type
> application/html vs. application/xhtml+xml. Does anyone know the
> original impetus to using application/xhtml+xml (despite the fact that
> it's technically the correct choice) vs. just using application/html for
> everything? I'm sure there was a good reason behind it and I'd rather
> know what that reason was before I got changing things
>
Presumably the motivation is so you know ahead of time that you can
invoke an XML parser rather than an SGML/HTML parser.
Note: http://www.w3.org/TR/xhtml-media-types/ states that text/html is
considered acceptable for HTML-compatible XHTML 1.0 but no other version
of XHTML 1.0. One of the main issues with making XHTML 1.0-compatible
is to make sure there is a space before the final / in the last
singleton: <foo /> rather than <foo/>
-hpa
next prev parent reply other threads:[~2007-04-24 0:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-20 3:02 bug with gitweb on kernel.org Nicolas Pitre
2007-04-23 0:09 ` J.H.
2007-04-23 1:16 ` Nicolas Pitre
2007-04-23 2:22 ` J.H.
2007-04-24 0:18 ` H. Peter Anvin [this message]
2007-04-24 0:44 ` H. Peter Anvin
2007-04-24 6:40 ` Johan Herland
2007-04-24 1:06 ` Jakub Narebski
2007-04-24 1:06 ` J.H.
2007-04-24 7:40 ` Johan Herland
[not found] ` <200704240933.58680.johherla@online.no>
2007-04-24 7:50 ` J.H.
2007-04-24 6:42 ` Johan Herland
2007-04-24 8:19 ` J.H.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=462D4CEC.6010204@zytor.com \
--to=hpa@zytor.com \
--cc=git@vger.kernel.org \
--cc=nico@cam.org \
--cc=warthog19@eaglescrag.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.