# 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 <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: gnu-website-guidelines.html\n"
"POT-Creation-Date: 2025-05-06 09:26+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\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: <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: <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 web designs that look great under "
"one version of one browser, and ugly under many others.  Of course, please "
"don't install any of the proprietary web browsers available if you don't "
"already use them anyway."
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:gnu@gnu.org\">&lt;gnu@gnu.org&gt;</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 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: <ul><li>
msgid ""
"Generally, the use of JavaScript is not allowed.  Exceptions to this need to "
"be reviewed and approved by the Chief GNUisance on a case-by-case basis."
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=\"/server/standards/boilerplate-source.txt\"> 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 &ldquo;Posted in 20XX without FSF permission to "
"modify&rdquo; 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:webmasters@gnu.org\">&lt;webmasters@gnu.org&gt;</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 ""
"The term &ldquo;nonfree&rdquo; is preferred over &ldquo;non-free&rdquo;; "
"likewise, &ldquo;noncommercial&rdquo; over &ldquo;non-commercial.&rdquo;"
msgstr ""

#. type: Content of: <ul><li><ul><li>
msgid ""
"In ordinary text, HTML entities "
"&ldquo;<code>&amp;ldquo;</code>&hellip;<code>&amp;rdquo;</code>&rdquo; and "
"&ldquo;<code>&amp;lsquo;</code>&hellip;<code>&amp;rsquo;</code>&rdquo; 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 id=\"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 and descriptive name; the special 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><var>article</var>.html</code>, and its translations "
"<code><var>article</var>.<var>lang</var>.html</code>&mdash; "
"<code><var>lang</var></code> should contain the two-letter language code "
"from <a href=\"//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 (lowercase).  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 ""
"Check if the linked host supports both HTTPS and HTTP and use "
"protocol-relative URLs (e.g. <code>//www.example.org</code>) if it does."
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 and double-check that the anchor actually works."
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 ""
"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><p>
msgid "Cite people with e-mail addresses this way:"
msgstr ""

#. type: Content of: <ul><li><p>
msgid ""
"<code> &lt;a href=\"//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>"
msgstr ""

#. type: Content of: <ul><li><p>
msgid "which browsers display this way:"
msgstr ""

#. type: Content of: <ul><li><p>
msgid ""
"<a href=\"//www.stallman.org/\">Richard Stallman</a> <a "
"href=\"mailto:rms@gnu.org\">&lt;rms@gnu.org&gt;</a>"
msgstr ""

#. type: Content of: <ul><li><p>
msgid ""
"It is less confusing to the user, because it's clear what is a 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: <ul><li>
msgid ""
"When embedding static resources like videos that are not in the "
"<code>www</code> CVS repository along with the rest of the www.gnu.org "
"pages, it's important that the URL used to embed the asset be a subdomain of "
"gnu.org, so that the Third-party Request Blocker add-on shipped with GNU "
"IceCat would not consider it a third-party asset which it would prevent from "
"being loaded.  For example, when embedding videos from FSF campaigns on "
"www.gnu.org, use <code>static.gnu.org</code> rather than "
"<code>static.fsf.org</code>.  Both of these addresses have been set to point "
"to the same machine, so they can be used interchangeably."
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=\"//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=\"//www.w3.org/TR/html401/struct/global.html#h-7.1\">required "
"elements</a> such as <code>&lt;html&gt;</code>, <code>&lt;head&gt;</code>, "
"<code>&lt;title&gt;</code>, <code>&lt;body&gt;</code>, etc. when using "
"(X)HTML, and always include the appropriate DTD or Schema reference.  This "
"appeases overly pedantic web 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 &lt;head&gt; element should contain this line:"
msgstr ""

#. type: Content of: <ul><li><p>
msgid "<code>&lt;link rel=\"author\" href=\"mailto:webmasters@gnu.org\"&gt;</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, &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.  Repeating the main heading in the &lt;title&gt; 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 &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>."
msgstr ""

#. type: Content of: <ul><li>
msgid "Acronyms/abbreviations:"
msgstr ""

#. type: Content of: <ul><li><ul><li>
msgid ""
"Never use <code>&lt;acronym&gt;</code>: HTML&nbsp;5 obsoletes it in favor of "
"<code>&lt;abbr&gt;</code>."
msgstr ""

#. type: Content of: <ul><li><ul><li>
msgid ""
"Don't use <code>&lt;abbr&gt;</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>&lt;abbr "
"title=\"Expanded Abbreviation\"&gt;EA&lt;/abbr&gt;</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=\"//www.w3.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 &ldquo;skip link&rdquo; 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 "
"&ldquo;boilerplate&rdquo;) 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=\"/server/standards/boilerplate-source.txt\"> original source</a> of "
"the boilerplate instead, and follow the instructions in it."
msgstr ""

#. type: Content of: <ul><li>
msgid ""
"The XHTML templated pages must follow the <a "
"href=\"//www.w3.org/TR/xhtml1/\">XHTML-1.0 guidelines</a>."
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 "
"<code>/layout.css</code>; it covers most of our use cases."
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 ""
"In addition to <code>/layout.css</code>, some pages have specialized "
"stylesheets: <code>/graphics/graphics.css</code> for the GNU Art section, "
"and <code>/side-menu.css</code> for the Malware and Education sections."
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 &lt;style&gt; 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: <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 <code>/mini.css</code> (the Yahoo "
"User Interface reset and base stylesheet, version&nbsp;2), as these pages "
"are usually very basic, plain pages with little or no formatting."
msgstr ""

#. type: Content of: <ul><li>
msgid "There are dedicated stylesheets for software manuals.  The main ones are:"
msgstr ""

#. type: Content of: <ul><li><ul><li>
msgid "<code>/style.css</code>;"
msgstr ""

#. type: Content of: <ul><li><ul><li>
msgid ""
"<a href=\"/software/gnulib/manual.css\">gnulib.css</a>, which imports "
"<code>/style.css</code> and adds a few more definitions; it is used by "
"<code>gendocs.sh</code> to <a "
"href=\"/prep/maintain/html_node/Invoking-gendocs_002esh.html\"> regenerate "
"Texinfo manuals</a>."
msgstr ""

#. type: Content of: <ul><li>
msgid ""
"Translators maintain stylesheets (<code>/style.<var>lang</var>.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, to ensure indexability "
"by search engines and accessibility.  For instance:"
msgstr ""

#. type: Content of: <ul><li><p>
msgid ""
"<code>&lt;img src=\"/graphics/*.jpg\" alt=\"&amp;nbsp;[DESCRIPTIVE "
"TEXT]&amp;nbsp;\"&gt;</code>"
msgstr ""

#. type: Content of: <ul><li>
msgid ""
"We add the non-breaking spaces (&amp;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 PO4A/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><p>
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>&lt;img src=\"/graphics/*.jpg\" alt=\"&amp;nbsp;[DESCRIPTIVE "
"TEXT]&amp;nbsp;\" style=\"width: 10em; height: auto;\" /&gt;</code>"
msgstr ""

#. type: Content of: <ul><li><p>
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.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 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>&lt;div class=\"pict wide\" style=\"width: 25em\"&gt;&lt;img "
"src=\"/graphics/*.jpg\" alt=\"&amp;nbsp;[DESCRIPTIVE TEXT]&amp;nbsp;\" "
"/&gt;&lt;/div&gt;</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 "&nbsp;[Image of the Head of a GNU]&nbsp;"
msgstr ""

#. type: Content of: <ul><li><p>
msgid "</a>"
msgstr ""

#. type: Content of: <ul><li><pre>
#, no-wrap
msgid ""
"&lt;p class=\"imgleft\"&gt;\n"
"&lt;a href=\"/graphics/agnuhead.html\"&gt;\n"
"&lt;img src=\"/graphics/gnu-head-sm.jpg\"\n"
"     alt=\"&nbsp;[Image of the Head of a GNU]&nbsp;\"\n"
"     style=\"width: 8em\" /&gt;&lt;/a&gt;\n"
"&lt;/p&gt;\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&mdash;all pages which are "
"given links on our site&mdash;are friendly to the free software movement.  "
"Some pages will obviously not meet such standards; if the site flames the "
"Free Software Foundation and/or the GNU Project, 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&mdash;for example, included in a newsfeed on the main "
"page&mdash;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 &ldquo;promotion&rdquo; 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 &ldquo;Windows&rdquo; and "
"&ldquo;Microsoft Windows XP Home Edition.&rdquo;"
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 "
"&ldquo;well-known&rdquo; are major operating systems (Windows, Mac OS, Sun "
"OS, HP-UX) and primary common applications such as Office, Internet "
"Explorer, Chrome, 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 GNU software provides support for "
"it, or to compare it against the features of well-known proprietary "
"software.  For example, the following text&mdash;and not much "
"else&mdash;would be acceptable:"
msgstr ""

#. type: Content of: <dl><dd><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 or third party organizations, may "
"discuss such software in greater detail, but links and other methods of "
"encouragement to &ldquo;learn more&rdquo; 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&mdash;whether "
"it be by omitting free software or by implying that open source is "
"superior&mdash;is usually unacceptable.  GNU software project pages should "
"have little mention of open source.  Here's an example of a tactful way to "
"do it:"
msgstr ""

#. type: Content of: <dl><dd><p>
msgid ""
"XYZ is part of the GNU Project, and is free/libre 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 group pages or pages of organizations listed in links.html "
"may talk in greater detail about open source; we state on those pages, "
"&ldquo;The FSF is not responsible for the contents of other websites, or how "
"up-to-date their information is.&rdquo;"
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 &ldquo;Linux.&rdquo; GNU software projects 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 our linking "
"guidelines, since they're understood to be the opinion of their individual "
"authors.  Similarly, on user group or third party organization 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 "
"encouraged the use of Flash, talked exclusively about open source software, "
"and do not advocate users' freedom to redistribute and change 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 &ldquo;free software&rdquo; rather than "
"&ldquo;open source.&rdquo; 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: <dl><dt>
msgid ""
"Does the page work even if the user's browser refuses to run JavaScript "
"code?"
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 ""
"In some cases, however, we can still refer to such pages and resources by "
"using workarounds to bypass the JavaScript requirement."
msgstr ""

#.  Add link to future article as follows: (See also 
#. <a href="/DIR/whats-wrong-with-github.html">
#. What's Wrong with GitHub</a>.)
#. type: Content of: <dl><dd><p>
msgid ""
"One possibility is to use an instance of <a "
"href=\"https://codeberg.org/gothub/gothub\">GotHub</a>&mdash;a free software "
"frontend for GitHub that works without JavaScript&mdash;to replace links to "
"pages and resources hosted at GitHub, a website that requires running "
"nonfree JavaScript to be usable as intended."
msgstr ""

#. type: Content of: <dl><dd><p>
msgid ""
"Currently (March 2024), GotHub is not actively maintained and it lacks some "
"functionalities. For example, it doesn't offer a way to browse repositories "
"or download the source code without visiting the GitHub website, and it "
"doesn't provide a git clone URL. Still, GotHub is helpful for some "
"usages. For example, it works well for linking to individual files."
msgstr ""

#. type: Content of: <dl><dd><p>
msgid ""
"<strong>* Software packages</strong>. A useful file for software projects is "
"the README file; it contains a description of the package, which is usually "
"the first thing a user wants to see before attempting to fetch the "
"repository. We have applied this solution several times in www.gnu.org; for "
"example, we replaced this:"
msgstr ""

#. type: Content of: <dl><dd><p>
msgid ""
"<span "
"class=\"bad\"><code><del>https://github.com/pbatard/rufus</del></code></span>"
msgstr ""

#. type: Content of: <dl><dd><p>
msgid "with this:"
msgstr ""

#. type: Content of: <dl><dd><p>
msgid ""
"<span "
"class=\"good\"><code>https://gothub.projectsegfau.lt/pbatard/rufus</code></span>."
msgstr ""

#. type: Content of: <dl><dd><p>
msgid ""
"Another solution is to link directly to the tarball of a tagged commit on "
"GitHub. The drawback of this method is that it is not very useful for "
"tracking the project over time."
msgstr ""

#. type: Content of: <dl><dd><p>
msgid ""
"<strong>* Graphics, documents, manuals</strong>. These resources are "
"sometimes hosted in user pages that do not require JavaScript to be fully "
"usable, even when they are hosted inside an area of the GitHub website. In "
"these cases, it is okay to link to such pages. For example, we replaced a "
"link to"
msgstr ""

#. type: Content of: <dl><dd><p>
msgid ""
"<span "
"class=\"bad\"><code><del>https://github.com/foocorp/gnu-fm/blob/main/clients/meego/librefm/src/librefm-logo.png</del></code></span>"
msgstr ""

#. type: Content of: <dl><dd><p>
msgid "with a link to"
msgstr ""

#. type: Content of: <dl><dd><p>
msgid ""
"<span "
"class=\"good\"><code>https://raw.githubusercontent.com/foocorp/gnu-fm/main/clients/meego/librefm/src/librefm-logo.png</code> "
"</span>."
msgstr ""

#. type: Content of: <dl><dd><p>
msgid "And we have links to documents such as"
msgstr ""

#. type: Content of: <dl><dd><p>
msgid ""
"<span "
"class=\"good\"><code>https://raw.githubusercontent.com/scootergrisen/licenser/master/gpl-3.0.da.txt</code></span>."
msgstr ""

#. type: Content of: <dl><dd><p>
msgid ""
"Sometimes a resource may be hosted in more than one acceptable place.  It "
"can be a personal page in GitHub or somewhere else, or in some unrelated "
"website. When evaluating which one to choose, consider factors such as: "
"What's the status of the document? Is it a final version or is it likely to "
"be modified anytime soon? Is the URL reliably stable, or is it likely to be "
"moved?"
msgstr ""

#. type: Content of: <dl><dd><p>
msgid ""
"For example, in the past we had the case of a manual that was listed in "
"other-free-books.html with this URL:"
msgstr ""

#. type: Content of: <dl><dd><p>
msgid ""
"<span "
"class=\"bad\"><code><del>https://github.com/davidam/orgguide-es</del></code></span>."
msgstr ""

#. type: Content of: <dl><dd><p>
msgid "At the time, we had three possibilitites to replace that bad link:"
msgstr ""

#. type: Content of: <dl><dd><p>
msgid "1. GotHub"
msgstr ""

#. type: Content of: <dl><dd><p>
msgid ""
"<span "
"class=\"good\"><code>https://gothub.projectsegfau.lt/raw/davidam/davidam.github.io/master/docu/orgguide.es.pdf</code></span>"
msgstr ""

#. type: Content of: <dl><dd><p>
msgid "2. Author's personal space at GitHub"
msgstr ""

#. type: Content of: <dl><dd><p>
msgid ""
"<span "
"class=\"good\"><code>https://raw.githubusercontent.com/davidam/davidam.github.io/master/docu/orgguide.es.pdf</code> "
"</span>"
msgstr ""

#. type: Content of: <dl><dd><p>
msgid "3. Publisher/Bookstore"
msgstr ""

#. type: Content of: <dl><dd><p>
msgid ""
"<span "
"class=\"good\"><code>https://traficantes.net/sites/default/files/pdfs/orgguide.es_.pdf</code></span>"
msgstr ""

#. type: Content of: <dl><dd><p>
msgid ""
"We decided for the third one, since it didn't seem that the manual was "
"likely to be updated to a new version, and <cite>Traficantes de "
"Sueños</cite> is an established, well-known publisher."
msgstr ""

#. type: Content of: <dl><dd><p>
msgid ""
"Issue trackers on GitHub can be viewed and browsed without JavaScript, but "
"active participation entails an account that can't be created without "
"running nonfree JavaScript. It's okay to link to closed issues, like we did "
"for"
msgstr ""

#. type: Content of: <dl><dd><p>
msgid ""
"<span "
"class=\"good\"><code>https://github.com/w3c/fingerprinting-guidance/issues/8</code></span>."
msgstr ""

#. type: Content of: <dl><dd><p>
msgid ""
"Another possibility for closed issues is to link to the archived page at the "
"Wayback Machine."
msgstr ""

#. type: Content of: <dl><dd><p>
msgid ""
"Lastly, consider the possibility of talking to maintainers and authors to "
"explain the problem. Hopefully they will move the repo somewhere else or "
"post the material in a place we can link to."
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 "For reference manual, execute <kbd>info cvs</kbd>."
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 ""
"<kbd>cvs -z3 -d:ext:<var>username</var>@cvs.savannah.gnu.org:/web/www co "
"www</kbd>\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 ""
"<kbd>cvs -z3 -d:pserver:anonymous@cvs.savannah.gnu.org:/web/www co "
"www</kbd>\n"
msgstr ""

#. type: Content of: <ul><li><p>
msgid "Check out the web repository of the <var>fooproject</var>:"
msgstr ""

#. type: Content of: <ul><li><pre>
#, no-wrap
msgid ""
"<kbd>cvs -z3 "
"-d:ext:<var>username</var>@cvs.savannah.gnu.org:/web/<var>fooproject</var> "
"\\\n"
"         co <var>fooproject</var></kbd>\n"
msgstr ""

#. type: Content of: <ul><li><p>
msgid ""
"You will get a working directory, <code><var>fooproject</var></code>, with "
"the same structure as the <code>www/software/<var>fooproject</var></code> "
"subdirectory.  Note, however, that the <var>fooproject</var> 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 "<kbd>cvs add <var>foo</var></kbd>\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 "<kbd>cvs update -P <var>foo</var></kbd>\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 "<kbd>cvs diff -U2 <var>foo</var></kbd>\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 "<kbd>cvs commit <var>foo</var></kbd>\n"
msgstr ""

#. type: Content of: <ul><li><p>
msgid ""
"This will open a text editor where you should enter a log message.  It will "
"also show you a list of all files to be committed. The commit will occur "
"upon exiting the editor."
msgstr ""

#. type: Content of: <ul><li><p>
msgid "Alternatively:"
msgstr ""

#. type: Content of: <ul><li><pre>
#, no-wrap
msgid "<kbd>cvs commit -m \"Log message\" <var>foo</var></kbd>\n"
msgstr ""

#. type: Content of: <ul><li><p>
msgid ""
"This option is somewhat less safe, as it doesn't show you a list of the "
"files to be committed. Moreover, a minor typo in the log message (omitting "
"the space between the message and the filename) may result in committing "
"<em>all</em> modified files in a directory, because the filename will not be "
"treated as an argument, but as part of the message."
msgstr ""

#. type: Content of: <ul><li><p>
msgid ""
"<strong>It's important to write good commit log messages to help project "
"members and future generations <em>find</em> specific changes in a given "
"file and <em>understand</em> why your changes were made.</strong>"
msgstr ""

#. type: Content of: <ul><li><div><ul><li>
msgid ""
"Without being excessively verbose, log messages should describe as clearly "
"as possible the nature of the commit."
msgstr ""

#. type: Content of: <ul><li><div><ul><li>
msgid ""
"<span class=\"good\">Good: <code>Update link to "
"<var>XYZ</var>.</code></span>"
msgstr ""

#. type: Content of: <ul><li><div><ul><li>
msgid "<span class=\"bad\">Bad: <code><del>Update a link.</del></code></span>"
msgstr ""

#. type: Content of: <ul><li><div><ul><li>
msgid ""
"Always include a reference to any related RT tickets and/or mailing lists "
"discussions. If no such reference exists, mention the name of the person(s) "
"who authorized the change."
msgstr ""

#. type: Content of: <ul><li><div><ul><li>
msgid ""
"For dates, we use either the American-style notation "
"(Sept.&nbsp;27,&nbsp;2023) or the ISO 8601 international standard format "
"(2023-09-27)."
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 (&ldquo;#&rdquo;) 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><var>dir</var>.html</code> exists in the "
"<code>/<var>dir</var></code> directory, and <code>index.html</code> does not "
"exist, <code>/<var>dir</var>/.symlinks</code> should contain a line like "
"this:"
msgstr ""

#. type: Content of: <pre>
#, no-wrap
msgid "<var>dir</var>.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=\"#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><var>page</var>.<var>ll</var>.html</code> or "
"<code><var>page</var>.<var>ll</var>-<var>cc</var>.html</code>, where "
"<var>ll</var> and <var>cc</var> 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> &lt;meta http-equiv=\"refresh\" content=\"0; "
"url=https://www.gnu.org/<var>target</var>\"&gt; </code>"
msgstr ""

#. type: Content of: <h4>
msgid "Server-side 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 &lt;sysadmin@gnu.org&gt; 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=\"//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=\"//www.w3.org/\">The World Wide Web Consortium</a>."
msgstr ""

#. type: Content of: <ul><li><ul><li>
msgid ""
"The GNU web server follows the w3.org <a "
"href=\"//www.w3.org/Provider/Style/Overview.html\">Style Guide</a>."
msgstr ""

#. type: Content of: <ul><li><ul><li>
msgid ""
"Use of <a href=\"//w3.org/TR/WCAG21/\">WCAG 2.1</a> helps ensure "
"accessibility for a wide range of people with disabilities."
msgstr ""

#. type: Content of: <ul><li>
msgid "On gnu.org:"
msgstr ""

#. type: Content of: <ul><li><ul><li>
msgid "<a href=\"#content\">The GNU Website Guidelines</a> (this page);"
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=\"/help/help.html\">How to help</a> with our <a "
"href=\"/server/server.html\">web server</a> and other tasks."
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 &amp; GNU inquiries to <a "
"href=\"mailto:gnu@gnu.org\">&lt;gnu@gnu.org&gt;</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:webmasters@gnu.org\">&lt;webmasters@gnu.org&gt;</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:web-translators@gnu.org">
#
#.         &lt;web-translators@gnu.org&gt;</a>.</p>
#
#.         <p>For information on coordinating and contributing 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 contributing translations of this "
"article."
msgstr ""

#. type: Content of: <div><p>
msgid ""
"Copyright &copy; 2010, 2013-2021, 2023, 2024, 2025 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 ""