[wwwdocs] More replacing <a name=...> by id= attributes

Message ID alpine.LSU.2.21.1806021500590.5519@anthias.pfeifer.com
State New
Headers show
Series
  • [wwwdocs] More replacing <a name=...> by id= attributes
Related show

Commit Message

Gerald Pfeifer June 10, 2018, 1:34 p.m.
This continues what I started last weekend, a primary step to
move our pages to HTML 5.

Applied.

Gerald

Patch

Index: svnwrite.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/svnwrite.html,v
retrieving revision 1.38
diff -u -r1.38 svnwrite.html
--- svnwrite.html	6 Feb 2017 12:42:17 -0000	1.38
+++ svnwrite.html	2 Jun 2018 13:01:00 -0000
@@ -1,9 +1,5 @@ 
 <html>
 <head>
-<meta name="description"
-      content="Instructions for read-write access to the GCC SVN repository." />
-<meta name="keywords"
-      content="GCC, patches, checking in, SVN, SSH, access policy" />
 <title>Read-write SVN access</title>
 </head>
 
@@ -30,7 +26,7 @@ 
 </ol>
 
 <hr />
-<h2><a name="authenticated">Authenticated access</a></h2>
+<h2 id="authenticated">Authenticated access</h2>
 
 <p>We provide authenticated access via the SSH protocol.  This needs to
 be sponsored by an existing maintainer (someone with "write after approval"
@@ -59,7 +55,7 @@ 
 access policies below.</p>
 
 <hr />
-<h2><a name="setup">Setting up your local SVN tree</a></h2>
+<h2 id="setup">Setting up your local SVN tree</h2>
 
 <p>Once your account has been set up, check out the GCC sources by 
 issuing the command:</p>
@@ -90,7 +86,7 @@ 
 </code></p></blockquote>
 
 <hr />
-<h2><a name="policies">Write access policies</a></h2>
+<h2 id="policies">Write access policies</h2>
 
 <p>The GCC project grants developers various levels of write access to
 and review authority over the GCC master sources.  We have not put any
@@ -166,7 +162,7 @@ 
 
 
 <hr />
-<h2><a name="testing">Testing changes</a></h2>
+<h2 id="testing">Testing changes</h2>
 
 <p>All changes must be tested according to the 
 <a href="contribute.html#testing">instructions for testing patches</a>
@@ -195,7 +191,7 @@ 
 revocation of check-in privileges by the Steering Committee.</p>
 
 <hr />
-<h2><a name="checkin">Checking in a change</a></h2>
+<h2 id="checkin">Checking in a change</h2>
 
 <p>The following is meant to provide a very quick overview of how to
 check in a change.  It is not meant to be a replacement for the SVN
@@ -250,7 +246,7 @@ 
 </ol>
 
 <hr />
-<h2><a name="example">Example check-in session</a></h2>
+<h2 id="example">Example check-in session</h2>
 
 <p>Here's an actual check-in session for a patch John Carr recently
 sent to the GCC list.  This was the ChangeLog for his change:</p>
@@ -410,7 +406,7 @@ 
 like "Merge from mainline" or similar.</p>
 
 <hr />
-<h2><a name="account">Tips&amp;Tricks around your account</a></h2>
+<h2 id="account">Tips&amp;Tricks around your account</h2>
 
 <p>Your gcc.gnu.org account also receives e-mail (and is what you
 use for Bugzilla).  If you ever need to change the address e-mail to
Index: releases.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/releases.html,v
retrieving revision 1.132
diff -u -r1.132 releases.html
--- releases.html	2 May 2018 10:21:15 -0000	1.132
+++ releases.html	2 Jun 2018 13:01:00 -0000
@@ -8,7 +8,7 @@ 
 
 <h1>GCC Releases</h1>
 
-<h2><a name="download">Download</a></h2>
+<h2 id="download">Download</h2>
 
 <p>Source code for GCC releases may be downloaded from our
 <a href="mirrors.html">mirror sites</a>.</p>
@@ -24,7 +24,7 @@ 
 <a href="svn.html">using SVN</a>.</p>
 
 
-<h2><a name="timeline">GCC Timeline</a></h2>
+<h2 id="timeline">GCC Timeline</h2>
 
 <p>The table is sorted by date.  Note that starting with version 3.3.4,
 we provide bug releases for older release branches for those users
Index: search.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/search.html,v
retrieving revision 1.192
diff -u -r1.192 search.html
--- search.html	10 Dec 2017 11:12:42 -0000	1.192
+++ search.html	2 Jun 2018 13:01:02 -0000
@@ -2226,11 +2226,11 @@ 
 </form>
 <hr />
 
-<a name="syntax"></a>
-
+<p id="syntax">
 In a <em>boolean expression</em>, the words searched for, or parts inside
 parentheses <b>()</b> are separated by the operator-words <b>and</b>,
 <b>or</b> and <b>not</b>.  Examples of correct expressions are:
+</p>
 
 <ul>
 <li><b>cat and dog</b></li>
Index: lists.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/lists.html,v
retrieving revision 1.113
diff -u -r1.113 lists.html
--- lists.html	10 Mar 2018 16:32:33 -0000	1.113
+++ lists.html	2 Jun 2018 13:01:02 -0000
@@ -147,7 +147,7 @@ 
 
 <p>To post a message, just send mail to <i>listname</i><code>@gcc.gnu.org</code>.</p>
 
-<h2><a name="policies">Policies</a></h2>
+<h2 id="policies">Policies</h2>
 
 <p>Our lists have a maximum message size of 100KB, only the gcc-prs list
 allows for a larger maximum message size of 2MB.  If your message exceeds
@@ -312,9 +312,8 @@ 
 
 <hr />
 
-<p>This search will allow you to search the contents gcc.gnu.org.</p>
+<p id="searchbox">Search the contents gcc.gnu.org:</p>
 
-<a name="searchbox"></a>
 <include searchbox.ihtml>
 
 </body>
Index: develop.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/develop.html,v
retrieving revision 1.182
diff -u -r1.182 develop.html
--- develop.html	20 May 2018 20:23:05 -0000	1.182
+++ develop.html	2 Jun 2018 13:01:02 -0000
@@ -99,7 +99,7 @@ 
 
 <p>Development on our main branch will proceed in three stages.</p>
 
-<h4><a name="stage1">Stage 1</a></h4>
+<h4 id="stage1">Stage 1</h4>
 
 <p>During this period, changes of any nature may be made to the
 compiler.  In particular, major changes may be merged from branches.
@@ -115,19 +115,19 @@ 
 to attempt to order the inclusion of major features in an organized
 manner.</p>
 
-<h4><a name="stage2">Stage 2</a></h4>
+<h4 id="stage2">Stage 2</h4>
 
 <p>Stage 2 has been abandoned in favor of an extended feature driven
 Stage 1 since the development of GCC 4.4.</p>
 
-<h4><a name="stage3">Stage 3</a></h4>
+<h4 id="stage3">Stage 3</h4>
 
 <p>During this two-month period, the only (non-documentation) changes
 that may be made are changes that fix bugs or new ports which do not
 require changes to other parts of the compiler.
 New functionality may not be introduced during this period.</p>
 
-<h4><a name="stage4">Stage 4</a></h4>
+<h4 id="stage4">Stage 4</h4>
 
 <p>During this period, the only (non-documentation) changes that may
 be made are changes that fix regressions.  Other changes may not be
@@ -252,7 +252,7 @@ 
 without having to adjust their source code.  Avoiding changes that
 reject code that was previously accepted makes this possible.</p>
 
-<h3><a name="num_scheme">Version Numbering Scheme for GCC 5 and Up</a></h3>
+<h3 id="num_scheme">Version Numbering Scheme for GCC 5 and Up</h3>
 
 <p>Starting with GCC 5 we will bump the major version number for
 each release.  The version number and DEV-PHASE will develop in the following
@@ -289,7 +289,7 @@ 
 number carried little to no useful information.</p>
 
 
-<h3><a name="timeline">Release Timeline</a></h3>
+<h3 id="timeline">Release Timeline</h3>
 
 <p>Here is a history of recent and a <em>tentative</em> timeline of upcoming
 stages of development, branch points, and releases:</p>
Index: contribute.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/contribute.html,v
retrieving revision 1.87
diff -u -r1.87 contribute.html
--- contribute.html	9 Apr 2015 21:49:31 -0000	1.87
+++ contribute.html	2 Jun 2018 13:01:02 -0000
@@ -29,7 +29,7 @@ 
 
 <hr />
 
-<h2><a name="legal">Legal Prerequisites</a></h2>
+<h2 id="legal">Legal Prerequisites</h2>
 
 <p>Before we can incorporate significant contributions, certain
 legal requirements must be met.</p>
@@ -57,7 +57,7 @@ 
 copyright assignment on file.</p>
 
 
-<h2><a name="standards">Coding Standards</a></h2>
+<h2 id="standards">Coding Standards</h2>
 
 <p>All contributions must conform to the <a
 href="http://www.gnu.org/prep/standards_toc.html">GNU Coding
@@ -73,7 +73,7 @@ 
 contrib/check_GNU_style.sh</a>.</p>
 
 <!-- also referenced from svnwrite.html -->
-<h2><a name="testing">Testing Patches</a></h2>
+<h2 id="testing">Testing Patches</h2>
 
 <p>All patches must be thoroughly tested.  We encourage you to test
 changes with as many host and target combinations as is practical.  In
@@ -130,7 +130,7 @@ 
 to it.  Include all your new testcases in your testsuite run.</p>
 
 
-<h2><a name="docchanges">Documentation Changes</a></h2>
+<h2 id="docchanges">Documentation Changes</h2>
 
 <p>Documentation changes do not require a new bootstrap (a working
 bootstrap is necessary to get the build environment correct), but you
@@ -141,7 +141,7 @@ 
 eliminate them all.</p>
 
 
-<h2><a name="webchanges">Web Site Changes</a></h2>
+<h2 id="webchanges">Web Site Changes</h2>
 
 <p>Changes to the web site must
 <a href="http://validator.w3.org/">validate</a> as XHTML 1.0
@@ -164,7 +164,7 @@ 
 <p>More <a href="about.html#cvs">about our web pages</a>.</p>
 
 
-<h2><a name="patches">Submitting Patches</a></h2>
+<h2 id="patches">Submitting Patches</h2>
 
 <p>Every patch must have several pieces of information, <em>before</em> we
 can properly evaluate it:</p>
@@ -284,7 +284,7 @@ 
 to point out lack of write access in your initial submission, too.</p>
  
 
-<h2><a name="announce">Announcing Changes (to our Users)</a></h2>
+<h2 id="announce">Announcing Changes (to our Users)</h2>
 
 <p>Everything that requires a user to edit his Makefiles or his source code
 is a good candidate for being mentioned in the release notes.</p>