www-commits
[Top][All Lists]
Advanced

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

www/server/standards gnu-website-guidelines.htm...


From: Ineiev
Subject: www/server/standards gnu-website-guidelines.htm...
Date: Mon, 10 Sep 2018 03:42:41 -0400 (EDT)

CVSROOT:        /web/www
Module name:    www
Changes by:     Ineiev <ineiev> 18/09/10 03:42:41

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

Log message:
        Fix and normalize links; add spaces.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/server/standards/gnu-website-guidelines.html?cvsroot=www&r1=1.3&r2=1.4
http://web.cvs.savannah.gnu.org/viewcvs/www/server/standards/README.webmastering.html?cvsroot=www&r1=1.202&r2=1.203

Patches:
Index: gnu-website-guidelines.html
===================================================================
RCS file: /web/www/www/server/standards/gnu-website-guidelines.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -b -r1.3 -r1.4
--- gnu-website-guidelines.html 9 Sep 2018 12:27:44 -0000       1.3
+++ gnu-website-guidelines.html 10 Sep 2018 07:42:40 -0000      1.4
@@ -1,5 +1,5 @@
 <!--#include virtual="/server/header.html" -->
-<!-- Parent-Version: 1.84 -->
+<!-- Parent-Version: 1.85 -->
 <title>Website Guidelines - GNU Project - Free Software Foundation</title>
 <style type="text/css" media="print,screen"><!--
 ul li { margin-top: 1em; }
@@ -121,8 +121,7 @@
 get such a permission from the author, please discuss the issue with
 the FSF before posting it.  This applies to CSS as well as to HTML.</li>
 
-<li>
-If ultimately we decide to post a new page we don't have permission to
+<li>If ultimately we decide to post a new page we don't have permission to
 modify, put the text &ldquo;Posted in 20XX without FSF permission to
 modify&rdquo; inside an HTML comment, just after the copyright notice.</li>
 
@@ -498,7 +497,7 @@
 
 <li>If you are adding a small floating image to a page that uses
 <code>layout.css</code> (the stylesheet for <a
-href="/server/standards/README.webmastering#templating">templated pages</a>),
+href="/server/standards/README.webmastering.html#templating">templated 
pages</a>),
 you may want to use the <code>imgright</code> or <code>imgleft</code> class
 (defined in the IMAGES section of the stylesheet). This will ensure that
 the floating direction is reversed if the page is translated into an RTL
@@ -856,7 +855,7 @@
 The current method actually takes advantage of the flexibility of URL
 rewriting. Thus a single HTML entry in the .symlinks file defines links
 to all possible translations that follow our <a
-href="/server/fsf-html-style-sheet.html#NamingTranslations">naming
+href="#NamingTranslations">naming
 conventions</a>. This makes it impossible to use
 symlinks to redirect to and from HTML files whose names look like
 translations, that is, <code>page.<var>LL</var>.html</code> or
@@ -926,8 +925,7 @@
 
 <li>On gnu.org:
   <ul>
-    <li><a href="/server/standards/gnu-website-guidelines.html">The
-    GNU Website Guidelines</a>;</li>
+    <li><a href="#content">The GNU Website Guidelines</a>;</li>
 
     <li>Guidelines for
     <a href="/server/standards/README.editors.html">Web Page Creation</a> at
@@ -1023,7 +1021,7 @@
 
 <p class="unprintable">Updated:
 <!-- timestamp start -->
-$Date: 2018/09/09 12:27:44 $
+$Date: 2018/09/10 07:42:40 $
 <!-- timestamp end --></p>
 </div>
 </div>

Index: README.webmastering.html
===================================================================
RCS file: /web/www/www/server/standards/README.webmastering.html,v
retrieving revision 1.202
retrieving revision 1.203
diff -u -b -r1.202 -r1.203
--- README.webmastering.html    9 Sep 2018 10:34:27 -0000       1.202
+++ README.webmastering.html    10 Sep 2018 07:42:40 -0000      1.203
@@ -1,5 +1,5 @@
 <!--#include virtual="/server/header.html" -->
-<!-- Parent-Version: 1.84 -->
+<!-- Parent-Version: 1.85 -->
 <title>Webmastering Guidelines - GNU Project - Free Software Foundation</title>
 <style type="text/css" media="print,screen"><!--
 .summary { margin-top: 1.3em; }
@@ -134,14 +134,15 @@
 <p>Sometimes people send mails asking us to make links to different
 software packages.  Before making such links, it's important to check
 the page that the link points to and make sure that it does not make any
-references to nonfree software (see our <a href="#pollinking">linking
+references to nonfree software (see our <a
+href="/server/standards/gnu-website-guidelines.html#pollinking">linking
 policies</a>).  When in doubt, it is best to post a
 summary of what you found on the page back to the webmasters list (but
 not to the requestor!), and ask someone else to take it from there.</p>
 
 <p>We do not have links to websites of the <a
-href="/distros/common-distros.html">well-known</a> GNU/Linux system
-distributions, or to the well-known BSD system distributions, because
+href="/distros/common-distros.html">well-known GNU/Linux system
+distributions</a>, or to the well-known BSD system distributions, because
 all those sites explicitly describe, and facilitate access to, various
 nonfree programs.</p>
 
@@ -239,7 +240,9 @@
 <a href="#thankgnu">Thank GNU procedure</a>.</li>
 
 <li>If the message is about making a link on one of our pages, see
-the <a href="#pollinking">linking policies</a>.</li>
+the <a
+href="/server/standards/gnu-website-guidelines.html#pollinking">linking
+policies</a>.</li>
 
 <li>If the message is about adding an image or a joke, be sure to get
 the explicit ok for it to be released under a free
@@ -495,7 +498,7 @@
 Website Guidelines</a>.</span></p>
 
 <p>To create a new page in the main part of gnu.org, please <a
-href="/server/standards/gnu-website-guidelines#templating">use the
+href="/server/standards/gnu-website-guidelines.html#templating">use the
 boilerplate</a>.</p>
 
 
@@ -527,14 +530,14 @@
 <p>Occasionally, RMS will mail an article, usually in plain text, to
 webmasters and ask that they put it on the site. The plain text needs to be
 converted to XHTML and <a
-href="/server/standards/gnu-website-guidelines#templating">put into our
+href="/server/standards/gnu-website-guidelines.html#templating">put into our
 standard boilerplate</a>.  There are a few things you should take care of
 while doing the conversion:</p>
 
 <ul>
 <li>Fix any obvious typos. If in doubt, contact the author.</li>
 <li>Follow the <a
-href="/server/standards/gnu-website-guidelines#orthography">spelling and
+href="/server/standards/gnu-website-guidelines.html#orthography">spelling and
 punctuation guidelines</a>.</li>
 <li>Add the author's name below the &lt;h2&gt; header.</li>
 </ul>
@@ -625,7 +628,7 @@
 <ul>
 <li>If the person requesting the link is a friend of the GNU Project,
 check the page against our <a 
-href="/server/standards/gnu-website-guidelines#pollinking">linking
+href="/server/standards/gnu-website-guidelines.html#pollinking">linking
 criteria</a>, and if it passes, add the link as requested.  If it doesn't,
 say so in your reply to the requestor, outlining in detail what the
 problem(s) are.</li>
@@ -812,7 +815,7 @@
 
 <p>When considering a request, err on the side of caution. If the use of
 an image isn't <a
-href="/server/standards/gnu-website-guidelines#pollinking">something
+href="/server/standards/gnu-website-guidelines.html#pollinking">something
 we'd link to</a>, for example, then it isn't something we should give
 permission for. Feel free to discuss any requests on www-discuss before
 responding to them.</p>
@@ -932,7 +935,7 @@
 
 <p class="unprintable">Updated:
 <!-- timestamp start -->
-$Date: 2018/09/09 10:34:27 $
+$Date: 2018/09/10 07:42:40 $
 <!-- timestamp end -->
 </p>
 </div>



reply via email to

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