www-commits
[Top][All Lists]
Advanced

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

www/server/staging/standards gnu-website-guidel...


From: Therese Godefroy
Subject: www/server/staging/standards gnu-website-guidel...
Date: Wed, 17 Feb 2021 12:23:05 -0500 (EST)

CVSROOT:        /webcvs/www
Module name:    www
Changes by:     Therese Godefroy <th_g> 21/02/17 12:23:05

Modified files:
        server/staging/standards: gnu-website-guidelines.html 

Log message:
        Validation fixes; //stallman.org -> https://stallman.org;
        remove link to RFC6068 (unreadable for most people); expand 'YUI';
        em width for Any Browser icon; question about cryptic abbrev.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/server/staging/standards/gnu-website-guidelines.html?cvsroot=www&r1=1.12&r2=1.13

Patches:
Index: gnu-website-guidelines.html
===================================================================
RCS file: /webcvs/www/www/server/staging/standards/gnu-website-guidelines.html,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -b -r1.12 -r1.13
--- gnu-website-guidelines.html 17 Feb 2021 12:19:06 -0000      1.12
+++ gnu-website-guidelines.html 17 Feb 2021 17:23:04 -0000      1.13
@@ -1,6 +1,9 @@
 <!--#include virtual="/server/header.html" -->
 <!-- Parent-Version: 1.95 -->
 <title>Website Guidelines - GNU Project - Free Software Foundation</title>
+<style type="text/css"><!--
+  .summary li { list-style: none; }
+--></style>
  <!--#include virtual="/server/standards/po/gnu-website-guidelines.translist" 
-->
 <!--#include virtual="/server/banner.html" -->
 <h2>GNU Website Guidelines</h2>
@@ -10,7 +13,6 @@
   Keeping the site design simple helps accomplish that.
 </p>
 
-<style>.summary li {list-style: none;}</style>
 <div class="summary">
 <h3>Table of Contents</h3>
 <ul>
@@ -200,7 +202,7 @@
 rel="noopener">ISO 639-1</a>,
 and optionally an hyphen followed by the two-letter <i>Alpha-2</i> country code
 given in
-<a href="https://www.iso.org/obp/ui/#search/code/"rel="noopener";>ISO 
3166-1</a>.
+<a href="https://www.iso.org/obp/ui/#search/code/"; rel="noopener">ISO 
3166-1</a>.
 For example, the German translation of <code>not-ipr.html</code>
 should be named <code>not-ipr.de.html</code>; the Brazilian Portuguese
 translation should be named <code>not-ipr.pt-br.html</code>.</li>
@@ -261,17 +263,16 @@
 
 <li><p>Cite people with e-mail addresses this way:</p>
 <p class="emph-box"><code>
-&lt;a href="//www.stallman.org/"&gt;Richard Stallman&lt;/a&gt;
+&lt;a href="https://www.stallman.org/"&gt;Richard Stallman&lt;/a&gt;
 &lt;a href="mailto:rms@gnu.org"&gt;&amp;lt;rms@gnu.org&amp;gt;&lt;/a&gt;
 </code></p>
 <p>which browsers display this way:</p>
 <p class="emph-box" style="background-color: inherit">
-<a href="//www.stallman.org/">Richard Stallman</a>
+<a href="https://www.stallman.org/";>Richard Stallman</a>
 <a href="mailto:rms@gnu.org";>&lt;rms@gnu.org&gt;</a>
 </p>
 <p>It is less confusing to the user, because it's clear what is a link
-to another web page and what is an
-<a href="https://tools.ietf.org/html/rfc6068"; rel="noopener">RFC6068</a>
+to another web page and what is a
 <code>mailto:</code> anchor that will bring up a mail form to fill out
 and send, if this is supported by the client.  Also, if users save a copy
 of the page, they will have a copy of the e-mail address they can use without
@@ -421,9 +422,9 @@
 <code>/layout.css</code>; it covers most of our use cases.</li>
 
 <li>Mobile devices with very limited resources use <code>/mini.css</code>.
-This stylesheet is just the YUI (version&nbsp;2) reset and base stylesheets,
-as these devices typically have minimal need for various fonts and no need
-for fancy layouts.</li>
+This stylesheet is just the Yahoo User Interface (version&nbsp;2) reset and
+base stylesheets, as these devices typically have minimal need for various
+fonts and no need for fancy layouts.</li>
 
 <li>Printers use <code>/print.css</code>.  Note that the header, navigation
 bars and footer (except copyright and license) are unprintable.</li>
@@ -523,7 +524,7 @@
 alt="&amp;nbsp;[DESCRIPTIVE TEXT]&amp;nbsp;"
 style="width: 10em; height: auto;" width="77px" height="77px" /&gt;</code></p>
 This way, the page will look the same if the reader increases or
-decreases font size.<br>Specifying both <code>width</code> and
+decreases font size.<br />Specifying both <code>width</code> and
 <code>height</code> will reserve the space required for the image during
 the page loading phase.</li>
 
@@ -747,7 +748,7 @@
 
 <li>
 Before the initial checkout, set the environment variable
-<code>CVS_RSH=ssh</code>.<br>In alternative, you can replace
+<code>CVS_RSH=ssh</code>.<br />In alternative, you can replace
 <code>:ext:</code> with
 <a href="/software/trans-coord/manual/cvs/cvs.html#Connecting-with-rsh-or-ssh">
 <code>:extssh:</code></a> to use an external ssh program.</li>
@@ -957,7 +958,7 @@
       <img src="../graphics/icons/anybrowser.png" width="96px" height="18px"
       title="Visit the 'Best Viewed on Any Browser' campaign website"
       alt="Best Viewed on Any Browser"
-      style="vertical-align: middle" /></a>
+      style="vertical-align: middle; width: 6em; height: auto"  /></a>
       campaign.</li>
 
     <li>Use of <a href="https://w3.org/TR/2021/SPSD-html52-20210128/";
@@ -966,11 +967,11 @@
 
     <li>Use of <a href="https://www.w3.org/TR/2020/NOTE-css-2020-20201222/";
     rel="noopener">CSS3 RECs</a> in place of WDs and CRs allows for stable
-    cross-browser styling.</li>
+    cross-browser styling.</li><!-- What do these abbreviations stand for ?? 
-->
 
     <li>Use of <a href="https://www.w3.org/TR/2018/REC-WCAG21-20180605/";
     rel="noopener">WCAG&nbsp;2.1</a> ensures accessibility for a wide range of
-    people with disabilities.</li>
+    people with disabilities.</li><!-- expand WCAG? -->
   </ul>
 </li>
 
@@ -1072,7 +1073,7 @@
 
 <p class="unprintable">Updated:
 <!-- timestamp start -->
-$Date: 2021/02/17 12:19:06 $
+$Date: 2021/02/17 17:23:04 $
 <!-- timestamp end --></p>
 </div>
 </div><!-- for class="inner", starts in the banner include -->



reply via email to

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