CVSROOT: /web/www
Module name: www
Changes by: Pavel Kharitonov <ineiev> 12/01/29 06:22:46
Modified files:
server : fsf-html-style-sheet.html
server/standards: README.webmastering.html
Log message:
Update symlinks documentation.
Explain the naming conventions for pages and their translations.
Document that UTF-8 is the only encoding to be used.
Fix a couple of typos.
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/server/fsf-html-style-sheet.html?cvsroot=www&r1=1.47&r2=1.48
http://web.cvs.savannah.gnu.org/viewcvs/www/server/standards/README.webmastering.html?cvsroot=www&r1=1.136&r2=1.137
Patches:
Index: fsf-html-style-sheet.html
===================================================================
RCS file: /web/www/www/server/fsf-html-style-sheet.html,v
retrieving revision 1.47
retrieving revision 1.48
diff -u -b -r1.47 -r1.48
--- fsf-html-style-sheet.html 2 Jan 2012 02:40:34 -0000 1.47
+++ fsf-html-style-sheet.html 29 Jan 2012 06:22:25 -0000 1.48
@@ -109,11 +109,8 @@
and on the web. Again, use your judgement.
</ul>
-<li>Regarding character encoding, in general, the use of 8-bit
-Unicode makes life easy on our translators, so when using XHTML, UTF-8
-is preferred as a general rule. When using HTML please keep in mind the
-W3C recommendation and the appropriate character set respective to the
-language in question.</li>
+<li>Our server-side includes declare UTF-8 as the character encoding,
+so using any other encoding is problematic.</li>
<li>Please be considerate of all who access our web pages, and
accomodate them, including those who use text-only browsers, or old
@@ -278,6 +275,17 @@
names, the user will not get a highlighted link on the file names the
user hasn't explicitly referenced. So the user goes to pages the user
has already seen, which is irritating. Also, this helps mirroring.</li>
+
+<li id="NamingTranslations">If you translate your web pages in different
+languages, please use <code>article.html</code> name for the English
+files and <code>article.<var>LANG</var>.html</code> for the
+translations. <var>LANG</var> should contain two-letter language code
+from <a
+href="http://www.loc.gov/standards/iso639-2/php/code_list.php";>ISO
+639</a> and optional hyphen with two-letter country code given in ISO
+3166. 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>
</ul>
<h3><a name="UseofGraphics" id="UseofGraphics">Use of Graphics</a></h3>
@@ -405,7 +413,7 @@
<p>Updated:
<!-- timestamp start -->
-$Date: 2012/01/02 02:40:34 $
+$Date: 2012/01/29 06:22:25 $
<!-- timestamp end --></p>
</div>
Index: standards/README.webmastering.html
===================================================================
RCS file: /web/www/www/server/standards/README.webmastering.html,v
retrieving revision 1.136
retrieving revision 1.137
diff -u -b -r1.136 -r1.137
--- standards/README.webmastering.html 11 Jan 2012 22:26:21 -0000 1.136
+++ standards/README.webmastering.html 29 Jan 2012 06:22:39 -0000 1.137
@@ -180,7 +180,7 @@
<li>If the message is in a language you don't understand and it's not
spam, or you're not sure if it's spam, click ‘Basics’, then
-change the Queue field to ‘web-translators”.</li>
+change the Queue field to ‘web-translators’.</li>
<li>If the message is just a thank-you to us, or something else that
doesn't require action on our part, click ‘Resolve’.</li>
@@ -1069,18 +1069,20 @@
document root. The second file name may not contain any slash; it is the
name of the symbolic link to be created in the present directory.</p>
-<p>At one time, the command used to implement this feature was
-web-symlinks, a Perl script; <a
-href="http://cvs.savannah.gnu.org/viewvc/www/symlinks/?root=www";>it can
-be found in www's sources CVS</a>. It is completely different from the
-<a href="http://ibiblio.org/pub/linux/utils/file/";>symlinks utility</a>
-for verifying a system's symbolic links.
+<p>As a special case, if a file name ends in “.html”, single
+line defines links to all possible translations that follow our <a
+href="/server/fsf-html-style-sheet.html#NamingTranslations">naming
+conventions</a>. As a side effect, 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
+<code>page.<var>LL-CC</var>.html</code>, where LL and CC are two-letter
+codes. When you need such redirections, use the <a
+href="#htaccess">htaccess mechanism</a>.</p>
<p>These days, the .symlinks handling happens on <tt>www.gnu.org</tt>
-via a cron job that runs every five minutes. webmasters do not have
+via a cron job that runs every five minutes. Webmasters do not have
access to it.</p>
-
<h4 id="htaccess">.htaccess and redirections</h4>
<p>To browsers, the symbolic links in the previous section are
@@ -1133,7 +1135,7 @@
<p>Updated:
<!-- timestamp start -->
-$Date: 2012/01/11 22:26:21 $
+$Date: 2012/01/29 06:22:39 $
<!-- timestamp end -->
</p>
</div>
