[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www/server/standards/po gnu-website-guidelines....
|
From: |
GNUN |
|
Subject: |
www/server/standards/po gnu-website-guidelines.... |
|
Date: |
Sun, 17 Mar 2024 04:09:37 -0400 (EDT) |
CVSROOT: /web/www
Module name: www
Changes by: GNUN <gnun> 24/03/17 04:09:37
Modified files:
server/standards/po: gnu-website-guidelines.pot
gnu-website-guidelines.pt-br-diff.html
gnu-website-guidelines.pt-br.po
Log message:
Automatic update by GNUnited Nations.
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/server/standards/po/gnu-website-guidelines.pot?cvsroot=www&r1=1.30&r2=1.31
http://web.cvs.savannah.gnu.org/viewcvs/www/server/standards/po/gnu-website-guidelines.pt-br-diff.html?cvsroot=www&r1=1.8&r2=1.9
http://web.cvs.savannah.gnu.org/viewcvs/www/server/standards/po/gnu-website-guidelines.pt-br.po?cvsroot=www&r1=1.51&r2=1.52
Patches:
Index: gnu-website-guidelines.pot
===================================================================
RCS file: /web/www/www/server/standards/po/gnu-website-guidelines.pot,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -b -r1.30 -r1.31
--- gnu-website-guidelines.pot 11 Mar 2024 11:15:36 -0000 1.30
+++ gnu-website-guidelines.pot 17 Mar 2024 08:09:35 -0000 1.31
@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: gnu-website-guidelines.html\n"
-"POT-Creation-Date: 2024-03-11 10:58+0000\n"
+"POT-Creation-Date: 2024-03-17 07:57+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"
@@ -857,11 +857,11 @@
"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."
+"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>
@@ -925,22 +925,13 @@
#. 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."
+"Explorer, Chrome, Photoshop, Acrobat Reader, and Flash."
msgstr ""
#. type: Content of: <dl><dd><p>
@@ -952,7 +943,7 @@
"else—would be acceptable:"
msgstr ""
-#. type: Content of: <dl><dd><blockquote><p>
+#. 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 "
@@ -962,9 +953,9 @@
#. 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."
+"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 “learn more” should still be avoided."
msgstr ""
#. type: Content of: <dl><dt>
@@ -977,23 +968,23 @@
"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:"
+"have little mention of open source. Here's an example of a tactful way to "
+"do it:"
msgstr ""
-#. type: Content of: <dl><dd><blockquote><p>
+#. type: Content of: <dl><dd><p>
msgid ""
-"GNOME is part of the GNU Project, and is free software (sometimes referred "
-"to as open source software)."
+"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 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.”"
+"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, "
+"“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>
@@ -1004,7 +995,7 @@
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 "
+"GNU/Linux or just “Linux.” 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 ""
@@ -1014,10 +1005,10 @@
"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 "
+"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 pages, the contents of forums and wiki "
-"pages should not hold weight in these regards."
+"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>
@@ -1026,9 +1017,10 @@
"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."
+"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>
@@ -1051,6 +1043,207 @@
"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>—a free software "
+"frontend for GitHub that works without JavaScript—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.frontendfriendly.xyz/pbatard/rufus/blob/master/README.md</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.frontendfriendly.xyz/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 ""
Index: gnu-website-guidelines.pt-br-diff.html
===================================================================
RCS file:
/web/www/www/server/standards/po/gnu-website-guidelines.pt-br-diff.html,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- gnu-website-guidelines.pt-br-diff.html 11 Mar 2024 11:15:37 -0000
1.8
+++ gnu-website-guidelines.pt-br-diff.html 17 Mar 2024 08:09:35 -0000
1.9
@@ -572,21 +572,21 @@
are interested in.</li>
</ul>
-
<h3 id="pollinking" class="subheader">Appendix 1 - Linking
Policies</h3>
-
-<p>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.</p>
-
-<p>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.</p>
+<p>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.</p>
+
+<p>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 <span
class="removed"><del><strong>Foundation,</strong></del></span> <span
class="inserted"><ins><em>Foundation and/or the GNU Project,</em></ins></span>
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.</p>
<dl>
<dt>What's the context of the link?</dt>
@@ -615,9 +615,9 @@
them otherwise. As such, we avoid offering such free advertising,
either directly on our site or indirectly through links.</p>
-<p>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
+<p>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.</p>
@@ -635,21 +635,21 @@
there's a difference between “Windows” and
“Microsoft Windows XP Home Edition.”</p>
-<p>If the page requires <a
href="/philosophy/javascript-trap.html">nonfree,
+<span class="removed"><del><strong><p>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.</p>
+should not be made.</p></strong></del></span>
<p>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.</p>
+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, <span
class="inserted"><ins><em>Chrome,</em></ins></span> Photoshop, Acrobat Reader,
+and Flash.</p>
<p>GNU software project pages feel the full force of this policy.
Proprietary software should only be mentioned when the GNU software
@@ -657,14 +657,17 @@
well-known proprietary software. For example, the following
text—and not much else—would be acceptable:</p>
-<blockquote><p>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.</p></blockquote>
+<span
class="removed"><del><strong><blockquote><p>w3</strong></del></span>
+
+<span class="inserted"><ins><em><p
class="indent-para">w3</em></ins></span> 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 <span
class="removed"><del><strong>Windows.</p></blockquote></strong></del></span>
<span class="inserted"><ins><em>Windows.</p></em></ins></span>
<p>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.</p>
+philosophy pages, as well as links to user groups <span
class="inserted"><ins><em>or third party
+organizations,</em></ins></span> may discuss such software in greater detail,
but links
+and other methods of encouragement to “learn more” should
+still be avoided.</p>
</dd>
<dt>How does the page compare free software to open source?</dt>
@@ -674,17 +677,21 @@
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:</p>
-
-<blockquote><p>GNOME is part of the GNU Project, and is free
software (sometimes
-referred to as open source software).</p></blockquote>
-
-<p>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.”</p>
+project pages should have little mention of open source. <span
class="removed"><del><strong>The GNOME
+page used to provide a good</strong></del></span> <span
class="inserted"><ins><em>Here's an</em></ins></span>
+example of a tactful way to do it:</p>
+
+<span
class="removed"><del><strong><blockquote><p>GNOME</strong></del></span>
+
+<span class="inserted"><ins><em><p
class="indent-para">XYZ</em></ins></span> is part of the GNU Project, and is
<span class="removed"><del><strong>free</strong></del></span> <span
class="inserted"><ins><em>free/libre</em></ins></span>
+software (sometimes referred to as open source <span
class="removed"><del><strong>software).</p></blockquote></strong></del></span>
<span class="inserted"><ins><em>software).</p></em></ins></span>
+
+<p>Any exceptions to this rule should be apparent from the context. For
+instance, user <span class="removed"><del><strong>groups</strong></del></span>
<span class="inserted"><ins><em>group pages or</em></ins></span> pages <span
class="inserted"><ins><em>of organizations listed in
+links.html</em></ins></span> may talk in greater detail about open source; we
state on <span class="removed"><del><strong>the user groups page, “As
with our links
+page, the</strong></del></span>
+<span class="inserted"><ins><em>those pages, “The</em></ins></span> FSF
is not responsible for the contents of other
+websites, or how up-to-date their information is.”</p>
</dd>
<dt>How does the page treat the GNU Project?</dt>
@@ -692,44 +699,138 @@
<dd>
<p>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.</p>
-
-<p>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.</p>
-
-<p>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.</p>
+calls the system GNU/Linux or just “Linux.” GNU software <span
class="removed"><del><strong>project</strong></del></span>
+<span class="inserted"><ins><em>projects</em></ins></span> and user group
pages should almost never, if ever, fail to do
+this. Again, exceptions for other pages should be apparent from
context.</p>
+
+<p>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 <span class="removed"><del><strong>or</strong></del></span> <span
class="inserted"><ins><em>our</em></ins></span> linking guidelines, since
they're understood to be the
+opinion of their individual authors. Similarly, on user group <span
class="inserted"><ins><em>or third
+party organization</em></ins></span> pages, the contents of forums and wiki
pages should
+not hold weight in these regards.</p>
+
+<p>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 <span
class="removed"><del><strong>encourage</strong></del></span> <span
class="inserted"><ins><em>encouraged</em></ins></span> the use of <span
class="removed"><del><strong>Flash and</strong></del></span> <span
class="inserted"><ins><em>Flash,</em></ins></span> talked exclusively
+about open source <span class="inserted"><ins><em>software, and do not
advocate users' freedom to
+redistribute and change</em></ins></span> software. It's generally understood
that since
+these pages are not primarily about free software, the policies do not
+hold full force for them.</p>
<p>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.</p>
+rather than “open source.” We do, however, require that
+they not promote any nonfree software.</p>
-<p>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.</p>
+<p>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.</p>
</dd>
+
+<span class="inserted"><ins><em><dt id="javascript">Does the page work
even if the user's browser
+refuses to run JavaScript code?</dt>
+
+<dd>
+<p>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.</p>
+
+<p>In some cases, however, we can still refer to such pages and
+resources by using workarounds to bypass the JavaScript requirement.</p>
+
+<p id="gothub">One possibility is to use an instance of <a
+href="https://codeberg.org/gothub/gothub">GotHub</a>—a free
+software frontend for GitHub that works without JavaScript—to
+replace links to pages and resources hosted at GitHub, a website that
+requires running nonfree JavaScript to be usable as intended.
+<!-- Add link to future article as follows: (See also
+<a href="/DIR/whats-wrong-with-github.html">What's Wrong with
GitHub</a>.)-->
+</p>
+
+<p>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.</p>
+
+<p><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:<br />
+<span
class="bad"><code><del>https://github.com/pbatard/rufus</del></code></span>
<br />
+with this: <br />
+<span
class="good"><code>https://gothub.frontendfriendly.xyz/pbatard/rufus/blob/master/README.md</code></span>.</p>
+
+<p>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.</p>
+
+<p><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 <br />
+<span
class="bad"><code><del>https://github.com/foocorp/gnu-fm/blob/main/clients/meego/librefm/src/librefm-logo.png</del></code></span><br
/>
+with a link to <br />
+<span
class="good"><code>https://raw.githubusercontent.com/foocorp/gnu-fm/main/clients/meego/librefm/src/librefm-logo.png</code>
+</span>. <br />
+And we have links to documents such as <br />
+<span
class="good"><code>https://raw.githubusercontent.com/scootergrisen/licenser/master/gpl-3.0.da.txt</code></span>.
+</p>
+
+<p>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?</p>
+
+<p>For example, in the past we had the case of a manual that was listed
+in other-free-books.html with this URL:<br />
+<span
class="bad"><code><del>https://github.com/davidam/orgguide-es</del></code></span>.<br
/>
+At the time, we had three possibilitites to replace that bad link: <br />
+1. GotHub<br />
+<span
class="good"><code>https://gothub.frontendfriendly.xyz/raw/davidam/davidam.github.io/master/docu/orgguide.es.pdf</code></span><br
/>
+2. Author's personal space at GitHub<br />
+<span
class="good"><code>https://raw.githubusercontent.com/davidam/davidam.github.io/master/docu/orgguide.es.pdf</code>
+</span><br />
+3. Publisher/Bookstore<br />
+<span
class="good"><code>https://traficantes.net/sites/default/files/pdfs/orgguide.es_.pdf</code></span><br
/>
+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.</p>
+
+<p>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 <br />
+<span
class="good"><code>https://github.com/w3c/fingerprinting-guidance/issues/8</code></span>.
<br />
+Another possibility for closed issues is to link to the archived page at
+the Wayback Machine.</p>
+
+<p>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.</p>
+</dd></em></ins></span>
</dl>
+
<h3 id="repo" class="subheader">Appendix 2 - Working with Web CVS
Repositories</h3>
@@ -1088,7 +1189,7 @@
<p class="unprintable">Updated:
<!-- timestamp start -->
-$Date: 2024/03/11 11:15:37 $
+$Date: 2024/03/17 08:09:35 $
<!-- timestamp end --></p>
</div>
</div><!-- for class="inner", starts in the banner include -->
Index: gnu-website-guidelines.pt-br.po
===================================================================
RCS file: /web/www/www/server/standards/po/gnu-website-guidelines.pt-br.po,v
retrieving revision 1.51
retrieving revision 1.52
diff -u -b -r1.51 -r1.52
--- gnu-website-guidelines.pt-br.po 11 Mar 2024 11:15:37 -0000 1.51
+++ gnu-website-guidelines.pt-br.po 17 Mar 2024 08:09:35 -0000 1.52
@@ -6,7 +6,7 @@
msgid ""
msgstr ""
"Project-Id-Version: gnu-website-guidelines.html\n"
-"POT-Creation-Date: 2024-03-11 10:58+0000\n"
+"POT-Creation-Date: 2024-03-17 07:57+0000\n"
"PO-Revision-Date: 2021-05-03 10:15-0300\n"
"Last-Translator: Rafael Fontenelle <rafaelff@gnome.org>\n"
"Language-Team: Brazilian Portuguese <www-pt-br-general@gnu.org>\n"
@@ -1198,15 +1198,25 @@
"diretrizes de links; no entanto, também é um aspecto crucial do trabalho."
#. type: Content of: <p>
+#, fuzzy
+#| 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."
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."
+"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 ""
"Nós nos esforçamos para garantir que todas as páginas que promovemos
– "
"todas as páginas que recebem links em nosso site – sejam amigáveis ao
"
@@ -1310,21 +1320,15 @@
"diferença entre âWindowsâ e âMicrosoft Windows XP Home Editionâ."
#. 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 ""
-"Se a página exigir <a href=\"/philosophy/javascript-trap.html\">JavaScript "
-"não livre e não trivial</a> e houver falhas graves com o JavaScript "
-"desativado, o link não deverá ser criado. Da mesma forma, se a página "
-"incorporar o Flash que desempenha um papel importante, de modo que uma "
-"pessoa perderia algo importante se os vÃdeos não forem reproduzidos, o link
"
-"não deverá ser criado."
-
-#. type: Content of: <dl><dd><p>
+#, fuzzy
+#| 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."
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 "
@@ -1332,7 +1336,7 @@
"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."
+"Explorer, Chrome, Photoshop, Acrobat Reader, and Flash."
msgstr ""
"O assunto da referência também terá um papel na determinação de quão "
"problemática é uma referência. Se o software já é muito popular, é "
@@ -1356,7 +1360,12 @@
"privativo bem conhecido. Por exemplo, o texto a seguir Рe ṇo muito "
"mais – seria aceitável:"
-#. type: Content of: <dl><dd><blockquote><p>
+#. type: Content of: <dl><dd><p>
+#, fuzzy
+#| 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."
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 "
@@ -1369,11 +1378,17 @@
"<sup><a href=\"#TransNote1\">1</a></sup>"
#. type: Content of: <dl><dd><p>
+#, fuzzy
+#| 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."
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."
+"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 “learn more” should still be avoided."
msgstr ""
"Links que aparecem em outras áreas, como os depoimentos ou páginas de "
"filosofia, bem como links para grupos de usuários podem discutir esse "
@@ -1385,13 +1400,21 @@
msgstr "Como a página compara software livre ao código aberto?"
#. type: Content of: <dl><dd><p>
+#, fuzzy
+#| 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:"
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:"
+"have little mention of open source. Here's an example of a tactful way to "
+"do it:"
msgstr ""
"Quase todas as páginas que possuem links em nosso site devem, no mÃnimo, "
"tratar software livre e código aberto igualmente. Não fazer isso – "
@@ -1400,10 +1423,14 @@
"devem ter pouca menção a código aberto. A página do GNOME é usada para "
"fornecer um bom exemplo de uma maneira diplomática de fazer isso:"
-#. type: Content of: <dl><dd><blockquote><p>
+#. type: Content of: <dl><dd><p>
+#, fuzzy
+#| msgid ""
+#| "GNOME is part of the GNU Project, and is free software (sometimes "
+#| "referred to as open source software)."
msgid ""
-"GNOME is part of the GNU Project, and is free software (sometimes referred "
-"to as open source software)."
+"XYZ is part of the GNU Project, and is free/libre software (sometimes "
+"referred to as open source software)."
msgstr ""
"<a id=\"TransNote2-rev\"></a>\n"
"GNOME is part of the GNU Project, and is free software (sometimes referred "
@@ -1411,12 +1438,19 @@
"<sup><a href=\"#TransNote2\">2</a></sup>"
#. type: Content of: <dl><dd><p>
+#, fuzzy
+#| 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.”"
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.”"
+"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, "
+"“The FSF is not responsible for the contents of other websites, or how "
+"up-to-date their information is.”"
msgstr ""
"<a id=\"TransNote3-rev\"></a>\n"
"Qualquer exceção a esta regra deve ser aparente no contexto. Por exemplo,
as "
@@ -1431,12 +1465,19 @@
msgstr "Como a página trata o Projeto GNU?"
#. type: Content of: <dl><dd><p>
+#, fuzzy
+#| 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."
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."
+"Linux or just “Linux.” 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 ""
"As páginas para as quais acrescentamos link devem tratar bem o Projeto GNU. "
"O principal aspecto a ser observado a esse respeito é se a página chama o "
@@ -1445,14 +1486,23 @@
"Novamente, as exceções para outras páginas devem ser aparentes no
contexto."
#. type: Content of: <dl><dd><p>
+#, fuzzy
+#| 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."
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 "
+"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 pages, the contents of forums and wiki "
-"pages should not hold weight in these regards."
+"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 ""
"Isto posto, certas partes de uma página não devem ser consideradas contra "
"esses critérios. Por exemplo, suponha que fôssemos fazer um link para uma "
@@ -1464,14 +1514,25 @@
"ter peso nesses aspectos."
#. type: Content of: <dl><dd><p>
+#, fuzzy
+#| 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."
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."
+"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 ""
"Por fim, alguns sites são sempre considerados exceção com a maioria dessas
"
"diretrizes. Esses sites são geralmente sobre questões que são importantes,
"
@@ -1511,6 +1572,218 @@
"o RMS. Novas exceções sempre surgirão; mantenha uma mente aberta para essa
"
"possibilidade e esteja preparado para lidar com eles adequadamente."
+#. 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>
+#, fuzzy
+#| 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."
+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 ""
+"Se a página exigir <a href=\"/philosophy/javascript-trap.html\">JavaScript "
+"não livre e não trivial</a> e houver falhas graves com o JavaScript "
+"desativado, o link não deverá ser criado. Da mesma forma, se a página "
+"incorporar o Flash que desempenha um papel importante, de modo que uma "
+"pessoa perderia algo importante se os vÃdeos não forem reproduzidos, o link
"
+"não deverá ser criado."
+
+#. 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>—a free software frontend for GitHub that "
+"works without JavaScript—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.frontendfriendly.xyz/pbatard/rufus/";
+"blob/master/README.md</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.frontendfriendly.xyz/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 "Apêndice 2 - Trabalhando com repositórios CVS Web"