From: Gerald Pfeifer <gerald@pfeifer.com>
To: gcc-patches@gcc.gnu.org
Subject: [committed] wwwdocs: style: Simplify handling of <head> containers
Date: Fri, 21 Oct 2022 09:14:31 +0200 (CEST) [thread overview]
Message-ID: <20221021071435.00F4633E4A@hamza.pair.com> (raw)
This is the change actually triggering most of my changes the last week.
With that most of our web pages - the main page is still WIP - should now
pass validator.w3.org again:
Lose the trailing slash in <link rel="shortcut icon"> which we needed to
validate (most pages) as XHTML.
With that we no longer need to differentiate between XHTML and HTML pages
as much and can simplify the logic quite a bit. (Now only pages setting a
MetaHTML variable ADDSTYLE receive special treatment.)
---
htdocs/style.mhtml | 10 +++-------
1 file changed, 3 insertions(+), 7 deletions(-)
diff --git a/htdocs/style.mhtml b/htdocs/style.mhtml
index 08def35e..98641c25 100644
--- a/htdocs/style.mhtml
+++ b/htdocs/style.mhtml
@@ -1,13 +1,12 @@
;;; Set a couple of site-wide defaults, some of which we'll override in the
;;; following.
-<set-var NOSTYLE>
<set-var BACKPATH>
;;; The pages under install/ are generated from texinfo sources.
<if <match <get-var env::PREPROCESS_FILE> "install/.*">
- <unset-var NOSTYLE>
+ <set-var ADDSTYLE>
>
;;; Redefine the <head> tag so that we can add default <meta /> headers.
@@ -16,16 +15,13 @@
<verbatim>
<head>
</verbatim>
- <if <var-exists NOSTYLE>
- <group
- <link rel="shortcut icon" href="https://gcc.gnu.org/favicon.ico" />
- >
+ <if <var-exists ADDSTYLE>
<group
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
- <link rel="shortcut icon" href="https://gcc.gnu.org/favicon.ico">
<link rel="stylesheet" type="text/css" href="/gcc.css">
>
>
+ <link rel="shortcut icon" href="https://gcc.gnu.org/favicon.ico">
%body
<verbatim>
</head>
--
2.38.0
reply other threads:[~2022-10-21 7:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20221021071435.00F4633E4A@hamza.pair.com \
--to=gerald@pfeifer.com \
--cc=gcc-patches@gcc.gnu.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).