From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Jason Yundt <jason@jasonyundt.email>, git@vger.kernel.org
Cc: "brian m. carlson" <sandals@crustytoothpaste.net>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Subject: Re: [PATCH] gitweb: switch to a modern DOCTYPE
Date: Thu, 2 Jun 2022 14:26:43 +0700 [thread overview]
Message-ID: <530f7bb4-9f12-f681-0188-878054c4efbf@gmail.com> (raw)
In-Reply-To: <20220601012647.1439480-1-jason@jasonyundt.email>
On 6/1/22 08:26, Jason Yundt wrote:
> According to the HTML Standard FAQ:
>
> “What is the DOCTYPE for modern HTML documents?
>
> In text/html documents:
>
> <!DOCTYPE html>
>
> In documents delivered with an XML media type: no DOCTYPE is required
> and its use is generally unnecessary. However, you may use one if you
> want (see the following question). Note that the above is well-formed
> XML.”
>
> Source: [1]
>
> Gitweb uses an XHTML 1.0 DOCTYPE:
>
> <!DOCTYPE html PUBLIC
> "-//W3C//DTD XHTML 1.0 Strict//EN"
> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
>
> While that DOCTYPE is still valid [2], it has several disadvantages:
>
> 1. It’s misleading. The DTD that browsers are supposed to use with that
> DOCTYPE has nothing to do with XHTML 1.0 and isn’t available at the URL
> that is given [2].
> 2. It’s obsolete. XHTML 1.0 was last revised in 2002 and was superseded in
> 2018 [3].
> 3. It’s unreliable. Gitweb uses and ⋅ but lets an external file
> define them. “[…U]using entity references for characters in XML documents
> is unsafe if they are defined in an external file (except for <, >,
> &, ", and ').” [4]
>
> [1]: <https://github.com/whatwg/html/blob/main/FAQ.md#what-is-the-doctype-for-modern-html-documents>
> [2]: <https://html.spec.whatwg.org/multipage/xhtml.html#parsing-xhtml-documents>
> [3]: <https://www.w3.org/TR/xhtml1/#xhtml>
> [4]: <https://html.spec.whatwg.org/multipage/xhtml.html#writing-xhtml-documents>
>
> Signed-off-by: Jason Yundt <jason@jasonyundt.email>
So basically what this patch does is switch to HTML5, right? That is because
I can see DOCTYPE "upgrade" to use "<!DOCTYPE html>", which is the DOCTYPE
for HTML5. If it does, then mention HTML5 in v2.
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2022-06-02 7:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 1:26 [PATCH] gitweb: switch to a modern DOCTYPE Jason Yundt
2022-06-02 0:41 ` brian m. carlson
2022-06-02 6:10 ` Junio C Hamano
2022-06-02 7:26 ` Bagas Sanjaya [this message]
2022-06-02 11:43 ` [PATCH v2] gitweb: switch to an XHTML5 DOCTYPE Jason Yundt
2022-06-02 18:50 ` Junio C Hamano
2022-06-02 19:51 ` Jason Yundt
2022-06-02 21:47 ` brian m. carlson
2022-06-02 22:09 ` Junio C Hamano
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=530f7bb4-9f12-f681-0188-878054c4efbf@gmail.com \
--to=bagasdotme@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=jason@jasonyundt.email \
--cc=sandals@crustytoothpaste.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).