[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www/server/standards gnu-website-guidelines.htm...
|
From: |
GNUN |
|
Subject: |
www/server/standards gnu-website-guidelines.htm... |
|
Date: |
Sun, 9 Sep 2018 08:27:45 -0400 (EDT) |
CVSROOT: /web/www
Module name: www
Changes by: GNUN <gnun> 18/09/09 08:27:45
Modified files:
server/standards: gnu-website-guidelines.html
Added files:
server/standards/po: gnu-website-guidelines.pot
gnu-website-guidelines.translist
Log message:
Automatic update by GNUnited Nations.
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/server/standards/gnu-website-guidelines.html?cvsroot=www&r1=1.2&r2=1.3
http://web.cvs.savannah.gnu.org/viewcvs/www/server/standards/po/gnu-website-guidelines.pot?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/server/standards/po/gnu-website-guidelines.translist?cvsroot=www&rev=1.1
Patches:
Index: gnu-website-guidelines.html
===================================================================
RCS file: /web/www/www/server/standards/gnu-website-guidelines.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- gnu-website-guidelines.html 9 Sep 2018 12:07:15 -0000 1.2
+++ gnu-website-guidelines.html 9 Sep 2018 12:27:44 -0000 1.3
@@ -4,7 +4,7 @@
<style type="text/css" media="print,screen"><!--
ul li { margin-top: 1em; }
--></style>
-<!--#include virtual="/server/gnun/initial-translations-list.html" -->
+ <!--#include virtual="/server/standards/po/gnu-website-guidelines.translist"
-->
<!--#include virtual="/server/banner.html" -->
<h2>GNU Website Guidelines</h2>
@@ -1023,7 +1023,7 @@
<p class="unprintable">Updated:
<!-- timestamp start -->
-$Date: 2018/09/09 12:07:15 $
+$Date: 2018/09/09 12:27:44 $
<!-- timestamp end --></p>
</div>
</div>
Index: po/gnu-website-guidelines.pot
===================================================================
RCS file: po/gnu-website-guidelines.pot
diff -N po/gnu-website-guidelines.pot
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ po/gnu-website-guidelines.pot 9 Sep 2018 12:27:45 -0000 1.1
@@ -0,0 +1,1472 @@
+# LANGUAGE translation of
https://www.gnu.org/server/standards/gnu-website-guidelines.html
+# Copyright (C) YEAR Free Software Foundation, Inc.
+# This file is distributed under the same license as the original article.
+# FIRST AUTHOR <address@hidden>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: gnu-website-guidelines.html\n"
+"POT-Creation-Date: 2018-09-09 12:26+0000\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <address@hidden>\n"
+"Language-Team: LANGUAGE <address@hidden>\n"
+"Language: \n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=CHARSET\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. type: Content of: <title>
+msgid "Website Guidelines - GNU Project - Free Software Foundation"
+msgstr ""
+
+#. type: Content of: <h2>
+msgid "GNU Website Guidelines"
+msgstr ""
+
+#. type: Content of: <p>
+msgid ""
+"Our goal is to get information to people. Keeping the site design simple "
+"helps accomplish that."
+msgstr ""
+
+#. type: Content of: <p>
+msgid ""
+"Please be considerate of all who access our web pages, and accommodate them, "
+"including those who use text-only browsers or old browsers, as well as those "
+"with slow connections. We wish to prevent HTML design that looks great under "
+"one version of one browser, and ugly under many others. Of course, please "
+"don't install any of the proprietary software browsers available if you "
+"don't already use them anyway."
+msgstr ""
+
+#. type: Content of: <div><h3>
+msgid "Table of Contents"
+msgstr ""
+
+#. type: Content of: <div><ul><li>
+msgid "<a href=\"#GeneralGuidelines\">General Guidelines</a>"
+msgstr ""
+
+#. type: Content of: <div><ul><li>
+msgid "<a href=\"#CopyrightGuidelines\">Copyright Guidelines</a>"
+msgstr ""
+
+#. type: Content of: <div><ul><li>
+msgid "<a href=\"#orthography\">Spelling and Punctuation</a>"
+msgstr ""
+
+#. type: Content of: <div><ul><li>
+msgid "<a href=\"#filenames\">Filenames</a>"
+msgstr ""
+
+#. type: Content of: <div><ul><li>
+msgid "<a href=\"#urls\">URLs</a>"
+msgstr ""
+
+#. type: Content of: <div><ul><li>
+msgid "<a href=\"#HTMLGuidelines\">HTML Guidelines</a>"
+msgstr ""
+
+#. type: Content of: <div><ul><li>
+msgid "<a href=\"#tables\">Tables and menus</a>"
+msgstr ""
+
+#. type: Content of: <div><ul><li>
+msgid "<a href=\"#templating\">Using our page template</a>"
+msgstr ""
+
+#. type: Content of: <div><ul><li>
+msgid "<a href=\"#styling\">Page Styling</a>"
+msgstr ""
+
+#. type: Content of: <div><ul><li>
+msgid "<a href=\"#UseofGraphics\">Use of Graphics</a>"
+msgstr ""
+
+#. type: Content of: <div><ul><li>
+msgid "<a href=\"#pollinking\">Appendix 1 - Linking Policies</a>"
+msgstr ""
+
+#. type: Content of: <div><ul><li>
+msgid "<a href=\"#repo\">Appendix 2 - Working with Web CVS Repositories</a>"
+msgstr ""
+
+#. type: Content of: <div><ul><li><ul><li>
+msgid "<a href=\"#cvs\">Basic CVS commands</a>"
+msgstr ""
+
+#. type: Content of: <div><ul><li><ul><li>
+msgid "<a href=\"#symlinks\">Symbolic links</a>"
+msgstr ""
+
+#. type: Content of: <div><ul><li><ul><li>
+msgid "<a href=\"#htaccess\">.htaccess and redirections</a>"
+msgstr ""
+
+#. type: Content of: <div><ul><li><ul><li>
+msgid "<a href=\"#scripts\">Scripts</a>"
+msgstr ""
+
+#. type: Content of: <div><ul><li><ul><li>
+msgid "<a href=\"#sysadmins\">System administrators</a>"
+msgstr ""
+
+#. type: Content of: <div><ul><li>
+msgid "<a href=\"#UsefulResources\">Useful Resources</a>"
+msgstr ""
+
+#. type: Content of: <h3>
+msgid "General Guidelines"
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"The GNU web server has only <a href=\"/philosophy/free-sw.html\">free "
+"software</a> available. We prefer that only free software be used to "
+"prepare pages for the GNU web server."
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"The GNU website lists and links <strong>only</strong> to free software. The "
+"software's source code and executables have to be freely redistributable and "
+"modifiable to and by all people and organizations. If in doubt, ask <a "
+"href=\"mailto:address@hidden";><address@hidden></a>."
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"The GNU website gives priority to software covered by either the GNU General "
+"Public License or GNU Lesser General Public License."
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"The GNU website is more interested in substance than style. The use of "
+"graphics should be minimized so pages load fast over slow links."
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"Offer a document in as many formats as the GNU Project has it. For an "
+"example, see <a href=\"/licenses/fdl.html\">The GNU Free Documentation "
+"License</a>. This lets users get the document in the format most useful to "
+"them."
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"In addition to <a href=\"#CopyrightGuidelines\">copyright and license "
+"notices</a>, all pages should have contact info for both the FSF (or "
+"responsible party) and the address for bug reports (webmasters for general "
+"pages, but project-specific addresses otherwise) at the bottom of each "
+"page. The reason to note this at the bottom is so the user always finds "
+"this information at the same place on each page."
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"Before you take any graphics or text from another website, please ask for "
+"permission to use it. It's polite to do so. It is also essential for us to "
+"avoid copyright infringement."
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"Before adding a link, check that it follows our <a "
+"href=\"#pollinking\">linking criteria</a>."
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"Do not list an address of an individual, including the maintainer of a GNU "
+"package, unless explicitly asked to have it listed. Most GNU maintainers do "
+"not want a lot of extra mail and prefer to get bug reports, etc. from the "
+"GNU bug report <a href=\"/prep/mailinglists.html\">mailing lists</a>."
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"On pages with dated entries (e.g., /philosophy/latest-articles.html), the "
+"newer entries should be first (i.e., reverse chronological order)."
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid "Pages should not load CSS from servers other than those run by the FSF."
+msgstr ""
+
+#. type: Content of: <h3>
+msgid "Copyright Guidelines"
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"Every page should have a copyright notice. See the <a "
+"href=\"//web.cvs.savannah.gnu.org/viewvc/*checkout*/www/server/standards/boilerplate.html?root=www&content-type=text%2Fplain\">
"
+"boilerplate</a>, referred below."
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"Every page should have a notice giving everyone permission to distribute "
+"it. If you cannot get such a permission from the author, please discuss the "
+"issue with the webmasters before posting it. This applies to CSS as well as "
+"to HTML."
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"Normally you shouldn't post a page that isn't copyright FSF unless we have "
+"permission to modify the version we publish. If you cannot 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."
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"If ultimately we decide to post a new page we don't have permission to "
+"modify, put the text “Posted in 20XX without FSF permission to "
+"modify” inside an HTML comment, just after the copyright notice."
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"The user of our pages should always find the copyright information at the "
+"same place on each page. If the page is copyrighted by some other person or "
+"entity, use per or its copyright notice instead of the FSF copyright "
+"notice. Use the rest of the FSF's normal footer material, except when there "
+"is a specific reason to change something in it."
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"All pages that explain how to do something, such as how to use certain "
+"programs, are documentation. This includes all the pages in "
+"<code>/software/</code> that describe specific programs. By our principles, "
+"<a href=\"/philosophy/free-doc.html\"> documentation must be free</a>. So "
+"these pages must carry a <a "
+"href=\"/licenses/license-recommendations.html\">free license</a>. If such a "
+"page doesn't have a free license, please report the problem to <a "
+"href=\"mailto:address@hidden";><address@hidden></a>."
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"For other pages, use the same license as some other page that serves a "
+"similar kind of purpose."
+msgstr ""
+
+#. type: Content of: <h3>
+msgid "Spelling and Punctuation"
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"English pages should follow the standard American spelling, hyphenation and "
+"punctuation conventions."
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"Since these conventions are not always very specific, especially as regards "
+"hyphenation and quotes, gnu.org adds its own rules for the sake of "
+"consistency:"
+msgstr ""
+
+#. type: Content of: <ul><li><ul><li>
+msgid ""
+"“Nonfree” is preferred over “non-free;” likewise, "
+"“noncommercial” over “non-commercial”."
+msgstr ""
+
+#. type: Content of: <ul><li><ul><li>
+msgid ""
+"In ordinary text, HTML entities “&ldquo;...&rdquo;” and "
+"“&lsquo;...&rsquo;” are preferred over straight quotes "
+"(\"...\" and '...'). This doesn't apply to script-generated documents."
+msgstr ""
+
+#. type: Content of: <ul><li><ul><li>
+msgid ""
+"Where they exist, the double spaces after sentence breaks should be "
+"preserved. They enable Emacs sentence commands to do the right thing."
+msgstr ""
+
+#. type: Content of: outside any tag (error?)
+msgid "<a href=\"FilenameAndURLGuidelines\"></a>"
+msgstr ""
+
+#. type: Content of: <h3>
+msgid "Filenames"
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"To make simultaneous edition of many files easier, try and give each HTML "
+"file a unique name; the filename <code>index.html</code> should only be used "
+"as a symbolic link, as explained next."
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"Each directory in the web server tree should have a symbolic link named "
+"<code>index.html</code> to the top-level HTML file for that directory. Use "
+"the <a href=\"#symlinks\"><code>.symlinks</code></a> file to handle this."
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"If you translate your web page in different languages, please name the "
+"English file <code>ARTICLE.html</code>, and its translations "
+"<code>ARTICLE.LANG.html</code>. LANG should contain the two-letter language "
+"code from <a "
+"href=\"https://www.loc.gov/standards/iso639-2/php/code_list.php\";>ISO "
+"639</a>, and optionally an hyphen followed the 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>."
+msgstr ""
+
+#. type: Content of: <h3>
+msgid "URLs"
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"Hand-written URLs that refer to other files on www.gnu.org should be "
+"absolute, starting from the root page. That is, paths should start with "
+"<code>/</code> (e.g., <code>/gnu/about-gnu.html</code>; <em>not</em> "
+"<code>http://www.gnu.org/gnu/about-gnu.html</code>, and <em>not</em> "
+"<code>about-gnu.html</code>). This makes it easier to copy and paste links "
+"from other pages. Besides, links like <code>http://www.gnu.org/</code> will "
+"be wrong when the visitor uses HTTPS."
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"Collections of files produced automatically from Texinfo source contain "
+"links with relative file names. They always refer to another file in the "
+"same directory. These relative links are to be tolerated."
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"Don't use just a directory name in a URL; always include the specific "
+"filename. E.g., use <code>/gnu/gnu.html</code>, not just "
+"<code>/gnu/</code>. Never use <code>index.html</code> in a URL. Both of "
+"these are kindnesses to the user, as browsers change the highlighting on a "
+"link after it has been visited. If links to a given file use several "
+"different URLs, the URLs that haven't been explicitly referenced will not be "
+"highlighted as visited. So the user goes to pages he/she has already seen, "
+"which is irritating. Also, this eases maintenance of the site as things get "
+"moved around."
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"Be sure to omit the filename entirely when linking to an anchor in the same "
+"file."
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"Consider others linking to your page when removing an anchor or "
+"<code>id</code> attribute."
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"Cite FTP locations of source code with the full URL of the directory they "
+"are in:"
+msgstr ""
+
+#. type: Content of: <ul><li><p>
+msgid ""
+"<code> <a "
+"href=\"https://ftp.gnu.org/gnu/foo\">https://ftp.gnu.org/gnu/foo</a>
"
+"</code>"
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid "which browsers display this way:"
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid "<a href=\"https://ftp.gnu.org/gnu/\";>https://ftp.gnu.org/gnu/foo</a>"
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"We encourage FTP sites to use a directory for each package, and only put one "
+"package's files in each directory, so that the users can see what versions "
+"of that package and related information can be downloaded (e.g., a "
+"<code>README</code> file, information of what versions are available, "
+"documentations, fonts, etc.). Also, it means that the FTP location URLs do "
+"not need to be changed, on this and other sites, as new versions are "
+"released into that directory."
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid "Cite people with e-mail addresses this way:"
+msgstr ""
+
+#. type: Content of: <ul><li><p>
+msgid ""
+"<code> <a href=\"https://www.stallman.org/\">Richard "
+"Stallman</a> <a "
+"href=\"mailto:address@hidden">&lt;address@hidden&gt;</a>
</code>"
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"<a href=\"https://www.stallman.org/\";>Richard Stallman</a> <a "
+"href=\"mailto:address@hidden";><address@hidden></a>"
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"It is less confusing to the user, because it's clear what is a "
+"<code>http(s):</code> link 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 going "
+"back to their web browser. If the person doesn't have a web page, leave the "
+"name unanchored."
+msgstr ""
+
+#. type: Content of: <h3>
+msgid "HTML Guidelines"
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"HTML on the GNU web server should be strictly compliant with <a "
+"href=\"https://www.w3.org/standards/\";>W3C standards</a>."
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"Please follow the above mentioned web standards strictly. Don't neglect <a "
+"href=\"https://www.w3.org/TR/html401/struct/global.html#h-7.1\";>required "
+"elements</a> such as <html> <head> <title> <body>, "
+"etc. when using (X)HTML, and always include the appropriate DTD or Schema "
+"reference. This appeases overly pedantic browsers."
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"Do not add comments at the top of a document. Web browsers expect the "
+"doctype, XML declaration, or Schema to be at the top. Comments will confuse "
+"them, and often cause them to incorrectly interpret your markup."
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid "The <head> element should contain this line:"
+msgstr ""
+
+#. type: Content of: <ul><li><p>
+msgid "<code><link rev=\"made\" href=\"mailto:address@hidden"></code>"
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"Some browsers use this information to allow users to easily report problems "
+"they find on a page."
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"The first header tag, <h[n]>, should have its text duplicated at the "
+"start of the <title> tag. The <title> tag is used by many "
+"browsers in menus like the history and bookmarks lists, as a link to that "
+"page. Repeating the main heading in the <title> ensures that, when "
+"users click on an item in these menus, they get a page with the expected "
+"heading. Please properly use your headers in numerical order: 1, 2, "
+"etc. These are not used for looks, but for the organization of the document."
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"The <title> tag should include the phrases “GNU Project” "
+"and “Free Software Foundation” 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>."
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid "Acronyms/abbreviations:"
+msgstr ""
+
+#. type: Content of: <ul><li><ul><li>
+msgid ""
+"Never use <code><acronym></code>: HTML5 obsoletes it in favor of "
+"<code><abbr></code>."
+msgstr ""
+
+#. type: Content of: <ul><li><ul><li>
+msgid ""
+"Don't use <code><abbr></code> unless for a really compelling reason. "
+"Browsers render it in an ugly way."
+msgstr ""
+
+#. type: Content of: <ul><li><ul><li>
+msgid ""
+"When an abbreviation may be unfamiliar to a reader, give its expansion the "
+"first time it is used in a document, like this: <code><abbr "
+"title=\"Expanded Abbreviation\">EA</abbr></code> or <code>EA "
+"(Expanded Abbreviation)</code>."
+msgstr ""
+
+#. type: Content of: <ul><li><ul><li>
+msgid ""
+"Further occurrences, in any case, should be written without any markup: just "
+"<code>EA</code>."
+msgstr ""
+
+#. type: Content of: <ul><li><ul><li>
+msgid ""
+"For common-enough initialisms, such as GNU, FSF, BSD, RAM, HTML, DVD, and so "
+"on and so on, no markup is needed at all. Use your judgment."
+msgstr ""
+
+#. type: Content of: <h3>
+msgid "Tables and menus"
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid "Please use tables to organize data, not the presentation of the web
page."
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"Screen reader software used by most blind people reads the text from left to "
+"right, ignoring any tables that you make. If you use tables, you should make "
+"sure that reading a whole page left to right doesn't confuse such "
+"software. Please follow the <a href=\"https://www.w3c.org/wai\";>W3C web "
+"accessibility guidelines</a> to ensure that tables are properly marked for "
+"accessibility."
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"Some people like to organize links as a menu to the left or right of the "
+"main text when using graphical browsers. That does not work very well with "
+"text browsers since they will make the menu appear either on top of the page "
+"or at the bottom. If you have a menu that is more than 30 lines long, then "
+"it's very probable that a user viewing the page will never bother to read "
+"the text because it will be too far down. You should make an effort to keep "
+"such menus under 20 lines long so that the beginning of the article is "
+"visible on the first page when viewing it with a text browser. A menu bar of "
+"one or two horizontal lines might accomplish your purpose as well. Providing "
+"a “skip link” to the main text is another option."
+msgstr ""
+
+#. type: Content of: <h3>
+msgid "Using our page template"
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"To help people follow the above guidelines, a page template (or "
+"“boilerplate”) is provided for both the main part of the GNU "
+"website, and the software projects. Its use is mandatory for new pages in "
+"www.gnu.org, and highly recommended for software pages. Please don't start "
+"out with an existing page to create a new one; use the <a "
+"href=\"//web.cvs.savannah.gnu.org/viewvc/*checkout*/www/server/standards/boilerplate.html?root=www&content-type=text%2Fplain\">
"
+"original source</a> of the boilerplate instead, and follow the instructions "
+"in it."
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid "The templated pages must be valid XHTML."
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"Our server-side includes declare UTF-8 as the character encoding, so using "
+"any other encoding is problematic."
+msgstr ""
+
+#. type: Content of: <h3>
+msgid "Styling"
+msgstr ""
+
+#. type: Content of: <h4>
+msgid "Styling of templated pages"
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"Generic styling for desktops and smartphones is provided by two CSS: "
+"<code>/reset.css</code> (from the <a "
+"href=\"//web.archive.org/web/20070930230754/http://developer.yahoo.com:80/yui/\";>
"
+"YUI library, version 2</a>), which normalizes the default rendering of "
+"all HTML elements by the various browsers, and <code>/layout.css</code>, "
+"which contains gnu.org-specific formatting. A few responsive elements are "
+"defined in <code>/layout.css</code>. They cover most of our use cases."
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"Mobile devices with very limited resources use <code>/mini.css</code>. This "
+"stylesheet is just the YUI (version 2) reset and base stylesheets, as "
+"these devices typically have minimal need for various fonts and no need for "
+"fancy layouts."
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"Printers use <code>/print.css</code>. Note that the header, navigation bars "
+"and footer (except copyright and license) are unprintable."
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"If some special styling is needed for a specific page, it should be added to "
+"the page itself in a <style> element, between the SSI directives that "
+"include <code>header.html</code> and <code>banner.html</code>. If the style "
+"applies to a single element, it should normally be added as an attribute."
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"If you specify any color attribute in the HTML, you should specify all of "
+"them that are allowed for that tag. This is because some browsers allow "
+"users to specify defaults for the color attributes, and the user's choices "
+"could conflict with your choices, as your choices override the user's "
+"choices. In the worse case, the foreground and background could end up the "
+"same. Please use a stylesheet for this, and not HTML 3.2 (HTML 4 "
+"Transitional) deprecated markup."
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"<em>Note about grids:</em> Very few pages currently use them. In the "
+"event you'd like to create one that does, good starting points may be found "
+"in <a href=\"//yuilibrary.com/yui/docs/cssgrids/\">YUI version 3</a>, "
+"and <a href=\"//purecss.io/grids/\">Pure Grids</a>. The components provided "
+"by these libraries are licensed under the modified (3-clause) BSD license."
+msgstr ""
+
+#. type: Content of: <h4>
+msgid "Other stylesheets"
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"Historical pages (unmaintained translations for the most part) refer to "
+"<code>/gnu.css</code>, which in turn loads the <code>/mini.css</code>, as "
+"these pages are usually very basic, plain pages with little or no "
+"formatting."
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid "Some software manuals use a dedicated CSS, <code>/style.css</code>."
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"Translators maintain stylesheets (<code>/style.LANG.css</code>) that modify "
+"layout.css according to their own needs. The RTL languages (Arabic, Persian, "
+"and Hebrew) use <code>/style.rtl.css</code>."
+msgstr ""
+
+#. type: Content of: <h3>
+msgid "Use of Graphics"
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"The use of graphics should be minimized, so pages load fast over slow links, "
+"especially animations."
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"We do not use background images on our pages, as they make text "
+"significantly harder to read."
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"In the past, GIFs have had patent problems. However, now that the IBM and "
+"Unisys patents (and other patents worldwide that are relevant to LZW "
+"compression) have expired, GIFs that are based on the 87a or 89a standard "
+"are acceptable. Please be wary of proprietary applications that may include "
+"non-standard patented technologies (we'd prefer you use free software "
+"applications when authoring for our websites). In general, PNG or JPEG "
+"format are still safe, and are probably better from a technical "
+"standpoint. For details regarding the old GIF problem, see <a "
+"href=\"/philosophy/gif.html\">https://www.gnu.org/philosophy/gif.html</a>. "
+"Other formats are also allowed, though JPEG is the one most widely "
+"recognized by web browsers (avoid JPEG 2000, and be careful with PNG alpha "
+"channels; the former is not widely supported, and the latter are not fully "
+"supported by some older browsers)."
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"Before you take an image from another website, please ask for permission to "
+"use it."
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"Always have a textual alternative for in-line images, for people who have "
+"text-only access to the web. For instance:"
+msgstr ""
+
+#. type: Content of: <ul><li><p>
+msgid ""
+"<code><img src=\"/graphics/*.jpg\" alt=\"&nbsp;[DESCRIPTIVE "
+"TEXT]&nbsp;\"></code>"
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"We add the non-breaking spaces (&nbsp;) and square brackets to separate "
+"the DESCRIPTIVE TEXT from adjacent text, and help the user realize that this "
+"is a stand-in for an image. The point of using non-breaking spaces rather "
+"than normal ones is to make sure they find their way to the translatable "
+"strings that are extracted by the POA4/Gettext tools."
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"Make sure the image doesn't look too big or too small when displayed at its "
+"original size, using the browser's default font size."
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"Adjust image width or height in a style attribute, using scalable units such "
+"as <code>em</code> or <code>%</code>; for instance:"
+msgstr ""
+
+#. type: Content of: <ul><li><p>
+msgid ""
+"<code><img src=\"/graphics/*.jpg\" alt=\"&nbsp;[DESCRIPTIVE "
+"TEXT]&nbsp;\" style=\"width: 10em\" /></code>"
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"This way, the page will look the same if the reader increases or decreases "
+"font size."
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"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>), 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 language."
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"If the image you are adding is 12em wide or more, and the page is templated, "
+"you may find it convenient to use one of the responsive <code>pict</code> "
+"classes that are defined in the IMAGES section of <code>layout.css</code> "
+"(you can adjust the width in a style attribute if none of the predefined "
+"ones fits your needs); for instance:"
+msgstr ""
+
+#. type: Content of: <ul><li><p>
+msgid ""
+"<code><div class=\"pict wide\" style=\"width: 25em\"><img "
+"src=\"/graphics/*.jpg\" alt=\"&nbsp;[DESCRIPTIVE TEXT]&nbsp;\" "
+"/></div></code>"
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"Note that the <code>div</code> container is necessary because some browsers "
+"(e.g., NetSurf) don't know how to apply <code>max-width</code> to images."
+msgstr ""
+
+#. type: Content of: <ul><li><p>
+msgid ""
+"Link all images that are displayed throughout the website to the relevant "
+"page, usually in <code>/graphics/</code>. This can be done with code similar "
+"to this, which corresponds to the image on the left:"
+msgstr ""
+
+#. type: Content of: <ul><li><p><a>
+msgid "<a href=\"/graphics/agnuhead.html\">"
+msgstr ""
+
+#. type: Attribute 'alt' of: <ul><li><p><a><img>
+msgid " [Image of the Head of a GNU] "
+msgstr ""
+
+#. type: Content of: <ul><li><p>
+msgid "</a>"
+msgstr ""
+
+#. type: Content of: <ul><li><pre>
+#, no-wrap
+msgid ""
+"<p class=\"imgleft\">\n"
+"<a href=\"/graphics/agnuhead.html\">\n"
+"<img src=\"/graphics/gnu-head-sm.jpg\"\n"
+" alt=\" [Image of the Head of a GNU] \"\n"
+" style=\"width: 8em\" />\n"
+"</a></p>\n"
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"This will allow users to quickly go to pages related to the pictures they "
+"are interested in."
+msgstr ""
+
+#. type: Content of: <h3>
+msgid "Appendix 1 - Linking Policies"
+msgstr ""
+
+#. type: Content of: <p>
+msgid ""
+"One of the most complex aspects of maintaining web pages is following the "
+"linking guidelines; however, it's also a very crucial aspect of the job."
+msgstr ""
+
+#. type: Content of: <p>
+msgid ""
+"We strive to ensure that all pages we promote—all pages which are "
+"given links on our site—are friendly to the free software movement. "
+"Some pages will obviously not meet such standards; if the site flames the "
+"Free Software Foundation, or has no apparent relation to free software and "
+"surrounding issues, the link shouldn't be made. Beyond that, however, there "
+"are criteria used in determining whether or not it is appropriate to provide "
+"a link to a page from ours. They are listed below, in order of descending "
+"general importance."
+msgstr ""
+
+#. type: Content of: <dl><dt>
+msgid "What's the context of the link?"
+msgstr ""
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"The link's purpose on our site will play a role in determining how strongly "
+"it should be judged against the other criteria. Pages hosting GNU projects "
+"will be held to the highest standards. Pages about other free software and "
+"given high promotion—for example, included in a newsfeed on the main "
+"page—are a close second. Links on the philosophy page may be given "
+"more leeway in talking about proprietary software; GNU/Linux user group "
+"pages should call the system GNU/Linux almost always but are hardly checked "
+"on other criteria. Always keep this in mind when deciding how to weigh each "
+"aspect of these policies."
+msgstr ""
+
+#. type: Content of: <dl><dt>
+msgid "Does the page promote proprietary software?"
+msgstr ""
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"The big point made by the free software movement is that proprietary "
+"software presents an ethical dilemma: you cannot agree to such nonfree terms "
+"and treat those around you as you would like to be treated. When "
+"proprietary software is promoted, people get the impression that it is okay "
+"to use it, while we are trying to convince them otherwise. As such, we "
+"avoid offering such free advertising, either directly on our site or "
+"indirectly through links."
+msgstr ""
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"What's tricky about this criteria is the “promotion” point: "
+"there's a difference between mentioning proprietary software and making a "
+"sales pitch for it. Indeed, the GNU Project website mentions proprietary "
+"software throughout, but never gives people the impression that its use does "
+"not present ethical problems."
+msgstr ""
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"There are two things to keep in mind when determining whether a reference to "
+"proprietary software promotes it, or simply mentions it. First, how much "
+"information does it offer about the software? Second, how much information "
+"is the reader likely to actually gain from this page?"
+msgstr ""
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"Different pages provide different amounts of information about proprietary "
+"software; the more it provides, the more of a problem it poses for us. For "
+"example, some pages may link to the primary site for a proprietary software "
+"program. Others may describe its functionality in detail. Even the product "
+"name given matters; there's a difference between “Windows” and "
+"“Microsoft Windows XP Home Edition.”"
+msgstr ""
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"If the page requires <a href=\"/philosophy/javascript-trap.html\">nonfree, "
+"nontrivial JavaScript</a> and has serious failures with JavaScript disabled, "
+"the link shouldn't be made. Similarly, if the page has embedded Flash that "
+"plays an important role, so that a person would be missing something "
+"important if the videos do not play, the link should not be made."
+msgstr ""
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"The subject of the reference will also play a role in determining how "
+"problematic a reference is. If the software is already very popular, it's "
+"unlikely that a basic mention of it will be news to the reader. Some "
+"examples of proprietary software which are common enough to be considered "
+"“well-known” are major operating systems (Windows, Mac OS, Sun "
+"OS, HP-UX) and primary common applications such as Office, Internet "
+"Explorer, Photoshop, Acrobat Reader, and Flash."
+msgstr ""
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"GNU software project pages feel the full force of this policy. Proprietary "
+"software should only be mentioned when the software provides support for it, "
+"or to compare it against the features of well-known proprietary software. "
+"For example, the following text—and not much else—would be "
+"acceptable:"
+msgstr ""
+
+#. type: Content of: <dl><dd><blockquote><p>
+msgid ""
+"w3 is a web browser for GNU Emacs, similar to Internet Explorer. It can run "
+"on all platforms GNU Emacs runs on, including GNU/Linux, proprietary Unix "
+"systems, and Windows."
+msgstr ""
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"Links which appear in other areas, such as the testimonials or philosophy "
+"pages, as well as links to user groups may discuss such software in greater "
+"detail, but links and other methods of encouragement to “learn "
+"more” should still be avoided."
+msgstr ""
+
+#. type: Content of: <dl><dt>
+msgid "How does the page compare free software to open source?"
+msgstr ""
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"Almost all pages which have links on our site should, at the very least, "
+"treat free software and open source equally. Failure to do so—whether "
+"it be by omitting free software or by implying that open source is "
+"superior—is usually unacceptable. GNU software project pages should "
+"have little mention of open source. The GNOME page used to provide a good "
+"example of a tactful way to do it:"
+msgstr ""
+
+#. type: Content of: <dl><dd><blockquote><p>
+msgid ""
+"GNOME is part of the GNU Project, and is free software (sometimes referred "
+"to as open source software)."
+msgstr ""
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"Any exceptions to this rule should be apparent from the context. For "
+"instance, user groups pages may talk in greater detail about open source; we "
+"state on the user groups page, “As with our links page, the FSF is not "
+"responsible for the contents of other websites, or how up-to-date their "
+"information is.”"
+msgstr ""
+
+#. type: Content of: <dl><dt>
+msgid "How does the page treat the GNU Project?"
+msgstr ""
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"Pages which we link to should treat the GNU Project well. The primary thing "
+"to look out for in this regard is whether the page calls the system "
+"GNU/Linux or just “Linux.” GNU software project and user group "
+"pages should almost never, if ever, fail to do this. Again, exceptions for "
+"other pages should be apparent from context."
+msgstr ""
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"That said, certain parts of a page should not be considered against these "
+"criteria. For example, suppose we were to make a link to a page on a free "
+"software news site. Any advertisements or reader comments attached to the "
+"article would not be considered when determining whether it met or linking "
+"guidelines, since they're understood to be the opinion of their individual "
+"authors. Similarly, on user group pages, the contents of forums and wiki "
+"pages should not hold weight in these regards."
+msgstr ""
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"Finally, some sites are understood to always have exception with most of "
+"these guidelines. These sites are usually about issues which are important, "
+"but somewhat peripheral, to the free software movement. Several times we "
+"have linked to the Electronic Frontier Foundation's site, even though they "
+"encourage the use of Flash and talked exclusively about open source "
+"software. It's generally understood that since these pages are not "
+"primarily about free software, the policies do not hold full force for them."
+msgstr ""
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"As a final explanation (coming from RMS): Even for making links from "
+"www.gnu.org, we do not <em>require</em> that people call the system "
+"GNU/Linux or use the term “free software” rather than "
+"“open source.” We do, however, require that they not promote any "
+"nonfree software."
+msgstr ""
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"If all this seems complicated, that's because, unfortunately, it is. Don't "
+"worry; a knack for it comes with time and experience. You may mis-evaluate "
+"a few pages as you're learning to get a feel for what's acceptable and what "
+"isn't; please don't hesitate to get a second opinion from a more experienced "
+"webmaster, or someone in charge like the Chief Webmaster or RMS. New "
+"exceptions will always come up; keep an open mind to that possibility and be "
+"ready to handle them properly."
+msgstr ""
+
+#. type: Content of: <h3>
+msgid "Appendix 2 - Working with Web CVS Repositories"
+msgstr ""
+
+#. type: Content of: <h4>
+msgid "Basic CVS commands"
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"Before the initial checkout, set the environment variable "
+"<code>CVS_RSH=ssh</code>."
+msgstr ""
+
+#. type: Content of: <ul><li><p>
+msgid ""
+"If you have write access to www, check out the main www repository with your "
+"Savannah login:"
+msgstr ""
+
+#. type: Content of: <ul><li><pre>
+#, no-wrap
+msgid "cvs -z3 -d:ext:<username>@cvs.savannah.gnu.org:/web/www co www\n"
+msgstr ""
+
+#. type: Content of: <ul><li><p>
+msgid ""
+"You will get a working directory, <code>www</code>, with the same structure "
+"as our main website."
+msgstr ""
+
+#. type: Content of: <ul><li><p>
+msgid ""
+"If you don't have write access to www, you can still make an anonymous "
+"checkout of www:"
+msgstr ""
+
+#. type: Content of: <ul><li><pre>
+#, no-wrap
+msgid "cvs -z3 -d:pserver:address@hidden:/web/www co www\n"
+msgstr ""
+
+#. type: Content of: <ul><li><p>
+msgid "Check out the web repository of the fooproject:"
+msgstr ""
+
+#. type: Content of: <ul><li><pre>
+#, no-wrap
+msgid ""
+"cvs -z3 -d:ext:<username>@cvs.savannah.gnu.org:/web/fooproject co "
+"fooproject\n"
+msgstr ""
+
+#. type: Content of: <ul><li><p>
+msgid ""
+"You will get a working directory, <code>fooproject</code>, with the same "
+"structure as the <code>www/software/fooproject</code> subdirectory. Note, "
+"however, that the fooproject and www repositories are independent. The "
+"working directories can be anywhere in your filesystem."
+msgstr ""
+
+#. type: Content of: <ul><li><p>
+msgid ""
+"<em>Webmasters, please read <a "
+"href=\"/server/standards/README.webmastering.html#gnupackages\">Web pages "
+"for official GNU software</a> before committing anything to the web "
+"repository of a software project.</em>"
+msgstr ""
+
+#. type: Content of: <ul><li><p>
+msgid "Add a file or directory:"
+msgstr ""
+
+#. type: Content of: <ul><li><pre>
+#, no-wrap
+msgid "cvs add foo\n"
+msgstr ""
+
+#. type: Content of: <ul><li><p>
+msgid "Update before you edit a file:"
+msgstr ""
+
+#. type: Content of: <ul><li><pre>
+#, no-wrap
+msgid "cvs update -P foo\n"
+msgstr ""
+
+#. type: Content of: <ul><li><p>
+msgid "Check the changes you are going to commit:"
+msgstr ""
+
+#. type: Content of: <ul><li><pre>
+#, no-wrap
+msgid "cvs diff -U2 foo\n"
+msgstr ""
+
+#. type: Content of: <ul><li><p>
+msgid ""
+"Perform the commit (no need for <code>cvs add</code> if the file is already "
+"in the repository):"
+msgstr ""
+
+#. type: Content of: <ul><li><pre>
+#, no-wrap
+msgid "cvs commit foo\n"
+msgstr ""
+
+#. type: Content of: <ul><li><p>
+msgid ""
+"This will open a text editor where you should enter a log message. The "
+"commit will occur upon saving the message."
+msgstr ""
+
+#. type: Content of: <ul><li><p>
+msgid ""
+"Without being excessively verbose, log messages should describe as clearly "
+"as possible the nature of the commit, including any related ticket numbers "
+"from RT to allow future historians to understand why your changes were made."
+msgstr ""
+
+#. type: Content of: <ul><li><p>
+msgid ""
+"Whenever possible, changes to multiple files that share the same log message "
+"should be bundled in one commit. Do not bundle multiple unrelated changes in "
+"one commit."
+msgstr ""
+
+#. type: Content of: <ul><li><p>
+msgid ""
+"The changes (except to <a href=\"#symlinks\">.symlinks files</a>) should be "
+"visible on www.gnu.org within minutes."
+msgstr ""
+
+#. type: Content of: <p>
+msgid ""
+"For further details on CVS, such as reverting to a previous version, or "
+"looking at the <code>diff</code> output of a particular change, see the <a "
+"href=\"/software/trans-coord/manual/cvs/\">CVS documentation</a>."
+msgstr ""
+
+#. type: Content of: <h4>
+msgid "Symbolic links"
+msgstr ""
+
+#. type: Content of: <p>
+msgid ""
+"Since CVS is not able to handle symbolic links directly, a separate "
+"mechanism has been implemented to allow webmasters to maintain symbolic "
+"links, as follows. (Actual symbolic links are no longer created on "
+"www.gnu.org; mod_rewrite rules are used instead. But we'll keep this "
+"discussion talking about symlinks since it is easier to understand that "
+"way.)"
+msgstr ""
+
+#. type: Content of: <p>
+msgid ""
+"Being a symlink means that relative links from the linked page may break "
+"when the symlink jumps to a different directory."
+msgstr ""
+
+#. type: Content of: <p>
+msgid ""
+"Special files, named <code>.symlinks</code>, when committed to the CVS tree, "
+"are interpreted as specifications to build symbolic links. Each symbolic "
+"link specification from the .symlinks file is honored, i.e., the symbolic "
+"link is created if it does not exist yet. If a symbolic link is found in the "
+"directory and is not listed in the .symlinks file, it is removed."
+msgstr ""
+
+#. type: Content of: <p>
+msgid "The .symlinks files obey the <code>ln -s</code> format, as described
below:"
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid "Lines starting with a sharp sign (“#”) are ignored."
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"Lines that do not contain two strings separated by white space are silently "
+"ignored."
+msgstr ""
+
+#. type: Content of: <p>
+msgid "Here is an example of a .symlinks file:"
+msgstr ""
+
+#. type: Content of: <pre>
+#, no-wrap
+msgid ""
+"# Make a link named l.html to a target t.html.\n"
+"# Strictly equivalent to ln -s t.html l.html:\n"
+"t.html l.html\n"
+msgstr ""
+
+#. type: Content of: <p>
+msgid ""
+"On each line the first file name must be a relative path name to an existing "
+"file. The second file name may not contain any slash; it is the name of the "
+"symbolic link to be created in the present directory. For instance, if a "
+"page named <code>DIR.html</code> exists in the <code>/DIR</code> directory, "
+"and <code>index.html</code> does not exist, <code>/DIR/.symlinks</code> "
+"should contain a line like this:"
+msgstr ""
+
+#. type: Content of: <pre>
+#, no-wrap
+msgid "DIR.html index.html\n"
+msgstr ""
+
+#. type: Content of: <p>
+msgid ""
+"The <code>ln -s</code> analogy accounts for only part of the story. 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 "
+"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 "
+"<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>."
+msgstr ""
+
+#. type: Content of: <p>
+msgid ""
+"These days, the .symlinks handling happens on www.gnu.org via a cron job "
+"that runs twice an hour. Webmasters do not have access to it."
+msgstr ""
+
+#. type: Content of: <h4>
+msgid ".htaccess and redirections"
+msgstr ""
+
+#. type: Content of: <p>
+msgid ""
+"To browsers, the symbolic links in the previous section are "
+"indistinguishable from the actual file. You may want an actual redirection "
+"in some cases. You can do this either in the top-level control file "
+"<code>.htaccess</code>, or by using something like this as the file to be "
+"redirected:"
+msgstr ""
+
+#. type: Content of: <p>
+msgid ""
+"<code> <meta http-equiv=\"refresh\" content=\"0; "
+"url=http://www.gnu.org/target\"> </code>"
+msgstr ""
+
+#. type: Content of: <h4>
+msgid "Scripts"
+msgstr ""
+
+#. type: Content of: <p>
+msgid ""
+"A <a href=\"/server/source/source.html\">description of scripts and "
+"software</a> used on www.gnu.org is available. Please read it before "
+"writing any scripts, and also update it as needed if you have write access "
+"to www."
+msgstr ""
+
+#. type: Content of: <h4>
+msgid "System administrators"
+msgstr ""
+
+#. type: Content of: <p>
+msgid ""
+"The system administrators for GNU change from time to time. Please email "
+"the sysadmin list <address@hidden> rather than an individual, unless "
+"you have a specific reason to do so."
+msgstr ""
+
+#. type: Content of: <h3>
+msgid "Useful Resources"
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid "Outside gnu.org:"
+msgstr ""
+
+#. type: Content of: <ul><li><ul><li>
+msgid ""
+"We follow the guidelines of the <a "
+"href=\"https://www.anybrowser.org/campaign/\";>Best Viewed with Any "
+"Browser</a> campaign."
+msgstr ""
+
+#. type: Content of: <ul><li><ul><li>
+msgid ""
+"Basic info on the web and its technical specifications can be found at <a "
+"href=\"https://www.w3.org/\";>The World Wide Web Consortium</a>."
+msgstr ""
+
+#. type: Content of: <ul><li><ul><li>
+msgid ""
+"Use of the <a href=\"https://www.cs.tcd.ie/15445/UG.HTML\";>ISO</a> standard "
+"for the <a href=\"https://www.w3.org/MarkUp/\";>Hypertext Markup Language "
+"(HTML)</a> allows for consistent backwards compatibility among web user "
+"agents."
+msgstr ""
+
+#. type: Content of: <ul><li><ul><li>
+msgid ""
+"The GNU web server follows the w3.org <a "
+"href=\"https://www.w3.org/Provider/Style/Overview.html\";>Style Guide</a>."
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid "On gnu.org:"
+msgstr ""
+
+#. type: Content of: <ul><li><ul><li>
+msgid ""
+"<a href=\"/server/standards/gnu-website-guidelines.html\">The GNU Website "
+"Guidelines</a>;"
+msgstr ""
+
+#. type: Content of: <ul><li><ul><li>
+msgid ""
+"Guidelines for <a href=\"/server/standards/README.editors.html\">Web Page "
+"Creation</a> at www.gnu.org;"
+msgstr ""
+
+#. type: Content of: <ul><li><ul><li>
+msgid ""
+"<a href=\"/software/texinfo/manual/texinfo/html_node/Tips.html\"> Appendix B "
+"Tips and Hints</a>, and other style tips in the <a "
+"href=\"/software/texinfo/manual/texinfo/\">Texinfo Manual</a>;"
+msgstr ""
+
+#. type: Content of: <ul><li><ul><li>
+msgid ""
+"<a href=\"/accessibility/accessibility.html\">GNU Accessibility "
+"Statement</a>;"
+msgstr ""
+
+#. type: Content of: <ul><li><ul><li>
+msgid ""
+"<a href=\"/server/standards/README.webmastering.html\">GNU Webmastering "
+"Guidelines;</a>"
+msgstr ""
+
+#. type: Content of: <ul><li><ul><li>
+msgid ""
+"Guide to <a "
+"href=\"/server/standards/README.translations.html\">translating</a> GNU web "
+"pages into other languages;"
+msgstr ""
+
+#. type: Content of: <ul><li><ul><li>
+msgid ""
+"<a href=\"/software/trans-coord/manual/gnun/html_node/Webmaster-Tips.html\"> "
+"Tips for webmasters</a> to make translators' job easier;"
+msgstr ""
+
+#. type: Content of: <ul><li><ul><li>
+msgid ""
+"<a href=\"//savannah.gnu.org/maintenance/FrontPage/\">Documentation for "
+"Savannah</a>, the SourceForge clone dedicated to the GNU Project;"
+msgstr ""
+
+#. type: Content of: <ul><li><ul><li>
+msgid ""
+"<a "
+"href=\"//cvs.savannah.gnu.org/viewvc/gnumaint/README?root=womb&view=markup\">
"
+"README</a> for the <code>/gnumaint</code> directory in the <code>womb</code> "
+"Savannah group (those files are used by <a href=\"/prep/maintain/\">GNU "
+"maintainer administrators</a> to update the <code>/*/allgnupkgs.html</code> "
+"files in www);"
+msgstr ""
+
+#. type: Content of: <ul><li><ul><li>
+msgid ""
+"Here is the <a href=\"/server/tasks.html\">help</a> we need with our <a "
+"href=\"/server/server.html\">web server</a>."
+msgstr ""
+
+#. TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.
+#. type: Content of: <div>
+msgid "*GNUN-SLOT: TRANSLATOR'S NOTES*"
+msgstr ""
+
+#. type: Content of: <div><div><p>
+msgid ""
+"Please send general FSF & GNU inquiries to <a "
+"href=\"mailto:address@hidden";><address@hidden></a>. There are also <a "
+"href=\"/contact/\">other ways to contact</a> the FSF. Broken links and "
+"other corrections or suggestions can be sent to <a "
+"href=\"mailto:address@hidden";><address@hidden></a>."
+msgstr ""
+
+#. TRANSLATORS: Ignore the original text in this paragraph,
+#. replace it with the translation of these two:
+#
+#. We work hard and do our best to provide accurate, good quality
+#. translations. However, we are not exempt from imperfection.
+#. Please send your comments and general suggestions in this regard
+#. to <a href="mailto:address@hidden";>
+#
+#. <address@hidden></a>.</p>
+#
+#. <p>For information on coordinating and submitting translations of
+#. our web pages, see <a
+#. href="/server/standards/README.translations.html">Translations
+#. README</a>.
+#. type: Content of: <div><div><p>
+msgid ""
+"Please see the <a "
+"href=\"/server/standards/README.translations.html\">Translations README</a> "
+"for information on coordinating and submitting translations of this article."
+msgstr ""
+
+#. type: Content of: <div><p>
+msgid ""
+"Copyright © 2010, 2013, 2014, 2015, 2016, 2017, 2018 Free Software "
+"Foundation, Inc."
+msgstr ""
+
+#. type: Content of: <div><p>
+msgid ""
+"This page is licensed under a <a rel=\"license\" "
+"href=\"http://creativecommons.org/licenses/by-nd/4.0/\";>Creative Commons "
+"Attribution-NoDerivatives 4.0 International License</a>."
+msgstr ""
+
+#. TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.
+#. type: Content of: <div><div>
+msgid "*GNUN-SLOT: TRANSLATOR'S CREDITS*"
+msgstr ""
+
+#. timestamp start
+#. type: Content of: <div><p>
+msgid "Updated:"
+msgstr ""
Index: po/gnu-website-guidelines.translist
===================================================================
RCS file: po/gnu-website-guidelines.translist
diff -N po/gnu-website-guidelines.translist
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ po/gnu-website-guidelines.translist 9 Sep 2018 12:27:45 -0000 1.1
@@ -0,0 +1,10 @@
+<!-- begin translist file -->
+<!--#set var="TRANSLATION_LIST"
+value='<div id="translations">
+<p>
+<span dir="ltr" class="original"><a lang="en" hreflang="en"
href="/server/standards/gnu-website-guidelines.en.html">English</a> [en]</span>
+</p>
+</div>' -->
+<link rel="alternate" type="text/html"
href="/server/standards/gnu-website-guidelines.html" hreflang="x-default" />
+<link rel="alternate" type="text/html" lang="en" hreflang="en"
href="/server/standards/gnu-website-guidelines.en.html" title="English" />
+<!-- end translist file -->
- www/server/standards gnu-website-guidelines.htm...,
GNUN <=