www-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

www/server fsf-html-style-sheet.html


From: Therese Godefroy
Subject: www/server fsf-html-style-sheet.html
Date: Wed, 9 Aug 2017 09:42:25 -0400 (EDT)

CVSROOT:        /webcvs/www
Module name:    www
Changes by:     Therese Godefroy <th_g> 17/08/09 09:42:25

Modified files:
        server         : fsf-html-style-sheet.html 

Log message:
        Update to fit current practices; s/HTML/XHTML/ at line 258.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/server/fsf-html-style-sheet.html?cvsroot=www&r1=1.72&r2=1.73

Patches:
Index: fsf-html-style-sheet.html
===================================================================
RCS file: /webcvs/www/www/server/fsf-html-style-sheet.html,v
retrieving revision 1.72
retrieving revision 1.73
diff -u -b -r1.72 -r1.73
--- fsf-html-style-sheet.html   27 Jun 2017 06:48:10 -0000      1.72
+++ fsf-html-style-sheet.html   9 Aug 2017 13:42:24 -0000       1.73
@@ -5,8 +5,7 @@
 <!--#include virtual="/server/banner.html" -->
 <h2>The GNU/FSF Web Site Guidelines</h2>
 
-<p>These are style guidelines for writing WWW web pages in HTML for
-the GNU web server.</p>
+<p>These are style guidelines for writing web pages for the GNU server.</p>
 
 <p>The standards documented here are the default for the GNU
 project website. All pages should appear this way by
@@ -81,7 +80,7 @@
 those with slow Internet access or text-only browsers.</li>
 
 <li>Offer a document in as many formats as the GNU Project has it.
-For an example, see <a href="/copyleft/fdl.html">The GNU Free
+For an example, see <a href="/licenses/fdl.html">The GNU Free
 Documentation License</a>. This lets the user get the document in the
 format most useful to him.</li>
 
@@ -110,9 +109,9 @@
 W3C standards.</li>
 
 <li>A boilerplate for web pages, especially project web pages, is provided:
-<a href="/server/standards/boilerplate.html">view formatted</a>,
-<a 
href="http://web.cvs.savannah.gnu.org/viewvc/*checkout*/www/server/standards/boilerplate.html?root=www&amp;content-type=text%2Fplain";>view
 source</a> (with
-server-side includes intact).</li>
+<a 
href="http://web.cvs.savannah.gnu.org/viewvc/*checkout*/www/server/standards/boilerplate.html?root=www&amp;content-type=text%2Fplain";>
+view source</a> (with server-side includes intact). Pages using the
+boilerplate must be valid XHTML.</li>
 
 <li>Acronyms/abbreviations:
   <ul>
@@ -150,8 +149,8 @@
 <li>Please follow the above mentioned web standards strictly.  Don't
 neglect <a
 href="http://www.w3.org/TR/html401/struct/global.html#h-7.1";>required
-elements</a> such as &lt;HTML&gt; &lt;HEAD&gt; &lt;TITLE&gt;
-&lt;BODY&gt;, etc. when using (X)HTML, and always include the
+elements</a> such as &lt;html&gt; &lt;head&gt; &lt;title&gt;
+&lt;body&gt;, etc. when using (X)HTML, and always include the
 appropriate DTD or Schema reference. This appeases overly pedantic
 browsers.</li>
 
@@ -162,27 +161,27 @@
 always finds this contact information at the same place on each
 page.</li>
 
-<li>The first header tag, &lt;H[n]&gt;, should have its text
-duplicated at the start of the &lt;TITLE&gt; tag. The &lt;TITLE&gt; tag
+<li>The first header tag, &lt;h[n]&gt;, should have its text
+duplicated at the start of the &lt;title&gt; tag. The &lt;title&gt; tag
 is used by many browsers in menus like the history and bookmarks lists,
 as a link to that page. It helps the user to have them the same, so when
 he clicks on an item in a list, he gets a page with the same
-"TITLE". Please properly use your headers in numerical order: 1, 2,
+&ldquo;title&rdquo;. Please properly use your headers in numerical order: 1, 2,
 etc. These are not used for looks, but for the organization of the
 document.</li>
 
-<li>The &lt;TITLE&gt; tag should include the phrases "GNU Project"
-and "Free Software Foundation" so the pages will be found
-when WWW search engines are used. The default is to add this at the
+<li>The &lt;title&gt; tag should include the phrases &ldquo;GNU Project&rdquo;
+and &ldquo;Free Software Foundation&rdquo; so the pages will be found
+when web search engines are used. The default is to add this at the
 end: <code> - GNU Project - Free Software Foundation</code>.</li>
 
-<li>The &lt;HEAD&gt; pair should have this line after the
-&lt;TITLE&gt; pair:<br />
-&lt;LINK rev="made" href="mailto:address@hidden"&gt;<br />
+<li>The &lt;head&gt; pair should have this line after the
+&lt;title&gt; pair:<br />
+&lt;link rev="made" href="mailto:address@hidden"&gt;<br />
 Some browsers use this information to allow users to easily report
 problems they find on a page.</li>
-<li>On pages with dated entries (e.g., What's New, Thank GNUs, and
-GNU's Bulletins, the newer entries should be first (i.e., reverse
+<li>On pages with dated entries (e.g., Thank GNUs and
+GNU's Bulletins), the newer entries should be first (i.e., reverse
 chronological order).</li>
 
 <li>Cite people with e-mail addresses this way:
@@ -195,7 +194,7 @@
 <a href="http://www.stallman.org/";>Richard Stallman</a>
 <a href="mailto:address@hidden";>&lt;address@hidden&gt;</a><br />
 It is less confusing to the user, because it's clear what is a
-http: link to another WWW page and what is a mailto: anchor that
+http: link to another web page and what is a mailto: anchor that
 will bring up a mail form to fill out and send, if this is
 supported by the client. Also, if the user saves a copy of the
 page, he will have a copy of the e-mail address he can use, without
@@ -256,7 +255,7 @@
 marked for accessibility.</li>
 
 <li>SGML and XML are case sensitive. TITLE and title are not the
-same thing in HTML. (This means that text/html and
+same thing in XHTML. (This means that text/html and
 application/xhtml+xml are mutually exclusive, which also means that
 strictly speaking XHTML and HTML are mutually exclusive.)</li>
 
@@ -297,8 +296,8 @@
 file to handle this.</li>
 
 <li>Don't use just a directory name in a URL; always include the
-specific file name. E.g., use "/gnu/gnu-history.html" not just
-"/gnu/". Never use "index.html" in a URL. Both of these are kindnesses
+specific file name. E.g., use &ldquo;/gnu/gnu-history.html&rdquo; not just
+&ldquo;/gnu/&rdquo;. Never use &ldquo;index.html&rdquo; in a URL. Both of 
these are kindnesses
 to the users, as browsers change the highlighting on a link if a user
 has already seen it. If the link is known by several different file
 names, the user will not get a highlighted link on the file names the
@@ -322,7 +321,7 @@
 <ul>
 <li>The use of graphics should be minimized, so pages load fast
 over slow links, especially animations. The GNU Project is for
-everyone, even those with slow Internet access and/or text-only WWW
+everyone, even those with slow Internet access and/or text-only web
 browsers.</li>
 
 <li>In the past, GIFs have had patent problems. However, now that
@@ -371,7 +370,7 @@
 TEXT from adjacent text, and help the user realize that this is a
 stand-in for a graphic.</li>
 
-<li>Use width and height attributes for in-line images, but not in
+<li>Use width and height attributes for fixed-width in-line images, but not in
 ISO HTML:<br />
 &lt;img src="/graphics/*.jpg" alt=" [Image of DESCRIPTIVE TEXT] "
 width="999" height="666" /&gt;.<br />
@@ -384,7 +383,7 @@
 on our pages.</li>
 
 <li>Sometimes it can be useful to add some HTML tags, for example
-with &lt;SPAN&gt; and CSS, that gives a broader "white" area around
+with &lt;span&gt; and CSS, that gives a broader &ldquo;white&rdquo; area around
 a block of text. This can be used to draw more attention to one
 block in the text.</li>
 </ul>
@@ -400,7 +399,7 @@
 "http://www.anybrowser.org/campaign/";>Best Viewed with Any
 Browser</a> campaign.</li>
 
-<li>Basic info on the WWW and its technical specifications can be
+<li>Basic info on the web and its technical specifications can be
 found at <a href="http://www.w3.org/";>The World Wide Web
 Consortium</a>.</li>
 
@@ -473,7 +472,7 @@
 
 <p class="unprintable">Updated:
 <!-- timestamp start -->
-$Date: 2017/06/27 06:48:10 $
+$Date: 2017/08/09 13:42:24 $
 <!-- timestamp end --></p>
 </div>
 </div>



reply via email to

[Prev in Thread] Current Thread [Next in Thread]