www-commits
[Top][All Lists]
Advanced

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

www education/po/edu-cases-argentina.pt-br.po e...


From: GNUN
Subject: www education/po/edu-cases-argentina.pt-br.po e...
Date: Wed, 24 Jan 2018 07:33:23 -0500 (EST)

CVSROOT:        /web/www
Module name:    www
Changes by:     GNUN <gnun>     18/01/24 07:33:21

Modified files:
        education/po   : edu-cases-argentina.pt-br.po 
                         edu-cases-argentina.translist 
                         edu-cases-india.pt-br.po 
                         edu-cases-india.translist edu-cases.pt-br.po 
                         edu-cases.translist 
        gnu/po         : about-gnu.pt-br.po about-gnu.translist 
                         gnu-linux-faq.ar.po gnu-linux-faq.ca-diff.html 
                         gnu-linux-faq.ca.po gnu-linux-faq.de.po 
                         gnu-linux-faq.es.po gnu-linux-faq.fr.po 
                         gnu-linux-faq.hr-diff.html gnu-linux-faq.hr.po 
                         gnu-linux-faq.it.po gnu-linux-faq.ja-diff.html 
                         gnu-linux-faq.ja.po gnu-linux-faq.ko-diff.html 
                         gnu-linux-faq.ko.po gnu-linux-faq.nl.po 
                         gnu-linux-faq.pl-diff.html gnu-linux-faq.pl.po 
                         gnu-linux-faq.pot gnu-linux-faq.ru.po 
                         gnu-linux-faq.sq.po gnu-linux-faq.sr.po 
                         gnu-linux-faq.tr.po gnu-linux-faq.uk.po 
                         pronunciation.translist 
        licenses       : gpl-howto.es.html 
        licenses/po    : gpl-howto.es-en.html quick-guide-gplv3.pt-br.po 
                         quick-guide-gplv3.translist 
                         translations.pt-br.po translations.translist 
        philosophy     : copyright-and-globalization.pt-br.html 
                         dat.zh-cn.html drdobbs-letter.zh-cn.html 
                         university.pt-br.html 
        philosophy/po  : copyright-and-globalization.pt-br-en.html 
                         copyright-and-globalization.pt-br.po 
                         drdobbs-letter.zh-cn.po university.pt-br.po 
        server/po      : irc-rules.pt-br.po irc-rules.translist 
Added files:
        education      : edu-cases-argentina.pt-br.html 
                         edu-cases-india.pt-br.html edu-cases.pt-br.html 
        education/po   : edu-cases-argentina.pt-br-en.html 
                         edu-cases-india.pt-br-en.html 
                         edu-cases.pt-br-en.html 
        gnu            : about-gnu.pt-br.html pronunciation.pt-br.html 
        gnu/po         : about-gnu.pt-br-en.html 
                         pronunciation.pt-br-en.html 
        licenses       : quick-guide-gplv3.pt-br.html 
                         translations.pt-br.html 
        licenses/po    : quick-guide-gplv3.pt-br-en.html 
                         translations.pt-br-en.html 
        philosophy/po  : dat.zh-cn-en.html drdobbs-letter.zh-cn-en.html 
                         university.pt-br-en.html 
        server         : irc-rules.pt-br.html 
        server/po      : irc-rules.pt-br-en.html 

Log message:
        Automatic update by GNUnited Nations.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/education/edu-cases-argentina.pt-br.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/education/edu-cases-india.pt-br.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/education/edu-cases.pt-br.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/education/po/edu-cases-argentina.pt-br.po?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/education/po/edu-cases-argentina.translist?cvsroot=www&r1=1.15&r2=1.16
http://web.cvs.savannah.gnu.org/viewcvs/www/education/po/edu-cases-india.pt-br.po?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/education/po/edu-cases-india.translist?cvsroot=www&r1=1.15&r2=1.16
http://web.cvs.savannah.gnu.org/viewcvs/www/education/po/edu-cases.pt-br.po?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/education/po/edu-cases.translist?cvsroot=www&r1=1.18&r2=1.19
http://web.cvs.savannah.gnu.org/viewcvs/www/education/po/edu-cases-argentina.pt-br-en.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/education/po/edu-cases-india.pt-br-en.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/education/po/edu-cases.pt-br-en.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/about-gnu.pt-br.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/pronunciation.pt-br.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/about-gnu.pt-br.po?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/about-gnu.translist?cvsroot=www&r1=1.22&r2=1.23
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/gnu-linux-faq.ar.po?cvsroot=www&r1=1.61&r2=1.62
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/gnu-linux-faq.ca-diff.html?cvsroot=www&r1=1.11&r2=1.12
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/gnu-linux-faq.ca.po?cvsroot=www&r1=1.86&r2=1.87
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/gnu-linux-faq.de.po?cvsroot=www&r1=1.114&r2=1.115
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/gnu-linux-faq.es.po?cvsroot=www&r1=1.116&r2=1.117
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/gnu-linux-faq.fr.po?cvsroot=www&r1=1.107&r2=1.108
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/gnu-linux-faq.hr-diff.html?cvsroot=www&r1=1.27&r2=1.28
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/gnu-linux-faq.hr.po?cvsroot=www&r1=1.34&r2=1.35
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/gnu-linux-faq.it.po?cvsroot=www&r1=1.40&r2=1.41
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/gnu-linux-faq.ja-diff.html?cvsroot=www&r1=1.7&r2=1.8
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/gnu-linux-faq.ja.po?cvsroot=www&r1=1.75&r2=1.76
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/gnu-linux-faq.ko-diff.html?cvsroot=www&r1=1.9&r2=1.10
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/gnu-linux-faq.ko.po?cvsroot=www&r1=1.21&r2=1.22
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/gnu-linux-faq.nl.po?cvsroot=www&r1=1.55&r2=1.56
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/gnu-linux-faq.pl-diff.html?cvsroot=www&r1=1.14&r2=1.15
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/gnu-linux-faq.pl.po?cvsroot=www&r1=1.77&r2=1.78
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/gnu-linux-faq.pot?cvsroot=www&r1=1.49&r2=1.50
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/gnu-linux-faq.ru.po?cvsroot=www&r1=1.97&r2=1.98
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/gnu-linux-faq.sq.po?cvsroot=www&r1=1.96&r2=1.97
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/gnu-linux-faq.sr.po?cvsroot=www&r1=1.56&r2=1.57
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/gnu-linux-faq.tr.po?cvsroot=www&r1=1.60&r2=1.61
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/gnu-linux-faq.uk.po?cvsroot=www&r1=1.35&r2=1.36
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/pronunciation.translist?cvsroot=www&r1=1.7&r2=1.8
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/about-gnu.pt-br-en.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/pronunciation.pt-br-en.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/gpl-howto.es.html?cvsroot=www&r1=1.41&r2=1.42
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/quick-guide-gplv3.pt-br.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/translations.pt-br.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/gpl-howto.es-en.html?cvsroot=www&r1=1.27&r2=1.28
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/quick-guide-gplv3.pt-br.po?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/quick-guide-gplv3.translist?cvsroot=www&r1=1.14&r2=1.15
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/translations.pt-br.po?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/translations.translist?cvsroot=www&r1=1.11&r2=1.12
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/quick-guide-gplv3.pt-br-en.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/translations.pt-br-en.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/copyright-and-globalization.pt-br.html?cvsroot=www&r1=1.10&r2=1.11
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/dat.zh-cn.html?cvsroot=www&r1=1.3&r2=1.4
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/drdobbs-letter.zh-cn.html?cvsroot=www&r1=1.3&r2=1.4
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/university.pt-br.html?cvsroot=www&r1=1.5&r2=1.6
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/copyright-and-globalization.pt-br-en.html?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/copyright-and-globalization.pt-br.po?cvsroot=www&r1=1.5&r2=1.6
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/drdobbs-letter.zh-cn.po?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/university.pt-br.po?cvsroot=www&r1=1.3&r2=1.4
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/dat.zh-cn-en.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/drdobbs-letter.zh-cn-en.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/university.pt-br-en.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/server/irc-rules.pt-br.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/server/po/irc-rules.pt-br.po?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/server/po/irc-rules.translist?cvsroot=www&r1=1.14&r2=1.15
http://web.cvs.savannah.gnu.org/viewcvs/www/server/po/irc-rules.pt-br-en.html?cvsroot=www&rev=1.1

Patches:
Index: education/po/edu-cases-argentina.pt-br.po
===================================================================
RCS file: /web/www/www/education/po/edu-cases-argentina.pt-br.po,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- education/po/edu-cases-argentina.pt-br.po   24 Jan 2018 08:43:40 -0000      
1.1
+++ education/po/edu-cases-argentina.pt-br.po   24 Jan 2018 12:33:17 -0000      
1.2
@@ -85,6 +85,7 @@
 msgid "*GNUN-SLOT: TRANSLATOR'S NOTES*"
 msgstr " "
 
+# type: Content of: <div><p>
 #. type: Content of: <div><div><p>
 msgid ""
 "Please send general FSF &amp; GNU inquiries to <a 
href=\"mailto:address@hidden";
@@ -126,8 +127,6 @@
 "envio de traduções das páginas desse site."
 
 #. type: Content of: <div><p>
-#| msgid ""
-#| "Copyright &copy; 2014, 2015, 2016, 2017 Free Software Foundation, Inc."
 msgid "Copyright &copy; 2011, 2015, 2016 Free Software Foundation, Inc."
 msgstr "Copyright &copy; 2011, 2015, 2016 Free Software Foundation, Inc."
 
@@ -148,7 +147,8 @@
 "Traduzido por: Rafael Fontenelle <a href=\"mailto:address@hidden";>&lt;"
 "address@hidden&gt;</a>, 2017."
 
+# type: Content of: <div><p>
 #.  timestamp start 
 #. type: Content of: <div><p>
 msgid "Updated:"
-msgstr "Última atualização:"
+msgstr "Última atualização: "

Index: education/po/edu-cases-argentina.translist
===================================================================
RCS file: /web/www/www/education/po/edu-cases-argentina.translist,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -b -r1.15 -r1.16
--- education/po/edu-cases-argentina.translist  23 Jan 2016 18:29:43 -0000      
1.15
+++ education/po/edu-cases-argentina.translist  24 Jan 2018 12:33:17 -0000      
1.16
@@ -9,6 +9,7 @@
 <span dir="ltr"><a lang="hr" hreflang="hr" 
href="/education/edu-cases-argentina.hr.html">hrvatski</a>&nbsp;[hr]</span> 
&nbsp;
 <span dir="ltr"><a lang="it" hreflang="it" 
href="/education/edu-cases-argentina.it.html">italiano</a>&nbsp;[it]</span> 
&nbsp;
 <span dir="ltr"><a lang="ja" hreflang="ja" 
href="/education/edu-cases-argentina.ja.html">日本語</a>&nbsp;[ja]</span> 
&nbsp;
+<span dir="ltr"><a lang="pt-br" hreflang="pt-br" 
href="/education/edu-cases-argentina.pt-br.html">português&nbsp;do&nbsp;Brasil</a>&nbsp;[pt-br]</span>
 &nbsp;
 <span dir="ltr"><a lang="uk" hreflang="uk" 
href="/education/edu-cases-argentina.uk.html">українська</a>&nbsp;[uk]</span>
 &nbsp;
 </p>
 </div>' -->
@@ -20,5 +21,6 @@
 <link rel="alternate" type="text/html" lang="hr" hreflang="hr" 
href="/education/edu-cases-argentina.hr.html" title="hrvatski" />
 <link rel="alternate" type="text/html" lang="it" hreflang="it" 
href="/education/edu-cases-argentina.it.html" title="italiano" />
 <link rel="alternate" type="text/html" lang="ja" hreflang="ja" 
href="/education/edu-cases-argentina.ja.html" title="日本語" />
+<link rel="alternate" type="text/html" lang="pt-br" hreflang="pt-br" 
href="/education/edu-cases-argentina.pt-br.html" title="português do Brasil" />
 <link rel="alternate" type="text/html" lang="uk" hreflang="uk" 
href="/education/edu-cases-argentina.uk.html" title="українська" />
 <!-- end translist file -->

Index: education/po/edu-cases-india.pt-br.po
===================================================================
RCS file: /web/www/www/education/po/edu-cases-india.pt-br.po,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- education/po/edu-cases-india.pt-br.po       24 Jan 2018 08:43:40 -0000      
1.1
+++ education/po/edu-cases-india.pt-br.po       24 Jan 2018 12:33:17 -0000      
1.2
@@ -112,6 +112,7 @@
 msgid "*GNUN-SLOT: TRANSLATOR'S NOTES*"
 msgstr " "
 
+# type: Content of: <div><p>
 #. type: Content of: <div><div><p>
 msgid ""
 "Please send general FSF &amp; GNU inquiries to <a 
href=\"mailto:address@hidden";
@@ -173,7 +174,8 @@
 "Traduzido por: Rafael Fontenelle <a href=\"mailto:address@hidden";>&lt;"
 "address@hidden&gt;</a>, 2017."
 
+# type: Content of: <div><p>
 #.  timestamp start 
 #. type: Content of: <div><p>
 msgid "Updated:"
-msgstr "Última atualização:"
+msgstr "Última atualização: "

Index: education/po/edu-cases-india.translist
===================================================================
RCS file: /web/www/www/education/po/edu-cases-india.translist,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -b -r1.15 -r1.16
--- education/po/edu-cases-india.translist      23 Jan 2016 18:29:44 -0000      
1.15
+++ education/po/edu-cases-india.translist      24 Jan 2018 12:33:17 -0000      
1.16
@@ -9,6 +9,7 @@
 <span dir="ltr"><a lang="hr" hreflang="hr" 
href="/education/edu-cases-india.hr.html">hrvatski</a>&nbsp;[hr]</span> &nbsp;
 <span dir="ltr"><a lang="it" hreflang="it" 
href="/education/edu-cases-india.it.html">italiano</a>&nbsp;[it]</span> &nbsp;
 <span dir="ltr"><a lang="ja" hreflang="ja" 
href="/education/edu-cases-india.ja.html">日本語</a>&nbsp;[ja]</span> &nbsp;
+<span dir="ltr"><a lang="pt-br" hreflang="pt-br" 
href="/education/edu-cases-india.pt-br.html">português&nbsp;do&nbsp;Brasil</a>&nbsp;[pt-br]</span>
 &nbsp;
 <span dir="ltr"><a lang="uk" hreflang="uk" 
href="/education/edu-cases-india.uk.html">українська</a>&nbsp;[uk]</span>
 &nbsp;
 </p>
 </div>' -->
@@ -20,5 +21,6 @@
 <link rel="alternate" type="text/html" lang="hr" hreflang="hr" 
href="/education/edu-cases-india.hr.html" title="hrvatski" />
 <link rel="alternate" type="text/html" lang="it" hreflang="it" 
href="/education/edu-cases-india.it.html" title="italiano" />
 <link rel="alternate" type="text/html" lang="ja" hreflang="ja" 
href="/education/edu-cases-india.ja.html" title="日本語" />
+<link rel="alternate" type="text/html" lang="pt-br" hreflang="pt-br" 
href="/education/edu-cases-india.pt-br.html" title="português do Brasil" />
 <link rel="alternate" type="text/html" lang="uk" hreflang="uk" 
href="/education/edu-cases-india.uk.html" title="українська" />
 <!-- end translist file -->

Index: education/po/edu-cases.pt-br.po
===================================================================
RCS file: /web/www/www/education/po/edu-cases.pt-br.po,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- education/po/edu-cases.pt-br.po     24 Jan 2018 08:43:40 -0000      1.1
+++ education/po/edu-cases.pt-br.po     24 Jan 2018 12:33:17 -0000      1.2
@@ -122,14 +122,15 @@
 "One of the several thousand schools that migrated completely to Free "
 "Software under the government's project address@hidden"
 msgstr ""
-"Um dos vários milhares de escolas que migraram completamente para o "
-"Software Livre sob o projeto governamental address@hidden"
+"Um dos vários milhares de escolas que migraram completamente para o Software 
"
+"Livre sob o projeto governamental address@hidden"
 
 #. 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><p>
 #. type: Content of: <div><div><p>
 msgid ""
 "Please send general FSF &amp; GNU inquiries to <a 
href=\"mailto:address@hidden";
@@ -191,7 +192,8 @@
 "Traduzido por: Rafael Fontenelle <a href=\"mailto:address@hidden";>&lt;"
 "address@hidden&gt;</a>, 2017."
 
+# type: Content of: <div><p>
 #.  timestamp start 
 #. type: Content of: <div><p>
 msgid "Updated:"
-msgstr "Última atualização:"
+msgstr "Última atualização: "

Index: education/po/edu-cases.translist
===================================================================
RCS file: /web/www/www/education/po/edu-cases.translist,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -b -r1.18 -r1.19
--- education/po/edu-cases.translist    24 Jul 2016 14:28:50 -0000      1.18
+++ education/po/edu-cases.translist    24 Jan 2018 12:33:17 -0000      1.19
@@ -10,6 +10,7 @@
 <span dir="ltr"><a lang="it" hreflang="it" 
href="/education/edu-cases.it.html">italiano</a>&nbsp;[it]</span> &nbsp;
 <span dir="ltr"><a lang="ja" hreflang="ja" 
href="/education/edu-cases.ja.html">日本語</a>&nbsp;[ja]</span> &nbsp;
 <span dir="ltr"><a lang="nl" hreflang="nl" 
href="/education/edu-cases.nl.html">Nederlands</a>&nbsp;[nl]</span> &nbsp;
+<span dir="ltr"><a lang="pt-br" hreflang="pt-br" 
href="/education/edu-cases.pt-br.html">português&nbsp;do&nbsp;Brasil</a>&nbsp;[pt-br]</span>
 &nbsp;
 <span dir="ltr"><a lang="ru" hreflang="ru" 
href="/education/edu-cases.ru.html">русский</a>&nbsp;[ru]</span> &nbsp;
 <span dir="ltr"><a lang="sq" hreflang="sq" 
href="/education/edu-cases.sq.html">Shqip</a>&nbsp;[sq]</span> &nbsp;
 <span dir="ltr"><a lang="uk" hreflang="uk" 
href="/education/edu-cases.uk.html">українська</a>&nbsp;[uk]</span> 
&nbsp;
@@ -24,6 +25,7 @@
 <link rel="alternate" type="text/html" lang="it" hreflang="it" 
href="/education/edu-cases.it.html" title="italiano" />
 <link rel="alternate" type="text/html" lang="ja" hreflang="ja" 
href="/education/edu-cases.ja.html" title="日本語" />
 <link rel="alternate" type="text/html" lang="nl" hreflang="nl" 
href="/education/edu-cases.nl.html" title="Nederlands" />
+<link rel="alternate" type="text/html" lang="pt-br" hreflang="pt-br" 
href="/education/edu-cases.pt-br.html" title="português do Brasil" />
 <link rel="alternate" type="text/html" lang="ru" hreflang="ru" 
href="/education/edu-cases.ru.html" title="русский" />
 <link rel="alternate" type="text/html" lang="sq" hreflang="sq" 
href="/education/edu-cases.sq.html" title="Shqip" />
 <link rel="alternate" type="text/html" lang="uk" hreflang="uk" 
href="/education/edu-cases.uk.html" title="українська" />

Index: gnu/po/about-gnu.pt-br.po
===================================================================
RCS file: /web/www/www/gnu/po/about-gnu.pt-br.po,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- gnu/po/about-gnu.pt-br.po   24 Jan 2018 08:43:40 -0000      1.1
+++ gnu/po/about-gnu.pt-br.po   24 Jan 2018 12:33:17 -0000      1.2
@@ -159,6 +159,7 @@
 msgid "*GNUN-SLOT: TRANSLATOR'S NOTES*"
 msgstr " "
 
+# type: Content of: <div><p>
 #. type: Content of: <div><div><p>
 msgid ""
 "Please send general FSF &amp; GNU inquiries to <a 
href=\"mailto:address@hidden";
@@ -174,9 +175,6 @@
 "address@hidden&gt;</a>."
 
 #
-#
-#
-#
 #.  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
@@ -223,7 +221,8 @@
 "Traduzido por: Rafael Fontenelle <a href=\"mailto:address@hidden";>&lt;"
 "address@hidden&gt;</a>, 2018."
 
+# type: Content of: <div><p>
 #.  timestamp start 
 #. type: Content of: <div><p>
 msgid "Updated:"
-msgstr "Última atualização:"
+msgstr "Última atualização: "

Index: gnu/po/about-gnu.translist
===================================================================
RCS file: /web/www/www/gnu/po/about-gnu.translist,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -b -r1.22 -r1.23
--- gnu/po/about-gnu.translist  22 Nov 2017 02:58:31 -0000      1.22
+++ gnu/po/about-gnu.translist  24 Jan 2018 12:33:17 -0000      1.23
@@ -12,6 +12,7 @@
 <span dir="ltr"><a lang="ja" hreflang="ja" 
href="/gnu/about-gnu.ja.html">日本語</a>&nbsp;[ja]</span> &nbsp;
 <span dir="ltr"><a lang="nl" hreflang="nl" 
href="/gnu/about-gnu.nl.html">Nederlands</a>&nbsp;[nl]</span> &nbsp;
 <span dir="ltr"><a lang="pl" hreflang="pl" 
href="/gnu/about-gnu.pl.html">polski</a>&nbsp;[pl]</span> &nbsp;
+<span dir="ltr"><a lang="pt-br" hreflang="pt-br" 
href="/gnu/about-gnu.pt-br.html">português&nbsp;do&nbsp;Brasil</a>&nbsp;[pt-br]</span>
 &nbsp;
 <span dir="ltr"><a lang="ru" hreflang="ru" 
href="/gnu/about-gnu.ru.html">русский</a>&nbsp;[ru]</span> &nbsp;
 <span dir="ltr"><a lang="sq" hreflang="sq" 
href="/gnu/about-gnu.sq.html">Shqip</a>&nbsp;[sq]</span> &nbsp;
 <span dir="ltr"><a lang="uk" hreflang="uk" 
href="/gnu/about-gnu.uk.html">українська</a>&nbsp;[uk]</span> &nbsp;
@@ -29,6 +30,7 @@
 <link rel="alternate" type="text/html" lang="ja" hreflang="ja" 
href="/gnu/about-gnu.ja.html" title="日本語" />
 <link rel="alternate" type="text/html" lang="nl" hreflang="nl" 
href="/gnu/about-gnu.nl.html" title="Nederlands" />
 <link rel="alternate" type="text/html" lang="pl" hreflang="pl" 
href="/gnu/about-gnu.pl.html" title="polski" />
+<link rel="alternate" type="text/html" lang="pt-br" hreflang="pt-br" 
href="/gnu/about-gnu.pt-br.html" title="português do Brasil" />
 <link rel="alternate" type="text/html" lang="ru" hreflang="ru" 
href="/gnu/about-gnu.ru.html" title="русский" />
 <link rel="alternate" type="text/html" lang="sq" hreflang="sq" 
href="/gnu/about-gnu.sq.html" title="Shqip" />
 <link rel="alternate" type="text/html" lang="uk" hreflang="uk" 
href="/gnu/about-gnu.uk.html" title="українська" />

Index: gnu/po/gnu-linux-faq.ar.po
===================================================================
RCS file: /web/www/www/gnu/po/gnu-linux-faq.ar.po,v
retrieving revision 1.61
retrieving revision 1.62
diff -u -b -r1.61 -r1.62
--- gnu/po/gnu-linux-faq.ar.po  1 Jan 2018 06:21:52 -0000       1.61
+++ gnu/po/gnu-linux-faq.ar.po  24 Jan 2018 12:33:17 -0000      1.62
@@ -9,7 +9,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: gnu-linux-faq.html\n"
-"POT-Creation-Date: 2018-01-01 05:56+0000\n"
+"POT-Creation-Date: 2018-01-24 12:26+0000\n"
 "PO-Revision-Date: 2010-03-30 16:12+0300\n"
 "Last-Translator: Hossam Hossny <address@hidden>\n"
 "Language-Team: Arabic <>\n"
@@ -69,7 +69,7 @@
 #, fuzzy
 #| msgid "<a href=\"#why\">Why do you call it GNU/Linux and not Linux?</a>"
 msgid ""
-"<a href=\"#what\">What is the real relationship between GNU and Linux</a>"
+"<a href=\"#what\">What is the real relationship between GNU and Linux?</a>"
 msgstr "<a href=\"#why\">لماذا تسمونه غنو/لينكس بدلا م
ن لينكس؟</a>"
 
 #. type: Content of: <ul><li>
@@ -387,9 +387,13 @@
 msgstr "<a href=\"#wait\">لماذا تأخرتم كثيرًا في طلب 
تسميته غنو/لينكس؟</a>"
 
 #. type: Content of: <ul><li>
+#, fuzzy
+#| msgid ""
+#| "<a href=\"#allgpled\">Should the GNU/[name] convention be applied to all "
+#| "programs that are GPL'ed?</a>"
 msgid ""
-"<a href=\"#allgpled\">Should the GNU/[name] convention be applied to all "
-"programs that are GPL'ed?</a>"
+"<a href=\"#allgpled\">Should the GNU/<i>name</i> convention be applied to "
+"all programs that are GPL'ed?</a>"
 msgstr ""
 "<a href=\"#allgpled\">هل ينبغي أن تسمى كل البرامج 
الخاضعة لجي بي إل بغنو/"
 "<i>الاسم</i>؟</a>"
@@ -916,10 +920,15 @@
 "غنو من أجلها ولنعلم الناس أن الحرية هي 
التي أوجدت النظام."
 
 #. type: Content of: <dl><dt>
-msgid ""
-"Since everyone knows GNU's role in developing the system, doesn't the &ldquo;"
-"GNU/&rdquo; in the name go without saying? <span class=\"anchor-reference-id"
-"\">(<a href=\"#everyoneknows\">#everyoneknows</a>)</span>"
+#, fuzzy
+#| msgid ""
+#| "Since everyone knows GNU's role in developing the system, doesn't the "
+#| "&ldquo;GNU/&rdquo; in the name go without saying? <span class=\"anchor-"
+#| "reference-id\">(<a href=\"#everyoneknows\">#everyoneknows</a>)</span>"
+msgid ""
+"Since everyone knows the role of GNU in developing the system, doesn't the "
+"&ldquo;GNU/&rdquo; in the name go without saying? <span class=\"anchor-"
+"reference-id\">(<a href=\"#everyoneknows\">#everyoneknows</a>)</span>"
 msgstr ""
 "بما أن الجميع يعرف دور غنو في تطوير النظام
، ألا تعتبر &rdquo;غنو/&ldquo; "
 "بديهية ولا تحتاج الذكر؟ <span 
class=\"anchor-reference-id\">(<a href="

Index: gnu/po/gnu-linux-faq.ca-diff.html
===================================================================
RCS file: /web/www/www/gnu/po/gnu-linux-faq.ca-diff.html,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- gnu/po/gnu-linux-faq.ca-diff.html   1 Jan 2018 07:20:31 -0000       1.11
+++ gnu/po/gnu-linux-faq.ca-diff.html   24 Jan 2018 12:33:17 -0000      1.12
@@ -37,7 +37,7 @@
 
 &lt;li&gt;&lt;a <span class="removed"><del><strong>href="#whycare" 
id="TOCwhycare"&gt;Why</strong></del></span> <span 
class="inserted"><ins><em>href="#whycare"&gt;Why</em></ins></span> is the name 
important?&lt;/a&gt;&lt;/li&gt;
 
-&lt;li&gt;&lt;a <span class="removed"><del><strong>href="#howerror" 
id="TOChowerror"&gt;How</strong></del></span> <span 
class="inserted"><ins><em>href="#what"&gt;What is the real relationship between 
GNU and Linux&lt;/a&gt;&lt;/li&gt;
+&lt;li&gt;&lt;a <span class="removed"><del><strong>href="#howerror" 
id="TOChowerror"&gt;How</strong></del></span> <span 
class="inserted"><ins><em>href="#what"&gt;What is the real relationship between 
GNU and Linux?&lt;/a&gt;&lt;/li&gt;
 
 &lt;li&gt;&lt;a href="#howerror"&gt;How</em></ins></span> did it come about 
that most
     people call the system &ldquo;Linux&rdquo;?&lt;/a&gt;&lt;/li&gt;
@@ -179,7 +179,7 @@
 &lt;li&gt;&lt;a <span class="removed"><del><strong>href="#wait" 
id="TOCwait"&gt;Why</strong></del></span> <span 
class="inserted"><ins><em>href="#wait"&gt;Why</em></ins></span> did you wait so 
long before
     asking people to use the name GNU/Linux?&lt;/a&gt;&lt;/li&gt;
 
-&lt;li&gt;&lt;a <span class="removed"><del><strong>href="#allgpled" 
id="TOCallgpled"&gt;Should</strong></del></span> <span 
class="inserted"><ins><em>href="#allgpled"&gt;Should</em></ins></span> the 
GNU/[name] convention
+&lt;li&gt;&lt;a <span class="removed"><del><strong>href="#allgpled" 
id="TOCallgpled"&gt;Should</strong></del></span> <span 
class="inserted"><ins><em>href="#allgpled"&gt;Should</em></ins></span> the 
<span class="removed"><del><strong>GNU/[name]</strong></del></span> <span 
class="inserted"><ins><em>GNU/&lt;i&gt;name&lt;/i&gt;</em></ins></span> 
convention
     be applied to all programs that are GPL'ed?&lt;/a&gt;&lt;/li&gt;
 
 &lt;li&gt;&lt;a <span class="removed"><del><strong>href="#unix" 
id="TOCunix"&gt;Since</strong></del></span> <span 
class="inserted"><ins><em>href="#unix"&gt;Since</em></ins></span> much of GNU 
comes from Unix,
@@ -434,7 +434,8 @@
 &lt;/dd&gt;
 
 &lt;dt id="everyoneknows"&gt;Since everyone knows
-    GNU's role in developing the system, doesn't the &ldquo;GNU/&rdquo; in the
+    <span class="removed"><del><strong>GNU's</strong></del></span> <span 
class="inserted"><ins><em>the</em></ins></span> role
+    <span class="inserted"><ins><em>of GNU</em></ins></span> in developing the 
system, doesn't the &ldquo;GNU/&rdquo; in the
     name go without saying? &lt;span class="anchor-reference-id"&gt;(&lt;a 
href="#everyoneknows"&gt;#everyoneknows&lt;/a&gt;)&lt;/span&gt;&lt;/dt&gt;
 
 &lt;dd&gt;Experience shows that the system's users, and the computer-using
@@ -1570,7 +1571,7 @@
 
 &lt;p class="unprintable"&gt;Updated:
 &lt;!-- timestamp start --&gt;
-$Date: 2018/01/01 07:20:31 $
+$Date: 2018/01/24 12:33:17 $
 &lt;!-- timestamp end --&gt;
 &lt;/p&gt;
 &lt;/div&gt;

Index: gnu/po/gnu-linux-faq.ca.po
===================================================================
RCS file: /web/www/www/gnu/po/gnu-linux-faq.ca.po,v
retrieving revision 1.86
retrieving revision 1.87
diff -u -b -r1.86 -r1.87
--- gnu/po/gnu-linux-faq.ca.po  1 Jan 2018 06:21:52 -0000       1.86
+++ gnu/po/gnu-linux-faq.ca.po  24 Jan 2018 12:33:17 -0000      1.87
@@ -7,7 +7,7 @@
 msgstr ""
 "Project-Id-Version: gnu-linux-faq\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2018-01-01 05:56+0000\n"
+"POT-Creation-Date: 2018-01-24 12:26+0000\n"
 "PO-Revision-Date: 2016-09-18 09:47+0200\n"
 "Last-Translator: Miquel Puigpelat <address@hidden>\n"
 "Language-Team: Catalan <address@hidden>\n"
@@ -70,7 +70,7 @@
 #, fuzzy
 #| msgid "<a href=\"#why\">Why do you call it GNU/Linux and not Linux?</a>"
 msgid ""
-"<a href=\"#what\">What is the real relationship between GNU and Linux</a>"
+"<a href=\"#what\">What is the real relationship between GNU and Linux?</a>"
 msgstr "<a href=\"#why\">Per què l'anomeneu GNU/Linux i no Linux?</a>"
 
 #. type: Content of: <ul><li>
@@ -389,9 +389,13 @@
 "nom GNU/Linux?</a>"
 
 #. type: Content of: <ul><li>
+#, fuzzy
+#| msgid ""
+#| "<a href=\"#allgpled\">Should the GNU/[name] convention be applied to all "
+#| "programs that are GPL'ed?</a>"
 msgid ""
-"<a href=\"#allgpled\">Should the GNU/[name] convention be applied to all "
-"programs that are GPL'ed?</a>"
+"<a href=\"#allgpled\">Should the GNU/<i>name</i> convention be applied to "
+"all programs that are GPL'ed?</a>"
 msgstr ""
 "<a href=\"#allgpled\">Deuria aplicar-se la convenció GNU/[nom] a tots els "
 "programes que estan llicenciats amb la GPL?</a>"
@@ -990,10 +994,15 @@
 
 # type: Content of: <dl><dt>
 #. type: Content of: <dl><dt>
-msgid ""
-"Since everyone knows GNU's role in developing the system, doesn't the &ldquo;"
-"GNU/&rdquo; in the name go without saying? <span class=\"anchor-reference-id"
-"\">(<a href=\"#everyoneknows\">#everyoneknows</a>)</span>"
+#, fuzzy
+#| msgid ""
+#| "Since everyone knows GNU's role in developing the system, doesn't the "
+#| "&ldquo;GNU/&rdquo; in the name go without saying? <span class=\"anchor-"
+#| "reference-id\">(<a href=\"#everyoneknows\">#everyoneknows</a>)</span>"
+msgid ""
+"Since everyone knows the role of GNU in developing the system, doesn't the "
+"&ldquo;GNU/&rdquo; in the name go without saying? <span class=\"anchor-"
+"reference-id\">(<a href=\"#everyoneknows\">#everyoneknows</a>)</span>"
 msgstr ""
 "Atès que tothom sap el paper del GNU en el desenvolupament del sistema, no "
 "se sobreentén “GNU/\" sense dir-ho?"

Index: gnu/po/gnu-linux-faq.de.po
===================================================================
RCS file: /web/www/www/gnu/po/gnu-linux-faq.de.po,v
retrieving revision 1.114
retrieving revision 1.115
diff -u -b -r1.114 -r1.115
--- gnu/po/gnu-linux-faq.de.po  1 Jan 2018 06:21:52 -0000       1.114
+++ gnu/po/gnu-linux-faq.de.po  24 Jan 2018 12:33:17 -0000      1.115
@@ -8,7 +8,7 @@
 msgstr ""
 "Project-Id-Version: gnu-linux-faq.html\n"
 "Report-Msgid-Bugs-To: Webmasters <address@hidden>\n"
-"POT-Creation-Date: 2018-01-01 05:56+0000\n"
+"POT-Creation-Date: 2018-01-24 12:26+0000\n"
 "PO-Revision-Date: 2017-09-26 22:00+0200\n"
 "Last-Translator: Jоегg Kоhпе <joeko (AT) online [PUNKT] de>\n"
 "Language-Team: German <address@hidden>\n"
@@ -64,8 +64,13 @@
 msgstr "<a href=\"#whycare\">Warum ist der Name wichtig?</a>"
 
 #. type: Content of: <ul><li>
+# | <a href=\"#what\">What is the real relationship between GNU and
+# | Linux{+?+}</a>
+#, fuzzy
+#| msgid ""
+#| "<a href=\"#what\">What is the real relationship between GNU and Linux</a>"
 msgid ""
-"<a href=\"#what\">What is the real relationship between GNU and Linux</a>"
+"<a href=\"#what\">What is the real relationship between GNU and Linux?</a>"
 msgstr ""
 "<a href=\"#what\">Was ist die tatsächliche Beziehung zwischen <em>GNU</em> "
 "und <em>Linux</em>?</a>"
@@ -399,9 +404,15 @@
 "den Namen <b>GNU/Linux</b> zu verwenden?</a>"
 
 #. type: Content of: <ul><li>
+# | <a href=\"#allgpled\">Should the [-GNU/[name]-] {+GNU/<i>name</i>+}
+# | convention be applied to all programs that are GPL'ed?</a>
+#, fuzzy
+#| msgid ""
+#| "<a href=\"#allgpled\">Should the GNU/[name] convention be applied to all "
+#| "programs that are GPL'ed?</a>"
 msgid ""
-"<a href=\"#allgpled\">Should the GNU/[name] convention be applied to all "
-"programs that are GPL'ed?</a>"
+"<a href=\"#allgpled\">Should the GNU/<i>name</i> convention be applied to "
+"all programs that are GPL'ed?</a>"
 msgstr ""
 "<a href=\"#allgpled\">Sollte die GNU/[Name]-Konvention auf alle Programme "
 "angewandt werden, die GPL lizenziert sind?</a>"
@@ -982,10 +993,19 @@
 "Werte das System ins Leben gerufen haben."
 
 #. type: Content of: <dl><dt>
+# | Since everyone knows [-GNU's-] {+the+} role {+of GNU+} in developing the
+# | system, doesn't the &ldquo;GNU/&rdquo; in the name go without saying?
+# | <span class=\"anchor-reference-id\">(<a
+# | href=\"#everyoneknows\">#everyoneknows</a>)</span>
+#, fuzzy
+#| msgid ""
+#| "Since everyone knows GNU's role in developing the system, doesn't the "
+#| "&ldquo;GNU/&rdquo; in the name go without saying? <span class=\"anchor-"
+#| "reference-id\">(<a href=\"#everyoneknows\">#everyoneknows</a>)</span>"
 msgid ""
-"Since everyone knows GNU's role in developing the system, doesn't the &ldquo;"
-"GNU/&rdquo; in the name go without saying? <span class=\"anchor-reference-id"
-"\">(<a href=\"#everyoneknows\">#everyoneknows</a>)</span>"
+"Since everyone knows the role of GNU in developing the system, doesn't the "
+"&ldquo;GNU/&rdquo; in the name go without saying? <span class=\"anchor-"
+"reference-id\">(<a href=\"#everyoneknows\">#everyoneknows</a>)</span>"
 msgstr ""
 "Da jedem die Rolle von GNU bei der Entwicklung des Systems bekannt ist, ist "
 "die Erwähnung von <em>‚GNU/‘</em> im Namen noch nötig? <span 
class=\"anchor-"

Index: gnu/po/gnu-linux-faq.es.po
===================================================================
RCS file: /web/www/www/gnu/po/gnu-linux-faq.es.po,v
retrieving revision 1.116
retrieving revision 1.117
diff -u -b -r1.116 -r1.117
--- gnu/po/gnu-linux-faq.es.po  19 Jan 2018 01:01:54 -0000      1.116
+++ gnu/po/gnu-linux-faq.es.po  24 Jan 2018 12:33:17 -0000      1.117
@@ -10,7 +10,7 @@
 msgstr ""
 "Project-Id-Version: gnu-linux-faq.es\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2018-01-01 05:56+0000\n"
+"POT-Creation-Date: 2018-01-24 12:26+0000\n"
 "PO-Revision-Date: 2018-01-18 22:55+0100\n"
 "Last-Translator: Dora Scilipoti <dora AT gnu DOT org>\n"
 "Language-Team: Spanish <address@hidden>\n"
@@ -18,6 +18,7 @@
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
+"X-Outdated-Since: 2018-01-24 12:26+0000\n"
 "X-Generator: Poedit 1.6.10\n"
 "Plural-Forms: nplurals=2; plural=(n!=1);\n"
 
@@ -74,8 +75,13 @@
 msgstr "<a href=\"#whycare\">¿Por qué es importante el nombre?</a>"
 
 #. type: Content of: <ul><li>
+# | <a href=\"#what\">What is the real relationship between GNU and
+# | Linux{+?+}</a>
+#, fuzzy
+#| msgid ""
+#| "<a href=\"#what\">What is the real relationship between GNU and Linux</a>"
 msgid ""
-"<a href=\"#what\">What is the real relationship between GNU and Linux</a>"
+"<a href=\"#what\">What is the real relationship between GNU and Linux?</a>"
 msgstr ""
 "<a href=\"#what\">¿Cuál es la verdadera relación entre GNU y Linux?</a>"
 
@@ -398,9 +404,15 @@
 "empleara el nombre GNU/Linux?</a>"
 
 #. type: Content of: <ul><li>
+# | <a href=\"#allgpled\">Should the [-GNU/[name]-] {+GNU/<i>name</i>+}
+# | convention be applied to all programs that are GPL'ed?</a>
+#, fuzzy
+#| msgid ""
+#| "<a href=\"#allgpled\">Should the GNU/[name] convention be applied to all "
+#| "programs that are GPL'ed?</a>"
 msgid ""
-"<a href=\"#allgpled\">Should the GNU/[name] convention be applied to all "
-"programs that are GPL'ed?</a>"
+"<a href=\"#allgpled\">Should the GNU/<i>name</i> convention be applied to "
+"all programs that are GPL'ed?</a>"
 msgstr ""
 "<a href=\"#allgpled\">¿Debería la convención GNU/[nombre] aplicarse a 
todos "
 "los programas que estén bajo la GPL?</a>"
@@ -1000,10 +1012,19 @@
 
 # type: Content of: <dl><dt>
 #. type: Content of: <dl><dt>
-msgid ""
-"Since everyone knows GNU's role in developing the system, doesn't the &ldquo;"
-"GNU/&rdquo; in the name go without saying? <span class=\"anchor-reference-id"
-"\">(<a href=\"#everyoneknows\">#everyoneknows</a>)</span>"
+# | Since everyone knows [-GNU's-] {+the+} role {+of GNU+} in developing the
+# | system, doesn't the &ldquo;GNU/&rdquo; in the name go without saying?
+# | <span class=\"anchor-reference-id\">(<a
+# | href=\"#everyoneknows\">#everyoneknows</a>)</span>
+#, fuzzy
+#| msgid ""
+#| "Since everyone knows GNU's role in developing the system, doesn't the "
+#| "&ldquo;GNU/&rdquo; in the name go without saying? <span class=\"anchor-"
+#| "reference-id\">(<a href=\"#everyoneknows\">#everyoneknows</a>)</span>"
+msgid ""
+"Since everyone knows the role of GNU in developing the system, doesn't the "
+"&ldquo;GNU/&rdquo; in the name go without saying? <span class=\"anchor-"
+"reference-id\">(<a href=\"#everyoneknows\">#everyoneknows</a>)</span>"
 msgstr ""
 "Puesto que todos conocen el papel de GNU en el desarrollo del sistema, ¿no "
 "queda «GNU/» sobreentendido en el nombre sin necesidad de mencionarlo? 
<span "

Index: gnu/po/gnu-linux-faq.fr.po
===================================================================
RCS file: /web/www/www/gnu/po/gnu-linux-faq.fr.po,v
retrieving revision 1.107
retrieving revision 1.108
diff -u -b -r1.107 -r1.108
--- gnu/po/gnu-linux-faq.fr.po  1 Jan 2018 17:10:18 -0000       1.107
+++ gnu/po/gnu-linux-faq.fr.po  24 Jan 2018 12:33:18 -0000      1.108
@@ -10,7 +10,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: gnu-linux-faq.html\n"
-"POT-Creation-Date: 2018-01-01 05:56+0000\n"
+"POT-Creation-Date: 2018-01-24 12:26+0000\n"
 "PO-Revision-Date: 2018-01-01 17:56+0100\n"
 "Last-Translator: Sogal <sogal AT member.fsf.org>\n"
 "Language-Team: French <address@hidden>\n"
@@ -18,6 +18,7 @@
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
+"X-Outdated-Since: 2018-01-24 12:26+0000\n"
 "Plural-Forms: \n"
 "X-Generator: Gtranslator 2.91.5\n"
 
@@ -66,8 +67,13 @@
 msgstr "<a href=\"#whycare\">Pourquoi le nom est-il important ?</a>"
 
 #. type: Content of: <ul><li>
+# | <a href=\"#what\">What is the real relationship between GNU and
+# | Linux{+?+}</a>
+#, fuzzy
+#| msgid ""
+#| "<a href=\"#what\">What is the real relationship between GNU and Linux</a>"
 msgid ""
-"<a href=\"#what\">What is the real relationship between GNU and Linux</a>"
+"<a href=\"#what\">What is the real relationship between GNU and Linux?</a>"
 msgstr ""
 "<a href=\"#what\">Quelle est la relation exacte entre GNU et Linux ?</a>"
 
@@ -397,9 +403,15 @@
 "gens d'utiliser le nom GNU/Linux ?</a>"
 
 #. type: Content of: <ul><li>
+# | <a href=\"#allgpled\">Should the [-GNU/[name]-] {+GNU/<i>name</i>+}
+# | convention be applied to all programs that are GPL'ed?</a>
+#, fuzzy
+#| msgid ""
+#| "<a href=\"#allgpled\">Should the GNU/[name] convention be applied to all "
+#| "programs that are GPL'ed?</a>"
 msgid ""
-"<a href=\"#allgpled\">Should the GNU/[name] convention be applied to all "
-"programs that are GPL'ed?</a>"
+"<a href=\"#allgpled\">Should the GNU/<i>name</i> convention be applied to "
+"all programs that are GPL'ed?</a>"
 msgstr ""
 "<a href=\"#allgpled\">La convention GNU/[nom] doit-elle être appliquée à "
 "tous les programmes sous GPL ?</a>"
@@ -978,10 +990,19 @@
 "valeurs de liberté ont fait naître ce système."
 
 #. type: Content of: <dl><dt>
-msgid ""
-"Since everyone knows GNU's role in developing the system, doesn't the &ldquo;"
-"GNU/&rdquo; in the name go without saying? <span class=\"anchor-reference-id"
-"\">(<a href=\"#everyoneknows\">#everyoneknows</a>)</span>"
+# | Since everyone knows [-GNU's-] {+the+} role {+of GNU+} in developing the
+# | system, doesn't the &ldquo;GNU/&rdquo; in the name go without saying?
+# | <span class=\"anchor-reference-id\">(<a
+# | href=\"#everyoneknows\">#everyoneknows</a>)</span>
+#, fuzzy
+#| msgid ""
+#| "Since everyone knows GNU's role in developing the system, doesn't the "
+#| "&ldquo;GNU/&rdquo; in the name go without saying? <span class=\"anchor-"
+#| "reference-id\">(<a href=\"#everyoneknows\">#everyoneknows</a>)</span>"
+msgid ""
+"Since everyone knows the role of GNU in developing the system, doesn't the "
+"&ldquo;GNU/&rdquo; in the name go without saying? <span class=\"anchor-"
+"reference-id\">(<a href=\"#everyoneknows\">#everyoneknows</a>)</span>"
 msgstr ""
 "Puisque tout le monde connaît le rôle de GNU dans le développement du "
 "système, le « GNU/ » dans le nom ne va-t-il pas de soi ? <span class="

Index: gnu/po/gnu-linux-faq.hr-diff.html
===================================================================
RCS file: /web/www/www/gnu/po/gnu-linux-faq.hr-diff.html,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -b -r1.27 -r1.28
--- gnu/po/gnu-linux-faq.hr-diff.html   1 Jan 2018 07:20:31 -0000       1.27
+++ gnu/po/gnu-linux-faq.hr-diff.html   24 Jan 2018 12:33:18 -0000      1.28
@@ -37,7 +37,7 @@
 
 &lt;li&gt;&lt;a <span class="removed"><del><strong>href="#whycare" 
id="TOCwhycare"&gt;Why</strong></del></span> <span 
class="inserted"><ins><em>href="#whycare"&gt;Why</em></ins></span> is the name 
important?&lt;/a&gt;&lt;/li&gt;
 
-&lt;li&gt;&lt;a <span class="removed"><del><strong>href="#howerror" 
id="TOChowerror"&gt;How</strong></del></span> <span 
class="inserted"><ins><em>href="#what"&gt;What is the real relationship between 
GNU and Linux&lt;/a&gt;&lt;/li&gt;
+&lt;li&gt;&lt;a <span class="removed"><del><strong>href="#howerror" 
id="TOChowerror"&gt;How</strong></del></span> <span 
class="inserted"><ins><em>href="#what"&gt;What is the real relationship between 
GNU and Linux?&lt;/a&gt;&lt;/li&gt;
 
 &lt;li&gt;&lt;a href="#howerror"&gt;How</em></ins></span> did it come about 
that most
     people call the system &ldquo;Linux&rdquo;?&lt;/a&gt;&lt;/li&gt;
@@ -179,7 +179,7 @@
 &lt;li&gt;&lt;a <span class="removed"><del><strong>href="#wait" 
id="TOCwait"&gt;Why</strong></del></span> <span 
class="inserted"><ins><em>href="#wait"&gt;Why</em></ins></span> did you wait so 
long before
     asking people to use the name GNU/Linux?&lt;/a&gt;&lt;/li&gt;
 
-&lt;li&gt;&lt;a <span class="removed"><del><strong>href="#allgpled" 
id="TOCallgpled"&gt;Should</strong></del></span> <span 
class="inserted"><ins><em>href="#allgpled"&gt;Should</em></ins></span> the 
GNU/[name] convention
+&lt;li&gt;&lt;a <span class="removed"><del><strong>href="#allgpled" 
id="TOCallgpled"&gt;Should</strong></del></span> <span 
class="inserted"><ins><em>href="#allgpled"&gt;Should</em></ins></span> the 
<span class="removed"><del><strong>GNU/[name]</strong></del></span> <span 
class="inserted"><ins><em>GNU/&lt;i&gt;name&lt;/i&gt;</em></ins></span> 
convention
     be applied to all programs that are GPL'ed?&lt;/a&gt;&lt;/li&gt;
 
 &lt;li&gt;&lt;a <span class="removed"><del><strong>href="#unix" 
id="TOCunix"&gt;Since</strong></del></span> <span 
class="inserted"><ins><em>href="#unix"&gt;Since</em></ins></span> much of GNU 
comes from Unix,
@@ -434,7 +434,8 @@
 &lt;/dd&gt;
 
 &lt;dt id="everyoneknows"&gt;Since everyone knows
-    GNU's role in developing the system, doesn't the &ldquo;GNU/&rdquo; in the
+    <span class="removed"><del><strong>GNU's</strong></del></span> <span 
class="inserted"><ins><em>the</em></ins></span> role
+    <span class="inserted"><ins><em>of GNU</em></ins></span> in developing the 
system, doesn't the &ldquo;GNU/&rdquo; in the
     name go without saying? &lt;span class="anchor-reference-id"&gt;(&lt;a 
href="#everyoneknows"&gt;#everyoneknows&lt;/a&gt;)&lt;/span&gt;&lt;/dt&gt;
 
 &lt;dd&gt;Experience shows that the system's users, and the computer-using
@@ -593,12 +594,11 @@
 than the misuse</strong></del></span>
 <span class="inserted"><ins><em>Many &lt;a href="/distros/distros.html"&gt; 
packaged and installable
 versions</em></ins></span> of <span class="removed"><del><strong>the name 
&ldquo;Linux&rdquo;.  Normally an operating system</strong></del></span> <span 
class="inserted"><ins><em>GNU&lt;/a&gt; are available.  None of 
them</em></ins></span> is
-<span class="removed"><del><strong>developed as a single unified project, and 
the developers choose a
-name for</strong></del></span> <span class="inserted"><ins><em>called simply
+<span class="removed"><del><strong>developed as a single unified project, 
and</strong></del></span> <span class="inserted"><ins><em>called simply
 &ldquo;GNU&rdquo;, but GNU is what they basically are.
 
 &lt;p&gt;
-We expected to release the GNU system packaged for installation, but
+We expected to release</em></ins></span> the <span 
class="removed"><del><strong>developers choose</strong></del></span> <span 
class="inserted"><ins><em>GNU system packaged for installation, but
 this plan was overtaken by events: in 1992 others were already
 packaging GNU variants containing Linux.  Starting in 1993 we
 sponsored an effort to make a better and freer GNU/Linux distribution,
@@ -633,8 +633,8 @@
 &lt;dd&gt;
 That practice seems to be very rare&mdash;we can't find any examples other
 than the misuse of the name &ldquo;Linux&rdquo;.  Normally an operating system 
is
-developed as a single unified project, and the developers choose a
-name for</em></ins></span> the system as a whole.  The kernel usually does not 
have a
+developed as a single unified project, and the developers 
choose</em></ins></span> a
+name for the system as a whole.  The kernel usually does not have a
 name of its own&mdash;instead, people say &ldquo;the kernel of 
such-and-such&rdquo; or
 &ldquo;the such-and-such kernel&rdquo;.
 &lt;p&gt;
@@ -1585,7 +1585,7 @@
 
 <span class="inserted"><ins><em>&lt;p 
class="unprintable"&gt;Updated:</em></ins></span>
 &lt;!-- timestamp start --&gt;
-$Date: 2018/01/01 07:20:31 $
+$Date: 2018/01/24 12:33:18 $
 &lt;!-- timestamp end --&gt;
 &lt;/p&gt;
 &lt;/div&gt;

Index: gnu/po/gnu-linux-faq.hr.po
===================================================================
RCS file: /web/www/www/gnu/po/gnu-linux-faq.hr.po,v
retrieving revision 1.34
retrieving revision 1.35
diff -u -b -r1.34 -r1.35
--- gnu/po/gnu-linux-faq.hr.po  1 Jan 2018 06:21:53 -0000       1.34
+++ gnu/po/gnu-linux-faq.hr.po  24 Jan 2018 12:33:18 -0000      1.35
@@ -6,7 +6,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: gnu-linux-faq.html\n"
-"POT-Creation-Date: 2018-01-01 05:56+0000\n"
+"POT-Creation-Date: 2018-01-24 12:26+0000\n"
 "PO-Revision-Date: 2013-05-30 22:45+0100\n"
 "Last-Translator: Martina Bebek <address@hidden>\n"
 "Language-Team: GNU Croatian Translation Team <address@hidden>\n"
@@ -67,11 +67,11 @@
 
 #. type: Content of: <ul><li>
 # | <a [-href=\"#why\">Why do you call it GNU/Linux-] {+href=\"#what\">What is
-# | the real relationship between GNU+} and [-not Linux?</a>-] {+Linux</a>+}
+# | the real relationship between GNU+} and [-not-] Linux?</a>
 #, fuzzy
 #| msgid "<a href=\"#why\">Why do you call it GNU/Linux and not Linux?</a>"
 msgid ""
-"<a href=\"#what\">What is the real relationship between GNU and Linux</a>"
+"<a href=\"#what\">What is the real relationship between GNU and Linux?</a>"
 msgstr "<a href=\"#why\">Zašto naziv GNU/Linux a ne Linux?</a>"
 
 #. type: Content of: <ul><li>
@@ -443,9 +443,15 @@
 "korištenje naziva GNU/Linux?</a>"
 
 #. type: Content of: <ul><li>
+# | <a href=\"#allgpled\">Should the [-GNU/[name]-] {+GNU/<i>name</i>+}
+# | convention be applied to all programs that are GPL'ed?</a>
+#, fuzzy
+#| msgid ""
+#| "<a href=\"#allgpled\">Should the GNU/[name] convention be applied to all "
+#| "programs that are GPL'ed?</a>"
 msgid ""
-"<a href=\"#allgpled\">Should the GNU/[name] convention be applied to all "
-"programs that are GPL'ed?</a>"
+"<a href=\"#allgpled\">Should the GNU/<i>name</i> convention be applied to "
+"all programs that are GPL'ed?</a>"
 msgstr ""
 "<a href=\"#allgpled\">Bi li se pravilo o nazivu GNU/[naziv] trebalo "
 "slijediti u svim programima koji su pod licencom GPL?</a>"
@@ -1051,10 +1057,19 @@
 "slobode koje su iznjedrile ovaj sustav."
 
 #. type: Content of: <dl><dt>
+# | Since everyone knows [-GNU's-] {+the+} role {+of GNU+} in developing the
+# | system, doesn't the &ldquo;GNU/&rdquo; in the name go without saying?
+# | <span class=\"anchor-reference-id\">(<a
+# | href=\"#everyoneknows\">#everyoneknows</a>)</span>
+#, fuzzy
+#| msgid ""
+#| "Since everyone knows GNU's role in developing the system, doesn't the "
+#| "&ldquo;GNU/&rdquo; in the name go without saying? <span class=\"anchor-"
+#| "reference-id\">(<a href=\"#everyoneknows\">#everyoneknows</a>)</span>"
 msgid ""
-"Since everyone knows GNU's role in developing the system, doesn't the &ldquo;"
-"GNU/&rdquo; in the name go without saying? <span class=\"anchor-reference-id"
-"\">(<a href=\"#everyoneknows\">#everyoneknows</a>)</span>"
+"Since everyone knows the role of GNU in developing the system, doesn't the "
+"&ldquo;GNU/&rdquo; in the name go without saying? <span class=\"anchor-"
+"reference-id\">(<a href=\"#everyoneknows\">#everyoneknows</a>)</span>"
 msgstr ""
 "Kako svi znaju za ulogu GNU-a u razvoju sustava, nije li &ldquo;GNU/&rdquo; "
 "u nazivu podrazumijevano? <span class=\"anchor-reference-id\">(<a href="

Index: gnu/po/gnu-linux-faq.it.po
===================================================================
RCS file: /web/www/www/gnu/po/gnu-linux-faq.it.po,v
retrieving revision 1.40
retrieving revision 1.41
diff -u -b -r1.40 -r1.41
--- gnu/po/gnu-linux-faq.it.po  20 Jan 2018 19:31:06 -0000      1.40
+++ gnu/po/gnu-linux-faq.it.po  24 Jan 2018 12:33:18 -0000      1.41
@@ -7,7 +7,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: gnu-linux-faq.html\n"
-"POT-Creation-Date: 2018-01-01 05:56+0000\n"
+"POT-Creation-Date: 2018-01-24 12:26+0000\n"
 "PO-Revision-Date: 2018-01-20 19:53+0100\n"
 "Last-Translator: Andrea Pescetti <address@hidden>\n"
 "Language-Team: Italian <address@hidden>\n"
@@ -15,6 +15,7 @@
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
+"X-Outdated-Since: 2018-01-24 12:26+0000\n"
 "X-Generator: Poedit 2.0.3\n"
 
 #. type: Content of: <title>
@@ -61,8 +62,13 @@
 msgstr "<a href=\"#whycare\">Perché il nome è così importante?</a>"
 
 #. type: Content of: <ul><li>
+# | <a href=\"#what\">What is the real relationship between GNU and
+# | Linux{+?+}</a>
+#, fuzzy
+#| msgid ""
+#| "<a href=\"#what\">What is the real relationship between GNU and Linux</a>"
 msgid ""
-"<a href=\"#what\">What is the real relationship between GNU and Linux</a>"
+"<a href=\"#what\">What is the real relationship between GNU and Linux?</a>"
 msgstr "<a href=\"#what\">Qual è la vera relazione tra GNU e Linux?</a>"
 
 #. type: Content of: <ul><li>
@@ -386,9 +392,15 @@
 "gente di usare il nome GNU/Linux?</a>"
 
 #. type: Content of: <ul><li>
+# | <a href=\"#allgpled\">Should the [-GNU/[name]-] {+GNU/<i>name</i>+}
+# | convention be applied to all programs that are GPL'ed?</a>
+#, fuzzy
+#| msgid ""
+#| "<a href=\"#allgpled\">Should the GNU/[name] convention be applied to all "
+#| "programs that are GPL'ed?</a>"
 msgid ""
-"<a href=\"#allgpled\">Should the GNU/[name] convention be applied to all "
-"programs that are GPL'ed?</a>"
+"<a href=\"#allgpled\">Should the GNU/<i>name</i> convention be applied to "
+"all programs that are GPL'ed?</a>"
 msgstr ""
 "<a href=\"#allgpled\">Sarebbe giusto applicare la convenzione GNU/[nome] a "
 "tutti i programmi rilasciati sotto licenza GPL?</a>"
@@ -960,10 +972,19 @@
 "altri di questi valori che hanno portato alla creazione del sistema."
 
 #. type: Content of: <dl><dt>
-msgid ""
-"Since everyone knows GNU's role in developing the system, doesn't the &ldquo;"
-"GNU/&rdquo; in the name go without saying? <span class=\"anchor-reference-id"
-"\">(<a href=\"#everyoneknows\">#everyoneknows</a>)</span>"
+# | Since everyone knows [-GNU's-] {+the+} role {+of GNU+} in developing the
+# | system, doesn't the &ldquo;GNU/&rdquo; in the name go without saying?
+# | <span class=\"anchor-reference-id\">(<a
+# | href=\"#everyoneknows\">#everyoneknows</a>)</span>
+#, fuzzy
+#| msgid ""
+#| "Since everyone knows GNU's role in developing the system, doesn't the "
+#| "&ldquo;GNU/&rdquo; in the name go without saying? <span class=\"anchor-"
+#| "reference-id\">(<a href=\"#everyoneknows\">#everyoneknows</a>)</span>"
+msgid ""
+"Since everyone knows the role of GNU in developing the system, doesn't the "
+"&ldquo;GNU/&rdquo; in the name go without saying? <span class=\"anchor-"
+"reference-id\">(<a href=\"#everyoneknows\">#everyoneknows</a>)</span>"
 msgstr ""
 "Visto che tutti conoscono il ruolo di GNU nello sviluppo del sistema, c'è "
 "davvero bisogno di specificare la parola &ldquo;GNU/&rdquo;? <span class="

Index: gnu/po/gnu-linux-faq.ja-diff.html
===================================================================
RCS file: /web/www/www/gnu/po/gnu-linux-faq.ja-diff.html,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -b -r1.7 -r1.8
--- gnu/po/gnu-linux-faq.ja-diff.html   1 Jan 2018 07:20:31 -0000       1.7
+++ gnu/po/gnu-linux-faq.ja-diff.html   24 Jan 2018 12:33:18 -0000      1.8
@@ -37,7 +37,7 @@
 
 &lt;li&gt;&lt;a <span class="removed"><del><strong>href="#whycare" 
id="TOCwhycare"&gt;Why</strong></del></span> <span 
class="inserted"><ins><em>href="#whycare"&gt;Why</em></ins></span> is the name 
important?&lt;/a&gt;&lt;/li&gt;
 
-&lt;li&gt;&lt;a <span class="removed"><del><strong>href="#howerror" 
id="TOChowerror"&gt;How</strong></del></span> <span 
class="inserted"><ins><em>href="#what"&gt;What is the real relationship between 
GNU and Linux&lt;/a&gt;&lt;/li&gt;
+&lt;li&gt;&lt;a <span class="removed"><del><strong>href="#howerror" 
id="TOChowerror"&gt;How</strong></del></span> <span 
class="inserted"><ins><em>href="#what"&gt;What is the real relationship between 
GNU and Linux?&lt;/a&gt;&lt;/li&gt;
 
 &lt;li&gt;&lt;a href="#howerror"&gt;How</em></ins></span> did it come about 
that most
     people call the system &ldquo;Linux&rdquo;?&lt;/a&gt;&lt;/li&gt;
@@ -179,7 +179,7 @@
 &lt;li&gt;&lt;a <span class="removed"><del><strong>href="#wait" 
id="TOCwait"&gt;Why</strong></del></span> <span 
class="inserted"><ins><em>href="#wait"&gt;Why</em></ins></span> did you wait so 
long before
     asking people to use the name GNU/Linux?&lt;/a&gt;&lt;/li&gt;
 
-&lt;li&gt;&lt;a <span class="removed"><del><strong>href="#allgpled" 
id="TOCallgpled"&gt;Should</strong></del></span> <span 
class="inserted"><ins><em>href="#allgpled"&gt;Should</em></ins></span> the 
GNU/[name] convention
+&lt;li&gt;&lt;a <span class="removed"><del><strong>href="#allgpled" 
id="TOCallgpled"&gt;Should</strong></del></span> <span 
class="inserted"><ins><em>href="#allgpled"&gt;Should</em></ins></span> the 
<span class="removed"><del><strong>GNU/[name]</strong></del></span> <span 
class="inserted"><ins><em>GNU/&lt;i&gt;name&lt;/i&gt;</em></ins></span> 
convention
     be applied to all programs that are GPL'ed?&lt;/a&gt;&lt;/li&gt;
 
 &lt;li&gt;&lt;a <span class="removed"><del><strong>href="#unix" 
id="TOCunix"&gt;Since</strong></del></span> <span 
class="inserted"><ins><em>href="#unix"&gt;Since</em></ins></span> much of GNU 
comes from Unix,
@@ -434,7 +434,8 @@
 &lt;/dd&gt;
 
 &lt;dt id="everyoneknows"&gt;Since everyone knows
-    GNU's role in developing the system, doesn't the &ldquo;GNU/&rdquo; in the
+    <span class="removed"><del><strong>GNU's</strong></del></span> <span 
class="inserted"><ins><em>the</em></ins></span> role
+    <span class="inserted"><ins><em>of GNU</em></ins></span> in developing the 
system, doesn't the &ldquo;GNU/&rdquo; in the
     name go without saying? &lt;span class="anchor-reference-id"&gt;(&lt;a 
href="#everyoneknows"&gt;#everyoneknows&lt;/a&gt;)&lt;/span&gt;&lt;/dt&gt;
 
 &lt;dd&gt;Experience shows that the system's users, and the computer-using
@@ -1570,7 +1571,7 @@
 
 &lt;p class="unprintable"&gt;Updated:
 &lt;!-- timestamp start --&gt;
-$Date: 2018/01/01 07:20:31 $
+$Date: 2018/01/24 12:33:18 $
 &lt;!-- timestamp end --&gt;
 &lt;/p&gt;
 &lt;/div&gt;

Index: gnu/po/gnu-linux-faq.ja.po
===================================================================
RCS file: /web/www/www/gnu/po/gnu-linux-faq.ja.po,v
retrieving revision 1.75
retrieving revision 1.76
diff -u -b -r1.75 -r1.76
--- gnu/po/gnu-linux-faq.ja.po  1 Jan 2018 06:21:53 -0000       1.75
+++ gnu/po/gnu-linux-faq.ja.po  24 Jan 2018 12:33:18 -0000      1.76
@@ -6,7 +6,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: gnu-linux-faq.html\n"
-"POT-Creation-Date: 2018-01-01 05:56+0000\n"
+"POT-Creation-Date: 2018-01-24 12:26+0000\n"
 "PO-Revision-Date: 2016-08-22 13:11+0900\n"
 "Last-Translator: NIIBE Yutaka <address@hidden>\n"
 "Language-Team: Japanese <address@hidden>\n"
@@ -63,7 +63,7 @@
 #, fuzzy
 #| msgid "<a href=\"#why\">Why do you call it GNU/Linux and not Linux?</a>"
 msgid ""
-"<a href=\"#what\">What is the real relationship between GNU and Linux</a>"
+"<a href=\"#what\">What is the real relationship between GNU and Linux?</a>"
 msgstr "<a 
href=\"#why\">なぜそれをGNU/Linuxと呼びLinuxと呼ばないのですか?</a>"
 
 #. type: Content of: <ul><li>
@@ -389,9 +389,13 @@
 "待ったのはなぜですか?</a>"
 
 #. type: Content of: <ul><li>
+#, fuzzy
+#| msgid ""
+#| "<a href=\"#allgpled\">Should the GNU/[name] convention be applied to all "
+#| "programs that are GPL'ed?</a>"
 msgid ""
-"<a href=\"#allgpled\">Should the GNU/[name] convention be applied to all "
-"programs that are GPL'ed?</a>"
+"<a href=\"#allgpled\">Should the GNU/<i>name</i> convention be applied to "
+"all programs that are GPL'ed?</a>"
 msgstr ""
 "<a href=\"#allgpled\">GNU/[name]の慣例はGPLのすべてのプログラム
に適用されるべ"
 "きですか?</a>"
@@ -959,10 +963,15 @@
 "たらした自由の価値を、ほかの人々
に伝えようとするのです。"
 
 #. type: Content of: <dl><dt>
-msgid ""
-"Since everyone knows GNU's role in developing the system, doesn't the &ldquo;"
-"GNU/&rdquo; in the name go without saying? <span class=\"anchor-reference-id"
-"\">(<a href=\"#everyoneknows\">#everyoneknows</a>)</span>"
+#, fuzzy
+#| msgid ""
+#| "Since everyone knows GNU's role in developing the system, doesn't the "
+#| "&ldquo;GNU/&rdquo; in the name go without saying? <span class=\"anchor-"
+#| "reference-id\">(<a href=\"#everyoneknows\">#everyoneknows</a>)</span>"
+msgid ""
+"Since everyone knows the role of GNU in developing the system, doesn't the "
+"&ldquo;GNU/&rdquo; in the name go without saying? <span class=\"anchor-"
+"reference-id\">(<a href=\"#everyoneknows\">#everyoneknows</a>)</span>"
 msgstr ""
 "システムを開発するGNUの役割をみんなが知っているのだ
から、名前の中に&ldquo;"
 "GNU/&rdquo;はなくても良いのではないでしょうか?<span 
class=\"anchor-reference-"

Index: gnu/po/gnu-linux-faq.ko-diff.html
===================================================================
RCS file: /web/www/www/gnu/po/gnu-linux-faq.ko-diff.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- gnu/po/gnu-linux-faq.ko-diff.html   1 Jan 2018 07:20:31 -0000       1.9
+++ gnu/po/gnu-linux-faq.ko-diff.html   24 Jan 2018 12:33:18 -0000      1.10
@@ -37,7 +37,7 @@
 
 &lt;li&gt;&lt;a <span class="removed"><del><strong>href="#whycare" 
id="TOCwhycare"&gt;Why</strong></del></span> <span 
class="inserted"><ins><em>href="#whycare"&gt;Why</em></ins></span> is the name 
important?&lt;/a&gt;&lt;/li&gt;
 
-&lt;li&gt;&lt;a <span class="removed"><del><strong>href="#howerror" 
id="TOChowerror"&gt;How</strong></del></span> <span 
class="inserted"><ins><em>href="#what"&gt;What is the real relationship between 
GNU and Linux&lt;/a&gt;&lt;/li&gt;
+&lt;li&gt;&lt;a <span class="removed"><del><strong>href="#howerror" 
id="TOChowerror"&gt;How</strong></del></span> <span 
class="inserted"><ins><em>href="#what"&gt;What is the real relationship between 
GNU and Linux?&lt;/a&gt;&lt;/li&gt;
 
 &lt;li&gt;&lt;a href="#howerror"&gt;How</em></ins></span> did it come about 
that most
     people call the system &ldquo;Linux&rdquo;?&lt;/a&gt;&lt;/li&gt;
@@ -179,7 +179,7 @@
 &lt;li&gt;&lt;a <span class="removed"><del><strong>href="#wait" 
id="TOCwait"&gt;Why</strong></del></span> <span 
class="inserted"><ins><em>href="#wait"&gt;Why</em></ins></span> did you wait so 
long before
     asking people to use the name GNU/Linux?&lt;/a&gt;&lt;/li&gt;
 
-&lt;li&gt;&lt;a <span class="removed"><del><strong>href="#allgpled" 
id="TOCallgpled"&gt;Should</strong></del></span> <span 
class="inserted"><ins><em>href="#allgpled"&gt;Should</em></ins></span> the 
GNU/[name] convention
+&lt;li&gt;&lt;a <span class="removed"><del><strong>href="#allgpled" 
id="TOCallgpled"&gt;Should</strong></del></span> <span 
class="inserted"><ins><em>href="#allgpled"&gt;Should</em></ins></span> the 
<span class="removed"><del><strong>GNU/[name]</strong></del></span> <span 
class="inserted"><ins><em>GNU/&lt;i&gt;name&lt;/i&gt;</em></ins></span> 
convention
     be applied to all programs that are GPL'ed?&lt;/a&gt;&lt;/li&gt;
 
 &lt;li&gt;&lt;a <span class="removed"><del><strong>href="#unix" 
id="TOCunix"&gt;Since</strong></del></span> <span 
class="inserted"><ins><em>href="#unix"&gt;Since</em></ins></span> much of GNU 
comes from Unix,
@@ -434,7 +434,8 @@
 &lt;/dd&gt;
 
 &lt;dt id="everyoneknows"&gt;Since everyone knows
-    GNU's role in developing the system, doesn't the &ldquo;GNU/&rdquo; in the
+    <span class="removed"><del><strong>GNU's</strong></del></span> <span 
class="inserted"><ins><em>the</em></ins></span> role
+    <span class="inserted"><ins><em>of GNU</em></ins></span> in developing the 
system, doesn't the &ldquo;GNU/&rdquo; in the
     name go without saying? &lt;span class="anchor-reference-id"&gt;(&lt;a 
href="#everyoneknows"&gt;#everyoneknows&lt;/a&gt;)&lt;/span&gt;&lt;/dt&gt;
 
 &lt;dd&gt;Experience shows that the system's users, and the computer-using
@@ -1574,7 +1575,7 @@
 
 &lt;p class="unprintable"&gt;Updated:
 &lt;!-- timestamp start --&gt;
-$Date: 2018/01/01 07:20:31 $
+$Date: 2018/01/24 12:33:18 $
 &lt;!-- timestamp end --&gt;
 &lt;/p&gt;
 &lt;/div&gt;

Index: gnu/po/gnu-linux-faq.ko.po
===================================================================
RCS file: /web/www/www/gnu/po/gnu-linux-faq.ko.po,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -b -r1.21 -r1.22
--- gnu/po/gnu-linux-faq.ko.po  1 Jan 2018 06:21:53 -0000       1.21
+++ gnu/po/gnu-linux-faq.ko.po  24 Jan 2018 12:33:18 -0000      1.22
@@ -6,7 +6,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: gnu-linux-faq.html\n"
-"POT-Creation-Date: 2018-01-01 05:56+0000\n"
+"POT-Creation-Date: 2018-01-24 12:26+0000\n"
 "PO-Revision-Date: 2016-05-21 13:58+0900\n"
 "Last-Translator: Jongmin Yoon <address@hidden>\n"
 "Language-Team: Korean <address@hidden>\n"
@@ -63,7 +63,7 @@
 #, fuzzy
 #| msgid "<a href=\"#why\">Why do you call it GNU/Linux and not Linux?</a>"
 msgid ""
-"<a href=\"#what\">What is the real relationship between GNU and Linux</a>"
+"<a href=\"#what\">What is the real relationship between GNU and Linux?</a>"
 msgstr "<a href=\"#why\"> 왜 Linux가 아니라 GNU/Linux라고 
부르나요?</a>"
 
 #. type: Content of: <ul><li>
@@ -387,9 +387,13 @@
 "그리 오래 기다렸었나요?</a>"
 
 #. type: Content of: <ul><li>
+#, fuzzy
+#| msgid ""
+#| "<a href=\"#allgpled\">Should the GNU/[name] convention be applied to all "
+#| "programs that are GPL'ed?</a>"
 msgid ""
-"<a href=\"#allgpled\">Should the GNU/[name] convention be applied to all "
-"programs that are GPL'ed?</a>"
+"<a href=\"#allgpled\">Should the GNU/<i>name</i> convention be applied to "
+"all programs that are GPL'ed?</a>"
 msgstr ""
 "<a href=\"#allgpled\">GNU/[name]은 GPL 프로그램에전부 ì 
ìš©í•´ì•¼í•˜ë‚˜ìš”?</a>"
 
@@ -940,10 +944,15 @@
 "는 것입니다."
 
 #. type: Content of: <dl><dt>
-msgid ""
-"Since everyone knows GNU's role in developing the system, doesn't the &ldquo;"
-"GNU/&rdquo; in the name go without saying? <span class=\"anchor-reference-id"
-"\">(<a href=\"#everyoneknows\">#everyoneknows</a>)</span>"
+#, fuzzy
+#| msgid ""
+#| "Since everyone knows GNU's role in developing the system, doesn't the "
+#| "&ldquo;GNU/&rdquo; in the name go without saying? <span class=\"anchor-"
+#| "reference-id\">(<a href=\"#everyoneknows\">#everyoneknows</a>)</span>"
+msgid ""
+"Since everyone knows the role of GNU in developing the system, doesn't the "
+"&ldquo;GNU/&rdquo; in the name go without saying? <span class=\"anchor-"
+"reference-id\">(<a href=\"#everyoneknows\">#everyoneknows</a>)</span>"
 msgstr ""
 "모든 사람이 시스템 개발에서 GNU가 한 일을 알기 때문에 
이름에서 &ldquo;GNU/"
 "&rdquo;는 없어도 되지 않을까요?<span 
class=\"anchor-reference-id\">(<a href="

Index: gnu/po/gnu-linux-faq.nl.po
===================================================================
RCS file: /web/www/www/gnu/po/gnu-linux-faq.nl.po,v
retrieving revision 1.55
retrieving revision 1.56
diff -u -b -r1.55 -r1.56
--- gnu/po/gnu-linux-faq.nl.po  1 Jan 2018 06:21:53 -0000       1.55
+++ gnu/po/gnu-linux-faq.nl.po  24 Jan 2018 12:33:18 -0000      1.56
@@ -9,7 +9,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: gnu-linux-faq.html\n"
-"POT-Creation-Date: 2018-01-01 05:56+0000\n"
+"POT-Creation-Date: 2018-01-24 12:26+0000\n"
 "PO-Revision-Date: \n"
 "Last-Translator: Justin van Steijn <address@hidden>\n"
 "Language-Team: Dutch\n"
@@ -65,8 +65,13 @@
 msgstr "<a href=\"#whycare\">Waarom is de naam belangrijk?</a>"
 
 #. type: Content of: <ul><li>
+# | <a href=\"#what\">What is the real relationship between GNU and
+# | Linux{+?+}</a>
+#, fuzzy
+#| msgid ""
+#| "<a href=\"#what\">What is the real relationship between GNU and Linux</a>"
 msgid ""
-"<a href=\"#what\">What is the real relationship between GNU and Linux</a>"
+"<a href=\"#what\">What is the real relationship between GNU and Linux?</a>"
 msgstr "<a href=\"#what\">Wat is de echte relatie tussen GNU en Linux?</a>"
 
 #. type: Content of: <ul><li>
@@ -390,9 +395,15 @@
 "systeem GNU/Linux te noemen?</a>"
 
 #. type: Content of: <ul><li>
+# | <a href=\"#allgpled\">Should the [-GNU/[name]-] {+GNU/<i>name</i>+}
+# | convention be applied to all programs that are GPL'ed?</a>
+#, fuzzy
+#| msgid ""
+#| "<a href=\"#allgpled\">Should the GNU/[name] convention be applied to all "
+#| "programs that are GPL'ed?</a>"
 msgid ""
-"<a href=\"#allgpled\">Should the GNU/[name] convention be applied to all "
-"programs that are GPL'ed?</a>"
+"<a href=\"#allgpled\">Should the GNU/<i>name</i> convention be applied to "
+"all programs that are GPL'ed?</a>"
 msgstr ""
 "<a href=\"#allgpled\">Moeten we de constructie GNU/[naam] toepassen op alle "
 "programma's die onder de GPL vallen?</a>"
@@ -963,10 +974,19 @@
 "waarden dit systeem hebben opgeleverd."
 
 #. type: Content of: <dl><dt>
+# | Since everyone knows [-GNU's-] {+the+} role {+of GNU+} in developing the
+# | system, doesn't the &ldquo;GNU/&rdquo; in the name go without saying?
+# | <span class=\"anchor-reference-id\">(<a
+# | href=\"#everyoneknows\">#everyoneknows</a>)</span>
+#, fuzzy
+#| msgid ""
+#| "Since everyone knows GNU's role in developing the system, doesn't the "
+#| "&ldquo;GNU/&rdquo; in the name go without saying? <span class=\"anchor-"
+#| "reference-id\">(<a href=\"#everyoneknows\">#everyoneknows</a>)</span>"
 msgid ""
-"Since everyone knows GNU's role in developing the system, doesn't the &ldquo;"
-"GNU/&rdquo; in the name go without saying? <span class=\"anchor-reference-id"
-"\">(<a href=\"#everyoneknows\">#everyoneknows</a>)</span>"
+"Since everyone knows the role of GNU in developing the system, doesn't the "
+"&ldquo;GNU/&rdquo; in the name go without saying? <span class=\"anchor-"
+"reference-id\">(<a href=\"#everyoneknows\">#everyoneknows</a>)</span>"
 msgstr ""
 "Iedereen kent toch de rol van GNU in de ontwikkeling van dit systeem, "
 "spreekt het &ldquo;GNU/&rdquo; dan niet vanzelf? <span class=\"anchor-"

Index: gnu/po/gnu-linux-faq.pl-diff.html
===================================================================
RCS file: /web/www/www/gnu/po/gnu-linux-faq.pl-diff.html,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -b -r1.14 -r1.15
--- gnu/po/gnu-linux-faq.pl-diff.html   1 Jan 2018 07:20:31 -0000       1.14
+++ gnu/po/gnu-linux-faq.pl-diff.html   24 Jan 2018 12:33:18 -0000      1.15
@@ -37,7 +37,7 @@
 
 &lt;li&gt;&lt;a <span class="removed"><del><strong>href="#whycare" 
id="TOCwhycare"&gt;Why</strong></del></span> <span 
class="inserted"><ins><em>href="#whycare"&gt;Why</em></ins></span> is the name 
important?&lt;/a&gt;&lt;/li&gt;
 
-&lt;li&gt;&lt;a <span class="removed"><del><strong>href="#howerror" 
id="TOChowerror"&gt;How</strong></del></span> <span 
class="inserted"><ins><em>href="#what"&gt;What is the real relationship between 
GNU and Linux&lt;/a&gt;&lt;/li&gt;
+&lt;li&gt;&lt;a <span class="removed"><del><strong>href="#howerror" 
id="TOChowerror"&gt;How</strong></del></span> <span 
class="inserted"><ins><em>href="#what"&gt;What is the real relationship between 
GNU and Linux?&lt;/a&gt;&lt;/li&gt;
 
 &lt;li&gt;&lt;a href="#howerror"&gt;How</em></ins></span> did it come about 
that most
     people call the system &ldquo;Linux&rdquo;?&lt;/a&gt;&lt;/li&gt;
@@ -179,7 +179,7 @@
 &lt;li&gt;&lt;a <span class="removed"><del><strong>href="#wait" 
id="TOCwait"&gt;Why</strong></del></span> <span 
class="inserted"><ins><em>href="#wait"&gt;Why</em></ins></span> did you wait so 
long before
     asking people to use the name GNU/Linux?&lt;/a&gt;&lt;/li&gt;
 
-&lt;li&gt;&lt;a <span class="removed"><del><strong>href="#allgpled" 
id="TOCallgpled"&gt;Should</strong></del></span> <span 
class="inserted"><ins><em>href="#allgpled"&gt;Should</em></ins></span> the 
GNU/[name] convention
+&lt;li&gt;&lt;a <span class="removed"><del><strong>href="#allgpled" 
id="TOCallgpled"&gt;Should</strong></del></span> <span 
class="inserted"><ins><em>href="#allgpled"&gt;Should</em></ins></span> the 
<span class="removed"><del><strong>GNU/[name]</strong></del></span> <span 
class="inserted"><ins><em>GNU/&lt;i&gt;name&lt;/i&gt;</em></ins></span> 
convention
     be applied to all programs that are GPL'ed?&lt;/a&gt;&lt;/li&gt;
 
 &lt;li&gt;&lt;a <span class="removed"><del><strong>href="#unix" 
id="TOCunix"&gt;Since</strong></del></span> <span 
class="inserted"><ins><em>href="#unix"&gt;Since</em></ins></span> much of GNU 
comes from Unix,
@@ -434,7 +434,8 @@
 &lt;/dd&gt;
 
 &lt;dt id="everyoneknows"&gt;Since everyone knows
-    GNU's role in developing the system, doesn't the &ldquo;GNU/&rdquo; in the
+    <span class="removed"><del><strong>GNU's</strong></del></span> <span 
class="inserted"><ins><em>the</em></ins></span> role
+    <span class="inserted"><ins><em>of GNU</em></ins></span> in developing the 
system, doesn't the &ldquo;GNU/&rdquo; in the
     name go without saying? &lt;span class="anchor-reference-id"&gt;(&lt;a 
href="#everyoneknows"&gt;#everyoneknows&lt;/a&gt;)&lt;/span&gt;&lt;/dt&gt;
 
 &lt;dd&gt;Experience shows that the system's users, and the computer-using
@@ -1574,7 +1575,7 @@
 
 &lt;p class="unprintable"&gt;Updated:
 &lt;!-- timestamp start --&gt;
-$Date: 2018/01/01 07:20:31 $
+$Date: 2018/01/24 12:33:18 $
 &lt;!-- timestamp end --&gt;
 &lt;/p&gt;
 &lt;/div&gt;

Index: gnu/po/gnu-linux-faq.pl.po
===================================================================
RCS file: /web/www/www/gnu/po/gnu-linux-faq.pl.po,v
retrieving revision 1.77
retrieving revision 1.78
diff -u -b -r1.77 -r1.78
--- gnu/po/gnu-linux-faq.pl.po  1 Jan 2018 06:21:53 -0000       1.77
+++ gnu/po/gnu-linux-faq.pl.po  24 Jan 2018 12:33:18 -0000      1.78
@@ -8,7 +8,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: gnu-linux-faq.html\n"
-"POT-Creation-Date: 2018-01-01 05:56+0000\n"
+"POT-Creation-Date: 2018-01-24 12:26+0000\n"
 "PO-Revision-Date: 2016-02-16 21:20-0600\n"
 "Last-Translator: Jan Owoc <jsowoc AT gmail.com>\n"
 "Language-Team: Polish <address@hidden>\n"
@@ -71,11 +71,11 @@
 
 #. type: Content of: <ul><li>
 # | <a [-href=\"#why\">Why do you call it GNU/Linux-] {+href=\"#what\">What is
-# | the real relationship between GNU+} and [-not Linux?</a>-] {+Linux</a>+}
+# | the real relationship between GNU+} and [-not-] Linux?</a>
 #, fuzzy
 #| msgid "<a href=\"#why\">Why do you call it GNU/Linux and not Linux?</a>"
 msgid ""
-"<a href=\"#what\">What is the real relationship between GNU and Linux</a>"
+"<a href=\"#what\">What is the real relationship between GNU and Linux?</a>"
 msgstr ""
 "<a href=\"#why\">Czemu nazywacie ten system GNU/Linux a&nbsp;nie Linux?</a>"
 
@@ -420,9 +420,15 @@
 "o używanie nazwy GNU/Linux?</a>"
 
 #. type: Content of: <ul><li>
+# | <a href=\"#allgpled\">Should the [-GNU/[name]-] {+GNU/<i>name</i>+}
+# | convention be applied to all programs that are GPL'ed?</a>
+#, fuzzy
+#| msgid ""
+#| "<a href=\"#allgpled\">Should the GNU/[name] convention be applied to all "
+#| "programs that are GPL'ed?</a>"
 msgid ""
-"<a href=\"#allgpled\">Should the GNU/[name] convention be applied to all "
-"programs that are GPL'ed?</a>"
+"<a href=\"#allgpled\">Should the GNU/<i>name</i> convention be applied to "
+"all programs that are GPL'ed?</a>"
 msgstr ""
 "<a href=\"#allgpled\">Czy&nbsp;konwencja GNU/[nazwa] powinna być stosowana "
 "do&nbsp;wszystkich programów udostępnianych na&nbsp;licencji GPL?  </a>"
@@ -1017,10 +1023,19 @@
 "powstania systemu operacyjnego."
 
 #. type: Content of: <dl><dt>
-msgid ""
-"Since everyone knows GNU's role in developing the system, doesn't the &ldquo;"
-"GNU/&rdquo; in the name go without saying? <span class=\"anchor-reference-id"
-"\">(<a href=\"#everyoneknows\">#everyoneknows</a>)</span>"
+# | Since everyone knows [-GNU's-] {+the+} role {+of GNU+} in developing the
+# | system, doesn't the &ldquo;GNU/&rdquo; in the name go without saying?
+# | <span class=\"anchor-reference-id\">(<a
+# | href=\"#everyoneknows\">#everyoneknows</a>)</span>
+#, fuzzy
+#| msgid ""
+#| "Since everyone knows GNU's role in developing the system, doesn't the "
+#| "&ldquo;GNU/&rdquo; in the name go without saying? <span class=\"anchor-"
+#| "reference-id\">(<a href=\"#everyoneknows\">#everyoneknows</a>)</span>"
+msgid ""
+"Since everyone knows the role of GNU in developing the system, doesn't the "
+"&ldquo;GNU/&rdquo; in the name go without saying? <span class=\"anchor-"
+"reference-id\">(<a href=\"#everyoneknows\">#everyoneknows</a>)</span>"
 msgstr ""
 "Skoro wszyscy znają rolę [Projektu] GNU w&nbsp;rozwoju systemu 
operacyjnego, "
 "czy&nbsp;przedrostek \"GNU/\" nie będzie oczywisty bez&nbsp;używania go? "

Index: gnu/po/gnu-linux-faq.pot
===================================================================
RCS file: /web/www/www/gnu/po/gnu-linux-faq.pot,v
retrieving revision 1.49
retrieving revision 1.50
diff -u -b -r1.49 -r1.50
--- gnu/po/gnu-linux-faq.pot    1 Jan 2018 06:21:53 -0000       1.49
+++ gnu/po/gnu-linux-faq.pot    24 Jan 2018 12:33:18 -0000      1.50
@@ -7,7 +7,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: gnu-linux-faq.html\n"
-"POT-Creation-Date: 2018-01-01 05:56+0000\n"
+"POT-Creation-Date: 2018-01-24 12:26+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <address@hidden>\n"
 "Language-Team: LANGUAGE <address@hidden>\n"
@@ -51,7 +51,7 @@
 msgstr ""
 
 #. type: Content of: <ul><li>
-msgid "<a href=\"#what\">What is the real relationship between GNU and 
Linux</a>"
+msgid "<a href=\"#what\">What is the real relationship between GNU and 
Linux?</a>"
 msgstr ""
 
 #. type: Content of: <ul><li>
@@ -291,8 +291,8 @@
 
 #. type: Content of: <ul><li>
 msgid ""
-"<a href=\"#allgpled\">Should the GNU/[name] convention be applied to all "
-"programs that are GPL'ed?</a>"
+"<a href=\"#allgpled\">Should the GNU/<i>name</i> convention be applied to "
+"all programs that are GPL'ed?</a>"
 msgstr ""
 
 #. type: Content of: <ul><li>
@@ -683,7 +683,7 @@
 
 #. type: Content of: <dl><dt>
 msgid ""
-"Since everyone knows GNU's role in developing the system, doesn't the "
+"Since everyone knows the role of GNU in developing the system, doesn't the "
 "&ldquo;GNU/&rdquo; in the name go without saying? <span "
 "class=\"anchor-reference-id\">(<a "
 "href=\"#everyoneknows\">#everyoneknows</a>)</span>"

Index: gnu/po/gnu-linux-faq.ru.po
===================================================================
RCS file: /web/www/www/gnu/po/gnu-linux-faq.ru.po,v
retrieving revision 1.97
retrieving revision 1.98
diff -u -b -r1.97 -r1.98
--- gnu/po/gnu-linux-faq.ru.po  1 Jan 2018 11:40:08 -0000       1.97
+++ gnu/po/gnu-linux-faq.ru.po  24 Jan 2018 12:33:18 -0000      1.98
@@ -8,7 +8,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: gnu-linux-faq.html\n"
-"POT-Creation-Date: 2018-01-01 05:56+0000\n"
+"POT-Creation-Date: 2018-01-24 12:26+0000\n"
 "PO-Revision-Date: 2018-01-01 17:17+0000\n"
 "Last-Translator: Ineiev <address@hidden>\n"
 "Language-Team: Russian <address@hidden>\n"
@@ -16,6 +16,7 @@
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
+"X-Outdated-Since: 2018-01-24 12:26+0000\n"
 "X-Poedit-Language: Russian\n"
 
 # type: Content of: <title>
@@ -69,8 +70,13 @@
 msgstr "<a href=\"#whycare\">Почему название важно?</a>"
 
 #. type: Content of: <ul><li>
+# | <a href=\"#what\">What is the real relationship between GNU and
+# | Linux{+?+}</a>
+#, fuzzy
+#| msgid ""
+#| "<a href=\"#what\">What is the real relationship between GNU and Linux</a>"
 msgid ""
-"<a href=\"#what\">What is the real relationship between GNU and Linux</a>"
+"<a href=\"#what\">What is the real relationship between GNU and Linux?</a>"
 msgstr "<a href=\"#what\">Какова на самом деле связь 
между GNU и Linux?</a>"
 
 #. type: Content of: <ul><li>
@@ -396,9 +402,15 @@
 "называть ее GNU/Linux?</a>"
 
 #. type: Content of: <ul><li>
+# | <a href=\"#allgpled\">Should the [-GNU/[name]-] {+GNU/<i>name</i>+}
+# | convention be applied to all programs that are GPL'ed?</a>
+#, fuzzy
+#| msgid ""
+#| "<a href=\"#allgpled\">Should the GNU/[name] convention be applied to all "
+#| "programs that are GPL'ed?</a>"
 msgid ""
-"<a href=\"#allgpled\">Should the GNU/[name] convention be applied to all "
-"programs that are GPL'ed?</a>"
+"<a href=\"#allgpled\">Should the GNU/<i>name</i> convention be applied to "
+"all programs that are GPL'ed?</a>"
 msgstr ""
 "<a href=\"#allgpled\">Должно ли применять схему 
&ldquo;GNU/[название]&rdquo; "
 "для обозначения всех программ под 
лицензией GPL?</a>"
@@ -1008,10 +1020,19 @@
 
 # type: Content of: <dl><dt>
 #. type: Content of: <dl><dt>
-msgid ""
-"Since everyone knows GNU's role in developing the system, doesn't the &ldquo;"
-"GNU/&rdquo; in the name go without saying? <span class=\"anchor-reference-id"
-"\">(<a href=\"#everyoneknows\">#everyoneknows</a>)</span>"
+# | Since everyone knows [-GNU's-] {+the+} role {+of GNU+} in developing the
+# | system, doesn't the &ldquo;GNU/&rdquo; in the name go without saying?
+# | <span class=\"anchor-reference-id\">(<a
+# | href=\"#everyoneknows\">#everyoneknows</a>)</span>
+#, fuzzy
+#| msgid ""
+#| "Since everyone knows GNU's role in developing the system, doesn't the "
+#| "&ldquo;GNU/&rdquo; in the name go without saying? <span class=\"anchor-"
+#| "reference-id\">(<a href=\"#everyoneknows\">#everyoneknows</a>)</span>"
+msgid ""
+"Since everyone knows the role of GNU in developing the system, doesn't the "
+"&ldquo;GNU/&rdquo; in the name go without saying? <span class=\"anchor-"
+"reference-id\">(<a href=\"#everyoneknows\">#everyoneknows</a>)</span>"
 msgstr ""
 "Поскольку все знают о роли GNU в разработке 
этой системы, разве не ясно и "
 "без слов, что речь идет о &ldquo;GNU/&rdquo;? <span 
class=\"anchor-reference-"

Index: gnu/po/gnu-linux-faq.sq.po
===================================================================
RCS file: /web/www/www/gnu/po/gnu-linux-faq.sq.po,v
retrieving revision 1.96
retrieving revision 1.97
diff -u -b -r1.96 -r1.97
--- gnu/po/gnu-linux-faq.sq.po  1 Jan 2018 06:21:53 -0000       1.96
+++ gnu/po/gnu-linux-faq.sq.po  24 Jan 2018 12:33:18 -0000      1.97
@@ -6,7 +6,7 @@
 msgstr ""
 "Project-Id-Version: gnu-linux-faq.html\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2018-01-01 05:56+0000\n"
+"POT-Creation-Date: 2018-01-24 12:26+0000\n"
 "PO-Revision-Date: 2017-11-20 13:31+0200\n"
 "Last-Translator: Besnik Bleta <address@hidden>\n"
 "Language-Team: sq\n"
@@ -62,8 +62,11 @@
 msgstr "<a href=\"#whycare\">Pse emri është i rëndësishëm?</a>"
 
 #. type: Content of: <ul><li>
+#, fuzzy
+#| msgid ""
+#| "<a href=\"#what\">What is the real relationship between GNU and Linux</a>"
 msgid ""
-"<a href=\"#what\">What is the real relationship between GNU and Linux</a>"
+"<a href=\"#what\">What is the real relationship between GNU and Linux?</a>"
 msgstr ""
 "<a href=\"#what\">Cila është marrëdhënia e vërtetë mes GNU-së dhe 
Linux-it</"
 "a>"
@@ -391,9 +394,13 @@
 "përdorin emrin GNU/Linux?</a>"
 
 #. type: Content of: <ul><li>
+#, fuzzy
+#| msgid ""
+#| "<a href=\"#allgpled\">Should the GNU/[name] convention be applied to all "
+#| "programs that are GPL'ed?</a>"
 msgid ""
-"<a href=\"#allgpled\">Should the GNU/[name] convention be applied to all "
-"programs that are GPL'ed?</a>"
+"<a href=\"#allgpled\">Should the GNU/<i>name</i> convention be applied to "
+"all programs that are GPL'ed?</a>"
 msgstr ""
 "<a href=\"#allgpled\">Nuk do të duhej që emërtimi i llojit GNU/[emër] të 
"
 "zbatohej te krejt programet që janë nën GPL?</a>"
@@ -960,10 +967,15 @@
 "që sistemin e pollën këto vlera të lirisë."
 
 #. type: Content of: <dl><dt>
+#, fuzzy
+#| msgid ""
+#| "Since everyone knows GNU's role in developing the system, doesn't the "
+#| "&ldquo;GNU/&rdquo; in the name go without saying? <span class=\"anchor-"
+#| "reference-id\">(<a href=\"#everyoneknows\">#everyoneknows</a>)</span>"
 msgid ""
-"Since everyone knows GNU's role in developing the system, doesn't the &ldquo;"
-"GNU/&rdquo; in the name go without saying? <span class=\"anchor-reference-id"
-"\">(<a href=\"#everyoneknows\">#everyoneknows</a>)</span>"
+"Since everyone knows the role of GNU in developing the system, doesn't the "
+"&ldquo;GNU/&rdquo; in the name go without saying? <span class=\"anchor-"
+"reference-id\">(<a href=\"#everyoneknows\">#everyoneknows</a>)</span>"
 msgstr ""
 "Meqë kushdo e njeh rolin e GNU-së në zhvillimin e sistemit, ka nevojë që 
të "
 "thuhet patjetër &ldquo;GNU/&rdquo;-ja te emri? <span class=\"anchor-"

Index: gnu/po/gnu-linux-faq.sr.po
===================================================================
RCS file: /web/www/www/gnu/po/gnu-linux-faq.sr.po,v
retrieving revision 1.56
retrieving revision 1.57
diff -u -b -r1.56 -r1.57
--- gnu/po/gnu-linux-faq.sr.po  1 Jan 2018 06:21:53 -0000       1.56
+++ gnu/po/gnu-linux-faq.sr.po  24 Jan 2018 12:33:18 -0000      1.57
@@ -9,7 +9,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: gnu-linux-faq.html\n"
-"POT-Creation-Date: 2018-01-01 05:56+0000\n"
+"POT-Creation-Date: 2018-01-24 12:26+0000\n"
 "PO-Revision-Date: 2008-07-25 13:26+0200\n"
 "Last-Translator: Strahinya Radich <address@hidden>\n"
 "Language-Team: Serbian <address@hidden>\n"
@@ -67,7 +67,7 @@
 #, fuzzy
 #| msgid "<a href=\"#why\">Why do you call it GNU/Linux and not Linux?</a>"
 msgid ""
-"<a href=\"#what\">What is the real relationship between GNU and Linux</a>"
+"<a href=\"#what\">What is the real relationship between GNU and Linux?</a>"
 msgstr "<a href=\"#why\">Зашто га зовете ГНУ са 
Линуксом а не Линукс?</a>"
 
 #. type: Content of: <ul><li>
@@ -392,9 +392,13 @@
 "да тражите од људи да користе назив ГНУ са 
Линуксом?</a>"
 
 #. type: Content of: <ul><li>
+#, fuzzy
+#| msgid ""
+#| "<a href=\"#allgpled\">Should the GNU/[name] convention be applied to all "
+#| "programs that are GPL'ed?</a>"
 msgid ""
-"<a href=\"#allgpled\">Should the GNU/[name] convention be applied to all "
-"programs that are GPL'ed?</a>"
+"<a href=\"#allgpled\">Should the GNU/<i>name</i> convention be applied to "
+"all programs that are GPL'ed?</a>"
 msgstr ""
 "<a href=\"#allgpled\">Треба ли правило ГНУ са [назив] 
примењивати на све "
 "програме који су под ОЈЛ?</a>"
@@ -945,10 +949,15 @@
 "управо вредности слободе изнеле систем на 
светлост дана."
 
 #. type: Content of: <dl><dt>
-msgid ""
-"Since everyone knows GNU's role in developing the system, doesn't the &ldquo;"
-"GNU/&rdquo; in the name go without saying? <span class=\"anchor-reference-id"
-"\">(<a href=\"#everyoneknows\">#everyoneknows</a>)</span>"
+#, fuzzy
+#| msgid ""
+#| "Since everyone knows GNU's role in developing the system, doesn't the "
+#| "&ldquo;GNU/&rdquo; in the name go without saying? <span class=\"anchor-"
+#| "reference-id\">(<a href=\"#everyoneknows\">#everyoneknows</a>)</span>"
+msgid ""
+"Since everyone knows the role of GNU in developing the system, doesn't the "
+"&ldquo;GNU/&rdquo; in the name go without saying? <span class=\"anchor-"
+"reference-id\">(<a href=\"#everyoneknows\">#everyoneknows</a>)</span>"
 msgstr ""
 "Пошто је свакоме позната улога ГНУ-а у 
развоју система, зар се „ГНУ са“ у "
 "имену не подразумева? <span 
class=\"anchor-reference-id\">(<a href="

Index: gnu/po/gnu-linux-faq.tr.po
===================================================================
RCS file: /web/www/www/gnu/po/gnu-linux-faq.tr.po,v
retrieving revision 1.60
retrieving revision 1.61
diff -u -b -r1.60 -r1.61
--- gnu/po/gnu-linux-faq.tr.po  1 Jan 2018 06:21:53 -0000       1.60
+++ gnu/po/gnu-linux-faq.tr.po  24 Jan 2018 12:33:18 -0000      1.61
@@ -12,7 +12,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: gnu-linux-faq.html\n"
-"POT-Creation-Date: 2018-01-01 05:56+0000\n"
+"POT-Creation-Date: 2018-01-24 12:26+0000\n"
 "PO-Revision-Date: 2010-01-07 13:09+0100\n"
 "Last-Translator: Firat Ozgul <address@hidden>\n"
 "Language-Team: Turkish <address@hidden>\n"
@@ -73,9 +73,13 @@
 msgstr "<a href=\"#whycare\">Peki ad neden önemli? </a>"
 
 #. type: Content of: <ul><li>
+#, fuzzy
+#| msgid "<a href=\"#why\">Why do you call it GNU/Linux and not Linux?</a>"
 msgid ""
-"<a href=\"#what\">What is the real relationship between GNU and Linux</a>"
+"<a href=\"#what\">What is the real relationship between GNU and Linux?</a>"
 msgstr ""
+"<a href=\"#why\">Neden sistemi Linux olarak değil de GNU/Linux olarak "
+"adlandırıyorsunuz?</a>"
 
 #. type: Content of: <ul><li>
 #, fuzzy
@@ -420,9 +424,13 @@
 "bu kadar geciktiniz?</a>"
 
 #. type: Content of: <ul><li>
+#, fuzzy
+#| msgid ""
+#| "<a href=\"#allgpled\">Should the GNU/[name] convention be applied to all "
+#| "programs that are GPL'ed?</a>"
 msgid ""
-"<a href=\"#allgpled\">Should the GNU/[name] convention be applied to all "
-"programs that are GPL'ed?</a>"
+"<a href=\"#allgpled\">Should the GNU/<i>name</i> convention be applied to "
+"all programs that are GPL'ed?</a>"
 msgstr ""
 "<a href=\"#allgpled\">GNU/[ad] şablonunun bütün GPL'li programlara "
 "uygulanması gerekiyor mu?</a>"
@@ -988,10 +996,15 @@
 "özgürlük değerleri olduğundan başkalarını haberdar etmek için 
istiyoruz."
 
 #. type: Content of: <dl><dt>
-msgid ""
-"Since everyone knows GNU's role in developing the system, doesn't the &ldquo;"
-"GNU/&rdquo; in the name go without saying? <span class=\"anchor-reference-id"
-"\">(<a href=\"#everyoneknows\">#everyoneknows</a>)</span>"
+#, fuzzy
+#| msgid ""
+#| "Since everyone knows GNU's role in developing the system, doesn't the "
+#| "&ldquo;GNU/&rdquo; in the name go without saying? <span class=\"anchor-"
+#| "reference-id\">(<a href=\"#everyoneknows\">#everyoneknows</a>)</span>"
+msgid ""
+"Since everyone knows the role of GNU in developing the system, doesn't the "
+"&ldquo;GNU/&rdquo; in the name go without saying? <span class=\"anchor-"
+"reference-id\">(<a href=\"#everyoneknows\">#everyoneknows</a>)</span>"
 msgstr ""
 "Herkes GNU'nun sistem gelişimindeki rolünü bildiğine göre, isimdeki 
&ldquo;"
 "GNU/&rdquo; kısmı atlansa olmaz mı? <span 
class=\"anchor-reference-id\">(<a "

Index: gnu/po/gnu-linux-faq.uk.po
===================================================================
RCS file: /web/www/www/gnu/po/gnu-linux-faq.uk.po,v
retrieving revision 1.35
retrieving revision 1.36
diff -u -b -r1.35 -r1.36
--- gnu/po/gnu-linux-faq.uk.po  1 Jan 2018 06:21:53 -0000       1.35
+++ gnu/po/gnu-linux-faq.uk.po  24 Jan 2018 12:33:18 -0000      1.36
@@ -6,7 +6,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: gnu-linux-faq.html\n"
-"POT-Creation-Date: 2018-01-01 05:56+0000\n"
+"POT-Creation-Date: 2018-01-24 12:26+0000\n"
 "PO-Revision-Date: 2017-12-10 14:50+0200\n"
 "Last-Translator: Andriy Bandura <address@hidden>\n"
 "Language-Team: Ukrainian <>\n"
@@ -65,8 +65,11 @@
 msgstr "<a href=\"#whycare\">Чому назва важлива?</a>"
 
 #. type: Content of: <ul><li>
+#, fuzzy
+#| msgid ""
+#| "<a href=\"#what\">What is the real relationship between GNU and Linux</a>"
 msgid ""
-"<a href=\"#what\">What is the real relationship between GNU and Linux</a>"
+"<a href=\"#what\">What is the real relationship between GNU and Linux?</a>"
 msgstr "<a href=\"#what\">Який насправді зв'язок між GNU 
та Linux?</a>"
 
 #. type: Content of: <ul><li>
@@ -390,9 +393,13 @@
 "називати GNU/Linux?</a>"
 
 #. type: Content of: <ul><li>
+#, fuzzy
+#| msgid ""
+#| "<a href=\"#allgpled\">Should the GNU/[name] convention be applied to all "
+#| "programs that are GPL'ed?</a>"
 msgid ""
-"<a href=\"#allgpled\">Should the GNU/[name] convention be applied to all "
-"programs that are GPL'ed?</a>"
+"<a href=\"#allgpled\">Should the GNU/<i>name</i> convention be applied to "
+"all programs that are GPL'ed?</a>"
 msgstr ""
 "<a href=\"#allgpled\">Чи слід застосовувати схему 
&ldquo;GNU/[назва]&rdquo; "
 "для позначення всіх програм під ліцензією 
GPL?</a>"
@@ -961,10 +968,15 @@
 "проінформувати інших людей, що ці 
цінності свободи дали життя цій системі."
 
 #. type: Content of: <dl><dt>
-msgid ""
-"Since everyone knows GNU's role in developing the system, doesn't the &ldquo;"
-"GNU/&rdquo; in the name go without saying? <span class=\"anchor-reference-id"
-"\">(<a href=\"#everyoneknows\">#everyoneknows</a>)</span>"
+#, fuzzy
+#| msgid ""
+#| "Since everyone knows GNU's role in developing the system, doesn't the "
+#| "&ldquo;GNU/&rdquo; in the name go without saying? <span class=\"anchor-"
+#| "reference-id\">(<a href=\"#everyoneknows\">#everyoneknows</a>)</span>"
+msgid ""
+"Since everyone knows the role of GNU in developing the system, doesn't the "
+"&ldquo;GNU/&rdquo; in the name go without saying? <span class=\"anchor-"
+"reference-id\">(<a href=\"#everyoneknows\">#everyoneknows</a>)</span>"
 msgstr ""
 "Оскільки всі знають про роль GNU у розробці 
цієї системи, хіба не ясно і без "
 "слів, що мова йде про &ldquo;GNU/&rdquo;? <span 
class=\"anchor-reference-id"

Index: gnu/po/pronunciation.translist
===================================================================
RCS file: /web/www/www/gnu/po/pronunciation.translist,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -b -r1.7 -r1.8
--- gnu/po/pronunciation.translist      31 Jan 2016 19:28:19 -0000      1.7
+++ gnu/po/pronunciation.translist      24 Jan 2018 12:33:18 -0000      1.8
@@ -9,6 +9,7 @@
 <span dir="ltr"><a lang="it" hreflang="it" 
href="/gnu/pronunciation.it.html">italiano</a>&nbsp;[it]</span> &nbsp;
 <span dir="ltr"><a lang="ja" hreflang="ja" 
href="/gnu/pronunciation.ja.html">日本語</a>&nbsp;[ja]</span> &nbsp;
 <span dir="ltr"><a lang="ko" hreflang="ko" 
href="/gnu/pronunciation.ko.html">한국어</a>&nbsp;[ko]</span> &nbsp;
+<span dir="ltr"><a lang="pt-br" hreflang="pt-br" 
href="/gnu/pronunciation.pt-br.html">português&nbsp;do&nbsp;Brasil</a>&nbsp;[pt-br]</span>
 &nbsp;
 <span dir="ltr"><a lang="ru" hreflang="ru" 
href="/gnu/pronunciation.ru.html">русский</a>&nbsp;[ru]</span> &nbsp;
 <span dir="ltr"><a lang="uk" hreflang="uk" 
href="/gnu/pronunciation.uk.html">українська</a>&nbsp;[uk]</span> 
&nbsp;
 </p>
@@ -21,6 +22,7 @@
 <link rel="alternate" type="text/html" lang="it" hreflang="it" 
href="/gnu/pronunciation.it.html" title="italiano" />
 <link rel="alternate" type="text/html" lang="ja" hreflang="ja" 
href="/gnu/pronunciation.ja.html" title="日本語" />
 <link rel="alternate" type="text/html" lang="ko" hreflang="ko" 
href="/gnu/pronunciation.ko.html" title="한국어" />
+<link rel="alternate" type="text/html" lang="pt-br" hreflang="pt-br" 
href="/gnu/pronunciation.pt-br.html" title="português do Brasil" />
 <link rel="alternate" type="text/html" lang="ru" hreflang="ru" 
href="/gnu/pronunciation.ru.html" title="русский" />
 <link rel="alternate" type="text/html" lang="uk" hreflang="uk" 
href="/gnu/pronunciation.uk.html" title="українська" />
 <!-- end translist file -->

Index: licenses/gpl-howto.es.html
===================================================================
RCS file: /web/www/www/licenses/gpl-howto.es.html,v
retrieving revision 1.41
retrieving revision 1.42
diff -u -b -r1.41 -r1.42
--- licenses/gpl-howto.es.html  19 Sep 2017 11:59:09 -0000      1.41
+++ licenses/gpl-howto.es.html  24 Jan 2018 12:33:19 -0000      1.42
@@ -34,7 +34,9 @@
 <ul>
 <li>Consiga una declaración de renuncia de copyright de su empleador o
 institución académica.</li>
-<li>Incluya en cada archivo las notas de copyright apropiadas.</li>
+<li>Incluya en cada archivo las notas de copyright apropiadas. Asegúrese de <a
+href="/licenses/identify-licenses-clearly.html">indicar claramente qué
+versiones de la licencia pueden utilizar los usuarios</a>.</li>
 <li>Añada un archivo COPYING que contenga una copia de la GPL o AGPL de 
GNU.</li>
 <li>Añada también un archivo COPYING:LESSER que contenga una copia de la 
LGPL de
 GNU, en caso de que utilice este licencia.</li>
@@ -314,8 +316,8 @@
      
      There is more detail about copyright years in the GNU Maintainers
      Information document, www.gnu.org/prep/maintain. -->
-<p>Copyright &copy; 2001, 2007, 2008, 2009, 2013, 2014, 2017 Free Software
-Foundation, Inc.</p>
+<p>Copyright &copy; 2001, 2007, 2008, 2009, 2013, 2014, 2017, 2018 Free
+Software Foundation, Inc.</p>
 
 <p>Esta página está bajo licencia <a rel="license"
 href="http://creativecommons.org/licenses/by-nd/4.0/deed.es_ES";>Creative
@@ -330,7 +332,7 @@
 <p class="unprintable"><!-- timestamp start -->
 Última actualización:
 
-$Date: 2017/09/19 11:59:09 $
+$Date: 2018/01/24 12:33:19 $
 
 <!-- timestamp end -->
 </p>

Index: licenses/po/gpl-howto.es-en.html
===================================================================
RCS file: /web/www/www/licenses/po/gpl-howto.es-en.html,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -b -r1.27 -r1.28
--- licenses/po/gpl-howto.es-en.html    19 Sep 2017 11:59:10 -0000      1.27
+++ licenses/po/gpl-howto.es-en.html    24 Jan 2018 12:33:19 -0000      1.28
@@ -28,7 +28,9 @@
 
 <ul>
 <li>Get a copyright disclaimer from your employer or school.</li>
-<li>Give each file the proper copyright notices.</li>
+<li>Give each file the proper copyright notices. Make
+sure <a href="/licenses/identify-licenses-clearly.html">to clearly
+identify which versions of the license users can use</a>.</li>
 <li>Add a COPYING file with a copy of the GNU GPL or GNU AGPL.</li>
 <li>Also add a COPYING.LESSER file with a copy of the GNU LGPL, if you
 use that.</li>
@@ -293,7 +295,7 @@
      There is more detail about copyright years in the GNU Maintainers
      Information document, www.gnu.org/prep/maintain. -->
 
-<p>Copyright &copy; 2001, 2007, 2008, 2009, 2013, 2014, 2017
+<p>Copyright &copy; 2001, 2007, 2008, 2009, 2013, 2014, 2017, 2018
 Free Software Foundation, Inc.</p>
 
 <p>This page is licensed under a <a rel="license"
@@ -304,7 +306,7 @@
 
 <p class="unprintable">Updated:
 <!-- timestamp start -->
-$Date: 2017/09/19 11:59:10 $
+$Date: 2018/01/24 12:33:19 $
 <!-- timestamp end -->
 </p>
 </div>

Index: licenses/po/quick-guide-gplv3.pt-br.po
===================================================================
RCS file: /web/www/www/licenses/po/quick-guide-gplv3.pt-br.po,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- licenses/po/quick-guide-gplv3.pt-br.po      24 Jan 2018 08:43:40 -0000      
1.1
+++ licenses/po/quick-guide-gplv3.pt-br.po      24 Jan 2018 12:33:19 -0000      
1.2
@@ -718,6 +718,7 @@
 msgid "*GNUN-SLOT: TRANSLATOR'S NOTES*"
 msgstr " "
 
+# type: Content of: <div><p>
 #. type: Content of: <div><div><p>
 msgid ""
 "Please send general FSF &amp; GNU inquiries to <a 
href=\"mailto:address@hidden";
@@ -770,18 +771,19 @@
 "creativecommons.org/licenses/by-nd/3.0/us/\">Creative Commons Attribution-"
 "NoDerivs 3.0 United States License</a>."
 msgstr ""
-"Esta página está sob <a rel=\"license\" href=\"https://creativecommons.org/";
-"licenses/by-nd/3.0/us/deed.pt_BR\">licença da Creative Commons Atribuição-"
-"SemDerivações 3.0 Estados Unidos</a>."
+"Esta página está licenciada sob uma licença <a rel=\"license\" 
href=\"http://";
+"creativecommons.org/licenses/by-nd/3.0/us/deed.pt_BR\">Creative Commons "
+"Atribuição-SemDerivações 3.0 Estados Unidos</a>."
 
 #. TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.
 #. type: Content of: <div><div>
 msgid "*GNUN-SLOT: TRANSLATOR'S CREDITS*"
 msgstr ""
-"Traduzido por: Rafael Fontenelle <a href=\"mailto:address@hidden"";
-">&lt;address@hidden&gt;</a>, 2018."
+"Traduzido por: Rafael Fontenelle <a href=\"mailto:address@hidden";>&lt;"
+"address@hidden&gt;</a>, 2018."
 
+# type: Content of: <div><p>
 #.  timestamp start 
 #. type: Content of: <div><p>
 msgid "Updated:"
-msgstr "Última atualização:"
+msgstr "Última atualização: "

Index: licenses/po/quick-guide-gplv3.translist
===================================================================
RCS file: /web/www/www/licenses/po/quick-guide-gplv3.translist,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -b -r1.14 -r1.15
--- licenses/po/quick-guide-gplv3.translist     23 Oct 2016 09:58:00 -0000      
1.14
+++ licenses/po/quick-guide-gplv3.translist     24 Jan 2018 12:33:19 -0000      
1.15
@@ -8,6 +8,7 @@
 <span dir="ltr"><a lang="fr" hreflang="fr" 
href="/licenses/quick-guide-gplv3.fr.html">français</a>&nbsp;[fr]</span> &nbsp;
 <span dir="ltr"><a lang="it" hreflang="it" 
href="/licenses/quick-guide-gplv3.it.html">italiano</a>&nbsp;[it]</span> &nbsp;
 <span dir="ltr"><a lang="ja" hreflang="ja" 
href="/licenses/quick-guide-gplv3.ja.html">日本語</a>&nbsp;[ja]</span> &nbsp;
+<span dir="ltr"><a lang="pt-br" hreflang="pt-br" 
href="/licenses/quick-guide-gplv3.pt-br.html">português&nbsp;do&nbsp;Brasil</a>&nbsp;[pt-br]</span>
 &nbsp;
 <span dir="ltr"><a lang="ru" hreflang="ru" 
href="/licenses/quick-guide-gplv3.ru.html">русский</a>&nbsp;[ru]</span> 
&nbsp;
 </p>
 </div>' -->
@@ -18,5 +19,6 @@
 <link rel="alternate" type="text/html" lang="fr" hreflang="fr" 
href="/licenses/quick-guide-gplv3.fr.html" title="français" />
 <link rel="alternate" type="text/html" lang="it" hreflang="it" 
href="/licenses/quick-guide-gplv3.it.html" title="italiano" />
 <link rel="alternate" type="text/html" lang="ja" hreflang="ja" 
href="/licenses/quick-guide-gplv3.ja.html" title="日本語" />
+<link rel="alternate" type="text/html" lang="pt-br" hreflang="pt-br" 
href="/licenses/quick-guide-gplv3.pt-br.html" title="português do Brasil" />
 <link rel="alternate" type="text/html" lang="ru" hreflang="ru" 
href="/licenses/quick-guide-gplv3.ru.html" title="русский" />
 <!-- end translist file -->

Index: licenses/po/translations.pt-br.po
===================================================================
RCS file: /web/www/www/licenses/po/translations.pt-br.po,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- licenses/po/translations.pt-br.po   24 Jan 2018 08:43:40 -0000      1.1
+++ licenses/po/translations.pt-br.po   24 Jan 2018 12:33:20 -0000      1.2
@@ -598,6 +598,7 @@
 msgid "*GNUN-SLOT: TRANSLATOR'S NOTES*"
 msgstr " "
 
+# type: Content of: <div><p>
 #. type: Content of: <div><div><p>
 msgid ""
 "Please send general FSF &amp; GNU inquiries to <a 
href=\"mailto:address@hidden";
@@ -613,8 +614,6 @@
 "address@hidden&gt;</a>."
 
 #
-#
-#
 #.  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
@@ -665,6 +664,7 @@
 "Traduzido por: Rafael Fontenelle\n"
 "<a href=\"mailto:address@hidden";>&lt;address@hidden&gt;</a>, 2018"
 
+# type: Content of: <div><p>
 #.  timestamp start 
 #. type: Content of: <div><p>
 msgid "Updated:"

Index: licenses/po/translations.translist
===================================================================
RCS file: /web/www/www/licenses/po/translations.translist,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- licenses/po/translations.translist  22 May 2015 06:07:09 -0000      1.11
+++ licenses/po/translations.translist  24 Jan 2018 12:33:20 -0000      1.12
@@ -10,6 +10,7 @@
 <span dir="ltr"><a lang="fr" hreflang="fr" 
href="/licenses/translations.fr.html">français</a>&nbsp;[fr]</span> &nbsp;
 <span dir="ltr"><a lang="ja" hreflang="ja" 
href="/licenses/translations.ja.html">日本語</a>&nbsp;[ja]</span> &nbsp;
 <span dir="ltr"><a lang="pl" hreflang="pl" 
href="/licenses/translations.pl.html">polski</a>&nbsp;[pl]</span> &nbsp;
+<span dir="ltr"><a lang="pt-br" hreflang="pt-br" 
href="/licenses/translations.pt-br.html">português&nbsp;do&nbsp;Brasil</a>&nbsp;[pt-br]</span>
 &nbsp;
 <span dir="ltr"><a lang="ru" hreflang="ru" 
href="/licenses/translations.ru.html">русский</a>&nbsp;[ru]</span> &nbsp;
 </p>
 </div>' -->
@@ -22,5 +23,6 @@
 <link rel="alternate" type="text/html" lang="fr" hreflang="fr" 
href="/licenses/translations.fr.html" title="français" />
 <link rel="alternate" type="text/html" lang="ja" hreflang="ja" 
href="/licenses/translations.ja.html" title="日本語" />
 <link rel="alternate" type="text/html" lang="pl" hreflang="pl" 
href="/licenses/translations.pl.html" title="polski" />
+<link rel="alternate" type="text/html" lang="pt-br" hreflang="pt-br" 
href="/licenses/translations.pt-br.html" title="português do Brasil" />
 <link rel="alternate" type="text/html" lang="ru" hreflang="ru" 
href="/licenses/translations.ru.html" title="русский" />
 <!-- end translist file -->

Index: philosophy/copyright-and-globalization.pt-br.html
===================================================================
RCS file: /web/www/www/philosophy/copyright-and-globalization.pt-br.html,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -b -r1.10 -r1.11
--- philosophy/copyright-and-globalization.pt-br.html   1 Jun 2017 09:01:32 
-0000       1.10
+++ philosophy/copyright-and-globalization.pt-br.html   24 Jan 2018 12:33:20 
-0000      1.11
@@ -1240,7 +1240,7 @@
 
 <!-- Regarding copyright, in general, standalone pages (as opposed to
      files generated as part of manuals) on the GNU web server should
-     be under CC BY-ND 3.0 US.  Please do NOT change or remove this
+     be under CC BY-ND 4.0.  Please do NOT change or remove this
      without talking with the webmasters or licensing team first.
      Please make sure the copyright date is consistent with the
      document.  For web pages, it is ok to list just the latest year the
@@ -1254,11 +1254,12 @@
      
      There is more detail about copyright years in the GNU Maintainers
      Information document, www.gnu.org/prep/maintain. -->
-<p>Copyright &copy; 2001, 2007, 2008, 2012, 2014 Free Software Foundation, 
Inc.</p>
+<p>Copyright &copy; 2001, 2007, 2008, 2012, 2014, 2018 Free Software
+Foundation, Inc.</p>
 
 <p>Esta página está licenciada sob uma licença <a rel="license"
-href="http://creativecommons.org/licenses/by-nd/3.0/us/deed.pt_BR";>Creative
-Commons Atribuição-SemDerivações 3.0 Estados Unidos</a>.</p>
+href="http://creativecommons.org/licenses/by-nd/4.0/deed.pt_BR";>Creative
+Commons Atribuição-SemDerivações 4.0 Internacional</a>.</p>
 
 <!--#include virtual="/server/bottom-notes.pt-br.html" -->
 <div class="translators-credits">
@@ -1270,7 +1271,7 @@
 <p class="unprintable"><!-- timestamp start -->
 Última atualização: 
 
-$Date: 2017/06/01 09:01:32 $
+$Date: 2018/01/24 12:33:20 $
 
 <!-- timestamp end -->
 </p>

Index: philosophy/dat.zh-cn.html
===================================================================
RCS file: /web/www/www/philosophy/dat.zh-cn.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -b -r1.3 -r1.4
--- philosophy/dat.zh-cn.html   30 Dec 2011 05:18:26 -0000      1.3
+++ philosophy/dat.zh-cn.html   24 Jan 2018 12:33:20 -0000      1.4
@@ -1,604 +1,215 @@
-<!DOCTYPE html PUBLIC "-//IETF//DTD HTML 2.0//EN">
-<HTML>
-<HEAD>
-<TITLE>DAT Õ÷Ë°µÄÕýÈ··½·¨ £­ GNU ¹¤³Ì £­ ×ÔÓÉÈí¼þ»ù½ð»á£¨FSF£©</TITLE>
-<meta http-equiv="Content-Type" content="text/html; charset=gb2312">
-<LINK REV="made" HREF="mailto:address@hidden";>
-</HEAD>
-<BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#1F00FF" ALINK="#FF0000" 
VLINK="#9900DD">
-<H3>DAT Õ÷Ë°µÄÕýÈ··½·¨</H3>
-<P>
-<A HREF="http://www.stallman.org/";><STRONG>Richard Stallman</STRONG></A>
-<P>
-<EM>
-[±¾ÎÄÒ»¾Å¾Å¶þÄê·¢±íÓÚ Wired ÔÓÖ¾£»
-ÎÄ×ÖûÓÐÐ޸ģ¬
-µ«ÊÇÌí¼ÓÁË·½À¨»¡ÖеÄ×¢ÊÍ
-£¨¿ÉÒÔÏÔʾǿµ÷ÎÄ×ÖµÄä¯ÀÀÆ÷½«Ç¿µ÷ÕâЩעÊÍ£©¡£]
-</EM>
-<P>
-
-<A HREF="/graphics/philosophicalgnu.html"><IMG 
SRC="/graphics/philosophical-gnu-sm.jpg"
-   ALT=" [ÕÜѧ GNU µÄͼÏñ] "
-   WIDTH="160" HEIGHT="200"></A>
-
-[
-<!-- Please keep this list alphabetical!!!  -->
-  <A HREF="/philosophy/dat.zh-cn.html">¼òÌåÖÐÎÄ</A>
-| <A HREF="/philosophy/dat.zh-tw.html">·±ÌåÖÐÎÄ</A>
-| <A HREF="/philosophy/dat.cs.html">½Ý¿ËÓï</A>
-| <A HREF="/philosophy/dat.en.html">Ó¢Óï</A>
-| <A HREF="/philosophy/dat.fr.html">·¨Óï</A>
-]
-
-<P>
-
-<HR>
-
-<P>
-
-<H4><EM>[ Ŀ¼ ]</EM></H4>
-
-<UL>
-  <LI><A HREF="#sec1"
-         NAME="toc1"><EM>°æȨÖƶȵÄÄ¿µÄºÎÔÚ£¿</EM></A>
-  <LI><A HREF="#sec2"
-         NAME="toc2"><EM>»Ø±¨Ï½µ</EM></A>
-  <LI><A HREF="#sec3"
-         NAME="toc3"><EM>ƽºâ</EM></A>
-  <LI><A HREF="#sec4"
-         NAME="toc4"><EM>¡¸¼¤Àø¡¹ÊÇ´íÎóµÄ¸ÅÄî</EM></A>
-  <LI><A HREF="#sec5"
-         NAME="toc5"><EM>Ë­Ó¦¸ÃµÃµ½×ʽð</EM></A>
-  <LI><A HREF="#sec6"
-         NAME="toc6"><EM>×ʽð·ÖÅä</EM></A>
-  <LI><A HREF="#sec7"
-         NAME="toc7"><EM>¹ÄÀø¼ÒÍ¥¸´ÖÆ</EM></A>
-  <LI><A HREF="#sec8"
-         NAME="toc8"><EM>ºâÁ¿Ã¿¸öÒôÀÖµÄʹÓÃ</EM></A>
-  <LI><A HREF="#sec9"
-         NAME="toc9"><EM>½áÂÛ</EM></A>
-  <LI><A HREF="#sec10"
-         NAME="toc10"><EM>Äã¿ÉÒÔ×öЩʲô</EM></A>
-  <LI><A HREF="/philosophy/philosophy.html">ÆäËû¶ÁÎï</A>
-</UL>
-
-<P>
-
-<HR>
-
-<P>
-
-³ªÆ¬¹«Ë¾¾ÞÍ·ÃDz¢²»Ï²»¶Êý×ÖÒôƵ´Å´ø¼Òô»ú£¨DAT£©£¬
-¾¡¹ÜËüÃÇ¿ÉÒÔÖÆ×÷ÍêÃÀµÄÒôÀÖ¼Òô´ø¸´ÖÆÆ·¡£
-ËûÃǵ£ÐĹ˿ÍÃǽ«×Ô¼º¸´ÖÆÒôÀÖ£¬
-´Ó¶øÍ£Ö¹¹ºÂòÊÂÏȼÖƵÄÒôÀÖ¡£
-
-<P>
-
-ͨ¹ýËßËÏÍþвµÄÊֶΣ¬
-ËûÃÇÒѾ­Óë DAT µÄÉú²ú³§ÉÌ´ï³ÉÁËЭÒ飬
-Éú²ú³§ÉÌΪËûÃÇÏúÊÛ¸ø¹Ë¿ÍµÄÿ¸ö DAT µ¥ÔªºÍÿÅÌ DAT ´Å´øÖ§¸¶·ÑÓá£
-Õâ±Ê·ÑÓý«·ÖÅä¸øÒôÀÖ²úÒµÖв»Í¬µÄ²ÎÓëÕߣº
-ÒôÀÖ¼Ò¡¢×÷Çú¼Ò¡¢ÒôÀÖ·¢ÐÐÉ̺ͳªÆ¬¹«Ë¾¡£
-³ý´ËÒÔÍ⣬
-DATÉú²úÉÌͬÒâ¼õÈõ DAT µ¥ÔªÒÔ±£Ö¤ÎÞ·¨Öظ´¸´ÖÆÊÂÏȼÖƵĴŴø¡£
-
-<P>
-
-ÏÖÔÚ³ªÆ¬¹«Ë¾ÒªÇó¹ú»á°ä²¼·¨Âɽ«¸Ã·ÑÓù涨Ϊ˰£¬
-²¢ÇÒ½ûÖ¹Éú²ú¹¦ÄÜÉÏûÓÐÇ¿ÖÆÏÞÖÆµÄ DAT ¼Òô»ú¡£
-
-<P>
-
-Õ÷ÊÕ¸ÃË°µÄÄ¿µÄÉù³ÆÊÇ¡¸²¹³¥¡¹
-ÒôÀÖ¼ÒÒòʹÓà DAT µÄ¸öÈ˵ĸ´ÖÆÐÐΪ¶ø¹¹³ÉµÄËðʧ¡£
-È»¶ø£¬
-Õâ±Ê×ʽðµÄ°Ù·ÖÖ®ÎåÊ®Æ߹鳪Ƭ¹«Ë¾ºÍÒôÀÖ·¢ÐÐÉÌËùÓÐ
-£­£­Ö»Ê£Ï²»µ½Ò»°ëµÄÊÕÈë¸ø²ÎÓë´´×÷¹ý³ÌµÄÈËÃÇ¡£
-Ê£ÏÂ×ʽðµÄ´ó²¿·ÖÓÖ½«½øÈëÒôÀÖ³¬¼¶¾ÞÐǵÄÑü°ü£¬
-Òò´ËºÜÉÙΪ¹ÄÀøÒôÀÖ´´×÷×÷³ö¹±Ïס£
-Óë´Ëͬʱ£¬
-DAT Óû§½«²»ÄÜÍêÈ«ÀûÓà DAT ¼¼ÊõµÄÍþÁ¦¡£
-
-<P>
-
-ÕâÀïÌá³öÒ»¸ö²»Í¬µÄ DAT ºÍ DAT ´Å´øÕ÷˰ϵͳµÄÌá°¸
-£­£­ÎªÖ§³ÖÒôÀÖ¶ø²»ÊÇΪÁËÓ­ºÏÌØȨ½×¼¶Éè¼ÆµÄÌá°¸¡£
-
-<P>
-
-<UL>
-<LI>ͨ¹ýÏò DAT É豸ºÍ DAT ´Å´øÕ÷Ë°À´³ï¼¯×ʽð£¬
-ÕýÈ統ǰÌá°¸ËùÌáµ½µÄ¡£
-<P>
-
-<LI>ʹÓõ÷²éϵͳÀ´ºâÁ¿Ã¿Ò»¸öÒôÀÖ×÷Æ·µÄ¸´Öƹã¶È¡£
-<P>
-
-<LI>½«×ʽðÍêÈ«·ÖÅä¸øÒôÀÖ´´×÷Õß¡£
-<P>
-
-<LI>µ÷Õûÿһ¸ö¹±Ï×ÕߵķÖÅä´Ó¶øËæן´ÖÆÊýµÄÔö´ó£¬
-ÿ·Ý¿½±´ÊÕÒæµÄÔö³¤ËٶȱäÂý¡£
-ÕâÑù¾Í¿ÉÒÔ¸ü¼ÓºÏÀíµÄ·ÖÅäÊÕÈë´Ó¶øÖ§³ÖºÜ´óÊýÁ¿µÄÒôÀÖ¼Ò¡£
-<P>
-
-<LI>²»ÏÞÖÆ DAT µÄ¹¦ÄÜ¡£
-</UL>
-<P>
-
-<H4><A HREF="#toc1"
-       NAME="sec1">°æȨÖƶȵÄÄ¿µÄºÎÔÚ£¿</A></H4>
-
-<P>
-
-³ªÆ¬¹¤ÒµÈÏΪËüÃǵÄ×÷·¨ÊÇÔÚ¡¸²¹³¥¡¹ÒôÀÖ¼Ò£¬
-²¢¼ÙÉèÿһ·Ý¿½±´¶¼Ó¦¸Ã¶ÔËûÃǸ¶·Ñ¡£
-ºÜ¶àÃÀ¹úÈËÏàÐÅ°æȨ·¨·´Ó³ÁË×÷Õß»òÒôÀÖ¼ÒÃǵÄ×ÔȻȨÀû
-£­£­Óɹ«¹²Õþ²ßµÄÌØÊ⿼ÂǸ³ÓèµÄȨÀû¡£
-È»¶ø£¬
-ÈκθÃÁìÓòµÄÂÉʦ¶¼ÖªµÀÕâÊÇÒ»ÖÖÎó½â£¬
-Ò»ÖÖΪÃÀ¹ú·¨ÖÆÌåϵËù·´¶ÔµÄ¹Ûµã¡£
-
-<P>
-
-ÃÀ¹úÏÜ·¨¸ø³öµÄ°æȨµÄÄ¿µÄÊÇΪÁË¡¸´Ù½ø¿ÆѧºÍÓÐÒæÒÕÊõµÄ·¢Õ¹¡¹¡£
-ÒôÀֵķ¢Õ¹Òâζ×ÅеĺͶàÖÖµÄÒôÀÖ¹©¹«ÖÚÐÀÉÍ£º
-°æȨӦ¸Ã´Ù½ø¹«¹²ÀûÒ棬
-¶ø²»ÊǸöÈËÀûÒæ¡£
-
-<P>
-
-È»¶øÍâÐÐÈ˺ÍÕþ¿ÍÃǾ­³£ÈÏΪ°æȨÊÇÒ»ÖÖ×ÔȻȨÀû£¬
-ÕâÍùÍùµ¼Ö°æȨÕþ²ßµÄ´íÎó¾ö¶¨¡£
-ÉõÖÁά»¤°æȨÌåϵϸ½ÚµÄ·¨ÔºÒ²¾­³£ÈôËÖÖÏë·¨°µÖÐÂûÑÓ£¬
-¾¡¹ÜËüÓ¦¸Ã±»Åųýµô¡£
-ÕâÊÇÒ»¸ö¸ÅÄî´íÎó£¬
-ÒòΪËü´íÎóµØ½«´ïµ½Ä¿µÄ£¨·¢Õ¹£©µÄÊֶΣ¨°æȨ£©×÷ΪËü±¾ÉíµÄÄ¿µÄ¡£
-
-<P>
-
-´Ù½øÒÕÊõµÄ·¢Õ¹²¢²»ÊÇÒªÖ¤Ã÷
-¡¸×÷ÕßÓµÓÐÌض¨°æȨµÄÏë·¨»ò°æȨµÄ´æÔÚÊǺÏÀíµÄ¡¹¡£
-°æȨֻÓÐÔÚÆä´Ù½ø×÷Óó¬¹ýÁË
-¡¸¶ÔÆä¶Ô³ý°æȨ³ÖÓÐÕßÖ®ÍâµÄÈ˵ĸºÃæÓ°Ï졹ʱ£¬
-²ÅÊÇÕýÈ·ºÏÀíµÄ¡£
-
-<P>
-
-ÈçºÎÅжÏÕâÖÖ´ú¼Û£¯ÊÕÒæ±È£¿
-Ëü²¿·ÖÈ¡¾öÓÚÊÂʵ£¨Ìض¨·¨ÂÉÊÇÈçºÎÓ°ÏìÒôÀֻºÍÒôÀÖÓû§µÄ£©£¬
-²¿·ÖÈ¡¾öÓÚÎÒÃǹØÓÚÕâЩ½á¹ûµÄ¼ÛÖµÅжϡ£
-
-<P>
-
-ÈÃÎÒÃǼÙÉèÖ§¸¶ DAT Ë°´Ù½øÁËÒôÀֻµÄÃ÷ÏÔÔö¼Óʱ֧¸¶ DAT Ë°ÊǺÏÊʵģ¬
-²¢ÇÒÑо¿Ò»ÏÂÈçºÎ·ÖÅä¸ÃË°ÒÔÈ¡µÃ×î´óÀûÒæ¡£
-µ«ÊÇÊ×ÏÈ£¬
-ÈÃÎÒÃǻعËÒ»ÏÂÓë¸ÃÒªÇóÏà¹ØµÄ»ù±¾¹æÔòºÍÊÂʵ¡£
-
-<P>
-
-<H4><A HREF="#toc2"
-       NAME="sec2">»Ø±¨Ï½µ</A></H4>
-
-<P>
-
-»Ø±¨Ï½µÀíÂÛÊǾ­¼ÃѧµÄÒ»¸öÆձ鶨ÂÉ¡£
-ËüÈÏΪ¡¸Ã¿´ÎÕë¶Ô¸ø¶¨Ä¿±ê¶øÔö¼ÓµÄŬÁ¦¡¹
-»ò¡¸Í¶×ÊËù²úÉúµÄ»Ø±¨Ôö¼Ó¡¹»áÔ½À´Ô½ÉÙ¡£
-Õâ¸öÀíÂÛ´æÔÚÀýÍ⣬
-µ«ËüÃǶ¼ÊǾֲ¿ÐԵģ»
-Èç¹ûÄã¼ÌÐøÔö¼ÓͶÈ룬
-×îÖÕÄã»áÍÑÀëÀýÍâ¡£
-
-<P>
-
-¾ÙÀý˵Ã÷£¬
-Äã¿ÉÒÔ²ÉÈ¡¸Ä½øµÀ·µÄ·½Ê½À´Ê¹µÃ½»Í¨±äµÃ¸ü¼Ó˳³©¡£
-³ÇÊÐÖÐÔÚ¶þʮӢÀïÓµ¼·µÄµÀ·Ôö¼ÓÒ»¸ö³µµÀ£¬
-¿ÉÄÜ¿ÉÒÔʹƽ¾ùʱËÙÌá¸ßÿСʱʮÎåÓ¢Àï¡£
-ÔÙÌí¼ÓÒ»Ìõ³µµÀ½«²»»áÓÐͬÑùµÄЧ¹û£»
-Õâ´Îƽ¾ùʱËÙ¿ÉÄÜÖ»ÄÜÌá¸ßÿСʱÎåÓ¢Àï¡£
-Èç¹û½»Í¨×èÈûÒѾ­²»ÔÙ´æÔڵĻ°£¬
-ÔÙÌí¼ÓÒ»¸ö³µµÀƽ¾ùʱËÙ¿ÉÄܲ»»áÓÐÈκÎÃ÷ÏԵı仯¡£
-È»¶øÿһÌõÔö¼ÓµÄ³µµÀ¶¼»á´øÀ´¸ü´óµÄ»ìÂÒ£¬
-ÒòΪ±ØÐëÀ­µ¹Ô½À´Ô½¶àµÄ½¨ÖþÎïÒÔÌÚ³ö¿Õ¼ä¡£
-
-<P>
-
-Ó¦ÓÃÓÚÒôÀֻ£¬
-»Ø±¨Ï½µ¸æËßÎÒÃÇ£¬
-ÿ´ÎÒôÀÖ¼ÒÃǵÄÊÕÈëÔö¼Ó¶¼¶ÔÒôÀֵĴ´ÔìÐÔ´æÔÚ¸üСµÄÓ°Ïì¡£
-
-<P>
-
-»Ø±¨Ï½µÀíÂÛÊǾܾøÈκÎʹÓö¼¡¸Ó¦¸Ã¡¹ÊÜ°æȨ±£»¤Õâ¸öÖ÷ÒâµÄµÚÒ»¸öÔ­Òò¡£
-ÊÔͼ¹ÄÀøÓµÓÐÕß¿ØÖÆÒôÀÖʹÓõķ½·½ÃæÃ棬
-»òÿһ¸ö¿ÉÄܵÄÊг¡¶¼¸øÓèËûÃǽðÇ®ÉϵĽ±Àø½«ÎÞ·¨»ñµÃÈκλر¨¡£
-À©Õ¹°æȨֻÄÜ¡¸´Ù½ø·¢Õ¹¡¹µ½Ìض¨µÄ³Ì¶È¡£
-¸ü¶àµÄÀ©Õ¹Ö»²»¹ýÊÇʹµÃ¹«ÖÚÃÇΪËûÃǵÄʹÓÃÏò×÷ÕßÖ§¸¶µÄ·ÑÓÃÔö¼Ó¡£
-ÔÚÌض¨³Ì¶ÈÖ®ÉϵÄÀ©Õ¹ÏÔÈ»ÊDz»ÊÜ»¶Ó­µÄ¡£
-
-<P>
-
-<H4><A HREF="#toc3"
-       NAME="sec3">ƽºâ</A></H4>
-
-<P>
-
-ÄÇЩ¶ÔÀ©Õ¹°æȨ¾ßÓмȶ¨ÐËȤµÄÈËÃÇÌôÆðÁËÂÛÕ½£¬
-ËûÃÇÉù³Æ°æȨӦ¸ÃÄÜÀ©Õ¹µ½Ê²Ã´µØ²½¾ÍÀ©Õ¹µ½Ê²Ã´µØ²½¡£
-µ«Êǻر¨Ï½µÀíÂÛʹµÃÕâÖÖÉùÃ÷ÏÔµÃÄÑÒÔÖÃÐÅ¡£
-ËùÒÔËûÃÇÓÖÔٴλص½ÁËÓ¦¸ÃÀ©Õ¹°æȨÒÔ×î´ó»¯·¢Õ¹ËٶȵĻùµã¡£
-¿ÉÊÇÕâÒ²ÊÇ´íÎóµÄ£¬
-ÒòΪËüºöÂÔÁËÆäËüÒòËصĴæÔÚ¡£
-°æȨÕýÈçÆäËüÈκÎÕþ¸®ÏîÄ¿Ò»Ñù£¬
-Ïò¹«ÖÚÇ¿¼Ó·ÑÓú͸ºµ£¡£
-ËüµÄÊÕÒæ¿ÉÄܲ»ÈçËüËù¸¶³öµÄ´ú¼Û¡£
-
-<P>
-
-Õþ¸®Íê³ÉºÜ¶àÖØÒªµÄÖ°ÄÜ£¬
-µ«ÊǼ¸ºõûÓÐÄÄÒ»ÏîÖ°ÄÜ¿ÉÒÔ˵Ӧ¸Ã±»À©Õ¹ÒÔ×î´ó»¯½á¹ûµÄ¡£
-ÀýÈ磬
-Õþ¸®ÐÞ½¨µÀ·£¬
-²¢ÇÒµÀ·ÊǷdz£ÓÐÓõġ£
-µ«ÊǼ¸ºõûÓÐÁìµ¼ÈË»áÔ¸ÒâÐÞ½¨ËûÃÇËùÄÜÐÞ½¨µÄÿһÌõµÀ·¡£
-µÀ·½¨ÉèºÄ×ʾ޴ó£¬
-¹«Ãñ»¹ÓÐÆäËüÐèÒªÓÃÇ®µÄµØ·½¡£
-Ì«¶àµÄ¼¯ÖÐÓÚµÀ·½¨Éè¾ÍÒâζ×ÅÆäËüÉç»áºÍ¸öÈ˵ÄÐèÒª½«ÎÞ·¨µÃµ½Âú×ã¡£
-
-<P>
-
-¶ÔÓÚ¸öÈ˾ö¶¨Ò²´æÔÚͬÑùµÄ¿¼ÂÇ¡£
-»¨¸ü¶àµÄÇ®£¬
-Äã¿ÉÒÔ¹ºÂòµ½¸ü´óºÍ¸üºÃµÄס·¿¡£
-´ó¶àÊýÈ˶¼Ï²»¶½Ï¹óµÄס·¿£¬
-ÿ¸öÈ˶¼Ò»Ñù¡£
-µ«ÊǸø¶¨ÓÐÏÞµÄ×ÊÔ´£¬
-ijÖ̶ֳÈÉÏÔÚס·¿»¨·Ñ½Ï¶à³ÉΪһÖÖ²»ºÃµÄ·ÖÅä¡£
-
-<P>
-
-°æȨ²¢²»Ö±½Ó»¨·Ñ¹«ÖÚµÄ×ʽð£¬
-µ«ÊÇËüµÄÈ·Ïòÿһ¸ö¹«Ãñ¶¼Ç¿¼ÓÁËÒ»ÖÖ´ú¼Û£­£­×ÔÓɵÄɥʧ¡£
-°æȨµÄ·¶Î§Ô½¹ã£¬
-ÎÒÃÇËù¸¶³öµÄ×ÔÓɾÍÔ½¶à¡£
-ÎÒÃÇÒ²Ðí¸üÔ¸ÒâÏíÊÜÎÒÃǵÄ×ÔÓɶø²»ÊÇÓÃËüÃÇÀ´×÷½»Òס£
-ÎÒÃDZØÐëͨ¹ý±È½ÏµÃʧÀ´¾ö¶¨ÈκΰæȨÖƶÈÉϵľö¶¨¡£
-
-<P>
-
-<H4><A HREF="#toc4"
-       NAME="sec4">¡¸¼¤Àø¡¹ÊÇ´íÎóµÄ¸ÅÄî</A></H4>
-
-<P>
-
-¶ÔÒôÀÖ´´×÷Ìṩ½ðÇ®¹ÄÀøµÄÏë·¨ÊÇ»ùÓÚ´íÎóÀí½âµÄ¡£
-ÒôÀÖ¼ÒÃÇÖ÷ÒªÆÚÍûÁíÍâµÄ±¨³ê£»
-ËûÃDZØÐëµÃµ½ÁíÍâµÄ±¨³ê¡£
-ºÜÉÙÓÐÒôÀÖ¼ÒÓÉÓÚËûÃǵÄÒôÀÖ¶ø¸»ÓУ»
-Ò»¸öÖ÷ҪĿ±êÊDzƸ»µÄÌì²Å»áͨ¹ý±ðµÄ·½Ê½À´×·ÇóËü¡£
-
-<P>
-
-ÊÂʵÉÏ£¬
-ÐÄÀíѧÑо¿±íÃ÷¿ÊÍûµÃµ½ÍâÀ´½±Àø£¨ÀýÈçÀûÈó£©
-ͨ³£»áËðº¦ÒôÀÖ´´×÷Ò»ÀàµÄ´´ÔìÐԻ¡£
-Äܹ»×öµÃºÃµÄÈËÃÇͨ³£ÊdzöÓÚËûÃÇ×ÔÉíµÄ¿ÊÍû²ÅÈ¥×÷µÄ¡£
-
-<P>
-
-Õâ²¢²»ÊÇ˵ÒôÀÖ¼ÒÃDz»ÔÚºõËûÃǵÄÊÕÈë¡£
-´ó¶àÊýÒôÀÖ¼ÒÏ£ÍûÄܹ»ÒÀ¿¿ÒôÀÖάÉú£¬
-ÒÔ±£Ö¤ËûÃÇ¿ÉÒÔ×ÔÓɵؽ«Ê±¼äͶÈëµ½ÆäÖС£
-Ö»ÒªËûÃÇÊÕÈë×ãÒÔÉú»î£¬
-ËûÃǾͿÉÒÔ´´×÷³öÄÜ´´×÷µÄ×îºÃµÄÒôÀÖ¡£
-ÎÒÃÇÒ²ÐíÏ£ÍûËûÃÇÓ¦¸ÃµÃµ½±È¸Õ¸ÕºÃ¶àһЩµÄÊÕÈ룬
-ÄÇÑùËûÃǾͿÉÒÔ¹ýµÃÏñ´ó¶àÊýÃÀ¹úÈËÒ»ÑùºÃ¡£
-µ«ÊÇÌṩËûÃdz¬³öÕâ¸ö³Ì¶ÈµÄ²Æ¸»£¬
-¹«ÖÚ²¢Ã»Óеõ½Ê²Ã´£­£­ÕâÊÇÒ»¸ö»Ø±¨Ï½µµÄÇé¿ö¡£
-
-<P>
-
-ÓÐÁËÕâÖÖÁ˽⣬
-ÈÃÎÒÃÇ¿¼ÂÇÈçºÎÉè¼Æ DAT ´Å´øË°ÒÔ´ïµ½°æȨµÄ±¾À´Ä¿µÄ¡£
-
-<P>
-
-<H4><A HREF="#toc5"
-       NAME="sec5">Ë­Ó¦¸ÃµÃµ½×ʽð</A></H4>
-
-<P>
-
-Èç¹û DAT Ë°µÄÄ¿µÄÊÇΪÁ˸üºÃµØ½±ÀøÒôÀÖ¼ÒºÍ×÷Çú¼Ò£¬
-ÄÇôËùÓеÄÊÕÈ붼Ӧ¸ÃÊôÓÚËûÃÇ£­£­¶ø²»Êǽö½öÖ»ÓаٷÖÖ®ËÄÊ®Èý¡£
-ÒôÀÖ¼ÒºÍ×÷Çú¼ÒÊÇÕæÕý´´ÔìÒôÀÖµÄÈË¡£
-ͨ³££¬
-Èç¹ûÍêȫûÓгªÆ¬¹«Ë¾ÎÒÃÇÒ²¿ÉÒÔÐÀÉÍÒôÀÖ¡£
-
-<P>
-
-³ªÆ¬¹«Ë¾µÄÈ·ÌṩÁËÓÐÒæµÄ·þÎñ£º
-ËûÃÇ·¢²¼Ô¤ÏȼÖÆÍê³ÉµÄÒôÀÖ¿½±´£¬
-ͨ³£ÖÊÁ¿ÓÅÐã¡£
-ÕâÖÖ·þÎñ±»¹ã·ºÊ¹Óã¬
-²¢ÇÒ¿ÉÄÜ»áά³ÖÏÂÈ¥¡£
-Ô¤ÏȼÖÆÒôÀÖ¿½±´µÄ¹ºÂòÕßΪ·þÎñ¸¶·ÑÒ²ÊÇÕýÈ·µÄ¡£
-µ«ÊÇΪ×Ô¼º»òÅóÓÑÃÇÖÆ×÷¿½±´µÄÌýÖÚ²¢Ã»ÓÐÏû·ÑÕâÖÖ·þÎñ£»
-ËûÃÇÖ»ÏíÓÃÁËÒôÀÖ¼ÒºÍ×÷Çú¼ÒÃǵŤ×÷¡£
-³ªÆ¬¹«Ë¾Ö»ÊǸ½´øµØ×÷³öÁËһЩ¹±Ï×£¬
-²¢ÇÒËûÃǵĽÇÉ«Ò²²»ÊDZØÐëµÄ¡£
-
-<P>
-
-<H4><A HREF="#toc6"
-       NAME="sec6">×ʽð·ÖÅä</A></H4>
-<P>
-
-ÿ¸öÒôÀÖ¼Ò»ò×÷Çú¼ÒÓ¦¸ÃµÃµ½Ë°ÊյĶà´ó·Ý¶î£¿
-³ªÆ¬¹«Ë¾½¨Òé¸ù¾Ý³ªÆ¬ÏúÊÛ±ÈÀý·ÖÅä½ðÇ®¡£
-
-<P>
-
-¸ù¾ÝÒôÀÖ¼Ò×÷Æ·±»¸´ÖƵĶàÉÙ·ÖÅä×ʽð»ò¶à»òÉÙ¾ßÓÐÒ»¶¨µÄÒâÒå¡£
-µ«ÊÇÑϸñµÄ¸ù¾Ý±ÈÀý»®·Ö²¢²»ÊÇ×îºÃµÄ½â¾ö·½·¨¡£
-Èç¹ûÿһ¸öÒôÀÖ¼Ò¶¼¸ù¾ÝËûÃÇ×÷Æ·¸´ÖÆÊýÁ¿µÄÑϸñ±ÈÀý·ÖÅäÊÕÈ룬
-ÄÇô´óÁ¿µÄÊÕÈë¾Í»áÁ÷Èë¾ÞÐÇÃǵĿڴüÖУ¬
-Õâ»áʹµÃËûÃDZÈÏÖÔÚ¸ü¸»ÓС£
-Õâ¶Ô´Ù½øÒôÀÖÎÄ»¯»òÕ߶àÑù»¯Ã»ÓÐʲôºÃ´¦¡£
-
-<P>
-
-ͨ¹ýËæ×Å¿½±´ÊýµÄÔö¼Ó¶øÖð½¥¼õÉÙÒôÀÖ¼ÒµÄË°ÊÕÊÕÒ棬
-ÎÒÃÇ¿ÉÒÔ¸üÓÐЧµÄ´Ù½øÒôÀֵķ¢Õ¹¡£
-ÀýÈ磬
-ÎÒÃÇ¿ÉÒÔ¼ÆËãÒ»ÖÖ¡¸Ð£ÕýµÄ¿½±´ÊýÁ¿¡¹£¬
-ÔÚ³¬¹ýÒ»¸öÌض¨µÄµãÖ®ºó£¬
-Ëü±Èʵ¼ÊÊýÁ¿µÄÔö³¤ÒªÂýµÄ¶à¡£
-
-<P>
-
-Öð½¥¼õÉÙÊÕÈëµÄЧ¹û½«Ê¹µÃÊÕÈëµÄ·ÖÅä¸ü¼Ó¹ã·º£¬
-¹©Ñø¸ü¶àÒôÀÖ¼Ò¹ýÉÏÊʵ±Ë®Æ½µÄÉú»î¡£
-Õâ¹ÄÀøÁ˶àÑù»¯£¬
-ÕýÊÇ°æȨÖƶÈËùÓ¦¸Ã×öµÄ¡£
-
-<P>
-
-ÃÀ¹úÕþ¸®ÒѾ­½¨Á¢ÁË×ÊÖúÒÕÊõ¶àÑù»¯µÄ¼Æ»­£ºNEA¡£
-È»¶ø£¬
-NEA ¾èÖúÈËÓµÓÐÎÞÏÞȨÀû£¬
-ÕâʹµÃËûÃdzÉΪÕùÂÛµÄÖÐÐÄ£¬
-ÓÐʱºòÒòΪһ²¿·Ö¹«Öںܲ»Ï²»¶Õâ·Ý×÷Æ·£¬
-ÓÐʱºòÊÇÒòΪ¼¸ºõûÓÐÈËÃ÷ȷϲ»¶Ëü¡£
-·ÖÅä DAT Ë°ÊÕÊÕÈëͬʱҲ»áÓÐÖ§³Ö¸ü¶à·ÇÖ÷Á÷ÒôÀÖ¼ÒµÄЧ¹û¡£
-È»¶ø£¬
-Ëü²»»áÖ§³Ö×÷ƷûÓÐÈËϲ»¶µÄÒôÀÖ¼Ò¡£
-´ËÍ⣬
-ÒòΪËü²¢Ã»Óаüº¬ÈκÎÅжϣ¬
-ûÓÐÈκÎÎä¶ÏµÄ¾ö¶¨£¬
-¼¸ºõûÓÐΪÌض¨Ô­Òò¶ø¾Ü¾øµÄ¿Õ¼ä¡£
-
-<P>
-
-<H4><A HREF="#toc7"
-       NAME="sec7">¹ÄÀø¼ÒÍ¥¸´ÖÆ</A></H4>
-
-<P>
-
-³ªÆ¬¹«Ë¾µÄ½¨ÒéÖÐÒªÇóʹµÃ¼ÒÍ¥ÌýÖÚºÜÄÑÖÆ×÷¿½±´¡£
-ÌرðµÄ£¬
-ËüÒªÇóÏû·ÑÕßµÄ DAT »úÓ¦¸Ã¾Ü¾ø¸´ÖÆÒ»·ÝÔÚÏû·ÑÕß DAT »úÉÏÖÆ×÷µÄ¿½±´¡£
-ÕâÏîÒªÇóµÄÂÛµãÊÇ»ùÓÚ¼ÒÍ¥¿½±´ÊDz»¹«Æ½µÄ¡£
-
-<P>
-
-ÔÚ¹ýÈ¥£¬
-ºÜ¶àÈ˶¼ÈÏΪËüÊDz»¹«Æ½µÄ£¬
-ÒòΪËü½µµÍÁËÒôÀÖ¼ÒµÄÊÕÈë¡£
-DAT Ë°ÊÕʹµÃÕâ¸öÔ­Òò¹ýʱÁË¡£
-Ò»µ©¼ÒÍ¥¿½±´È·ÊµÍ¨¹ý DAT Ë°¶ÔÒôÀÖ¼ÒµÄÊÕÈë×÷³öÁ˹±Ï×£¬
-×èÄÓ¼ÒÍ¥¿½±´µÄÔ­Òò¾ÍÏûʧÁË¡£
-
-<P>
-
-Òò´Ë£¬
-Èç¹û²ÉÓÃÁË DAT Ë°£¬
-¸´ÖÆ DAT ´Å´øµÄÄÜÁ¦¾Í²»Ó¦¸ÃµÃµ½ÏÞÖÆ¡£
-¼ÒÍ¥¸´ÖƱȳªÆ¬¹«Ë¾ºÍ³ªÆ¬É̵ê¸üΪÓÐЧ£»
-Ó¦¸Ã¹ÄÀøÒôÀÖ°®ºÃÕß¾¡¿ÉÄܶàµÄʹÓüÒÍ¥¸´ÖÆ¡£
-
-<P>
-
-<H4><A HREF="#toc8"
-       NAME="sec8">ºâÁ¿Ã¿¸öÒôÀÖµÄʹÓÃ</A></H4>
-
-<P>
-
-ÏÖÔÚ£¬
-¼¸ºõËùÓÐÃÀ¹úµÄ¼ÖÆÒôÀÖ¶¼ÊÇÔÚ³ªÆ¬É̵êËù¹ºÂòµÄ£»
-¼ÒÍ¥¸´ÖÆÖ»Õ¼ºÜÉٵķݶ
-ÕâÔںܳ¤Ê±¼äÄÚ¿ÉÄÜÈÔÈ»ÊÇÊÂʵ£¬
-ÒòΪ³ªÆ¬É̵êÌṩÁËÒ»¸ö³¡Ëù£¬
-ÔÚÄÇÀïÈËÃÇ¿ÉÒÔȥѰÕÒÌض¨µÄÒôÀÖ»òä¯ÀÀÒ»¸ö¹ã·ºµÄÑ¡Ôñ¡£
-Ö»ÒªÕâÏîÊÂʵÈÔȻά³Ö£¬
-ÎÒÃÇͨ³£¿ÉÒÔͨ¹ýͳ¼Æ³ªÆ¬µÄÏúÁ¿£¬
-ºÜºÃµØ¹À¼ÆÒ»¸öÒôÀÖµÄÌýÖÚÊýÁ¿¡£
-
-<P>
-
-×îºó£¬
-¼ÒÍ¥¸´ÖÆÒ²Ðí»á±äµÃÈç´ËÆձ飬
-ÒÔÖÁÓÚÓÉÏúÊÛÊý¾Ý¹À¼ÆÒôÀֵĴ«²¥ÒѾ­ÊDz»¹«Æ½µÄ¡£
-Õâ¶ÔûÓгªÆ¬¹«Ë¾°ïÖú¶ÀÁ¢·¢ÐÐÒôÀÖµÄÒôÀÖ¼ÒÒѾ­ÊDz»¹«Æ½µÄÁË£»
-¶øÇÒÈç¹ûÒôÀÖ¼ÒÐèÒª¶îÍâµÄÖ§³Ö£¬
-ÄǾÍÊÇËûÃÇ¡£
-ΪÁË·ÖÅäË°ÊÕ×ʽð£¬
-ÎÒÃÇÐèÒªÆäËûµÄ·½Ê½À´¹À¼ÆÒ»¸ö¸ø¶¨ÒôÀÖµÄʹÓá£
-
-<P>
-
-ÎÒÃÇ¿ÉÒÔͨ¹ýµ÷²éÀ´½øÐÐÕâЩ¹À¼Æ¡£
-ÓÐʱ£¬
-µ÷²éÔ±ÃÇ»áÏòËæ»úÑ¡ÔñµÄ¹«ÖÚÃÇÌáÎÊ£¬
-À´µ÷²éËûÃǸ´ÖÆÁ˶àÉÙÓаæȨµÄÒôÀÖ¡£
-±»Îʵ½µÄ¹«Ãñ²»±»Ç¿ÖÆÒªÇó»Ø´ð¡£
-µ«ÊÇûÓз£¿î»òÕß×ï¶ñ°éËæ×ÅÓµÓп½±´£¬
-Òò´Ë´ó¶àÊýÈ˶¼»áϲ»¶²ÎÓëµÄ¡£
-°®ºÃÕß»áÏ£Íû±»Ñ¡ÖУ¬
-ÕâÑùËûÃǾͿÉÒÔΪËûÃÇϲ»¶µÄÒôÀÖ×éÖ¯µÄ¸´ÖÆÊýÁ¿×÷³ö¹±Ïס£
-
-<P>
-
-ΪÁËÈõ÷²é¸üÓÐЧºÍ¹ã·º£¨Òò´Ë¸ü׼ȷ£©£¬
-µ÷²éÓ¦¸ÃÊÇ×Ô¶¯½øÐеġ£
-µ÷²é¾Ö¿ÉÒÔÓʼĶÁд¼ÇÒ俨¸øÑ¡¶¨µÄ²ÎÓëÕߣ¬
-ËûÃÇ¿ÉÒÔÂíÉϽ«ÕâЩ¿¨Óë DAT »úÏàÁ¬²¢½«ËüÃǼĻء£
-Èç¹ûÉè¼ÆºÏÀíµÄ»°£¬
-µ÷²é¾Ö²¢ÎÞ·¨ÖªµÀÌض¨¿¨µÄµÝ½»ÕßÊÇË­£¬
-Òò´ËÎÞ·¨µÃµ½Ë­ÓµÓп½±´µÄÐÅÏ¢£¬
-µ«ÊÇËûÃÇÈÔÈ»¿ÉÒԵõ½×¼È·µÄ×ÜÊý¡£
-
-<P>
-
-<H4><A HREF="#toc9"
-       NAME="sec9">½áÂÛ</A></H4>
-
-<P>
-
-³ªÆ¬¹«Ë¾Ìá³öÁËÒ»¸öͨ¹ýÏò¹«ÖÚÕ÷Ë°Ôö¼ÓËûÃÇÊÕÈëµÄºÜºÃµÄ¼Æ»­£¬
-µ«ÊÇÕâ²¢²»ÊÇ°æȨÖƶȵĺϷ¨µÄÄ¿µÄ¡£
-ͨ¹ý×¢ÖØ°æȨµÄ×îÖÕÄ¿µÄ¶ø²»Êǹý³ÌÊֶΣ¬
-ÎÒÃÇ¿ÉÒÔÉè¼ÆÒ»¸öϵͳÔÚÖ§³ÖÒôÀÖ¼ÒµÄͬʱ£¬
-Ò²¸³Ó蹫ÃñËæÒ⸴ÖÆÒôÀÖµÄÍêÈ«×ÔÓÉ¡£
-
-<P>
-
-<H4><A HREF="#toc10"
-       NAME="sec10">Äã¿ÉÒÔ×öЩʲô</A></H4>
-
-<P>
-
-<EM>
-[ÕâÒ»²¿·ÖÏÖÔÚÒѾ­²»ÔÙ¿ÉÐУ»
-ÒѾ­Ì«ÍíÁË£¬
-ÒòΪ DAT Ë°ÒѾ­»ñµÃͨ¹ý²¢°ä²¼ÁË¡£]
-</EM>
-<P>
-
-³ªÆ¬¹«Ë¾µÄ˵¿ÍÃÇÕýŬÁ¦¹¤×÷ÒÔͨ¹ýËûÃÇÐÎʽµÄ DAT Ë°¡£
-¼¸ºõûÓÐÓÐ×éÖ¯µÄ¿¹Ò飬
-Ò²¼¸ºõûÓй«ÖÚµÄÕùÂÛ¡£
-ËûÃǵÄÒé°¸ÒѾ­Ë͵½Á˲ÎÒéÔº¡£
-
-<P>
-
-ÕâƪÎÄÕÂÌṩÁËÒ»¸ö³ªÆ¬¹«Ë¾¼Æ»­Ö®ÍâµÄÑ¡Ôñ¡£
-ΪÁËÈÃÕâ¸öÑ¡Ôñ»òÆäËûÈκÎÑ¡ÔñÄܹ»Óлú»á£¬
-ÎÒÃDZØÐëÊ×ÏÈ×èÖ¹´Òæ²ÉÈ¡³ªÆ¬¹«Ë¾µÄ¼Æ»­¡£
-ΪÁË°ïÖú´ïµ½Õâ¸öÄ¿µÄ£¬
-ÇëÍùÒÔϵØַдÐÅ£º
-
-<P>
-
-<BLOCKQUOTE>
-     Congressman Barney Frank
-     437 Cherry St
-     West Newton, MA 02165
-<P>
-
-     Senator Metzenbaum
-     United States Senate
-     Washington, DC 20510
-<P>
-
-     House Subcommittee on Intellectual Property
-     House of Representatives
-     Washington, DC 20515
-
-</BLOCKQUOTE>
-
-´Ùʹ¹ú»á·ñ¾ö³ªÆ¬¹«Ë¾µÄ¼Æ»­£¬
-´Ó¶øÕâ¸ö»òÆäËûÑ¡ÔñÄܹ»±»¹«ÕýµÄ¿¼ÂÇ¡£
-дһ·â¶ÌÐÅÖ»ÐèÒª»¨Éϼ¸·ÖÖÓµÄʱ¼ä£¬
-µ«ÊǽáºÏÆäËûÈ˵ÄÐŽ«»á´óÓÐÖúÒæ¡£
-
-<P>
-
-Èç¹ûÄãÈÏʶÈκÎÒôÀÖ¼Ò¡¢×÷Çú¼Ò»òÕ߸èÇú×÷Õߣ¬
-Çë¸øËûÃÇÒ»·ÝÎÄÕµĿ½±´¡£
-ºÜ¶àÒôÀÖ¼Ò¸üϲ»¶Õâ¸ö³ªÆ¬¹«Ë¾Ë°Êռƻ­µÄÌæ´ú£¬
-ËûÃÇÓÐÇ¿ÁÒµÄÒÀ¾ÝÓÉÓÚËûÃǵĹØϵ¶øÐж¯¡£
-
-<P>
-
-
-<EM>
-[ÒÔÉÏÎÄÕÂÓÚÒ»¾Å¾Å¶þÄê·¢±íÔÚ Wired ÔÓÖ¾¡£
-³ªÆ¬¹«Ë¾µÄ DAT Ë°ËæºóÓÉ×Üͳ George ``read my lips'' Bush Ç©ÊðΪ·¨ÂÉ¡£
-¾¡¹ÜÕâʱÒѽìÒ»¾Å¾Å¶þÄêÑ¡¾Ù£¬
-ºÜÉÙÓÐÈË×¢Òâµ½ËûÔÙÒ»´ÎÍÆ·­ÁËËû²»»áÔö¼ÓÈκÎеÄË°¸³µÄ±£Ö¤¡£]
-</EM>
-<P>
-
-
-Copyright 1992 Richard M. Stallman
-<BR>
-Verbatim copying in any medium is permitted without fee
-provided the copyright notice and this notice are preserved.
-<P>
-
-<HR>
-
-<H4><A HREF="/philosophy/philosophy.html">ÆäËû¶ÁÎï</A></H4>
-
-<HR>
-
-<P>
-·µ»Ø <A HREF="/home.zh-cn.html">GNU Ê×Ò³</A>¡£
-
-<P>
-Ç뽫ÓÐ¹Ø ×ÔÓÉÈí¼þ»ù½ð»á Óë GNU µÄ ²éѯ Óë ÎÊÌâ Ë͵½
-<A HREF="mailto:address@hidden";><EM>address@hidden</EM></A>¡£
-ÄãÒ²¿ÉÒÔʹÓà <A HREF="/home.html#ContactInfo">ÆäËû·½·¨ÁªÂç</A>
-×ÔÓÉÈí¼þ»ù½ð»á¡£
-
-<P>
-Ç뽫ÓйØÍøÒ³µÄÒâ¼ûË͵½
-<A HREF="mailto:address@hidden";><EM>address@hidden</EM></A>£¬
-ÆäËûÎÊÌâÔòË͵½
-<A HREF="mailto:address@hidden";><EM>address@hidden</EM></A>¡£
-
-<P>
-Ç뽫ÓйØÖÐÎÄÒ³ÃæµÄÒâ¼ûË͵½
-<A HREF="mailto:address@hidden";><EM>address@hidden</EM></A>£¬
-ÆäËûÎÊÌâÔòË͵½
-<A HREF="mailto:address@hidden";><EM>address@hidden</EM></A>¡£
-
-<P>
-°æȨ±ê×¢¼ûÉÏ¡£
-<P>
-ÔÊÐíÔÚ²»±ä¸üÎļþÄÚÈݵÄÇ°ÌáÏ¿¯µÇ±¾Îĸ±±¾ÔÚÈκÎÐÎʽµÄýÌåÖУ¬
-²»ÐèÖ§¸¶³ê½ð£¬µ«Ðè±£Áô°æȨÐû¸æºÍ´ËÉùÃ÷¡£
-
-<P>
-·­Ò룺Áº ÃÈ¡£
-<BR>
-ÑéÖ¤£ºÁõ ÕѺꡣ
-<BR>
-Ç뽫Óйط­ÒëµÄÎÊÌâË͵½
-<A HREF="http://savannah.gnu.org/projects/chinese/";>GNU/CTT</A> µÄ
-<A HREF="mailto:address@hidden";>·­ÒëÈËÔ±</A>¡£
-
-<P>
-Updated:
-<!-- timestamp start -->
-$Date: 2011/12/30 05:18:26 $ $Author: ineiev $
-<!-- timestamp end -->
-<HR>
-</BODY>
-</HTML>
+<!--#set var="ENGLISH_PAGE" value="/philosophy/dat.en.html" -->
+
+<!--#include virtual="/server/header.zh-cn.html" -->
+<!-- Parent-Version: 1.77 -->
+
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>DAT征税的正确方法 - GNU工程 - 自由软件基金会</title>
+
+<!--#include virtual="/philosophy/po/dat.translist" -->
+<!--#include virtual="/server/banner.zh-cn.html" -->
+<h2>DAT征税的正确方法</h2>
+
+<p><a href="http://www.stallman.org/";><strong>Richard Stallman</strong></a> 
著</p>
+
+<p><em>[本文并不和软件直接相å…
³ã€‚本文涉及的问题和软件类似,是关于分享音乐。]</em></p>
+
+<p><em>[本文在1992年最初发表于连线(Wired)杂志;文章内
容没有改变;只是增加了方括号里以斜体或å…
¶ä»–强调方式表达的注释。]</em></p>
+
+<p><em>[原文讨论了使用(当时才出现的)数字音频磁带机分享音乐(当时还是假设)的问题,å›
 
为这正是美国税法要讨论的问题。现在,本文可以用于网络文件分享的问题。]</em></p>
+
+<p><em>[另一个解决方案在我的帮助下由已故的Francis
+Muguet提出,其中包含了一些本文的想法,被称为å…
¨çƒä¿æŠ¤ç³»ç»Ÿï¼ˆç”¨æ³•è¯­æ¥è¯´æ˜¯ï¼ŒM&eacute;c&eacute;nat
+Global)。这两个方案我都支持;就是说,采用哪一个,我都赞同。]</em></p>
+
+<p>唱片公司的巨头们并不喜欢数字音频磁带录音机(<acronym 
title="Digital Audio
+Tape">DAT</acronym>),尽管它们可以制作完美的音乐录音带复制品。他们æ‹
…心顾客们会自己复制音乐,从而停止购买事å…
ˆå½•åˆ¶çš„音乐。</p>
+
+<p>通过诉讼威胁的手段,他们已经与DAT的生产厂商达成了协议,生产厂商会为他们销售给顾客的每个DAT机和每盘DAT磁带支付一笔费用。该费用将分给音乐产业中不同的参与è€
…:音乐家、作曲家、音乐发行商和唱片å…
¬å¸ã€‚除此以外,DAT生产商同意减弱DAT机以保证无法制作事å…
ˆå½•åˆ¶çš„磁带的拷贝的拷贝。</p>
+
+<p>现在唱片å…
¬å¸è¦æ±‚国会颁布法律将该费用规定为税,并且禁止生产功能上没有强制限制的DAT录音机。</p>
+
+<p>征收该税的目的声称是&ldquo;补偿&rdquo;音乐家因
私人使用DAT复制而损失的收å…
¥ã€‚然而,这笔资金的百分之五十七归唱片å…
¬å¸å’ŒéŸ³ä¹å‘行商所有&mdash;只有剩下不到一半分给参与创作的人们。而这剩下资金的大部分又将进å
…¥éŸ³ä¹è¶…级巨星的腰包,因
此这不是鼓励为音乐创作作贡献。与此同时,DAT用户将不能完å
…¨åˆ©ç”¨DAT技术的威力。</p>
+
+<p>这里提议一个不同的DAT和DAT磁带征税系统&mdash;为支持音乐而不是为迎合特权阶级而设计的提案。</p>
+
+<ul>
+<li>通过向DAT设备和DAT磁带征税来筹集资金,正如当前提案所提到的。</li>
+<li>使用调查系统来衡量每一个音乐作品的复制广度。</li>
+<li>将资金完全分配给音乐创作者。</li>
+<li>调整每一个贡献者
的份额,使它越大时从每份拷贝获得的收益越少。这æ 
·å°±å¯ä»¥æ›´åŠ å¹¿æ³›åœ°åˆ†é…èµ„金从而充
分支持更大数量的音乐家。</li>
+<li>不限制DAT的功能。</li>
+</ul>
+
+<h3>版权制度的目的何在?</h3>
+
+<p>唱片业展示的提议是一种&ldquo;补偿&rdquo;音乐家的方法,他们假设每一份拷贝都应该对音乐家付费。很多美国人相信版权法反æ˜
 äº†ä½œè€…或音乐家们的自然权利&mdash;这些权利应该由公å…
±æ”¿ç­–给予特殊的考虑。然而,任何该领域的律师都知道这是一种误解,一种为美国法制体系所拒绝的观点。</p>
+
+<p>美国宪法阐述的版权的目的是为了&ldquo;促进科学和有益艺术的发展&rdquo;。音乐的发展意味着有新颖的和多æ
 ·çš„音乐供公众欣赏:版权应该促进公å…
±åˆ©ç›Šï¼Œè€Œä¸æ˜¯ä¸ªäººåˆ©ç›Šã€‚</p>
+
+<p>然而外行人和政客们经常认为版权是一种自然权利,这往往导致版权政策的错误决定。甚至定义版权体系细节的法院也经常让此种想法暗中蔓延,尽管它应该被排除掉。这是一个概念错误,å›
 
为它错误地将达到较大目的(发展)的手段(版权)作为目的本身。</p>
+
+<p>促进艺术的发展并不从根本上证明作者
拥有版权、甚或版权的存在是合理的。版权只有在å…
¶ä¿ƒè¿›ä½œç”¨è¶…过了其对除版权持有者之外的人的负担
时,才是正确合理的。</p>
+
+<p>如何判断这种代价/收益比?它部分取决于事实(特定法律是如何影响音乐活动和音乐用户的),部分取决于我们å
…³äºŽè¿™äº›ç»“果的价值判断。</p>
+
+<p>让我们假设,如果支付DAT税会显著促进音乐活动,那么支付DAT税是值得的,并且ç
 ”究一下如何细分该税以取得最大利益。但是,首å…
ˆè®©æˆ‘们回顾一下与该要求相关的基本原则和事实。</p>
+
+<h3>回报递减</h3>
+
+<p>回报递减理论是经济学的一个普遍定律。它认为每次针对给定目æ
 ‡è€Œå¢žåŠ çš„努力或投资所产生的回报增加
会越来越少。这个理论存在例外,但它们都是局部性的;如果ä½
 ç»§ç»­å¢žåŠ æŠ•å…¥ï¼Œæœ€ç»ˆä½ ä¼šè„±ç¦»ä¾‹å¤–。</p>
+
+<p>举例说明,你
可以采取改进道路的方式来使得交通变得更加顺畅
。为20英里的城市拥挤道路增加
一个车道,可能会使平均交通时速提高十五英里。再添加
一条车道将不会有同æ 
·çš„改善效果;这次平均时速可能只提高五英里。如果交通阻塞已经不再存在的话,再添åŠ
 ä¸€ä¸ªè½¦é“可能不会有任何明显的变化。然而每一条增加
的车道都会带来更大的位置变化,因为必
须拉倒越来越多的建筑物以腾出空间。</p>
+
+<p>应用于音乐活动,回报递减告诉我们,音乐家们的每次收å
…¥å¢žåŠ å¯¹éŸ³ä¹åˆ›é€ æ€§çš„影响都变得更小。</p>
+
+<p>回报递减理论是拒绝任何对音乐的使用都&ldquo;应该&rdquo;受版权保护这一想法的第一个原å›
 ã€‚试图鼓励所有者控制音乐使用的方方面面,或者
对每一个可能的市场都给予他们金钱上的奖励将无
法获得任何回报。扩展版权只能&ldquo;促进发展&rdquo;到特定的程度。更多的扩展只不过是使å
…¬ä¼—们向所有者支付的费用增加,而所有者
并不能做更多。在此之上的扩展显然是不受欢迎的。</p>
+
+<h3>取舍</h3>
+
+<p>那些对扩展版权具有既定å…
´è¶£çš„人们挑起了论战,他们声称版权&ldquo;应该&rdquo;扩展得越远越好。但是回报递减理论让这种声明变得不可能。所以他们退而求å
…
¶æ¬¡ï¼Œåˆå›žåˆ°ç‰ˆæƒçš„扩展应该使发展速度最大化的立场。但这也是错误的,å›
 ä¸ºå®ƒå¿½ç•¥äº†å…¶ä»–可取舍因素的存在。版权正如å…
¶ä»–任何政府项目一样,向公众强加费用和负担
。它的收益可能不如为它所付出的代价。</p>
+
+<p>政府完成很多重要的职能,但是几
乎没有哪一项职能可以说应该被扩展到产出最大化的程度。例如,政府修建道路,并且道路是非常有用的。但是å‡
 
乎没有领导人会热衷于修建他们所能修建的每一条道路。道路建设耗资巨大,å
…¬æ°‘还有其他需要用钱的地方。太专注于道路建设就意味着å…
¶ä»–社会和个人的需要将无法得到满足。</p>
+
+<p>同样的道理适用于个人决定。花更多的钱,你
可以购买到更大和更好的住房。其他条件一æ 
·æ—¶ï¼Œå¤§å¤šæ•°äººéƒ½å–œæ¬¢è¾ƒè´µçš„住房。但是假定资源有限,到达某种程度后,再在住房上花费更多就成为一种差劲的资源分é
…ã€‚</p>
+
+<p>版权并不直接花费公众的资金,但是它的确向每个å…
¬æ°‘都强加
了一种代价&mdash;自由的丧失。版权的范围越广,我们所付出的自由就越多。我们也许更愿意享受我们的自由而不是用它们来作交易。我们å¿
…须通过比较得失来判断每个版权制度的决定。</p>
+
+<h3>&ldquo;激励&rdquo;是错误的概念</h3>
+
+<p>对音乐创作提供金钱激励的想法建立在错误理解的基础之上。音乐家们主要期望å
…¶ä»–的回报;他们必须这æ 
·ã€‚很少有音乐家由于他们的音乐而富有;一个主要目æ 
‡æ˜¯è´¢å¯Œçš„天才会通过别的方式来追求它。</p>
+
+<p>事实上,心理学ç 
”究表明渴望得到外在的奖励(例如利润)一般会损害音乐创作这æ
 ·çš„创造
性活动。能够做得好的人通常是出于他们自身的理由才去做的。</p>
+
+<p>这并不是说音乐家们不在乎他们的收å…
¥ã€‚大多数音乐家希望能够依靠音乐谋生,这æ 
·ä»–们就可以自由地将时间投入其中。只要他们的收å…
¥è¶³ä»¥ç”Ÿæ´»ï¼Œä»–们就会尽可能地创作最好的音乐。我们也许希望他们应该得到比刚刚好多一些的收å
…¥ï¼Œé‚£æ ·ä»–们就可以过得像大多数美国人一æ 
·å¥½ã€‚但是提供给他们超出这个程度的财富并不能使å…
¬ä¼—得到更多&mdash;这是一个回报递减的情况。</p>
+
+<p>有了这种理解,让我们考虑如何设计DAT磁带税以达到版权的本来目的。</p>
+
+<h3>谁应该得到资金</h3>
+
+<p>如果DAT税的目的是为了更好地奖励音乐家和作曲家,那么所有的收å
…¥éƒ½åº”该属于他们&mdash;而不是仅仅
只有百分之四十三。音乐家和作曲家是真正创造
音乐的人。原则上,如果完全没有唱片å…
¬å¸æˆ‘们也可以欣赏音乐。</p>
+
+<p>唱片公司的确提供了有益的服务:他们发布预å…
ˆå½•åˆ¶å®Œæˆçš„音乐拷贝,通常是高质量的。这种服务被广泛使用,并且可能会这æ
 ·ä¿æŒä¸‹åŽ»ã€‚预先录制音乐拷贝的购买者
为服务付费也是正确的。但是为自己或朋友们制作拷贝的听众并没有消费这种服务;他们只享用了音乐家和作曲家们的工作。唱片å
…¬å¸åªæ˜¯é™„带地作出了一些贡献,并且他们的角色也不是必
须的。</p>
 
+<h3>分配资金</h3>
+
+<p>每个音乐家或作曲家应该得到税收的多大份额?唱片å…
¬å¸å»ºè®®æ ¹æ®å”±ç‰‡é”€å”®æ¯”例分配金钱。</p>
+
+<p>根据音乐家作品被复制的多少分配资金或多或少å…
·æœ‰ä¸€å®šçš„意义。但是严æ 
¼æŒ‰æ¯”例划分并不是最好的解决方法。如果每一个音乐家都按ç
…§å…¶ä½œå“å¤åˆ¶æ•°é‡çš„比例严格分配收入,那么å…
¶å¤§éƒ¨åˆ†çš„份额会使少量巨星们比现在更富有。这对促进音乐文化或è€
…多样化并没有什么好处。</p>
+
+<p>通过随着拷贝数的增加
而逐渐减少音乐家的税收收益,我们可以更有效地促进音乐的发展。例如,我们可以计算一个&ldquo;调整后拷贝数量&rdquo;,在è¶
…过特定节点之后,它比实际数量的增长要慢得多。</p>
+
+<p>逐渐减少收入的效果是使收入分配得更加广泛,供å…
»æ›´å¤šéŸ³ä¹å®¶è¿‡ä¸Šé€‚当水平的生活。这鼓励了多æ 
·åŒ–,正是版权制度应该做的。</p>
+
+<p>美国政府已经建立了资助艺术多样化的项目:<acronym 
title="National Endowment for the
+Arts,国家艺术基金">NEA</acronym>。然而,NEA基金拥有自由裁决的权利,这使得他们成为争论的中心,有时候å›
 ä¸ºä¸€éƒ¨åˆ†å…¬ä¼—会员很不喜欢某作品,有时候是因为几
乎没有人明确喜欢它。分配DAT税收收å…
¥ä¹Ÿä¼šæœ‰æ”¯æŒéžä¸»æµéŸ³ä¹å®¶çš„效果。然而,它不会支持作品没人喜欢的音乐家。此外,å›
 ä¸ºå®ƒå¹¶æ²¡æœ‰åŒ…
含任何自由裁决,也没有任何武断的决定,所以它几
乎没有因为特定原因而拒绝某作品的空间。</p>
+
+<p><em>[后来,有人问我一个有趣的问题:什么机构应该来&ldquo;管理&rdquo;这些资金的分é
…ã€‚因为这是税收,政府机构应该征收和分é…
è¿™äº›èµ„金。私人机构不应该介入。]</em></p>
+
+<h3>鼓励家庭复制</h3>
+
+<p>唱片å…
¬å¸çš„建议中要求使得家庭听众很难制作拷贝。特别地,它要求消费è€
…çš„DAT机拒绝复制在消费者
DAT机上制作的拷贝。这项要求的论点是基于家庭拷贝是不太å…
¬å¹³çš„假设之上的。</p>
+
+<p>在过去,很多人都认为它是不公平的,因
为它降低了音乐家的收入。DAT税收使得这个原因
过时了。一旦家庭拷贝确实通过DAT税对音乐家的收å…
¥ä½œå‡ºäº†è´¡çŒ®ï¼Œé˜»æŒ å®¶åº­æ‹·è´çš„原因就消失了。</p>
+
+<p>因
此,如果采用了DAT税,复制DAT磁带的能力就不应该得到限制。家庭复制比唱片å
…¬å¸å’Œå”±ç‰‡å•†åº—更为有效;应该鼓励音乐爱好者
尽可能多的使用家庭复制。</p>
+
+<h3>衡量每个音乐的使用</h3>
+
+<p>现在,几
乎所有美国的录制音乐都是在唱片商店购买的;家庭复制只å
 å¾ˆå°‘的份额。这在很长时间内可能仍然是实际情况,因
为唱片商店提供了一个场所,在那里人们可以去寻找特定的音乐或浏览广泛的选择。只要这项事实仍然保持,我们通常可以通过统计唱片的销量,很好地估计一个音乐的听众数量。</p>
+
+<p>最终,家庭复制也许会变得如此普遍,以至于由销售数据估计音乐的ä¼
 æ’­å·²ç»ä¸å†ä»¤äººæ»¡æ„ã€‚这对没有唱片å…
¬å¸å¸®åŠ©çš„独立发行音乐的音乐家已经是不å…
¬å¹³çš„了;而且如果还有音乐家需要额外的支持,那就是这些独立音乐家。为了分é
…ç¨Žæ”¶èµ„金,我们需要其他方法来估计某个音乐的使用。</p>
+
+<p>我们可以通过调查来进行这些估计。时不时地,调查员们会向随机选择的å
…
¬ä¼—们提问,来调查他们复制了多少有版权的音乐。被问到的å
…
¬æ°‘不被强制要求回答。但是由于复制并不犯法,也没有罚款,å›
 æ­¤å¤§å¤šæ•°äººéƒ½ä¼šå–œæ¬¢å‚与。乐迷会希望被选中,这æ 
·ä»–们就可以为喜爱的音乐团体的复制数量作出贡献。</p>
+
+<p>为了让调查更有效和广泛(因
此更准确),调查应该可以自动进行的。调查局可以邮寄读写记忆卡给选定的参与è€
…
,他们可以马上将这些卡与DAT机相连然后再把卡寄回。如果设计合理的话,调查局æ—
 æ³•çŸ¥é“是谁寄回了哪张卡,因此就无
法知道谁拷贝了什么,但是他们仍然可以得到准确的总数。</p>
+
+<h3>结论</h3>
+
+<p>唱片公司提出了一个通过向公众征税增加他们收å…
¥çš„很好的计划,但是这并不是版权制度的合法目的。通过注重版权的最终目的而不是过程手段,我们可以设计一个系统,它在支持音乐家的同时,也赋予å
…¬æ°‘按自己意愿复制音乐的完全自由。</p>
+
+<h3>你可以做些什么</h3>
+
+<p><em>[这一部分现在已经不再可行;已经太晚了,因
为DAT税已经在1992年被采纳&mdash;而且DAT录制机今天也过时了。不过,同æ
 
·çš„方法可以用于支持身处网络分享已经被立法的世界中的音乐家和å
…¶ä»–艺术家。]</em></p>
+
+<p>唱片å…
¬å¸çš„说客们正努力工作以通过他们的DAT税版本。少有组织起来的抗议,也少有å
…¬å¼€çš„辩论。他们的议案已经送到了参议院。</p>
+
+<p>这篇文章提供了一个唱片å…
¬å¸æ–¹æ¡ˆä¹‹å¤–的选择。为了让这个选择或å…
¶ä»–选择能够有机会,我们必须首先阻止匆忙采纳唱片å…
¬å¸çš„方案。为了帮助达到这个目的,请往以下地址写信:</p>
+
+<blockquote>
+<p>Congressman Barney Frank<br />
+437 Cherry St<br />
+West Newton, MA 02165</p>
+<p>Senator Metzenbaum<br />
+United States Senate<br />
+Washington, DC 20510</p>
+<p>House Subcommittee on Intellectual Property<br />
+House of Representatives<br />
+Washington, DC 20515</p>
+</blockquote>
+
+<p>促使国会否决唱片公司的方案,从而本文的方案或å…
¶ä»–选择能够被正当地考虑。写一封短信只需要花上几
分钟的时间,但是和å…
¶ä»–人的信联合在一起将会大有助益。</p>
+
+<p>如果你认识任何音乐家、作曲家或者歌曲作者
,请给他们本文的拷贝。相比于唱片å…
¬å¸çš„方案,很多音乐家更喜欢这个替代方案,而且他们有强烈的驱动来为他们自己的æ‹
…忧而行动。</p>
+
+<div class="translators-notes">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.-->
+ </div>
+</div>
+
+<!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.zh-cn.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<p>请将有å…
³è‡ªç”±è½¯ä»¶åŸºé‡‘会(FSF)&amp;GNU的一般性问题发送到<a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>。也可以通过<a
+href="/contact/">å…
¶ä»–联系方法</a>联系自由软件基金会(FSF)。请将无效链接,å…
¶ä»–错误或建议发送给<a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>。</p>
+
+<p>
+<!-- TRANSLATORS: Ignore the original text in this paragraph,
+        replace it with the translation of these two:
+
+        We work hard and do our best to provide accurate, good quality
+        translations.  However, we are not exempt from imperfection.
+        Please send your comments and general suggestions in this regard
+        to <a href="mailto:address@hidden";>
+
+        &lt;address@hidden&gt;</a>.</p>
+
+        <p>For information on coordinating and submitting translations of
+        our web pages, see <a
+        href="/server/standards/README.translations.html">Translations
+        README</a>. -->
+若您想翻译本文,请参看<a 
href="/server/standards/README.translations.html">翻译须知</a>。</p>
+</div>
+
+<p>Copyright &copy; 1992, 2010, 2014 Richard M. Stallman</p>
+
+<p>本页面使用<a rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/";>Creative Commons
+Attribution-NoDerivs 3.0 United States License</a>授权。</p>
+
+<!--#include virtual="/server/bottom-notes.zh-cn.html" -->
+<div class="translators-credits">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.-->
+<b>翻译</b>: 梁萌<br></br>
+<b>审校</b>: 刘昭宏 <a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a><br></br>
+<b>翻译团队</b>:<a rel="team"
+href="https://savannah.gnu.org/projects/www-zh-cn/";>&lt;CTT&gt;</a>,2018。</div>
+
+<p class="unprintable"><!-- timestamp start -->
+最后更新:
+
+$Date: 2018/01/24 12:33:20 $
+
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>

Index: philosophy/drdobbs-letter.zh-cn.html
===================================================================
RCS file: /web/www/www/philosophy/drdobbs-letter.zh-cn.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -b -r1.3 -r1.4
--- philosophy/drdobbs-letter.zh-cn.html        30 Dec 2011 05:18:27 -0000      
1.3
+++ philosophy/drdobbs-letter.zh-cn.html        24 Jan 2018 12:33:20 -0000      
1.4
@@ -1,138 +1,134 @@
-<!DOCTYPE html PUBLIC "-//IETF//DTD HTML 2.0//EN">
-<HTML>
-<HEAD>
-<TITLE>¸ø Dr. Dobb's ÆÚ¿¯±à¼­µÄ¹«¿ªÐÅ - GNU ¼Æ»­ - ×ÔÓÉÈí¼þ»ù½ð»á (FSF)</TITLE>
-<meta http-equiv="Content-Type" content="text/html; charset=gb2312">
-<LINK REV="made" HREF="mailto:address@hidden";>
-</HEAD>
-<BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#1F00FF" ALINK="#FF0000" 
VLINK="#9900DD">
-<H3>¸ø Dr. Dobb's ÆÚ¿¯±à¼­µÄ¹«¿ªÐÅ</H3>
-<A HREF="/graphics/atypinggnu.html"><IMG SRC="/graphics/gnu-type-sm.jpg"
-   ALT=" [image of the typing GNU] "
-   WIDTH="137" HEIGHT="114"></A>
-
-[
-<!-- Please keep this list alphabetical -->
-<!-- PLEASE UPDATE THE LIST AT THE BOTTOM (OR TOP) OF THE PAGE TOO! -->
-  <A HREF="/philosophy/drdobbs-letter.ca.html">¼ÓÌ©ÂÞÄáÑÇÓï</A>
-| <A HREF="/philosophy/drdobbs-letter.zh-cn.html">¼òÌåÖÐÎÄ</A>
-| <A HREF="/philosophy/drdobbs-letter.zh-tw.html">·±ÌåÖÐÎÄ</A>
-| <A HREF="/philosophy/drdobbs-letter.en.html">Ó¢Óï</A>
-| <A HREF="/philosophy/drdobbs-letter.pt.html">ÆÏÌÑÑÀÓï</A>
-<!-- | A HREF="boilerplate.LG.html" LANGUAGE /A  -->
-<!-- Please keep this list alphabetical -->
-<!-- PLEASE UPDATE THE LIST AT THE BOTTOM (OR TOP) OF THE PAGE TOO! -->
-]
-<P>
-<HR>
-<P>
-±à¼­ÏÈÉúÄúºÃ£¬
-<p>
-ÎÒÏëÄú²¢²»ÖªµÀÒÔ"¿ª·ÅÔ´Âë"½«ÎÒºÍ Tim O'Reilly 
ÏÈÉúÁªÏëÔÚÒ»Æð¶ÔÎÒ¶øÑÔ»áÊÇÒ»ÖÖÍÚ¿à¡£
-<p>
-Èç¹ûÃÀ¹úÒé»áµÄ·ÇÃÀ»î¶¯Î¯Ô±»áÖÊÎÊÎÒ£º¡¸ÄãÊDz»ÊÇ»òÔø¾­ÊÇ¿ª·ÅÔ´ÂëÔ˶¯µÄÖ§³ÖÕߣ¿¡¹
-ÎÒ¿ÉÒÔÓä¿ì¶ø×Ô¸ºµØ»Ø´ð£º¡¸²»¡£¡¹ÎÒÓÉ 1984 ÄêÆð¾ÍÒ»Ö±Ï×Éíì¶
-<EM>×ÔÓÉÈí¼þ</EM> Ô˶¯ -- ×ÔÓÉ×ÔÔÚ°ãµÄ×ÔÓÉ¡£(²Î¼û GNU ÐûÑÔ£¬
-¿¯ÔØì¶ 1985 Äê 9 ÔºŠDr. Dobb's ÆÚ¿¯)
-<p>
-¼òµ¥µØ˵×ÔÓÉÈí¼þµÄÒ⺭´ú±íÁË£¬ÄãÓÐѧϰÈí¼þÄÚ²¿ÔË×÷µÄ×ÔÓÉ£¬ÐÞ¸ÄÈí¼þµÄ×ÔÓÉ£¬
-ÖØÐÂÉ¢²¼Èí¼þµÄ×ÔÓÉ£¬ÒÔ¼°×ÔÐиÄÁ¼Èí¼þ²¢½«Æ乫¿ª·¢ÐеÄ×ÔÓÉ¡£ (ϸ½ÚÇë²ÎÕÕ <a
-href="http://www.gnu.org/philosophy/free-sw.html";>
-http://www.gnu.org/philosophy/free-sw.html</a>  )ÄãÓ¦¸ÃµÃµ½ÕâЩ×ÔÓÉ£¬
-ÿ¸öÈ˶¼Ó¦¸ÃµÃµ½ËûÃÇ¡£ÎªÁ˺´ÎÀÉÏÊöµÄÕâЩ×ÔÓÉ£¬ÎÒ׫дÁË GNU ¹«ÖÚÐí¿ÉÖ¤
-(GNU GPL)£¬ËüÕÐÖÂÁË <A
-HREF="gpl-american-way.html">΢ÈíÇ¿ÁҵķÞÅ­</A> £¬
-µ«Ò²³ÉΪÁË×ÔÓÉÈí¼þÔ˶¯ºËÐÄ˼ÏëµÄÖØÒª²¿·Ö¡£
-<p>
-ááÀ´£¬ÔÚ 1998 Äêʱ£¬ÓÐһЩÍÅÌåÒÔ"¿ª·ÅÔ´Âë"Õâ¸ö×ÖÑÛΪºÅÕÙ¿ªÊ¼ÔË×÷¡£
-ÔÚijЩ·½Ã棬ËûÃǵÄÈ·¶Ô×ÔÓÉÈí¼þÔ˶¯×ö³öÁËʵÖÊÉϵűÏ×£¬
-È»¶øËûÃÇÈ´ÊÇ Õ¾ÔÚºÍÎÒÃǷdz£²»Í¬µÄÁ¢³¡À´¿´´ýÊÂÇéµÄ¡£
-ËûÃÇ¿ÌÒâ»Ø±ÜÁËÎÒÃÇÔÚ×ÔÓÉÈí¼þÔ˶¯ÖÐËù½ÒÖîµÄ×ÔÓÉÓëÔ­ÔòµÄÒéÌ⣻
-ËûÃǽöÒÔ¶ÌÆÚʵ¼ÊÀûÒæµÄÀíÓÉÀ´ÎªËûÃǵÄËù×÷ËùΪ±ç»¤¡£
-<p>
-ËûÃǶÔì¶"¿ª·ÅÔ´Âë"µÄ¶¨Òå±ÈÆð×ÔÓÉÈí¼þÊǽÏΪ¹ãÒåµÄ£¬»»¾ä»°Ëµ£¬
-¿ª·ÅÔ´ÂëµÄ¶¨ÒåÊǽ«×ÔÓÉÈí¼þµÄ¹¤×÷°üº¬ÔÚÄڵġ£È»¶øÏñ΢ÈíÒ»Ñù°Ñ
-GNU GPL ˵³É"¿ª·ÅÔ´ÂëÐí¿ÉÖ¤"£¬È´¾ø¶ÔÊÇÑÏÖصÄÎó½â¡£
-GNU GPL ÊÇÀ´×Ôì¶×ÔÓÉÈí¼þÔ˶¯ÔúʵÕÜѧµÄ¾ßÌå±íÏÖ£¬
-¶ø·ÇÀ´×Ô춿ª·ÅÔ´ÂëÔ˶¯¡£¶øÎÒÒ²²»ÊÇ¿ª·ÅÔ´ÂëÔ˶¯µÄÓµ»¤Õߣ¬´ÓÀ´¶¼²»ÊÇ¡£
-<p>
-Ïà½Ï֮ϣ¬Tim O'Reilly ÏÈÉúÔòÊÇ¿ª·ÅÔ´ÂëÔ˶¯µÄÖØÒªÈËÎï¡£ÖÁÉÙ£¬
-ÎÒÃdz£Ìýµ½Ëû̸ÂÛ¿ª·ÅÔ´ÂëµÄÊÂÇ顣Ȼ¶ø£¬ÌýÆäÑÔÖ®ÍâÒà¹ÛÆäÐеĻ°£¬
-Äã»á·¢ÏÖ´ó¶àÊý O'Reilly ³ö°æµÄÊÖ²áÆäʵ²¢²»·ûºÏ¿ª·ÅÔ´ÂëµÄ±ê×¼£¬
-¸üåØÂÛ×ÔÓÉÁË£¬Ö»ÓÐÉÙÊýÒÔ̸ÂÛ×ÔÓÉΪÖ÷ÌâµÄÊé¼®ÀýÍâ¡£
-¼ÈʹÃæ¶Ô HUAC (Òë×¢£ºÃÀ¹ú¼«ÓÒÅɲÎÒéÔ±Âó¿¨ÎýÔÚ 1950 Äê´ú³ÉÁ¢µÄίԱ»á£¬
-ÒÔËàÇå¹²²úµ³Îª½å¿Ú£¬ÔÚµ±Ê±½øÐÐÁ˲»ÉÙÕþÖÎÆȺ¦µÄÐж¯¡£È«ÃûΪ£º
-House Un-American Activities Committee£¬ËõдHUAC¡£)£¬
-ËûÒ²ÄÜÇáÒ×µÄΪ×Ô¼º±ç½â -- ¡¸àÞ£¬Êǵģ¬ÎÒµÄȷ̸ÂÛ¹ý¿ª·ÅÔ´Â룬
-²»¹ýÊÂʵÉÏÎÒ²¢Ã»ÓÐͶÈëÆäÖС£¡¹
-<p>
-Èç¹û O'Reilly ÔÚδÀ´¿ªÊ¼··ÊÛ¡¸×ÔÓÉ¡¹µÄÊé¼®£¬
-Ëû½«ÄܳÉΪ×ÔÓÉÈí¼þÔ˶¯µÄʵÖÊÖ§³ÖÕß²»È»Ó¦¸ÃÖÁÉÙÒ²³ÆµÃÉÏÊÇ¿ª·ÅÔ´ÂëÔ˶¯µÄÖ§³ÖÕß¡£
-[2001 ÄêÍíÆÚ£¬O'Reilly ³ö°æÉçÒѾ­³ö°æÁËһЩ¶îÍâµÄ×ÔÓÉÊé¼®¡£
-ÎÒÃǷdz£¸Ð¼¤Æä¶Ô×ÔÓÉÈí¼þÉçÍŵűÏ×£¬Ò²Ï£Íû½«À´ÄÜ¿´µ½¸ü¶àÏñÕâÑùµÄÐж¯¡£]
-<p>
-Ëæ׎üÀ´Å·ÖÞ×ÔÓÉÈí¼þ»ù½ð»á( FSF-Europe )µÄ³ÉÁ¢£¬
-ÒÔ¼°¼´½«³ÉÁ¢µÄÓ¡¶È×ÔÓÉÈí¼þ»ù½ð»á(FSF-India)µÄµ½À´£¬
-×ÔÓÉÈí¼þÔ˶¯Õý²»¶ÏµÄ³É³¤×Â׳¡£Çë²»ÒªÔÙ°ÑÎÒÃǵÄÉçÍźÍÆäËûÔ˶¯Åª»ìÁË¡£
-<p>
-×£     °²ºÃ
-<p>
-<ul>
-×ÔÓÉÈí¼þ»ù½ð»á»á³¤£¬Àí²éµÂ£®Ë¹¶à¶ûÂü ¾´Æô
-</ul>
-<p>
-<HR>
-
-[
-<!-- Please keep this list alphabetical -->
-<!-- PLEASE UPDATE THE LIST AT THE BOTTOM (OR TOP) OF THE PAGE TOO! -->
-  <A HREF="/philosophy/drdobbs-letter.ca.html">¼ÓÌ©ÂÞÄáÑÇÓï</A>
-| <A HREF="/philosophy/drdobbs-letter.zh-cn.html">¼òÌåÖÐÎÄ</A>
-| <A HREF="/philosophy/drdobbs-letter.zh-tw.html">·±ÌåÖÐÎÄ</A>
-| <A HREF="/philosophy/drdobbs-letter.en.html">Ó¢Óï</A>
-| <A HREF="/philosophy/drdobbs-letter.pt.html">ÆÏÌÑÑÀÓï</A>
-<!-- | A HREF="boilerplate.LG.html" LANGUAGE /A  -->
-<!-- Please keep this list alphabetical -->
-<!-- PLEASE UPDATE THE LIST AT THE BOTTOM (OR TOP) OF THE PAGE TOO! -->
-]
-
-<P>
-·µ»Ø <a href="/home.html">GNU Ê×Ò³</a>¡£
-
-<P>
-Ç뽫ÓÐ¹Ø ×ÔÓÉÈí¼þ»ù½ð»áÒÔ¼° GNU µÄ ²éѯºÍÎÊÌâ ·¢Ë͵½
-<a href="mailto:address@hidden";><em>address@hidden</em></a>¡£
-<br>
-Ò²¿ÉÒÔͨ¹ý <a href="/home.html#ContactInfo">ÆäËû·½·¨</a> ÁªÏµ×ÔÓÉÈí¼þ»ù½ð»á¡£
-
-<P>
-Ç뽫ÓйØÍøÒ³µÄÒâ¼û·¢Ë͵½
-<a href="mailto:address@hidden";><em>address@hidden</em></a>¡¢
-
-<br>
-ÆäËûÎÊÌâÔò·¢Ë͵½ <a href="mailto:address@hidden";><em>address@hidden</em></a>¡£
-
-<P>
-Copyright (C) 2000 Free Software Foundation, Inc.,
-51 Franklin St, Fifth Floor, Boston, MA  02110,  USA
-
-<P>±¾ÎÄÔÊÐíÔÚ²»±ä¸üÎļþÄÚÈݵÄÇ°ÌáÏ¿¯µÇÔÚÈκÎÐÍ̬µÄýÌåÖУ¬µ«Ðè±£Áô´Ë×¢¼Ç¡£
-
-<P>
-ÖÐÎÄ·­Ò룺»Æ ÐûÁú
-<BR>
-·­ÒëУÕý£ºÂí ѩƼ
-<BR>
-Ç뽫Óйط­ÒëµÄÎÊÌâË͵½
-<A HREF="http://savannah.gnu.org/projects/chinese/";>GNU ÖÐÒëС×é</A>¡£
-
-<P>
-Updated:
-<!-- hhmts start -->
-$Date: 2011/12/30 05:18:27 $ $Author: ineiev $
-<!-- hhmts end -->
-<HR>
-</BODY>
-</HTML>
+<!--#set var="ENGLISH_PAGE" value="/philosophy/drdobbs-letter.en.html" -->
 
+<!--#include virtual="/server/header.zh-cn.html" -->
+<!-- Parent-Version: 1.77 -->
 
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>致Dr. Dobb's期刊编辑的公开信 - GNU工程 - 
自由软件基金会</title>
+
+<!--#include virtual="/philosophy/po/drdobbs-letter.translist" -->
+<!--#include virtual="/server/banner.zh-cn.html" -->
+<h2>致Dr. Dobb's期刊编辑的公开信</h2>
+
+<p>
+亲爱的编辑,
+</p>
+<p>
+我确信您没有意识到以&ldquo;开源&rdquo;把我和Tim O'Reillyå…
ˆç”Ÿè”系在一起是多么的讽刺。
+</p>
+<p>
+如果美国议会的非美活动委员会询问我:&ldquo;你
现在是不是或曾经是开源运动的支持者
?&rdquo;我可以愉快而自豪地回答不。我从1984年起就一直献身于<em>自由软件运动</em>&mdash;自由自在的自由。(参见GNU宣言,刊载於1985年9月号Dr.
+Dobb's 期刊。)
+</p>
+<p>
+自由软件意味着,简单地说,你有学习
软件如何工作的自由、修改软件的自由、重新发布软件的自由以及发布修改后软件的自由。(细节请参看<a
+href="/philosophy/free-sw.html">http://www.gnu.org/philosophy/free-sw.html</a>。)ä½
 
应该得到这些自由,每个人都应该得到它们。为了捍卫所有用户的这些自由,以自由软件运动的精神,我撰写了GNU通用å
…¬ä¼—许可证(GNU
+GPL),它招致了微软最强烈的忿怒。
+</p>
+<p>
+多年以后,在1998年,另一个团体以&ldquo;开源&rdquo;这个字眼开始运作。实é™
…
上,他们对自由软件社区做出了贡献,然而他们的立场非常不同。他们刻意回避了我们在自由软件运动中所提出的自由与原则问题;他们ä»
…以短期实际利益的理由来为他们的所作所为辩护。
+</p>
+<p>
+他们对&ldquo;开源&rdquo;的定义比自由软件更为广义,因此包
含了我的工作。然而像微软一样把GNU
+GPL说成是一个&ldquo;开源许可证&rdquo;,却不仅仅
只是误导。GNU
+GPL包
含着自由软件运动的坚定哲学;它并不是来自于开源运动。我不是开源运动的拥护è€
…,从来都不是。
+</p>
+<p>
+相较之下,Tim
+O'Reilly则是开源运动的指导性人物,至少,常听到他谈论开源。然而,听å
…¶è¨€ä¹‹å¤–亦观其行的话,你会发现大多数O'Reilly联合å…
¬å¸å‡ºç‰ˆçš„手册并不符合开源的æ 
‡å‡†ï¼Œæ›´é‘论自由了。少数以自由为主题的书籍是例外。既使面对<abbr
+title="House Un-American Activities Committee">HUAC</abbr><sup><a
+href="#TransNote1">1</a></sup>,他也能轻易为自己辩解&mdash;&ldquo;是的,我的确谈论过开源,不过我并没有真正投å
…¥å…¶ä¸­ã€‚&rdquo;
+</p>
+<p>
+如果O'Reilly在未来开始销售自由如自由软件般的书籍,他将能成为自由软件运动的真正支持è€
…,或者至少也称得上是开源运动的支持者
。[2001年晚期,O'Reilly联合出版社已经出版了一些额外的自由书籍。我们非常感激å
…¶å¯¹è‡ªç”±è½¯ä»¶ç¤¾åŒºçš„贡献,我们期望能看到更多像这æ 
·çš„行动。]
+</p>
+<p>
+随着近来欧洲自由软件基金会(FSF-Europe)的成立,以及即将成立的印度自由软件基金会(FSF-India)的到来,自由软件运动正不断地茁壮成长。请不要在我们的社区把自由软件运动和å
…¶ä»–运动弄混了。
+</p>
+<p>
+真诚的,
+</p>
+<p>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Richard Stallman,自由软件基金会主席
+</p>
+
+<div class="translators-notes">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.-->
+<h3>译注</h3>
+<ol>
+<li id="TransNote1">HUAC,全名为:House Un-American Activities
+Committee,美国极右派参议员麦卡锡在1950年代成立的委员会,以肃æ¸
…共产党为藉口,在当时进行了不少政治迫害的行动。</li>
+</ol></div>
+</div>
+
+<!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.zh-cn.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<p>请将有å…
³è‡ªç”±è½¯ä»¶åŸºé‡‘会(FSF)&amp;GNU的一般性问题发送到<a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>。也可以通过<a
+href="/contact/">å…
¶ä»–联系方法</a>联系自由软件基金会(FSF)。请将无效链接,å…
¶ä»–错误或建议发送给<a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>。</p>
+
+<p>
+<!-- TRANSLATORS: Ignore the original text in this paragraph,
+        replace it with the translation of these two:
+
+        We work hard and do our best to provide accurate, good quality
+        translations.  However, we are not exempt from imperfection.
+        Please send your comments and general suggestions in this regard
+        to <a href="mailto:address@hidden";>
+
+        &lt;address@hidden&gt;</a>.</p>
+
+        <p>For information on coordinating and submitting translations of
+        our web pages, see <a
+        href="/server/standards/README.translations.html">Translations
+        README</a>. -->
+若您想翻译本文,请参看<a 
href="/server/standards/README.translations.html">翻译须知</a>。</p>
+</div>
+
+<!-- Regarding copyright, in general, standalone pages (as opposed to
+     files generated as part of manuals) on the GNU web server should
+     be under CC BY-ND 3.0 US.  Please do NOT change or remove this
+     without talking with the webmasters or licensing team first.
+     Please make sure the copyright date is consistent with the
+     document.  For web pages, it is ok to list just the latest year the
+     document was modified, or published.
+     
+     If you wish to list earlier years, that is ok too.
+     Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
+     years, as long as each year in the range is in fact a copyrightable
+     year, i.e., a year in which the document was published (including
+     being publicly visible on the web or in a revision control system).
+     
+     There is more detail about copyright years in the GNU Maintainers
+     Information document, www.gnu.org/prep/maintain. -->
+<p>Copyright &copy; 2000, 2007, 2014 Free Software Foundation, Inc.</p>
+
+<p>本页面使用<a rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/";>Creative Commons
+Attribution-NoDerivs 3.0 United States License</a>授权。</p>
+
+<!--#include virtual="/server/bottom-notes.zh-cn.html" -->
+<div class="translators-credits">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.-->
+<b>翻译</b>: 黄宣龙<br></br>
+<b>审校</b>: 马雪萍<br></br>
+<b>翻译团队</b>:<a rel="team"
+href="https://savannah.gnu.org/projects/www-zh-cn/";>&lt;CTT&gt;</a>,2018。</div>
+
+<p class="unprintable"><!-- timestamp start -->
+最后更新:
+
+$Date: 2018/01/24 12:33:20 $
+
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>

Index: philosophy/university.pt-br.html
===================================================================
RCS file: /web/www/www/philosophy/university.pt-br.html,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -b -r1.5 -r1.6
--- philosophy/university.pt-br.html    21 Jan 2015 14:19:24 -0000      1.5
+++ philosophy/university.pt-br.html    24 Jan 2018 12:33:20 -0000      1.6
@@ -1,9 +1,3 @@
-<!--#set var="PO_FILE"
- value='<a href="/philosophy/po/university.pt-br.po">
- http://www.gnu.org/philosophy/po/university.pt-br.po</a>'
- --><!--#set var="ORIGINAL_FILE" value="/philosophy/university.html"
- --><!--#set var="DIFF_FILE" value=""
- --><!--#set var="OUTDATED_SINCE" value="2002-04-13" -->
 <!--#set var="ENGLISH_PAGE" value="/philosophy/university.en.html" -->
 
 <!--#include virtual="/server/header.pt-br.html" -->
@@ -15,126 +9,131 @@
 
 <!--#include virtual="/philosophy/po/university.translist" -->
 <!--#include virtual="/server/banner.pt-br.html" -->
-<!--#include virtual="/server/outdated.pt-br.html" -->
 <h2>Lance Software Livre Caso Você Trabalhe em uma Universidade</h2>
 
 <p>
-Nós, do movimento pelo software livre, acreditamos que os usuários de
-computador devem ter a liberdade de modificar e redistribuir os programas
-que eles usam. Na língua inglesa, “livre” <cite>(free)</cite>, significa
-“liberdade”, mas também “gratuito”. Essa particularidade, leva muitas
-pessoas à compreenderem erradamente os ideais de nosso movimento. O termo
-“livre” <cite>(free)</cite> para nós se refere à liberdade. Isso implica 
que
-os usuários tem a liberdade de executar, modificar e redistribuir os
-programas. O software livre contribui para o aperfeiçoamento do conhecimento
-humano, enquanto os programas proprietários não. As Universidades deveriam
-encorajar o desenvolvimento de software livre em consideração dos avanço do
-conhecimento humano, da mesma maneira que eles encorajam seus cientistas e
-outros catedráticos a publicar seus trabalhos.</p>
-
-<p>
-Porém muitos administradores de universidades tem uma atitudades
-conservadora em relação ao software (e também sobre a ciência). Eles veem 
os
-programas como uma oportunidade para lucro, não como uma oportunidade para
-contribuir para o conhecimento humano. Os desenvolvedores de software livre
-vem lidando com essa situação nos últimos 20 anos.</p>
-
-<p>
-Em 1984, quando eu iniciei o desenvolvimento do <a
-href="/gnu/thegnuproject.html">sistema operacional GNU</a>, minha primeira
-decisão foi pedir demissão de meu trabalho no MIT. Fiz isso para que a
-licença de desenvolvimento do MIT não interferisse no lançamento do GNU como
-um software livre. Eu havia planejado uma estratégia para licenciar os
-programas GNU de mode que garantisse que todas as versões modificadas também
-fossem software livre. Essa estratégia foi formalizada na <a
-href="/licenses/gpl.html">Licença Publica Geral GNU</a> (GNU GPL). Ou seja,
-saí do MIT pois não queria que os administradores do MIT pudessem me proibir
-de usar a GNU GPL.</p>
-
-<p>
-Durante esses anos, funcionários de várias universidades tem vindo até a
-Fundação Software Livre para pedir conselhos de como evitar o controle dos
-administradores que veem programas apenas como algo para se vender. Um
-método muito eficaz, aplicável também para projetos já em desenvolvimento, 
é
-basear seu trabalho em um programa já existente e lançado sob a GNU
-GPL. Então, você pode falar para o administrador: “Nós não temos 
permissão
-para lançar uma versão modificada à menos que ela use a GNU GPL. Qualquer
-outra licença estaremos infrigindo o copyright.” Depois de ver os cifrões 
de
-dólar desvanecer na frente dos seus olhos, eles em geral concordam em lançar
-como um software livre.</p>
-
-<p>
-Você pode também pedir ajuda ao financiador do projeto. Quando um grupo da
-NYU (New York University) desenvolveu o GNU Ada Compiler, com o
-financiamento da Força Aérea Americana, o contrato estabelecia que possíveis
-ganhos financeiros do projeto deveriam ser doados para a Fundação Software
-Livre. Primeiro estabeleçeram o acordo com o financiador, depois comunicaram
-aos administradores da universidade. Então, eles preferiram ter um contrato
-para desenvolver software livre do que não ter nenhum contrato.</p>
-
-<p>
-Seja lá como for, aborde o assunto muito cedo — bem antes que o programa já
-esteja pronto. Enquanto o programa ainda estiver em fase desenvolvimento
-eles vão precisar de você. Diga aos administradores que você irá terminar o
-programa, tornar ele usável, apenas se eles concordarem em tornar o programa
-um software livre. Caso contrário, você irá desenvolvê-lo até o ponto de
-poder escrever um artigo científico sobre ele e nunca irá concluir uma
-versão boa o suficiente para ser lançado comercialmente. Quando os
-administradores perceberem que suas escolhas são ter um programa livre com
-os créditos para a universidade ou nada, eles irão escolher a primeira
-opção.</p>
-
-<p>
-Porém nem todas as universidades tem políticas restritivas. A Universidade
-do Texas, tem uma política que determina que, por default, todos os
-programas desenvolvidos lá sejam licenciados com a GNU GPL. O mesmo aconteçe
-na Univates, no Brasil, e no Instituro Internacional de Tecnologia da
-Informação, em Hyderabad, Índia. Tendo o apoio do corpo docente, você terá
-mais chance de propor um apoio institucional da universidade. Apresente o
-assunto como um princípio: a universidade tem como missão contribuir para o
-avanço do conhecimento humano ou sua missão é meramente continuar aí?</p>
-
-<p>
-Para qualquer estratégia que você tiver será preciso primeiramente ter a
-determinação de adotar uma perspectiva ética, como nós fazemos no Movimento
-Software Livre. Tratar o público eticamente, os programas devem ser livres
-para todas as pessoas.</p>
-
-<p>
-Muitos desenvolvedores de software livre defendem sua posição com argumentos
-de salientam a praticidade. Dizem que permitir outros desenvolvedores de
-compartilhar mudanças no programa é um método de tornar os programas mais
-poderosos e confiáveis. Se esses valores orientam sua motivação de
-desenvolver software livre, tudo bem, agradecemos sua contribuição. Porém,
-acreditamos que esses valores não são suficientes para manter sua posição
-firme quando os administradores da universidade tentarem o persuadir a
-tornar seu programa um software proprietário. </p>
-
-<p>
-Por exemplo, eles pode argumentar que “nós podemos torná-los ainda mais
-poderosos e confiáveis com o dinheiro que vamos ganhar com ele”. É difícil
-saber se isso acontecerá ou não verdade, mas também não é fácil provar o
-contrário. Eles podem inclusive sugerir uma licença que permita cópias
-grátis para uso acadêmico. Com isso ele dirá que você terá a cooperação 
da
-comunidade acadêmica, que é a que você realmente precisa. </p>
-
-<p>
-Se você partir de valores “pragmáticos” será difícil dar uma boa 
razão para
-rejeitar essas propostas, mas você poderá fazer isso se basear sua 
motivação
-em valores éticos e políticos. De que vale desenvolver um programa poderoso
-e conviável sacrificando a liberdade dos usuários? A liberdade não tem a
-mesma importância fora da comunidade acadêmica? As respostas são óbvias se 
a
-liberdade e a comunidade forem os seus objetivos. O software livre respeita
-a liberdade dos usuários, enquanto softwares proprietários a negam. </p>
+Nós, do movimento pelo software livre (“free software movement”),
+acreditamos que os usuários de computador devem ter a liberdade de modificar
+e redistribuir os softwares que eles usam. O “free” de “free software”
+refere-se a liberdade: isso significa que os usuários têm a liberdade para
+executar, modificar e redistribuir os softwares. O software livre contribui
+para o aperfeiçoamento do conhecimento humano, ao contrário dos softwares
+não livres. As universidades devem, portanto, encorajar o desenvolvimento de
+software livre para o bem dos avanços do conhecimento humano, da mesma
+maneira que eles encorajam seus cientistas e outros estudiosos a publicar
+seus trabalhos.</p>
+
+<p>
+Porém muitos administradores de universidades têm uma atitude conservadora
+em relação ao software (e também em relação à ciência). Eles veem os
+programas como uma oportunidade para obter lucro, não como uma oportunidade
+para contribuir para o conhecimento humano. Os desenvolvedores de software
+livre vêm lidando com essa situação nos últimos 20 anos.</p>
+
+<p>
+Quando eu iniciei o desenvolvimento do <a
+href="/gnu/thegnuproject.html">sistema operacional GNU</a>, em 1984, minha
+primeira decisão foi pedir demissão de meu trabalho no MIT. Fiz isso
+especificamente para que o escritório de licenciamento do MIT não
+interferisse no lançamento do GNU como um software livre. Eu havia planejado
+uma estratégia para licenciar os programas no GNU de modo que garantisse que
+todas as versões modificadas também fossem software livre &ndash; uma
+abordagem que se formalizou como a <a href="/licenses/gpl.html">Licença
+Pública Geral GNU</a> (GNU GPL) &ndash; e eu não queria ter que implorar
+para a administração do MIT para me deixar usá-la.</p>
+
+<p>
+Ao longo dos anos, funcionários de várias universidades têm vindo à Free
+Software Foundation para pedir conselhos de como evitar o controle dos
+administradores que veem software apenas como algo para se vender. Um método
+muito eficaz, aplicável também para projetos já em desenvolvimento, é 
basear
+seu trabalho em um programa já existente e lançado sob a GNU GPL. Então,
+você pode falar para os administradores: “Nós não temos permissão para
+lançar uma versão modificada a menos que ela use a GNU GPL &ndash; qualquer
+outra licença estaríamos infringindo o copyright”. Depois de ver os 
cifrões
+de dólar desvanecerem na frente dos seus olhos, eles geralmente concordam em
+lançar como um software livre.</p>
+
+<p>
+Você também pode pedir ajuda ao financiador do seu projeto. Quando um grupo
+da NYU (Universidade de Nova Iorque) desenvolveu o GNU Ada Compiler, com o
+financiamento da Força Aérea Americana, o contrato estabelecia que o código
+resultante devia ser doado à Free Software Foundation. Primeiro estabeleça o
+acordo com o financiador, depois mostre à administração da universidade que
+isso não está aberto a negociação. Eles prefeririam ter um contrato para
+desenvolver software livre do que não ter nenhum contrato, então eles muito
+provavelmente aceitarão.</p>
+
+<p>
+Seja lá como for, aborde o assunto logo cedo &ndash; bem antes do programa
+estar quase pronto. Neste ponto, a universidade ainda vai precisar de você,
+então você pode fazer jogo duro: diga à administração que você irá 
terminar
+o programa, e torná-lo usável, apenas se eles concordarem em torná-lo um
+software livre (e concordar com sua escolha de licença de software
+livre). Caso contrário, você irá desenvolvê-lo até o ponto de poder 
escrever
+um artigo científico sobre ele e nunca irá concluir uma versão boa o
+suficiente para ser lançado comercialmente. Quando os administradores
+perceberem que suas escolhas são ter um software livre com os créditos para
+a universidade ou nada, eles irão escolher a primeira opção.</p>
+<p>
+A FSF algumas vezes consegue persuadir sua universidade a aceitar a Licença
+Pública Geral GNU ou aceitar a GPL versão 3. Se você não conseguir fazer
+sozinho, por favor nos dê uma chance de ajudá-lo. Envie um e-mail para
address@hidden e coloque “urgent” no campo de assunto.</p>
+
+<p>
+Nem todas as universidades têm políticas restritivas. A Universidade do
+Texas tem uma política que facilita o lançamento de softwares desenvolvidos
+lá como software livre sob a Licença Pública Geral GNU. A Univates, no
+Brasil, e o Instituto Internacional de Tecnologia da Informação, em
+Hyderabad, Índia, têm políticas em favor do lançamento de software sob a
+GPL. Tendo o apoio do corpo docente, você terá mais chance de instituir tal
+política na sua universidade. Apresente a questão como um princípio: a
+universidade tem como missão contribuir para o avanço do conhecimento humano
+ou seu único propósito é perpetuar a si própria?</p>
+
+<p>
+Na persuasão da universidade, ajuda abordar a questão com determinação e
+baseado em uma perspectiva ética, como nós fazemos no movimento software
+livre. Para tratar o público eticamente, os software devem ser livres para
+todas as pessoas.</p>
+
+<p>
+Muitos desenvolvedores de software livre apresentam argumentos estritamente
+práticos para fazê-lo: eles defendem a permissão de outros compartilharem e
+alterarem software como uma forma de torná-lo mais poderoso e confiável. Se
+esses valores lhe motivarem a desenvolver software livre, tudo bem,
+agradecemos sua contribuição. Mas esses valores não são suficientes para
+manter sua posição firme quando os administradores da universidade lhe
+pressionarem ou persuadirem a tornar seu programa não livre.</p>
+
+<p>
+Por exemplo, eles podem argumentar que “nós podemos torná-lo ainda mais
+poderoso e confiável com o dinheiro que vamos ganhar com ele”. Essa 
alegação
+pode ou não se tornar realidade no final, mas é difícil provar o contrário
+antecipadamente. Eles podem inclusive sugerir uma licença para oferecer
+cópias “grátis, somente para uso acadêmico”, o que diria ao público 
geral
+que eles não merecem liberdade e argumentaria que você obteria a cooperação
+da academia, o que é tudo (segundo eles) que você precisa.</p>
+
+<p>
+Se você partir de valores de apenas conveniência, é difícil dar uma boa
+razão para rejeitar essas propostas, mas você poderá fazer isso com
+facilidade se basear sua motivação em valores éticos e políticos. De que
+vale desenvolver um programa poderoso e confiável aos custos da liberdade
+dos usuários? A liberdade não deveria se aplicar fora da academia assim como
+dentro dela? As respostas são óbvias se a liberdade e a comunidade forem os
+seus objetivos. O software livre respeita a liberdade dos usuários, enquanto
+softwares não livres a negam.</p>
 
 <p>
 Nada fortalece mais sua posição do que saber que a liberdade de sua
-comunidade depende, em alguma instância, de você. </p>
+comunidade depende, em alguma instância, de você.</p>
 
 <hr />
 <blockquote id="fsfs"><p class="big">Este ensaio foi publicado em <a
-href="http://shop.fsf.org/product/free-software-free-society/";><cite>Software
-Livre, Sociedade Livre: Artigos selecionados de Richard
+href="http://shop.fsf.org/product/free-software-free-society/";><cite>Free
+Software, Free Society: The Selected Essays of Richard
 M. Stallman</cite></a>.</p></blockquote>
 
 <div class="translators-notes">
@@ -189,13 +188,15 @@
 <div class="translators-credits">
 
 <!--TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.-->
-Traduzida por: Cláudio Machado <a
-href="mailto:address@hidden";>&lt;address@hidden&gt;</a></div>
+Traduzido por: Cláudio Machado <a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>,
+2002. Rafael Fontenelle <a href="mailto:address@hidden";>
+&lt;address@hidden&gt;</a>, 2018.</div>
 
 <p class="unprintable"><!-- timestamp start -->
 Última atualização: 
 
-$Date: 2015/01/21 14:19:24 $
+$Date: 2018/01/24 12:33:20 $
 
 <!-- timestamp end -->
 </p>

Index: philosophy/po/copyright-and-globalization.pt-br-en.html
===================================================================
RCS file: /web/www/www/philosophy/po/copyright-and-globalization.pt-br-en.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- philosophy/po/copyright-and-globalization.pt-br-en.html     21 Jan 2015 
14:29:38 -0000      1.1
+++ philosophy/po/copyright-and-globalization.pt-br-en.html     24 Jan 2018 
12:33:20 -0000      1.2
@@ -1036,7 +1036,7 @@
 essay in which I want to use still images, even from films, they are
 much harder to get permission to use, and the prices charged to use
 those still images are much higher &mdash; even when I make arguments
-about intellectual inquiry and the the legal category of &ldquo;fair
+about intellectual inquiry and the legal category of &ldquo;fair
 use.&rdquo; So I think, in this moment of extended transformation, the
 longer-term prospects may, in fact, not be as disturbing as what's
 happening in the shorter term.  But in any case, we need to understand
@@ -1288,7 +1288,7 @@
 
 <!-- Regarding copyright, in general, standalone pages (as opposed to
      files generated as part of manuals) on the GNU web server should
-     be under CC BY-ND 3.0 US.  Please do NOT change or remove this
+     be under CC BY-ND 4.0.  Please do NOT change or remove this
      without talking with the webmasters or licensing team first.
      Please make sure the copyright date is consistent with the
      document.  For web pages, it is ok to list just the latest year the
@@ -1303,17 +1303,17 @@
      There is more detail about copyright years in the GNU Maintainers
      Information document, www.gnu.org/prep/maintain. -->
 
-<p>Copyright &copy; 2001, 2007, 2008, 2012, 2014 Free Software Foundation, 
Inc.</p>
+<p>Copyright &copy; 2001, 2007, 2008, 2012, 2014, 2018 Free Software 
Foundation, Inc.</p>
 
 <p>This page is licensed under a <a rel="license"
-href="http://creativecommons.org/licenses/by-nd/3.0/us/";>Creative
-Commons Attribution-NoDerivs 3.0 United States License</a>.</p>
+href="http://creativecommons.org/licenses/by-nd/4.0/";>Creative
+Commons Attribution-NoDerivatives 4.0 International License</a>.</p>
 
 <!--#include virtual="/server/bottom-notes.html" -->
 
 <p class="unprintable">Updated:
 <!-- timestamp start -->
-$Date: 2015/01/21 14:29:38 $
+$Date: 2018/01/24 12:33:20 $
 <!-- timestamp end -->
 </p>
 </div>

Index: philosophy/po/copyright-and-globalization.pt-br.po
===================================================================
RCS file: /web/www/www/philosophy/po/copyright-and-globalization.pt-br.po,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -b -r1.5 -r1.6
--- philosophy/po/copyright-and-globalization.pt-br.po  24 Jan 2018 08:42:44 
-0000      1.5
+++ philosophy/po/copyright-and-globalization.pt-br.po  24 Jan 2018 12:33:20 
-0000      1.6
@@ -17,7 +17,6 @@
 "Content-Transfer-Encoding: 8bit\n"
 "Plural-Forms: nplurals=2; plural=(n > 1);\n"
 "X-Generator: Virtaal 1.0.0-beta1\n"
-"X-Outdated-Since: 2018-01-22 19:25+0000\n"
 
 #. type: Content of: <title>
 msgid ""
@@ -2720,8 +2719,8 @@
 "creativecommons.org/licenses/by-nd/4.0/\">Creative Commons Attribution-"
 "NoDerivatives 4.0 International License</a>."
 msgstr ""
-"Esta página está licenciada sob uma licença <a rel=\"license\" href=\""
-"http://creativecommons.org/licenses/by-nd/4.0/deed.pt_BR\";>Creative Commons "
+"Esta página está licenciada sob uma licença <a rel=\"license\" 
href=\"http://";
+"creativecommons.org/licenses/by-nd/4.0/deed.pt_BR\">Creative Commons "
 "Atribuição-SemDerivações 4.0 Internacional</a>."
 
 #. TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.

Index: philosophy/po/drdobbs-letter.zh-cn.po
===================================================================
RCS file: /web/www/www/philosophy/po/drdobbs-letter.zh-cn.po,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- philosophy/po/drdobbs-letter.zh-cn.po       24 Jan 2018 09:54:38 -0000      
1.1
+++ philosophy/po/drdobbs-letter.zh-cn.po       24 Jan 2018 12:33:21 -0000      
1.2
@@ -14,7 +14,7 @@
 "Language: zh_CN\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit"
+"Content-Transfer-Encoding: 8bit\n"
 
 #. type: Content of: <title>
 msgid ""

Index: philosophy/po/university.pt-br.po
===================================================================
RCS file: /web/www/www/philosophy/po/university.pt-br.po,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -b -r1.3 -r1.4
--- philosophy/po/university.pt-br.po   24 Jan 2018 08:42:59 -0000      1.3
+++ philosophy/po/university.pt-br.po   24 Jan 2018 12:33:21 -0000      1.4
@@ -18,7 +18,6 @@
 "Content-Transfer-Encoding: 8bit\n"
 "Plural-Forms: nplurals=2; plural=(n > 1);\n"
 "X-Generator: Virtaal 1.0.0-beta1\n"
-"Outdated-Since: 2002-04-13 18:42+0000\n"
 
 #. type: Content of: <title>
 msgid ""
@@ -75,9 +74,9 @@
 "interfere with releasing GNU as free software.  I had planned an approach "
 "for licensing the programs in GNU that would ensure that all modified "
 "versions must be free software as well&mdash;an approach that developed into "
-"the <a href=\"/licenses/gpl.html\">GNU General Public License</a> (GNU "
-"GPL)&mdash;and I did not want to have to beg the MIT administration to let "
-"me use it."
+"the <a href=\"/licenses/gpl.html\">GNU General Public License</a> (GNU GPL)"
+"&mdash;and I did not want to have to beg the MIT administration to let me "
+"use it."
 msgstr ""
 "Quando eu iniciei o desenvolvimento do <a href=\"/gnu/thegnuproject.html"
 "\">sistema operacional GNU</a>, em 1984, minha primeira decisão foi pedir "
@@ -279,6 +278,7 @@
 msgid "*GNUN-SLOT: TRANSLATOR'S NOTES*"
 msgstr " "
 
+# type: Content of: <div><p>
 #. type: Content of: <div><div><p>
 msgid ""
 "Please send general FSF &amp; GNU inquiries to <a 
href=\"mailto:address@hidden";
@@ -341,6 +341,7 @@
 "\">&lt;address@hidden&gt;</a>, 2002. Rafael Fontenelle <a href="
 "\"mailto:address@hidden";> &lt;address@hidden&gt;</a>, 2018."
 
+# type: Content of: <div><p>
 #.  timestamp start 
 #. type: Content of: <div><p>
 msgid "Updated:"

Index: server/po/irc-rules.pt-br.po
===================================================================
RCS file: /web/www/www/server/po/irc-rules.pt-br.po,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- server/po/irc-rules.pt-br.po        24 Jan 2018 08:43:40 -0000      1.1
+++ server/po/irc-rules.pt-br.po        24 Jan 2018 12:33:21 -0000      1.2
@@ -18,7 +18,8 @@
 "X-Generator: Virtaal 1.0.0-beta1\n"
 
 #. type: Content of: <title>
-msgid "GNU and FSF related IRC channels - GNU Project - Free Software 
Foundation"
+msgid ""
+"GNU and FSF related IRC channels - GNU Project - Free Software Foundation"
 msgstr ""
 "Canais IRC relacionados ao GNU e à FSF - Projeto GNU - Free Software "
 "Foundation"
@@ -51,14 +52,14 @@
 "comunidade de software livre. O objetivo dos canais IRC do GNU e da FSF é "
 "fornecer um lugar para a comunidade discutir coisas e falar sobre software "
 "livre e outras questões que afetam os direitos dos usuários de computador, "
-"como a Gestão Digital de Restrições (<cite>Digital Restrictions "
-"Management</cite>)."
+"como a Gestão Digital de Restrições (<cite>Digital Restrictions 
Management</"
+"cite>)."
 
 #. type: Content of: <p>
 msgid ""
 "<b>If you have problems with any of these channels, with trolls or abusive "
-"members, please email us at: <a "
-"href=\"mailto:address@hidden";>address@hidden</a>.</b>"
+"members, please email us at: <a href=\"mailto:address@hidden";
+"\">address@hidden</a>.</b>"
 msgstr ""
 "<b>Se você tiver problemas com qualquer um desses canais, com trolls ou "
 "membros abusivos, por favor nos contate em: <a href=\"mailto:address@hidden";
@@ -112,12 +113,12 @@
 #. type: Content of: <ul><li>
 msgid ""
 "<a href=\"irc://irc.gnu.org/libreplanet\">#libreplanet</a> &mdash; "
-"Discussion of the LibrePlanet website, and <a "
-"href=\"http://www.fsf.org/conference/\";>conference</a>."
+"Discussion of the LibrePlanet website, and <a href=\"http://www.fsf.org/";
+"conference/\">conference</a>."
 msgstr ""
 "<a href=\"irc://irc.gnu.org/libreplanet\">#libreplanet</a> &mdash; Discussão 
"
-"sobre o site do LibrePlanet e <a href=\"http://www.fsf.org/conference/\"";
-">conferência</a>."
+"sobre o site do LibrePlanet e <a href=\"http://www.fsf.org/conference/";
+"\">conferência</a>."
 
 #. type: Content of: <ul><li>
 msgid ""
@@ -145,8 +146,8 @@
 
 #. type: Content of: <ul><li>
 msgid ""
-"<a href=\"irc://irc.oftc.net/savannah\">#savannah</a> &mdash; <a "
-"href=\"http://savannah.gnu.org/\";>Savannah.GNU.org</a> hangout channel"
+"<a href=\"irc://irc.oftc.net/savannah\">#savannah</a> &mdash; <a href="
+"\"http://savannah.gnu.org/\";>Savannah.GNU.org</a> hangout channel"
 msgstr ""
 "<a href=\"irc://irc.oftc.net/savannah\">#savannah</a> &mdash; canal para "
 "bate-papo do <a href=\"http://savannah.gnu.org/\";>Savannah.GNU.org</a>"
@@ -321,8 +322,8 @@
 msgstr ""
 "Freenode também mantém <a href=\"http://freenode.net/changuide\";>uma lista "
 "de diretrizes de canais</a> que você também deve considerar. Certas "
-"discussões como GNU contra BSD, vi contra <a href=\"/software/emacs/\""
-">Emacs</a> são muitas vezes saudáveis para a discussão de software livre e 
"
+"discussões como GNU contra BSD, vi contra <a href=\"/software/emacs/"
+"\">Emacs</a> são muitas vezes saudáveis para a discussão de software livre 
e "
 "nós encorajamos um debate saudável."
 
 #. type: Content of: <h3>
@@ -333,8 +334,8 @@
 msgid ""
 "IRC is there for everyone, not just seasoned GNU developers.  It is "
 "unreasonable to expect everyone to ignore a user who is misbehaving, and if "
-"you have a GNU or FSF cloak, you may be reassigned an "
-"&ldquo;unaffiliated&rdquo; cloak if you continue to abuse your privileges."
+"you have a GNU or FSF cloak, you may be reassigned an &ldquo;"
+"unaffiliated&rdquo; cloak if you continue to abuse your privileges."
 msgstr ""
 "O IRC está disponível para todos, e não apenas para desenvolvedores "
 "experientes do GNU. Não é razoável esperar que todos ignorem um usuário 
que "
@@ -347,24 +348,22 @@
 msgid "*GNUN-SLOT: TRANSLATOR'S NOTES*"
 msgstr " "
 
+# type: Content of: <div><p>
 #. type: Content of: <div><div><p>
 msgid ""
-"Please send general FSF &amp; GNU inquiries to <a "
-"href=\"mailto:address@hidden";>&lt;address@hidden&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:address@hidden";>&lt;address@hidden&gt;</a>."
+"Please send general FSF &amp; GNU inquiries to <a 
href=\"mailto:address@hidden";
+"\">&lt;address@hidden&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:address@hidden";>&lt;address@hidden"
+"org&gt;</a>."
 msgstr ""
 "Envie perguntas em geral sobre a FSF e o GNU para <a 
href=\"mailto:address@hidden";
 "org\">&lt;address@hidden&gt;</a>. Também existem <a 
href=\"/contact/\">outros "
 "meios de contatar</a> a FSF.  Links quebrados e outras correções ou "
-"sugestões podem ser enviadas para <a href=\"mailto:address@hidden"";
-">&lt;address@hidden&gt;</a>."
+"sugestões podem ser enviadas para <a href=\"mailto:address@hidden";>&lt;"
+"address@hidden&gt;</a>."
 
 #
-#
-#
-#
 #.  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
@@ -378,16 +377,16 @@
 #.         README</a>. 
 #. type: Content of: <div><div><p>
 msgid ""
-"Please see the <a "
-"href=\"/server/standards/README.translations.html\">Translations README</a> "
-"for information on coordinating and submitting translations of this article."
+"Please see the <a href=\"/server/standards/README.translations.html"
+"\">Translations README</a> for information on coordinating and submitting "
+"translations of this article."
 msgstr ""
 "A equipe de traduções para o português brasileiro se esforça para 
oferecer "
 "traduções acuradas e de boa qualidade, mas não estamos isentos de erros. 
Por "
-"favor, envie seus comentários e sugestões em geral sobre as traduções 
para <"
-"a href=\"mailto:address@hidden";>&lt;address@hidden&gt;</a>"
-". </p><p>Consulte o <a href=\"/server/standards/README.translations.html\">"
-"Guia para as traduções</a> para mais informações sobre a coordenação e 
o "
+"favor, envie seus comentários e sugestões em geral sobre as traduções 
para "
+"<a href=\"mailto:address@hidden";>&lt;address@hidden&gt;</"
+"a>. </p><p>Consulte o <a href=\"/server/standards/README.translations.html"
+"\">Guia para as traduções</a> para mais informações sobre a coordenação 
e o "
 "envio de traduções das páginas desse site."
 
 #. type: Content of: <div><p>
@@ -402,22 +401,23 @@
 
 #. 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>."
+"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 ""
-"Esta página está licenciada sob uma licença <a rel=\"license\" href=\""
-"http://creativecommons.org/licenses/by-nd/4.0/deed.pt_BR\";>Creative Commons "
+"Esta página está licenciada sob uma licença <a rel=\"license\" 
href=\"http://";
+"creativecommons.org/licenses/by-nd/4.0/deed.pt_BR\">Creative Commons "
 "Atribuição-SemDerivações 4.0 Internacional</a>."
 
 #. TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.
 #. type: Content of: <div><div>
 msgid "*GNUN-SLOT: TRANSLATOR'S CREDITS*"
 msgstr ""
-"Traduzido por: Rafael Fontenelle <a href=\"mailto:address@hidden"";
-">&lt;address@hidden&gt;</a>, 2018"
+"Traduzido por: Rafael Fontenelle <a href=\"mailto:address@hidden";>&lt;"
+"address@hidden&gt;</a>, 2018"
 
+# type: Content of: <div><p>
 #.  timestamp start 
 #. type: Content of: <div><p>
 msgid "Updated:"
-msgstr "Última atualização:"
+msgstr "Última atualização: "

Index: server/po/irc-rules.translist
===================================================================
RCS file: /web/www/www/server/po/irc-rules.translist,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -b -r1.14 -r1.15
--- server/po/irc-rules.translist       20 May 2015 14:57:31 -0000      1.14
+++ server/po/irc-rules.translist       24 Jan 2018 12:33:21 -0000      1.15
@@ -8,6 +8,7 @@
 <span dir="ltr"><a lang="es" hreflang="es" 
href="/server/irc-rules.es.html">español</a>&nbsp;[es]</span> &nbsp;
 <span dir="ltr"><a lang="fr" hreflang="fr" 
href="/server/irc-rules.fr.html">français</a>&nbsp;[fr]</span> &nbsp;
 <span dir="ltr"><a lang="ja" hreflang="ja" 
href="/server/irc-rules.ja.html">日本語</a>&nbsp;[ja]</span> &nbsp;
+<span dir="ltr"><a lang="pt-br" hreflang="pt-br" 
href="/server/irc-rules.pt-br.html">português&nbsp;do&nbsp;Brasil</a>&nbsp;[pt-br]</span>
 &nbsp;
 <span dir="ltr"><a lang="sq" hreflang="sq" 
href="/server/irc-rules.sq.html">Shqip</a>&nbsp;[sq]</span> &nbsp;
 </p>
 </div>' -->
@@ -18,5 +19,6 @@
 <link rel="alternate" type="text/html" lang="es" hreflang="es" 
href="/server/irc-rules.es.html" title="español" />
 <link rel="alternate" type="text/html" lang="fr" hreflang="fr" 
href="/server/irc-rules.fr.html" title="français" />
 <link rel="alternate" type="text/html" lang="ja" hreflang="ja" 
href="/server/irc-rules.ja.html" title="日本語" />
+<link rel="alternate" type="text/html" lang="pt-br" hreflang="pt-br" 
href="/server/irc-rules.pt-br.html" title="português do Brasil" />
 <link rel="alternate" type="text/html" lang="sq" hreflang="sq" 
href="/server/irc-rules.sq.html" title="Shqip" />
 <!-- end translist file -->

Index: education/edu-cases-argentina.pt-br.html
===================================================================
RCS file: education/edu-cases-argentina.pt-br.html
diff -N education/edu-cases-argentina.pt-br.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ education/edu-cases-argentina.pt-br.html    24 Jan 2018 12:33:16 -0000      
1.1
@@ -0,0 +1,116 @@
+<!--#set var="ENGLISH_PAGE" value="/education/edu-cases-argentina.en.html" -->
+
+<!--#include virtual="/server/header.pt-br.html" -->
+<!-- Parent-Version: 1.79 -->
+<!--#set var="DISABLE_TOP_ADDENDUM" value="yes" -->
+
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>Estudos de Caso na Argentina - Projeto GNU - Free Software 
Foundation</title>
+
+<!--#include virtual="/education/po/edu-cases-argentina.translist" -->
+<!--#include virtual="/server/banner.pt-br.html" -->
+<!--#include virtual="/education/education-menu.pt-br.html" -->
+<p class="edu-breadcrumb">
+<a href="/education/education.html">Educação</a> &rarr; <a
+href="/education/edu-cases.html">Estudos de Caso</a> &rarr; Argentina</p>
+
+<!--GNUN: OUT-OF-DATE NOTICE-->
+<!--#if expr="$OUTDATED_SINCE" -->
+<!--#else -->
+<!--#if expr="$LANGUAGE_SUFFIX" -->
+<!--#set var="DISABLE_TOP_ADDENDUM" value="no" -->
+<!--#include virtual="/server/top-addendum.pt-br.html" -->
+<!--#endif -->
+<!--#endif -->
+<h2>Estudos de Caso na Argentina</h2>
+
+<p>O território administrativo da Argentina é dividido em vinte e três 
estados
+autônomos políticos chamados províncias. Essas províncias desenvolvem sua
+própria política educacional, atendendo apenas a certas diretrizes básicas
+do governo nacional. Isso permite que as instituições educacionais adaptem
+seus currículos às suas necessidades locais. Saiba mais sobre o <a href=
+"http://en.wikipedia.org/wiki/Argentina#Education";>sistema educacional da
+Argentina</a> na Wikipédia.</p>
+
+<p>Abaixo estão listadas algumas das instituições educacionais da Argentina 
que
+estão usando Software Livre.</p>
+
+<!-- Add new entries of educational institutions in this country in 
+alphabetical order by the name of the institution -->
+<ul>
+<li><a href= "/education/edu-cases-argentina-ecen.html"> Escuela Cristiana
+Evang&eacute;lica de Neuqu&eacute;n (ECEN)</a>
+
+<p>Uma professora do primário com poucas habilidades técnicas consegue que 
sua
+escola migre completamente para o Software Livre, alegando que o software
+proprietário é contra os valores morais e éticos promovidos pela 
escola.</p></li>
+</ul>
+
+<a href="/education/edu-cases.html">Voltar para Estudos de Casos</a>
+
+<div class="translators-notes">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.-->
+ </div>
+</div>
+
+<!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.pt-br.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<p>Envie perguntas em geral sobre a FSF e o GNU para <a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>. Também existem <a
+href="/contact/">outros meios de contatar</a> a FSF.  Links quebrados e
+outras correções ou sugestões podem ser enviadas para <a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>.</p>
+
+<p>
+<!-- TRANSLATORS: Ignore the original text in this paragraph,
+        replace it with the translation of these two:
+
+        We work hard and do our best to provide accurate, good quality
+        translations.  However, we are not exempt from imperfection.
+        Please send your comments and general suggestions in this regard
+        to <a href="mailto:address@hidden";>
+
+        &lt;address@hidden&gt;</a>.</p>
+
+        <p>For information on coordinating and submitting translations of
+        our web pages, see <a
+        href="/server/standards/README.translations.html">Translations
+        README</a>. -->
+A equipe de traduções para o português brasileiro se esforça para oferecer
+traduções acuradas e de boa qualidade, mas não estamos isentos de erros. Por
+favor, envie seus comentários e sugestões em geral sobre as traduções para
+<a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>.
+</p><p>Consulte o <a href="/server/standards/README.translations.html">Guia
+para as traduções</a> para mais informações sobre a coordenação e o 
envio de
+traduções das páginas desse site.</p>
+</div>
+
+<p>Copyright &copy; 2011, 2015, 2016 Free Software Foundation, Inc.</p>
+
+<p>Esta página está licenciada sob uma licença <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/4.0/deed.pt_BR";>Creative
+Commons Atribuição-SemDerivações 4.0 Internacional</a>.</p>
+
+<!--#include virtual="/server/bottom-notes.pt-br.html" -->
+<div class="translators-credits">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.-->
+Traduzido por: Rafael Fontenelle <a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>, 2017.</div>
+
+<p class="unprintable"><!-- timestamp start -->
+Última atualização: 
+
+$Date: 2018/01/24 12:33:16 $
+
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>

Index: education/edu-cases-india.pt-br.html
===================================================================
RCS file: education/edu-cases-india.pt-br.html
diff -N education/edu-cases-india.pt-br.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ education/edu-cases-india.pt-br.html        24 Jan 2018 12:33:16 -0000      
1.1
@@ -0,0 +1,130 @@
+<!--#set var="ENGLISH_PAGE" value="/education/edu-cases-india.en.html" -->
+
+<!--#include virtual="/server/header.pt-br.html" -->
+<!-- Parent-Version: 1.79 -->
+<!--#set var="DISABLE_TOP_ADDENDUM" value="yes" -->
+
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>Estudos de Caso na Índia - Projeto GNU - Free Software 
Foundation</title>
+
+<!--#include virtual="/education/po/edu-cases-india.translist" -->
+<!--#include virtual="/server/banner.pt-br.html" -->
+<!--#include virtual="/education/education-menu.pt-br.html" -->
+<p class="edu-breadcrumb">
+   <a href="/education/education.html">Educação</a> &rarr; <a
+href="/education/edu-cases.html">Estudos de Caso</a> &rarr; Índia</p>
+
+<!--GNUN: OUT-OF-DATE NOTICE-->
+<!--#if expr="$OUTDATED_SINCE" -->
+<!--#else -->
+<!--#if expr="$LANGUAGE_SUFFIX" -->
+<!--#set var="DISABLE_TOP_ADDENDUM" value="no" -->
+<!--#include virtual="/server/top-addendum.pt-br.html" -->
+<!--#endif -->
+<!--#endif -->
+<h2>Estudos de Caso na Índia</h2>
+
+<p>Um <a href="/education/edu-system-india.html">artigo</a>, do cientista
+indiano Dr. V. Sasi Kumar, que explica em detalhes como o sistema
+educacional está estruturado na Índia, com notas significativas sobre o seu
+desenvolvimento ao longo da história. O artigo também cobre o caso de
+Kerala, o estado na Índia que implementou com sucesso o Software Livre em
+milhares de escolas graças ao projeto do governo <a
+href="https://www.itschool.gov.in/";>address@hidden</a>.</p>
+
+<p>Algumas noções sobre o <a href=
+"http://en.wikipedia.org/wiki/Education_in_India";>sistema educacional na
+Índia</a> também podem ser encontradas na Wikipédia.</p>
+
+<p>Abaixo estão listadas algumas das instituições educacionais da Índia que
+estão usando Software Livre.</p>
+
+<!-- Add new entries of educational institutions in this country in 
+alphabetical order by the name of the institution -->
+<ul>
+<li><a href= "/education/edu-cases-india-ambedkar.html">Centro de Computação
+Comunitária de Ambedkar (AC3)</a>
+
+<p>Um grupo de defensores do Software Livre instalou um centro computacional em
+uma favela em Bangalore para ensinar habilidades de informática para
+crianças desprivilegiadas.</p></li>
+</ul>
+
+<ul>           
+<li><a href= "/education/edu-cases-india-irimpanam.html">Escola de Ensino
+Profissionalizante de Irimpanam (VHSS Irimpanam)</a>
+
+<p>Um dos vários milhares de escolas que estão usando exclusivamente Software
+Livre como o resultado de um <a href=
+"https://www.itschool.gov.in/";>projeto</a> realizado pelo governo no estado
+de Kerala.</p></li>
+</ul>
+
+<a href="/education/edu-cases.html">Voltar para Estudos de Caso</a>
+
+<div class="translators-notes">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.-->
+ </div>
+</div>
+
+<!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.pt-br.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<p>Envie perguntas em geral sobre a FSF e o GNU para <a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>. Também existem <a
+href="/contact/">outros meios de contatar</a> a FSF.  Links quebrados e
+outras correções ou sugestões podem ser enviadas para <a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>.</p>
+
+<p>
+<!-- TRANSLATORS: Ignore the original text in this paragraph,
+        replace it with the translation of these two:
+
+        We work hard and do our best to provide accurate, good quality
+        translations.  However, we are not exempt from imperfection.
+        Please send your comments and general suggestions in this regard
+        to <a href="mailto:address@hidden";>
+
+        &lt;address@hidden&gt;</a>.</p>
+
+        <p>For information on coordinating and submitting translations of
+        our web pages, see <a
+        href="/server/standards/README.translations.html">Translations
+        README</a>. -->
+A equipe de traduções para o português brasileiro se esforça para oferecer
+traduções acuradas e de boa qualidade, mas não estamos isentos de erros. Por
+favor, envie seus comentários e sugestões em geral sobre as traduções para
+<a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>.
+</p><p>Consulte o <a href="/server/standards/README.translations.html">Guia
+para as traduções</a> para mais informações sobre a coordenação e o 
envio de
+traduções das páginas desse site.</p>
+</div>
+
+<p>Copyright &copy; 2011, 2015, 2016 Free Software Foundation, Inc.</p>
+
+<p>Esta página está licenciada sob uma licença <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/4.0/deed.pt_BR";>Creative
+Commons Atribuição-SemDerivações 4.0 Internacional</a>.</p>
+
+<!--#include virtual="/server/bottom-notes.pt-br.html" -->
+<div class="translators-credits">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.-->
+Traduzido por: Rafael Fontenelle <a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>, 2017.</div>
+
+<p class="unprintable"><!-- timestamp start -->
+Última atualização: 
+
+$Date: 2018/01/24 12:33:16 $
+
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>

Index: education/edu-cases.pt-br.html
===================================================================
RCS file: education/edu-cases.pt-br.html
diff -N education/edu-cases.pt-br.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ education/edu-cases.pt-br.html      24 Jan 2018 12:33:16 -0000      1.1
@@ -0,0 +1,135 @@
+<!--#set var="ENGLISH_PAGE" value="/education/edu-cases.en.html" -->
+
+<!--#include virtual="/server/header.pt-br.html" -->
+<!-- Parent-Version: 1.79 -->
+<!--#set var="DISABLE_TOP_ADDENDUM" value="yes" -->
+
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>Estudos de Caso - Projeto GNU - Free Software Foundation</title>
+
+<!--#include virtual="/education/po/edu-cases.translist" -->
+<!--#include virtual="/server/banner.pt-br.html" -->
+<!--#include virtual="/education/education-menu.pt-br.html" -->
+<p class="edu-breadcrumb">
+<a href="/education/education.html">Educação</a> &rarr; Estudos de Caso</p>
+
+<!--GNUN: OUT-OF-DATE NOTICE-->
+<!--#if expr="$OUTDATED_SINCE" -->
+<!--#else -->
+<!--#if expr="$LANGUAGE_SUFFIX" -->
+<!--#set var="DISABLE_TOP_ADDENDUM" value="no" -->
+<!--#include virtual="/server/top-addendum.pt-br.html" -->
+<!--#endif -->
+<!--#endif -->
+<h2>Estudos de Caso</h2>
+
+<p>Realizamos pesquisas mundiais para examinar casos de instituições
+educacionais públicas e privadas, bem como ambientes educacionais informais
+que implementaram com sucesso o uso de Software Livre. Nós não tentamos
+construir um banco de dados abrangente aqui. Em vez disso, apresentamos
+casos específicos de sucesso, na crença de que o testemunho será inspirador
+para qualquer pessoa que considere a primeira instalação ou migração para o
+Software Livre.</p>
+ 
+<p>Se você sabe de um caso que poderia ser incluído aqui, por favor nos 
contate
+em <a href="mailto:address@hidden";>&lt;address@hidden&gt;</a> para nos
+avisar.</p>
+
+<!-- Begin country-wise Index. Add countries in alphabetical order  -->
+<!-- End of Country-wise Index -->
+<!-- Begin country-wise Section. Add new countries in alphabetical order -->
+<a href="/education/edu-cases-argentina.html">Argentina</a> | <a
+href="/education/edu-cases-india.html">Índia</a>
+
+
+
+
+               
+<h3 id="Argentina">Argentina</h3>
+
+<!-- Add entries under corresponding country in alphabetical order by the name 
of the school -->
+<p><a href="/education/edu-cases-argentina-ecen.html">Escuela Cristiana
+Evangélica de Neuquén (ECEN)</a> <br />
+Uma professora de ensino fundamental com poucas habilidades técnicas
+consegue fazer a escola dela migrar todas as estações de trabalho, incluindo
+os escritórios da administração e a biblioteca.</p>
+               
+<h3 id="India">Índia</h3>
+
+<p><a href="/education/edu-cases-india-ambedkar.html">Centro de Computação
+Comunitária de Ambedkar (AC3)</a> <br />
+Um grupo de defensores de Software Livre em Bangalore ensina habilidades de
+informática a crianças desprivilegiados usando exclusivamente sistemas e
+programas livres.</p>
+
+<p><a href="/education/edu-cases-india-irimpanam.html">Escola de Ensino
+Profissionalizante de Irimpanam (VHSS Irimpanam)</a> <br />
+Um dos vários milhares de escolas que migraram completamente para o Software
+Livre sob o projeto governamental address@hidden</p>
+
+<div class="translators-notes">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.-->
+ </div>
+</div>
+
+<!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.pt-br.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<p>Envie perguntas em geral sobre a FSF e o GNU para <a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>. Também existem <a
+href="/contact/">outros meios de contatar</a> a FSF.  Links quebrados e
+outras correções ou sugestões podem ser enviadas para <a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>.</p>
+
+<p>
+<!-- TRANSLATORS: Ignore the original text in this paragraph,
+        replace it with the translation of these two:
+
+        We work hard and do our best to provide accurate, good quality
+        translations.  However, we are not exempt from imperfection.
+        Please send your comments and general suggestions in this regard
+        to <a href="mailto:address@hidden";>
+
+        &lt;address@hidden&gt;</a>.</p>
+
+        <p>For information on coordinating and submitting translations of
+        our web pages, see <a
+        href="/server/standards/README.translations.html">Translations
+        README</a>. -->
+A equipe de traduções para o português brasileiro se esforça para oferecer
+traduções acuradas e de boa qualidade, mas não estamos isentos de erros. Por
+favor, envie seus comentários e sugestões em geral sobre as traduções para
+<a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>.
+</p><p>Consulte o <a href="/server/standards/README.translations.html">Guia
+para as traduções</a> para mais informações sobre a coordenação e o 
envio de
+traduções das páginas desse site.</p>
+</div>
+
+<p>Copyright &copy; 2011, 2016 Free Software Foundation, Inc.</p>
+
+<p>Esta página está licenciada sob uma licença <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/4.0/deed.pt_BR";>Creative
+Commons Atribuição-SemDerivações 4.0 Internacional</a>.</p>
+
+<!--#include virtual="/server/bottom-notes.pt-br.html" -->
+<div class="translators-credits">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.-->
+Traduzido por: Rafael Fontenelle <a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>, 2017.</div>
+
+<p class="unprintable"><!-- timestamp start -->
+Última atualização: 
+
+$Date: 2018/01/24 12:33:16 $
+
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>

Index: education/po/edu-cases-argentina.pt-br-en.html
===================================================================
RCS file: education/po/edu-cases-argentina.pt-br-en.html
diff -N education/po/edu-cases-argentina.pt-br-en.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ education/po/edu-cases-argentina.pt-br-en.html      24 Jan 2018 12:33:17 
-0000      1.1
@@ -0,0 +1,96 @@
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.79 -->
+<!--#set var="DISABLE_TOP_ADDENDUM" value="yes" -->
+
+<title>Case Studies in Argentina
+- GNU Project - Free Software Foundation</title>
+
+<!--#include virtual="/education/po/edu-cases-argentina.translist" -->
+<!--#include virtual="/server/banner.html" -->
+<!--#include virtual="/education/education-menu.html" -->
+<p class="edu-breadcrumb">
+<a href="/education/education.html">Education</a> &rarr; 
+<a href="/education/edu-cases.html">Case Studies</a> &rarr; Argentina</p>
+<!--GNUN: OUT-OF-DATE NOTICE-->
+<!--#if expr="$OUTDATED_SINCE" --><!--#else -->
+<!--#if expr="$LANGUAGE_SUFFIX" -->
+<!--#set var="DISABLE_TOP_ADDENDUM" value="no" -->
+<!--#include virtual="/server/top-addendum.html" -->
+<!--#endif -->
+<!--#endif -->
+<h2>Case Studies in Argentina</h2>
+
+<p>Argentina's administrative territory is divided into twenty three 
+political autonomous states called  provinces. These provinces develop 
+their own educational policy, attending just to certain basic guidelines 
+from the National Government. This allows educational institutions to 
+adapt their curricula to their local needs. Learn more about the
+<a href= "http://en.wikipedia.org/wiki/Argentina#Education";>education
+system of Argentina</a> in Wikipedia.</p>
+
+<p>Below are listed some of the educational institutions in Argentina 
+who are using Free Software.</p>
+
+<!-- Add new entries of educational institutions in this country in 
+alphabetical order by the name of the institution -->
+
+<ul>
+<li><a href= "/education/edu-cases-argentina-ecen.html">
+Escuela Cristiana Evang&eacute;lica de Neuqu&eacute;n (ECEN)</a>
+
+<p>An elementary teacher with little technical skills manages to get her 
+school to completely migrate to Free Software on the grounds that 
+proprietary software is against the moral and ethical values promoted by 
+the school.</p></li>
+</ul>
+
+<a href="/education/edu-cases.html">Back to Case Studies</a>
+
+</div><!-- for id="content", starts in the include above -->
+
+<!--#include virtual="/server/footer.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<p>Please send general FSF &amp; GNU inquiries to
+<a href="mailto:address@hidden";>&lt;address@hidden&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:address@hidden";>&lt;address@hidden&gt;</a>.</p>
+
+<p><!-- TRANSLATORS: Ignore the original text in this paragraph,
+        replace it with the translation of these two:
+
+        We work hard and do our best to provide accurate, good quality
+        translations.  However, we are not exempt from imperfection.
+        Please send your comments and general suggestions in this regard
+        to <a href="mailto:address@hidden";>
+        &lt;address@hidden&gt;</a>.</p>
+
+        <p>For information on coordinating and submitting translations of
+        our web pages, see <a
+        href="/server/standards/README.translations.html">Translations
+        README</a>. -->
+Please see the <a
+href="/server/standards/README.translations.html">Translations
+README</a> for information on coordinating and submitting translations
+of this article.</p>
+</div>
+
+<p>Copyright &copy; 2011, 2015, 2016 Free Software Foundation, Inc.</p>
+
+<p>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>.</p>
+
+<!--#include virtual="/server/bottom-notes.html" -->
+
+<p class="unprintable">Updated:
+<!-- timestamp start -->
+$Date: 2018/01/24 12:33:17 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>

Index: education/po/edu-cases-india.pt-br-en.html
===================================================================
RCS file: education/po/edu-cases-india.pt-br-en.html
diff -N education/po/edu-cases-india.pt-br-en.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ education/po/edu-cases-india.pt-br-en.html  24 Jan 2018 12:33:17 -0000      
1.1
@@ -0,0 +1,110 @@
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.79 -->
+<!--#set var="DISABLE_TOP_ADDENDUM" value="yes" -->
+
+<title>Case Studies in India
+- GNU Project - Free Software Foundation</title>
+
+<!--#include virtual="/education/po/edu-cases-india.translist" -->
+<!--#include virtual="/server/banner.html" -->
+
+<!--#include virtual="/education/education-menu.html" -->
+<p class="edu-breadcrumb">
+   <a href="/education/education.html">Education</a> &rarr; 
+   <a href="/education/edu-cases.html">Case Studies</a> &rarr; India</p>
+<!--GNUN: OUT-OF-DATE NOTICE-->
+<!--#if expr="$OUTDATED_SINCE" --><!--#else -->
+<!--#if expr="$LANGUAGE_SUFFIX" -->
+<!--#set var="DISABLE_TOP_ADDENDUM" value="no" -->
+<!--#include virtual="/server/top-addendum.html" -->
+<!--#endif -->
+<!--#endif -->
+<h2>Case Studies in India</h2>
+
+<p>An <a href="/education/edu-system-india.html">article</a> by Indian
+scientist Dr. V. Sasi Kumar which explains in detail how the education 
+system is structured in India, with significant notes on its development 
+throughout history. The article also covers the case of Kerala, the
+state in India which successfully implemented Free Software in thousands 
+of schools thanks to the government's project 
+<a href="https://www.itschool.gov.in/";>address@hidden</a>.</p>
+
+<p>Some notions on the
+<a href= "http://en.wikipedia.org/wiki/Education_in_India";>education
+system of India</a> can also be found in Wikipedia.</p>
+
+<p>Below are listed some of the educational institutions in India who 
+are using Free Software.</p>
+
+<!-- Add new entries of educational institutions in this country in 
+alphabetical order by the name of the institution -->
+
+<ul>
+<li><a href= "/education/edu-cases-india-ambedkar.html">Ambedkar Community 
+Computing Center (AC3)</a>
+
+<p>A group of Free Software advocates set up a computing center in a 
+slum in Bangalore to teach computer skills to underprivileged 
+children.</p></li>
+</ul>
+
+<ul>           
+<li><a href= "/education/edu-cases-india-irimpanam.html">Vocational Higher 
+Secondary School Irimpanam (VHSS Irimpanam)</a>
+
+<p>One of the several thousand schools that are using exclusively Free
+Software as the result of a 
+<a href= "https://www.itschool.gov.in/";>project</a>
+carried out by the government in the state of Kerala.</p></li>
+</ul>
+
+<a href="/education/edu-cases.html">Back to Case Studies</a>
+
+</div><!-- for id="content", starts in the include above -->
+
+<!--#include virtual="/server/footer.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<p>Please send general FSF &amp; GNU inquiries to
+<a href="mailto:address@hidden";>&lt;address@hidden&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:address@hidden";>&lt;address@hidden&gt;</a>.</p>
+
+<p><!-- TRANSLATORS: Ignore the original text in this paragraph,
+        replace it with the translation of these two:
+
+        We work hard and do our best to provide accurate, good quality
+        translations.  However, we are not exempt from imperfection.
+        Please send your comments and general suggestions in this regard
+        to <a href="mailto:address@hidden";>
+        &lt;address@hidden&gt;</a>.</p>
+
+        <p>For information on coordinating and submitting translations of
+        our web pages, see <a
+        href="/server/standards/README.translations.html">Translations
+        README</a>. -->
+Please see the <a
+href="/server/standards/README.translations.html">Translations
+README</a> for information on coordinating and submitting translations
+of this article.</p>
+</div>
+
+<p>Copyright &copy; 2011, 2015, 2016 Free Software Foundation, Inc.</p>
+
+<p>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>.</p>
+
+<!--#include virtual="/server/bottom-notes.html" -->
+
+<p class="unprintable">Updated:
+<!-- timestamp start -->
+$Date: 2018/01/24 12:33:17 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>

Index: education/po/edu-cases.pt-br-en.html
===================================================================
RCS file: education/po/edu-cases.pt-br-en.html
diff -N education/po/edu-cases.pt-br-en.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ education/po/edu-cases.pt-br-en.html        24 Jan 2018 12:33:17 -0000      
1.1
@@ -0,0 +1,113 @@
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.79 -->
+<!--#set var="DISABLE_TOP_ADDENDUM" value="yes" -->
+
+<title>Case Studies
+- GNU Project - Free Software Foundation</title>
+
+<!--#include virtual="/education/po/edu-cases.translist" -->
+<!--#include virtual="/server/banner.html" -->
+<!--#include virtual="/education/education-menu.html" -->
+<p class="edu-breadcrumb">
+<a href="/education/education.html">Education</a> &rarr; Case Studies</p>
+<!--GNUN: OUT-OF-DATE NOTICE-->
+<!--#if expr="$OUTDATED_SINCE" --><!--#else -->
+<!--#if expr="$LANGUAGE_SUFFIX" -->
+<!--#set var="DISABLE_TOP_ADDENDUM" value="no" -->
+<!--#include virtual="/server/top-addendum.html" -->
+<!--#endif -->
+<!--#endif -->
+<h2>Case Studies</h2>
+
+<p>We perform worldwide research to examine cases of private and public 
+educational institutions as well as informal educational environments
+that have successfully implemented the use of Free Software. We do not
+attempt to build a comprehensive database here. Instead, we present 
+specific cases of success, in the belief that testimony will be 
+inspiring to anyone considering first time installation or migration to 
+Free Software.</p>
+ 
+<p>If you know of a case that could be included here, please contact us 
+<a href="mailto:address@hidden";>&lt;address@hidden&gt;</a>
+to let us know.</p>
+               
+<!-- Begin country-wise Index. Add countries in alphabetical order  -->
+               
+<a href="/education/edu-cases-argentina.html">Argentina</a> |
+<a href="/education/edu-cases-india.html">India</a>
+
+<!-- End of Country-wise Index -->
+
+<!-- Begin country-wise Section. Add new countries in alphabetical order -->
+               
+<h3 id="Argentina">Argentina</h3>
+               
+<!-- Add entries under corresponding country in alphabetical order by the name 
of the school -->
+               
+<p><a href="/education/edu-cases-argentina-ecen.html">Escuela 
+Cristiana Evang&eacute;lica de Neuqu&eacute;n (ECEN)</a> <br />
+An elementary teacher with little technical skills manages to get her
+school to migrate all work stations, including the administration 
+offices and the library.</p>
+               
+<h3 id="India">India</h3>
+
+<p><a href="/education/edu-cases-india-ambedkar.html">Ambedkar Community 
+Computing Center (AC3)</a> <br />
+A group of Free Software advocates in Bangalore teaches computer skills 
+to underprivileged children using exclusively Free systems and 
+programs.</p>
+
+<p><a href="/education/edu-cases-india-irimpanam.html">Vocational Higher 
+Secondary School Irimpanam (VHSS Irimpanam)</a> <br />
+One of the several thousand schools that migrated completely to Free
+Software under the government's project address@hidden</p>
+
+</div><!-- for id="content", starts in the include above -->
+
+<!--#include virtual="/server/footer.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<p>Please send general FSF &amp; GNU inquiries to
+<a href="mailto:address@hidden";>&lt;address@hidden&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:address@hidden";>&lt;address@hidden&gt;</a>.</p>
+
+<p><!-- TRANSLATORS: Ignore the original text in this paragraph,
+        replace it with the translation of these two:
+
+        We work hard and do our best to provide accurate, good quality
+        translations.  However, we are not exempt from imperfection.
+        Please send your comments and general suggestions in this regard
+        to <a href="mailto:address@hidden";>
+        &lt;address@hidden&gt;</a>.</p>
+
+        <p>For information on coordinating and submitting translations of
+        our web pages, see <a
+        href="/server/standards/README.translations.html">Translations
+        README</a>. -->
+Please see the <a
+href="/server/standards/README.translations.html">Translations
+README</a> for information on coordinating and submitting translations
+of this article.</p>
+</div>
+
+<p>Copyright &copy; 2011, 2016 Free Software Foundation, Inc.</p>
+
+<p>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>.</p>
+
+<!--#include virtual="/server/bottom-notes.html" -->
+
+<p class="unprintable">Updated:
+<!-- timestamp start -->
+$Date: 2018/01/24 12:33:17 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>

Index: gnu/about-gnu.pt-br.html
===================================================================
RCS file: gnu/about-gnu.pt-br.html
diff -N gnu/about-gnu.pt-br.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ gnu/about-gnu.pt-br.html    24 Jan 2018 12:33:17 -0000      1.1
@@ -0,0 +1,156 @@
+<!--#set var="ENGLISH_PAGE" value="/gnu/about-gnu.en.html" -->
+
+<!--#include virtual="/server/header.pt-br.html" -->
+<!-- Parent-Version: 1.84 -->
+
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>Sobre o Sistema Operacional do GNU - Projeto GNU - Free Software 
Foundation</title>
+
+<!--#include virtual="/gnu/po/about-gnu.translist" -->
+<!--#include virtual="/server/banner.pt-br.html" -->
+<h2>Sobre o Sistema Operacional do GNU</h2>
+
+<blockquote>
+<p>O nome “GNU” é um acrônimo recursivo para “GNU's Not Unix!”; ela 
é
+pronunciada como <a href="/gnu/pronunciation.html">uma sílaba com um g
+forte</a>.</p>
+</blockquote>
+
+<p>[<a href="/gnu/gnu.html">Outros artigos históricos e gerais sobre o
+GNU.</a>]</p>
+
+<p>O GNU foi lançado por Richard Stallman (rms) em 1983, como um sistema
+operacional que seria reunido por pessoas que trabalham juntas pela
+liberdade de todos os usuários de software para controlar sua
+computação. rms permanece sendo o hoje <cite>Cheif GNUisance</cite>.</p>
+
+<p>O objetivo principal e contínuo do GNU é oferecer um sistema compatível 
com
+o Unix que seria 100% <a href="/philosophy/free-sw.html">software
+livre</a>. Não 95% livre, não 99,5%, mas 100%. O nome do sistema, GNU, é um
+acrônimo recursivo que significa “GNU's Not Unix” (em português, “GNU 
Não é
+Unix”) &mdash; uma maneira de homenagear as ideias técnicas do Unix,
+enquanto ao mesmo tempo diz que o GNU é algo diferente. Tecnicamente, o GNU
+é como o Unix. Mas, ao contrário do Unix, o GNU dá liberdade a seus
+usuários.</p>
+
+<p><a href="/distros/free-distros.html">Distribuições de sistema totalmente
+livre</a> (“distros”) que atendem a este objetivo estão disponíveis hoje,
+muitas usando o <a
+href="http://www.fsfla.org/svnwiki/selibre/linux-libre/";>kernel
+Linux-libre</a> (a <a href="/gnu/linux-and-gnu.html">relação entre GNU e o
+kernel Linux</a> é descrita mais detalhadamente em outro lugar). Os <a
+href="/software/software.html">pacotes GNU</a> foram criados para trabalhar
+em conjunto de forma que possamos ter um sistema GNU funcional. Descobriu-se
+que eles também servem como um “upstream” comum para muitas distros, 
então
+contribuições para pacotes GNU ajudam a comunidade de software livre como um
+todo. Naturalmente, o trabalho no GNU está em andamento, com o objetivo de
+criar um sistema que dê a maior liberdade aos usuários de computadores. Os
+pacotes GNU incluem aplicativos orientados a usuários, utilitários,
+ferramentas, bibliotecas e até jogos &mdash; todos os programas que um
+sistema operacional pode oferecer aos seus usuários. <a
+href="/help/evaluation.html">Novos pacotes são bem-vindos.</a> </p>
+
+<p>Milhares de pessoas se juntaram para tornar o GNU o sucesso que é hoje, e 
há
+<a href="/help/help.html">muitas formas de contribuir</a>, tanto técnicas
+como não técnicas. Os desenvolvedores do GNU se reúnem de tempos em tempos
+em <a href="/ghm/ghm.html">GNU Hackers Meetings</a> (“Reuniões de Hackers do
+GNU”), às vezes como parte das conferências do <a
+href="http://libreplanet.org/";>LibrePlanet</a>, a maior comunidade de
+software livre.</p>
+
+<p>O GNU sido apoiado de várias maneiras pela <a
+href="http://www.fsf.org/";>Free Software Foundation</a>, a organização sem
+fins lucrativos também fundada pelo rms para defender ideais de software
+livre. Entre outras coisas, a FSF aceita atribuições de copyrights e
+isenções de responsabilidade, para que possa atuar no tribunal em nome dos
+programas GNU. (Para ser claro, contribuir com um programa para o GNU,
+<em>não</em> exige a transferência do copyright para a FSF. Se você atribuir
+o copyright, a FSF aplicará a GPL para o programa se alguém violá-la; se
+você mantiver o copyright, a aplicação dependerá de você.)</p>
+
+<p>O objetivo final é fornecer software livre para fazer todos os trabalhos 
que
+os usuários de computadores desejam fazer &mdash; e assim fazer o software
+proprietário uma coisa do passado.</p>
+
+<div class="translators-notes">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.-->
+ </div>
+</div>
+
+<!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.pt-br.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<p>Envie perguntas em geral sobre a FSF e o GNU para <a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>. Também existem <a
+href="/contact/">outros meios de contatar</a> a FSF.  Links quebrados e
+outras correções ou sugestões podem ser enviadas para <a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>.</p>
+
+<p>
+<!-- TRANSLATORS: Ignore the original text in this paragraph,
+        replace it with the translation of these two:
+
+        We work hard and do our best to provide accurate, good quality
+        translations.  However, we are not exempt from imperfection.
+        Please send your comments and general suggestions in this regard
+        to <a href="mailto:address@hidden";>
+
+        &lt;address@hidden&gt;</a>.</p>
+
+        <p>For information on coordinating and submitting translations of
+        our web pages, see <a
+        href="/server/standards/README.translations.html">Translations
+        README</a>. -->
+A equipe de traduções para o português brasileiro se esforça para oferecer
+traduções acuradas e de boa qualidade, mas não estamos isentos de erros. Por
+favor, envie seus comentários e sugestões em geral sobre as traduções para
+<a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>.
+</p><p>Consulte o <a href="/server/standards/README.translations.html">Guia
+para as traduções</a> para mais informações sobre a coordenação e o 
envio de
+traduções das páginas desse site.</p>
+</div>
+
+<!-- Regarding copyright, in general, standalone pages (as opposed to
+     files generated as part of manuals) on the GNU web server should
+     be under CC BY-ND 4.0.  Please do NOT change or remove this
+     without talking with the webmasters or licensing team first.
+     Please make sure the copyright date is consistent with the
+     document.  For web pages, it is ok to list just the latest year the
+     document was modified, or published.
+     
+     If you wish to list earlier years, that is ok too.
+     Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
+     years, as long as each year in the range is in fact a copyrightable
+     year, i.e., a year in which the document was published (including
+     being publicly visible on the web or in a revision control system).
+     
+     There is more detail about copyright years in the GNU Maintainers
+     Information document, www.gnu.org/prep/maintain. -->
+<p>Copyright &copy; 2014, 2017, 2018 Free Software Foundation, Inc.</p>
+
+<p>Esta página está licenciada sob uma licença <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/4.0/deed.pt_BR";>Creative
+Commons Atribuição-SemDerivações 4.0 Internacional</a>.</p>
+
+<!--#include virtual="/server/bottom-notes.pt-br.html" -->
+<div class="translators-credits">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.-->
+Traduzido por: Rafael Fontenelle <a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>, 2018.</div>
+
+<p class="unprintable"><!-- timestamp start -->
+Última atualização: 
+
+$Date: 2018/01/24 12:33:17 $
+
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>

Index: gnu/pronunciation.pt-br.html
===================================================================
RCS file: gnu/pronunciation.pt-br.html
diff -N gnu/pronunciation.pt-br.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ gnu/pronunciation.pt-br.html        24 Jan 2018 12:33:17 -0000      1.1
@@ -0,0 +1,129 @@
+<!--#set var="ENGLISH_PAGE" value="/gnu/pronunciation.en.html" -->
+
+<!--#include virtual="/server/html5-header.pt-br.html" -->
+<!-- Parent-Version: 1.77 -->
+
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>Como pronunciar GNU - Projeto GNU - Free Software Foundation</title>
+
+<!--#include virtual="/gnu/po/pronunciation.translist" -->
+<!--#include virtual="/server/banner.pt-br.html" -->
+<h2>Como pronunciar GNU</h2>
+
+<p>O nome “GNU” é um acrônimo recursivo para “GNU's Not Unix!”, que, 
em
+português, é traduzido como “GNU Não é Unix!”; ele é pronunciado como
+“menu”, com “g” em vez de “me”, e como o herbívoro africano 
“gnu”.</p>
+
+<p>
+Essa é uma gravação do <a href="http://www.stallman.org/";>Richard
+Stallman</a> dizendo “GNU” e outra com uma explicação curta sobre como 
GNU
+recebeu o nome:
+</p>
+
+<p><strong>Como dizer “GNU”:</strong></p>
+<audio src="/audio/gnu-pronunciation.ogg" controls="controls">
+<a href="/audio/gnu-pronunciation.ogg">Como dizer GNU</a>
+</audio>
+
+<p><strong>Como GNU recebeu o nome:</strong></p>
+<audio src="/audio/how-gnu-was-named.ogg" controls="controls">    
+<a href="/audio/how-gnu-was-named.ogg">Como GNU recebeu o nome</a>
+</audio>
+
+<p>A combinação de <a href="/gnu/linux-and-gnu.html">GNU e Linux</a> é o
+<strong>sistema operacional GNU/Linux</strong>, agora usado por milhões e,
+por vezes, incorretamente chamado apenas de “Linux”.</p>
+<p>Para mais informações detalhadas e histórico do Sistema Operacional GNU,
+visite <a href="/gnu/">http://www.gnu.org/gnu/</a></p>
+
+<h3 id="license">Licença das gravações</h3>
+
+<p>Copyright (C) 2001 Richard M. Stallman</p>
+
+<p>Essas gravações estão licenciadas sob uma licença <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/deed.pt_BR";>Creative
+Commons Atribuição-SemDerivações 3.0 Estados Unidos</a>.</p>
+
+<div class="translators-notes">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.-->
+ </div>
+</div>
+
+<!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.pt-br.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<p>Envie perguntas em geral sobre a FSF e o GNU para <a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>. Também existem <a
+href="/contact/">outros meios de contatar</a> a FSF.  Links quebrados e
+outras correções ou sugestões podem ser enviadas para <a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>.</p>
+
+<p>
+<!-- TRANSLATORS: Ignore the original text in this paragraph,
+        replace it with the translation of these two:
+
+        We work hard and do our best to provide accurate, good quality
+        translations.  However, we are not exempt from imperfection.
+        Please send your comments and general suggestions in this regard
+        to <a href="mailto:address@hidden";>
+
+        &lt;address@hidden&gt;</a>.</p>
+
+        <p>For information on coordinating and submitting translations of
+        our web pages, see <a
+        href="/server/standards/README.translations.html">Translations
+        README</a>. -->
+A equipe de traduções para o português brasileiro se esforça para oferecer
+traduções acuradas e de boa qualidade, mas não estamos isentos de erros. Por
+favor, envie seus comentários e sugestões em geral sobre as traduções para
+<a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>.
+</p><p>Consulte o <a href="/server/standards/README.translations.html">Guia
+para as traduções</a> para mais informações sobre a coordenação e o 
envio de
+traduções das páginas desse site.</p>
+</div>
+
+<!-- Regarding copyright, in general, standalone pages (as opposed to
+     files generated as part of manuals) on the GNU web server should
+     be under CC BY-ND 3.0 US.  Please do NOT change or remove this
+     without talking with the webmasters or licensing team first.
+     Please make sure the copyright date is consistent with the
+     document.  For web pages, it is ok to list just the latest year the
+     document was modified, or published.
+     
+     If you wish to list earlier years, that is ok too.
+     Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
+     years, as long as each year in the range is in fact a copyrightable
+     year, i.e., a year in which the document was published (including
+     being publicly visible on the web or in a revision control system).
+     
+     There is more detail about copyright years in the GNU Maintainers
+     Information document, www.gnu.org/prep/maintain. -->
+<p>Copyright &copy; 2010, 2013, 2014 Free Software Foundation, Inc.</p>
+
+<p>Esta página está licenciada sob uma licença <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/deed.pt_BR";>Creative
+Commons Atribuição-SemDerivações 3.0 Estados Unidos</a>.</p>
+
+<!--#include virtual="/server/bottom-notes.pt-br.html" -->
+<div class="translators-credits">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.-->
+Traduzido por: Rafael Fontenelle <a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>, 2017</div>
+
+<p class="unprintable"><!-- timestamp start -->
+Última atualização: 
+
+$Date: 2018/01/24 12:33:17 $
+
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>
+

Index: gnu/po/about-gnu.pt-br-en.html
===================================================================
RCS file: gnu/po/about-gnu.pt-br-en.html
diff -N gnu/po/about-gnu.pt-br-en.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ gnu/po/about-gnu.pt-br-en.html      24 Jan 2018 12:33:17 -0000      1.1
@@ -0,0 +1,132 @@
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.84 -->
+<title>About the GNU Operating System
+- GNU Project - Free Software Foundation</title>
+<!--#include virtual="/gnu/po/about-gnu.translist" -->
+<!--#include virtual="/server/banner.html" -->
+<h2>About the GNU Operating System</h2>
+
+<blockquote>
+<p>The name &ldquo;GNU&rdquo; is a recursive acronym for &ldquo;GNU's Not
+Unix!&rdquo;; it is pronounced as <a href="/gnu/pronunciation.html">
+one syllable with a hard g</a>.</p>
+</blockquote>
+
+<p>[<a href="/gnu/gnu.html">Other historical and general articles about
+GNU.</a>]</p>
+
+<p>GNU was launched by Richard Stallman (rms) in 1983, as an
+operating system which would be put together by people working
+together for the freedom of all software users to control their
+computing.  rms remains the Chief GNUisance today.</p>
+
+<p>The primary and continuing goal of GNU is to offer a Unix-compatible
+system that would be 100% <a href="/philosophy/free-sw.html">free
+software</a>.  Not 95% free, not 99.5%, but 100%.  The name of the
+system, GNU, is a recursive acronym meaning GNU's Not Unix&mdash;a way
+of paying tribute to the technical ideas of Unix, while at the same time
+saying that GNU is something different.  Technically, GNU is like Unix.
+But unlike Unix, GNU gives its users freedom.</p>
+
+<p><a href="/distros/free-distros.html">Completely free system
+distributions</a> (&ldquo;distros&rdquo;) meeting this goal are
+available today, many using the <a
+href="http://www.fsfla.org/svnwiki/selibre/linux-libre/";>Linux-libre 
kernel</a> (the <a
+href="/gnu/linux-and-gnu.html">relationship between GNU and the Linux
+kernel</a> is described more fully elsewhere).  The <a
+href="/software/software.html">GNU packages</a> have been designed to
+work together so we could have a functioning GNU system.  It has turned
+out that they also serve as a common &ldquo;upstream&rdquo; for many
+distros, so contributions to GNU packages help the free software
+community as a whole.  Naturally, work on GNU is ongoing, with the goal
+to create a system that gives the greatest freedom to computer users.
+GNU packages include user-oriented applications, utilities, tools,
+libraries, even games&mdash;all the programs that an operating system
+can usefully offer to its users.  <a href="/help/evaluation.html">New
+packages are welcome.</a> </p>
+
+<p>Thousands of people have joined in to make GNU the success it is
+today, and there are <a href="/help/help.html">many ways to
+contribute</a>, both technical and non-technical.  GNU developers gather
+from time to time in <a href="/ghm/ghm.html">GNU Hackers Meetings</a>,
+sometimes as part of the larger free software community <a
+href="http://libreplanet.org/";>LibrePlanet</a> conferences.</p>
+
+<p>GNU has been supported in several ways by the <a
+href="http://www.fsf.org/";>Free Software Foundation</a>, the nonprofit
+organization also founded by rms to advocate free software ideals.
+Among other things, the FSF accepts copyright assignments and
+disclaimers, so it can act in court on behalf of GNU programs.  (To be
+clear, contributing a program to GNU does <em>not</em> require
+transferring copyright to the FSF.  If you do assign copyright, the FSF
+will enforce the GPL for the program if someone violates it; if you keep
+the copyright, enforcement will be up to you.)</p>
+
+<p>The ultimate goal is to provide free software to do all of the
+jobs computer users want to do&mdash;and thus make proprietary software
+a thing of the past.</p>
+
+</div><!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<p>Please send general FSF &amp; GNU inquiries to
+<a href="mailto:address@hidden";>&lt;address@hidden&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:address@hidden";>&lt;address@hidden&gt;</a>.</p>
+
+<p><!-- TRANSLATORS: Ignore the original text in this paragraph,
+        replace it with the translation of these two:
+
+        We work hard and do our best to provide accurate, good quality
+        translations.  However, we are not exempt from imperfection.
+        Please send your comments and general suggestions in this regard
+        to <a href="mailto:address@hidden";>
+        &lt;address@hidden&gt;</a>.</p>
+
+        <p>For information on coordinating and submitting translations of
+        our web pages, see <a
+        href="/server/standards/README.translations.html">Translations
+        README</a>. -->
+Please see the <a
+href="/server/standards/README.translations.html">Translations
+README</a> for information on coordinating and submitting translations
+of this article.</p>
+</div>
+
+<!-- Regarding copyright, in general, standalone pages (as opposed to
+     files generated as part of manuals) on the GNU web server should
+     be under CC BY-ND 4.0.  Please do NOT change or remove this
+     without talking with the webmasters or licensing team first.
+     Please make sure the copyright date is consistent with the
+     document.  For web pages, it is ok to list just the latest year the
+     document was modified, or published.
+     
+     If you wish to list earlier years, that is ok too.
+     Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
+     years, as long as each year in the range is in fact a copyrightable
+     year, i.e., a year in which the document was published (including
+     being publicly visible on the web or in a revision control system).
+     
+     There is more detail about copyright years in the GNU Maintainers
+     Information document, www.gnu.org/prep/maintain. -->
+
+<p>Copyright &copy; 2014, 2017, 2018 Free Software Foundation, Inc.</p>
+
+<p>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>.</p>
+
+<!--#include virtual="/server/bottom-notes.html" -->
+
+<p class="unprintable">Updated:
+<!-- timestamp start -->
+$Date: 2018/01/24 12:33:17 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>

Index: gnu/po/pronunciation.pt-br-en.html
===================================================================
RCS file: gnu/po/pronunciation.pt-br-en.html
diff -N gnu/po/pronunciation.pt-br-en.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ gnu/po/pronunciation.pt-br-en.html  24 Jan 2018 12:33:18 -0000      1.1
@@ -0,0 +1,110 @@
+<!--#include virtual="/server/html5-header.html" -->
+<!-- Parent-Version: 1.77 -->
+<title>How To Pronounce GNU
+- GNU Project - Free Software Foundation</title>
+<!--#include virtual="/gnu/po/pronunciation.translist" -->
+<!--#include virtual="/server/banner.html" -->
+<h2>How To Pronounce GNU</h2>
+
+<p>The name &ldquo;GNU&rdquo; is a recursive acronym for &ldquo;GNU's Not 
+Unix!&rdquo;; it is pronounced as one syllable with a hard g, like
+&ldquo;grew&rdquo; but with the letter &ldquo;n&rdquo; instead of
+&ldquo;r&rdquo;.</p>
+
+<p>
+This is a recording of <a href="http://www.stallman.org/";>Richard Stallman</a>
+saying &ldquo;GNU&rdquo; and another with a short explanation about how GNU
+was named:
+</p>
+
+<p><strong>How to say &ldquo;GNU&rdquo;:</strong></p>
+<audio src="/audio/gnu-pronunciation.ogg" controls="controls">
+<a href="/audio/gnu-pronunciation.ogg">How To Say GNU</a>
+</audio>
+
+<p><strong>How GNU Was Named:</strong></p>
+<audio src="/audio/how-gnu-was-named.ogg" controls="controls">    
+<a href="/audio/how-gnu-was-named.ogg">How GNU Was Named</a>
+</audio>
+
+<p>The combination of <a href="/gnu/linux-and-gnu.html">GNU and
+Linux</a> is the <strong>GNU/Linux operating system</strong>, now used
+by millions and sometimes incorrectly called simply
+&ldquo;Linux&rdquo;.</p>
+<p>For more detailed information and history of the GNU
+Operating System visit 
+<a href="/gnu/">http://www.gnu.org/gnu/</a></p>
+
+<h3 id="license">License Of The Recordings</h3>
+
+<p>Copyright (C) 2001 Richard M. Stallman</p>
+
+<p>These recordings are licensed under a <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/";>Creative
+Commons Attribution-NoDerivs 3.0 United States License</a>.</p>
+
+</div><!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<p>Please send general FSF &amp; GNU inquiries to
+<a href="mailto:address@hidden";>&lt;address@hidden&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:address@hidden";>&lt;address@hidden&gt;</a>.</p>
+
+<p><!-- TRANSLATORS: Ignore the original text in this paragraph,
+        replace it with the translation of these two:
+
+        We work hard and do our best to provide accurate, good quality
+        translations.  However, we are not exempt from imperfection.
+        Please send your comments and general suggestions in this regard
+        to <a href="mailto:address@hidden";>
+        &lt;address@hidden&gt;</a>.</p>
+
+        <p>For information on coordinating and submitting translations of
+        our web pages, see <a
+        href="/server/standards/README.translations.html">Translations
+        README</a>. -->
+Please see the <a
+href="/server/standards/README.translations.html">Translations
+README</a> for information on coordinating and submitting translations
+of this article.</p>
+</div>
+
+<!-- Regarding copyright, in general, standalone pages (as opposed to
+     files generated as part of manuals) on the GNU web server should
+     be under CC BY-ND 3.0 US.  Please do NOT change or remove this
+     without talking with the webmasters or licensing team first.
+     Please make sure the copyright date is consistent with the
+     document.  For web pages, it is ok to list just the latest year the
+     document was modified, or published.
+     
+     If you wish to list earlier years, that is ok too.
+     Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
+     years, as long as each year in the range is in fact a copyrightable
+     year, i.e., a year in which the document was published (including
+     being publicly visible on the web or in a revision control system).
+     
+     There is more detail about copyright years in the GNU Maintainers
+     Information document, www.gnu.org/prep/maintain. -->
+
+<p>Copyright &copy; 2010, 2013, 2014 Free Software Foundation, Inc.</p>
+
+<p>This page is licensed under a <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/";>Creative
+Commons Attribution-NoDerivs 3.0 United States License</a>.</p>
+
+<!--#include virtual="/server/bottom-notes.html" -->
+
+<p class="unprintable">Updated:
+<!-- timestamp start -->
+$Date: 2018/01/24 12:33:18 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>
+

Index: licenses/quick-guide-gplv3.pt-br.html
===================================================================
RCS file: licenses/quick-guide-gplv3.pt-br.html
diff -N licenses/quick-guide-gplv3.pt-br.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ licenses/quick-guide-gplv3.pt-br.html       24 Jan 2018 12:33:19 -0000      
1.1
@@ -0,0 +1,389 @@
+<!--#set var="ENGLISH_PAGE" value="/licenses/quick-guide-gplv3.en.html" -->
+
+<!--#include virtual="/server/header.pt-br.html" -->
+<!-- Parent-Version: 1.77 -->
+
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>Um guia rápido para a GPLv3 - Projeto GNU - Free Software 
Foundation</title>
+
+<!--#include virtual="/licenses/po/quick-guide-gplv3.translist" -->
+<!--#include virtual="/server/banner.pt-br.html" -->
+<h2>Um guia rápido para a GPLv3</h2>
+
+<img class="imgright" src="/graphics/gplv3-127x51.png" alt="[Logo da GPLv3]" />
+
+<p>por <strong>Brett Smith</strong></p>
+
+<p>[Esse artigo também está disponível nos formatos <a
+href="/licenses/quick-guide-gplv3.pdf">PDF</a> e <a
+href="/licenses/quick-guide-gplv3.tar.gz">reStructuredText</a>.]</p>
+
+<p>Após um ano e meio de consulta pública, milhares de comentários e quatro
+rascunhos, a versão 3 da Licença Pública Geral GNU (<a class="reference
+external" href="/licenses/gpl-3.0.html">GPLv3</a>) foi finalmente publicada
+em 29 de junho de 2007. Embora tenha havido muita discussão sobre a licença
+desde que o primeiro rascunho apareceu, muitas pessoas não falaram sobre os
+benefícios que ela fornece aos desenvolvedores. Publicamos este guia para
+preencher essa lacuna. Começaremos com uma breve atualização sobre software
+livre, copyleft e os objetivos da GPL. Em seguida, analisaremos as
+principais mudanças na licença para ver como avançam esses objetivos e
+beneficiam os desenvolvedores.</p>
+<div class="section" id="the-foundations-of-the-gpl">
+<h3>Os fundamentos da GPL</h3>
+<p>Ninguém deve ser restrito pelo software que eles usam. Existem quatro
+liberdades que todos os usuários devem ter:</p>
+<ul class="simple">
+<li>a liberdade de usar o software para qualquer finalidade,</li>
+<li>a liberdade de mudar o software de acordo com suas necessidades,</li>
+<li>a liberdade de compartilhar o software com seus amigos e vizinhos e</li>
+<li>a liberdade de compartilhar as mudanças que você faz.</li>
+</ul>
+<p>Quando um programa oferece aos usuários todas essas quatro liberdades, 
nós o
+chamamos de <a class="reference external"
+href="/philosophy/free-sw.html">software livre</a> (“free software”).</p>
+<p>Os desenvolvedores que escrevem software podem lançá-lo nos termos da GNU
+GPL. Quando o fizerem, será software livre e permanecerá software livre, não
+importa quem mude ou distribua o programa. Chamamos isso de copyleft: o
+software é protegido por direitos autorais, mas em vez de usar esses
+direitos para restringir usuários como o software proprietário faz, usamos
+eles para garantir que cada usuário tenha liberdade.</p>
+<p>Atualizamos a GPL para proteger seu copyleft de ser prejudicado por
+desenvolvimentos legais ou tecnológicos. A versão mais recente protege os
+usuários de três ameaças recentes:</p>
+<ul class="simple">
+<li>Tivoização (“Tivoization”): algumas empresas criaram vários tipos 
diferentes
+de dispositivos que executam o software licenciado sob GPL e, em seguida,
+manipularam o hardware para que eles possam mudar o software que está sendo
+executado, mas você não pode. Se um dispositivo pode executar software
+arbitrário, é um computador de uso geral, e seu proprietário deve controlar
+o que faz. Quando um dispositivo o impede de fazer isso, chamamos isso de
+tivoização.</li>
+<li>Leis que proíbem o software livre: Legislação como o Lei dos Direitos
+Autorais do Milênio Digital (“Digital Millennium Copyright Act”) e a
+Diretiva de Direitos Autorais da União Europeia (“European Union Copyright
+Directive”) tornam crime criar ou compartilhar software que possa quebrar o
+DRM (“Gestão Digital de Restrições” ou “Digital Restrictions 
Management”,
+veja <a
+href="#neutralizing-laws-that-prohibit-free-software-but-not-forbidding-drm">abaixo</a>).
+Essas leis não devem interferir com os direitos que a GPL lhe concede.</li>
+<li>Ofertas de patentes discriminatórias: a Microsoft recentemente começou a
+dizer às pessoas que não processariam os usuários de software livre por
+infração de patente &ndash; desde que você obtenha o software de um
+fornecedor que esteja pagando à Microsoft pelo privilégio. Em última
+análise, a Microsoft está tentando coletar royalties pelo uso de software
+livre, o que interfere com a liberdade dos usuários. Nenhuma empresa deve
+ser capaz de fazer isso.</li>
+</ul>
+<p>A versão 3 também possui uma série de melhorias para tornar a licença 
mais
+fácil para todos usarem e entenderem. Mas mesmo com todas essas mudanças, a
+GPLv3 não é uma nova licença radical; em vez disso, é uma evolução da 
versão
+anterior. Embora muito do texto tenha mudado, muito disso simplesmente
+esclarece o que a GPLv2 disse. Com isso em mente, revisemos as principais
+mudanças na GPLv3 e falamos sobre como elas melhoram a licença para usuários
+e desenvolvedores.</p>
+</div>
+<div class="section" 
id="neutralizing-laws-that-prohibit-free-software-but-not-forbidding-drm">
+<h3>Neutralizando leis que proíbem software livre &ndash; mas não proibindo 
DRM</h3>
+<p>Você provavelmente está familiarizado com o Gestão Digital de 
Restrições
+(DRM) em DVDs e outras mídias. Você provavelmente também está familiarizado
+com as leis que tornam ilegal escrever suas próprias ferramentas para
+ignorar essas restrições, como o Lei dos Direitos Autorais do Milênio
+Digital e a Diretiva de Direitos Autorais da União Europeia. Ninguém deve
+ser capaz de lhe impedir de escrever qualquer código que você deseja e GPLv3
+protege esse direito para você.</p>
+<p>É sempre possível usar código sob GPL para escrever software que 
implementa
+DRM. No entanto, se alguém fizer isso com o código protegido pela GPLv3, a
+seção 3 diz que o sistema não irá contar como uma medida de 
“proteção”
+tecnológica efetiva. Isso significa que se você quebrar o DRM, você será
+livre para distribuir seu próprio software que faz isso, e você não será
+ameaçado pela DMCA ou leis similares.</p>
+<p>Como de costume, a GNU GPL não restringe o que as pessoas fazem no 
software;
+simplesmente os impede de restringir os outros.</p>
+</div>
+<div class="section" id="protecting-your-right-to-tinker">
+<h3>Protegendo seu direito de consertar</h3>
+<p>Tivoização é uma tentativa perigosa de reduzir a liberdade dos 
usuários: o
+direito de modificar seu software ficará sem sentido se nenhum dos seus
+computadores o deixar fazê-lo. A GPLv3 interrompe a tivoização, exigindo que
+o distribuidor lhe forneça qualquer informação ou dados necessários para
+instalar o software modificado no dispositivo. Isso pode ser tão simples
+como um conjunto de instruções, ou pode incluir dados especiais, como chaves
+criptográficas ou informações sobre como ignorar uma verificação de
+integridade no hardware. Dependerá de como o hardware foi projetado &ndash;
+mas não importa quais informações você precisa, você deve ser capaz de
+obtê-lo.</p>
+<p>Este requisito tem um escopo limitado. Os distribuidores ainda estão
+autorizados a usar chaves criptográficas para qualquer finalidade, e eles só
+serão obrigados a divulgar uma chave se você precisar dela para modificar o
+software sob a GPL no dispositivo que lhe deram. O próprio Projeto GNU usa o
+GnuPG para comprovar a integridade de todo o software em seu site FTP e
+medidas como essas são benéficas para os usuários. A GPLv3 não impede as
+pessoas de usar criptografia; não queremos isso. Isso impede as pessoas de
+tirar os direitos que a licença lhe fornece &ndash; seja através de leis de
+patentes, tecnologia ou qualquer outro meio.</p>
+</div>
+<div class="section" id="stronger-protection-against-patent-threats">
+<h3>Proteção mais forte contra ameaças de patentes</h3>
+<p>Nos 17 anos desde que a GPLv2 foi publicada, a paisagem de patentes dos
+softwares mudou consideravelmente e as licenças de software livre
+desenvolveram novas estratégias para abordá-las. A GPLv3 reflete essas
+mudanças também. Sempre que alguém transmite software coberto pela GPLv3 que
+eles tenham escrito ou modificado, eles devem fornecer a cada destinatário
+todas as licenças de patente necessárias para exercer os direitos que a GPL
+lhes dá. Além disso, se qualquer licenciado tentar usar um processo de
+patente para impedir que outro usuário exerça esses direitos, sua licença
+será terminada.</p>
+<p>O que isso significa para usuários e desenvolvedores é que eles poderão
+trabalhar com o software coberto com GPLv3 sem se preocupar que um
+contribuidor desesperado tentará processá-los por infração de patente mais
+tarde. Com essas mudanças, a GPLv3 oferece aos seus usuários mais defesas
+contra a agressão de patentes do que qualquer outra licença de software
+livre.</p>
+</div>
+<div class="section" id="clarifying-license-compatibility">
+<h3>Esclarecendo a compatibilidade da licença</h3>
+<p>Se você encontrou um código e queria incorporá-lo em um projeto sob GPL, 
a
+GPLv2 disse que a licença no outro código não tinha permissão para ter
+restrições que ainda não estavam na GPLv2. Sendo este o caso, dizíamos que 
a
+licença era compatível com GPL.</p>
+<p>No entanto, algumas licenças possuíam requisitos que não eram realmente
+restritivos, porque eram tão fáceis de cumprir. Por exemplo, algumas
+licenças dizem que não lhe dão permissão para usar certas marcas
+registradas. Essa não é realmente uma restrição adicional: se essa 
cláusula
+não existisse, você ainda não teria permissão para usar a marca
+registrada. Nós sempre dissemos que essas licenças eram compatíveis com a
+GPLv2 também.</p>
+<p>Agora, a GPLv3 fornece explicitamente a todos a permissão para usar um
+código que tenha requisitos como este. Esses novos termos devem ajudar a
+esclarecer os mal-entendidos sobre quais licenças são compatíveis com GPL,
+por que isso e o que você pode fazer com o código compatível com GPL.</p>
+</div>
+<div class="section" id="new-compatible-licenses">
+<h3>Novas licenças compatíveis</h3>
+<p>Além de esclarecer as regras sobre licenças que já são compatíveis com 
GPL,
+a GPLv3 também é recém-compatível com algumas outras licenças. A Licença
+Apache 2.0 é um exemplo excelente. Muitos desses softwares livres estão
+disponíveis sob esta licença, com comunidades fortes que o cercam. Esperamos
+que esta mudança na GPLv3 promova mais cooperação e compartilhamento na
+comunidade de software livre. O gráfico abaixo ajuda a ilustrar algumas
+relações de compatibilidade comuns entre diferentes licenças de software
+livre:</p>
+
+<!-- GNUN: localize URL /licenses/quick-guide-gplv3-compatibility.png -->
+<img alt="Um gráfico que ilustra relacionamentos de compatibilidade entre 
diferentes
+licenças de software livre. Para detalhes, veja a página da lista de
+licenças da FSF." class="align-center" 
src="/licenses/quick-guide-gplv3-compatibility.png" style="width: 594px; 
height: 498px;" />
+<p>As setas apontando de uma licença para outra indicam que a primeira 
licença
+é compatível com a segunda. Isso é verdade mesmo se você seguir várias 
setas
+para obter uma licença para outra; então, por exemplo, a licença ISC é
+compatível com a GPLv3. A GPLv2 é compatível com GPLv3 se o programa permite
+que você escolha “qualquer versão posterior” da GPL, que é o caso da 
maioria
+dos softwares lançados sob esta licença. Este diagrama não é abrangente
+(veja <a class="reference external" href="/licenses/license-list.html">nossa
+página de licenças</a> para obter uma lista mais completa de licenças
+compatíveis com GPLv2 e GPLv3), mas ilustra claramente que a GPLv3 é
+compatível com quase tudo que a GPLv2 é, e depois alguns.</p>
+<p>A GNU Affero GPL versão 3 também incorporou a reflexão. A Affero GPL
+original foi projetada para garantir que todos os usuários de um aplicativo
+web possam receber seu fonte. A GNU Affero GPL versão 3 amplia esse
+objetivo: é aplicável a todo software interativo de rede, então também
+servirá bem para programas como servidores de jogos. A provisão adicional
+também é mais flexível, de modo que, se alguém usa fonte sob AGPL em um
+aplicativo sem uma interface de rede, eles só terão que fornecer fonte do
+mesma maneira que a GPL sempre exigiu. Ao tornar essas duas licenças
+compatíveis, os desenvolvedores de software interativo de rede poderão
+fortalecer seus copyleft enquanto ainda estão construindo sobre o corpo
+maduro de código sob GPL disponível para eles.</p>
+</div>
+<div class="section" id="more-ways-for-developers-to-provide-source">
+<h3>Mais manerias para os desenvolvedores fornecerem o fonte</h3>
+<p>Um dos requisitos fundamentais da GPL é que quando você distribui código
+objeto para usuários, você também deve fornecer uma maneira de obter o
+fonte. A GPLv2 deu-lhe algumas maneiras de fazer isso e a GPLv3 mantém
+intactos alguns esclarecimentos. Ela também oferece novas maneiras de
+fornecer fonte quando você transmite o código objeto através de uma
+rede. Por exemplo, quando você hospeda um código objeto em um servidor web
+ou FTP, você pode simplesmente fornecer instruções que dizem aos visitantes
+como obter o fonte de um servidor de terceiros. Graças a esta nova opção, o
+cumprimento deste requisito deve ser mais fácil para muitos distribuidores
+pequenos que apenas fazem algumas mudanças em grandes corpos de fontes.</p>
+<p>A nova licença também facilita o transporte de código objeto via
+BitTorrent. Primeiro, as pessoas que estão apenas baixando ou semeando o
+torrent estão isentas dos requisitos da licença para transmitir o
+software. Então, quem inicia o torrent pode fornecer o fonte simplesmente
+dizendo a outros usuários torrent onde está disponível em um servidor de
+rede pública.</p>
+<p>Essas novas opções ajudam a manter a GPL em linha com os padrões da
+comunidade para oferecer fonte, sem tornar mais difícil para os usuários
+obter.</p>
+</div>
+<div class="section" 
id="less-source-to-distribute-new-system-libraries-exception">
+<h3>Menos fonte para distribuir: exceção de novas bibliotecas de sistema</h3>
+<p>Ambas as versões da GPL exigem que você forneça todo o fonte necessário 
para
+criar o software, incluindo bibliotecas de apoio, scripts de compilação, e
+assim por diante. Elas também desenham a linha nas Bibliotecas de Sistema:
+você não precisa fornecer o fonte de determinados componentes principais do
+sistema operacional, como a biblioteca C.</p>
+<p>A GPLv3 ajustou a definição de Biblioteca de Sistema para incluir o 
software
+que pode não vir diretamente com o sistema operacional, mas que todos os
+usuários do software podem razoavelmente esperar. Por exemplo, agora também
+inclui as bibliotecas padrão de linguagens de programação comuns, como
+Python e Ruby.</p>
+<p>A nova definição também deixa claro que você pode combinar o software 
sob
+GPL com Bibliotecas de Sistema incompatíveis com a GPL, como a biblioteca C
+do OpenSolaris, e distribuí-los juntos. Essas mudanças tornarão a vida mais
+fácil para os distribuidores de software livre que desejam fornecer essas
+combinações aos seus usuários.</p>
+</div>
+<div class="section" id="a-global-license">
+<h3>Uma licença global</h3>
+<p>GPLv2 fala muito sobre “distribution” (distribuição) &ndash; quando 
você
+compartilha o programa com outra pessoa, você está distribuindo-o. A licença
+nunca diz qual é a distribuição, porque o termo foi emprestado da lei de
+direitos autorais dos Estados Unidos. Esperávamos que os juízes fossem
+procurar lá pela definição. No entanto, mais tarde descobrimos que as leis
+de direitos autorais em outros países usam a mesma palavra, mas dão
+significados diferentes. Por isso, um juiz em tal país pode analisar a GPLv2
+de forma diferente do que um juiz nos Estados Unidos.</p>
+<p>GPLv3 usa um novo termo, “convey” (transmitir) e fornece uma 
definição para
+esse termo. “Convey” tem o mesmo significado que pretendemos para
+“distribute” (distribuir), mas agora que isso é explicado diretamente na
+licença, deve ser fácil para as pessoas em todos os lugares entenderem o que
+queríamos dizer. Existem outras alterações menores em toda a licença, que
+também ajudarão a garantir sua aplicação em todo o mundo.</p>
+</div>
+<div class="section" 
id="when-the-rules-are-broken-a-smooth-path-to-compliance">
+<h3>Quando as regras são quebradas: um caminho suave para a conformidade</h3>
+<p>Sob a GPLv2, se você violou a licença de forma alguma, seus direitos foram
+perdidos automaticamente e permanentemente. A única maneira de recuperá-los
+era peticionar ao detentor dos direitos autorais. Embora uma forte defesa
+contra as violações seja valiosa, essa política poderia causar muita dor de
+cabeça quando alguém acidentalmente foi de encontro às regras. Pedir a todos
+os detentores de direitos autorais para uma restauração formal da licença
+pode ser trabalhoso e oneroso: uma distribuição típica GNU/Linux se baseia
+no trabalho de milhares.</p>
+<p>A GPLv3 oferece um adiamento por bom comportamento: se você violar a
+licença, você receberá seus direitos de volta uma vez interrompida a
+violação, a menos que um detentor de direitos autorais entre em contato com
+você dentro de 60 dias. Depois de receber esse aviso, você pode ter seus
+direitos totalmente restaurados se você for um violador pela primeira vez e
+corrigir a violação dentro de 30 dias. Caso contrário, você pode resolver a
+questão caso a caso com os detentores de direitos autorais que entraram em
+contato com você e seus direitos serão restaurados depois.</p>
+<p>A conformidade da GPL sempre foi a principal prioridade do Laboratório de
+Conformidade da FSF (FSF Compliance Lab) e outros grupos que aplicam a
+licença em todo o mundo. Essas mudanças asseguram que a conformidade
+continua a ser a principal prioridade para os agentes responsáveis pela
+aplicação e dá incentivos aos incumprimentos para cumprir.</p>
+</div>
+<div class="section" id="the-latest-and-greatest">
+<h3>A melhor e mais recente</h3>
+<p>Algumas dessas mudanças provavelmente parecem menos importantes para você 
do
+que outras. Tudo bem. Todo projeto é diferente e precisa de coisas
+diferentes de sua licença. Mas as probabilidades são de que várias dessas
+melhorias serão de grande ajuda para você e para o seu trabalho.</p>
+<p>E, como um todo, todas essas atualizações representam algo mais: fizemos 
um
+copyleft melhor. Ela faz mais para proteger a liberdade dos usuários, mas
+também permite uma maior cooperação na comunidade de software livre. Mas
+atualizar a licença é apenas parte do trabalho: para que as pessoas obtenham
+os benefícios que a GPLv3 oferece, os desenvolvedores também precisam usá-la
+em seus projetos. Ao lançar seu próprio software sob a nova licença, todos
+os que lidam com ela &ndash; os usuários, outros desenvolvedores,
+distribuidores e até advogados &ndash; se beneficiarão. Esperamos que use a
+GPLv3 para sua próxima versão.</p>
+<p>Se você quiser saber mais sobre como atualizar seu projeto para GPLv3, o
+Laboratório de Conformidade da FSF ficaria feliz em ajudá-lo. No <a
+class="reference external" href="http://www.fsf.org/licensing/";>nosso
+site</a>, você pode encontrar <a class="reference external"
+href="http://www.fsf.org/licensing/licenses/gpl-howto.html";>instruções
+básicas para usar a licença</a> e um <a class="reference external"
+href="http://www.fsf.org/licensing/licenses/gpl-faq.html";>FAQ abordando
+preocupações comuns</a> que as pessoas têm sobre isso. Se a sua situação 
for
+mais complicada do que isso, <a class="reference external"
+href="mailto:licensing&#64;fsf.org";>contacte-nos</a> e faremos o que
+pudermos para ajudá-lo com a sua transição. Juntos, podemos ajudar a
+proteger a liberdade de todos os usuários.</p>
+</div>
+
+<div class="translators-notes">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.-->
+ </div>
+</div>
+
+<!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.pt-br.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<p>Envie perguntas em geral sobre a FSF e o GNU para <a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>. Também existem <a
+href="/contact/">outros meios de contatar</a> a FSF.  Links quebrados e
+outras correções ou sugestões podem ser enviadas para <a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>.</p>
+
+<p>
+<!-- TRANSLATORS: Ignore the original text in this paragraph,
+        replace it with the translation of these two:
+
+        We work hard and do our best to provide accurate, good quality
+        translations.  However, we are not exempt from imperfection.
+        Please send your comments and general suggestions in this regard
+        to <a href="mailto:address@hidden";>
+
+        &lt;address@hidden&gt;</a>.</p>
+
+        <p>For information on coordinating and submitting translations of
+        our web pages, see <a
+        href="/server/standards/README.translations.html">Translations
+        README</a>. -->
+A equipe de traduções para o português brasileiro se esforça para oferecer
+traduções acuradas e de boa qualidade, mas não estamos isentos de erros. Por
+favor, envie seus comentários e sugestões em geral sobre as traduções para
+<a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>.
+</p><p>Consulte o <a href="/server/standards/README.translations.html">Guia
+para as traduções</a> para mais informações sobre a coordenação e o 
envio de
+traduções das páginas desse site.</p>
+</div>
+
+<!-- Regarding copyright, in general, standalone pages (as opposed to
+     files generated as part of manuals) on the GNU web server should
+     be under CC BY-ND 3.0 US.  Please do NOT change or remove this
+     without talking with the webmasters or licensing team first.
+     Please make sure the copyright date is consistent with the
+     document.  For web pages, it is ok to list just the latest year the
+     document was modified, or published.
+     
+     If you wish to list earlier years, that is ok too.
+     Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
+     years, as long as each year in the range is in fact a copyrightable
+     year, i.e., a year in which the document was published (including
+     being publicly visible on the web or in a revision control system).
+     
+     There is more detail about copyright years in the GNU Maintainers
+     Information document, www.gnu.org/prep/maintain. -->
+<p>Copyright &copy; 2007, 2008, 2010, 2013, 2014 Free Software Foundation, 
Inc.</p>
+
+<p>Esta página está licenciada sob uma licença <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/deed.pt_BR";>Creative
+Commons Atribuição-SemDerivações 3.0 Estados Unidos</a>.</p>
+
+<!--#include virtual="/server/bottom-notes.pt-br.html" -->
+<div class="translators-credits">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.-->
+Traduzido por: Rafael Fontenelle <a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>, 2018.</div>
+
+<p class="unprintable"><!-- timestamp start -->
+Última atualização: 
+
+$Date: 2018/01/24 12:33:19 $
+
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>

Index: licenses/translations.pt-br.html
===================================================================
RCS file: licenses/translations.pt-br.html
diff -N licenses/translations.pt-br.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ licenses/translations.pt-br.html    24 Jan 2018 12:33:19 -0000      1.1
@@ -0,0 +1,427 @@
+<!--#set var="ENGLISH_PAGE" value="/licenses/translations.en.html" -->
+
+<!--#include virtual="/server/header.pt-br.html" -->
+<!-- Parent-Version: 1.84 -->
+
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>Traduções não oficiais - Projeto GNU - Free Software 
Foundation</title>
+<meta http-equiv="keywords" content="GNU, FSF, Free Software Foundation, 
Linux, Copyleft, Licenças" />
+
+<!--#include virtual="/licenses/po/translations.translist" -->
+<!--#include virtual="/server/banner.pt-br.html" -->
+<h2>Traduções não oficiais</h2>
+
+<h3 id="UnofficialTranslations">Informações sobre traduções não 
oficiais</h3>
+
+<p>
+A FSF não aprova as traduções de licenças como oficialmente válidas. O
+motivo é que verificá-las seria difícil e caro (precisando da ajuda de
+advogados bilíngues em outros países). Pior ainda, se um erro passasse
+despercebido, os resultados poderiam ser desastrosos para toda a comunidade
+de software livre. Desde que as traduções não sejam oficiais, elas não 
podem
+causar nenhum dano legal.</p>
+
+<p>Para ressaltar o fato de que essas traduções não são oficialmente 
válidas,
+não publicamos as traduções. Para deixar isso claro, não os publicamos no
+gnu.org, apenas o link para eles.</p>
+
+<p>A finalidade de fazer link às traduções é ajudar mais pessoas a entender
+nossas licenças. Para que isso aconteça, as traduções devem ser basicamente
+precisas, mesmo que não sejam perfeitas. Para produzir uma boa tradução, é
+essencial ter conceitos fundamentais totalmente compreendidos, como <a
+href="/licenses/copyleft.html">copyleft</a> e <a
+href="/philosophy/free-sw.html">definição de software livre</a>. Por esse
+motivo, aqueles que desejam contribuir com as traduções devem ter certeza de
+estarem bem familiarizados com esses conceitos, bem como com outros
+princípios filosóficos que podem aparecer no documento.</p>
+
+<p>Damos permissão para publicar traduções de licenças GNU em outros 
idiomas,
+desde que:</p>
+
+<ol id="rules">
+
+<li>Você rotule sua tradução como não oficial para informar as pessoas de 
que
+ela não conta legalmente como substituta da versão autêntica (veja abaixo
+como fazer isso).</li>
+
+<li>Você concorde em instalar mudanças a nosso pedido, se descobrirmos por
+outros amigos do GNU que as mudanças são necessárias para tornar a 
tradução
+mais clara.</li>
+
+<li>A tradução não esteja hospedada em um site comercial e não se refere a
+nenhuma empresa.</li>
+
+<li>A página que contém a tradução contenha nenhum link, exceto para 
fsf.org e
+gnu.org. Podemos aceitar links sobre outros pacotes de software livres, mas
+preferimos evitá-los.</li>
+
+<li>Você permita que outros copiem, modifiquem e republiquem sua tradução 
(e as
+versões modificadas de sua tradução) sujeito a estes termos colocando o
+seguinte aviso: “Você pode publicar esta tradução, modificada ou não
+modificada, apenas nos termos e, <a
+href="/licenses/translations.html">http://www.gnu.org/licenses/translations.html</a>”.</li>
+
+<li>Podemos aceitar pequenas exceções a essas regras em casos legados que 
são
+difíceis de corrigir.</li>
+
+</ol>
+
+<p>Nós não necessariamente fazemos link a todas as traduções não oficiais 
que
+conhecemos em qualquer idioma. Por exemplo, se uma tradução não oficial foi
+feita por uma organização de software livre que conhecemos e confiamos,
+vamos fazer o link a essa tradução ao invés de outros. Ainda não podemos
+torná-la oficial, mas esperamos que provavelmente esteja em sua maioria
+correta.</p>
+
+<p>
+Para rotular suas traduções como não oficiais, adicione o seguinte texto no
+início, tanto em inglês como em português. Substitua “GNU General Public
+License” (Licença Pública Geral GNU) e “GPL” com o nome e abreviação 
da
+licença que você está traduzindo, se não for a GPL:</p>
+
+<blockquote><p dir="ltr" style="text-align:left">
+
+<!--TRANSLATORS: If you translate this paragraph, retain the English
+text and put your translation below.  The entire <blockquote>
+ element
+has <p dir="ltr" style="text-align:left"> to work by default with RTL
+languages when the notice is not translated, so if your language is RTL,
+you *must* put your translation within
+</p><p dir="rtl" style="text-align:right">......</p><p> -->
+This is an unofficial translation of the GNU General Public License into
+<tt>Portuguese</tt>.  It was not published by the Free Software Foundation,
+and does not legally state the distribution terms for software that uses the
+GNU GPL&mdash;only the original English text of the GNU GPL does that.
+However, we hope that this translation will help <tt>language</tt> speakers
+understand the GNU GPL better.</p>
+
+<p>Essa é uma tradução não oficial da Licença Pública Geral GNU para
+<tt>português</tt>. Ela não foi publicada pela Free Software Foundation e
+não estabelece legalmente os termos de distribuição para software que usa a
+GNU GPL &mdash; apenas o texto original em inglês da GNU GPL faz
+isso. Porém, esperamos que essa tradução venha a ajudar so falantes do
+<tt>português</tt> a melhor entender a GNU GPL</p><p>
+</p></blockquote>
+
+<p>Se você fizer uma tradução (de qualquer licença), por favor informe os
+Gerentes de Traduções do GNU <a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>.
+Eles vão verificar para ter certeza de que sua tradução segue as diretrizes
+acima e vão fazer um link para ela a partir desta página.</p>
+
+<h3 id="GPL">A Licença Pública Geral GNU, versão 3</h3>
+
+<!-- Please keep entries alphabetical by language code RT #908353.         -->
+<!-- And to help users, include the language code in brackets.  -->
+<ul>
+  <li><!-- RT #816348 -->
+<code>[ar]</code> tradução para <a
+href="http://fairsultan.files.wordpress.com/2013/03/gpl-3-0-ar1.pdf";>árabe</a>
+da GPL (PDF)</li>
+  <li><!-- RT #710854 -->
+<code>[cs]</code> tradução para <a
+href="http://jxself.org/translations/gpl-3.cz.shtml";>tcheco</a> da GPL</li>
+  <li><!-- RT #1184539 -->
+<code>[da]</code> tradução para dinamarquês da GPL - <a
+href="http://netkoder.dk/licenser/gpl-3.0.da.html";>HTML</a>, <a
+href="http://netkoder.dk/licenser/gpl-3.0.da.txt";>texto simples</a>
+  </li>
+
+  <!-- TODO: the page should say it is CC-BY-ND -->
+<li><code>[de]</code> tradução para <a
+href="http://www.gnu.de/documents/gpl-3.0.de.html";>alemão</a> da GPL</li>
+
+  <!-- link to browsehappy.com; other links
+  <li>
+<code>[eo]</code>
+  <a href="http://zooplah.farvista.net/eo/programado/gpl3.html";>Esperanto</a>
+  translation of the GPL</li>
+-->
+<li><code>[fr]</code> tradução para <a
+href="http://dachary.org/loic/gpl-french.pdf";>francês</a> da GPL (PDF)</li>
+
+  <!-- TODO: the page should say it is CC-BY-ND -->
+<li><code>[hu]</code> tradução para <a
+href="http://gnu.hu/gplv3.html";>húngaro</a> da GPL</li> 
+  <li><code>[it]</code> tradução para italiano da GPL - <a
+href="http://katolaz.homeunix.net/gplv3/gplv3-it-final.html";>HTML</a>, <a
+href="http://katolaz.homeunix.net/gplv3/gplv3-it-final.ps";>PS</a>, <a
+href="http://katolaz.homeunix.net/gplv3/gplv3-it-final.pdf";>PDF</a>, <a
+href="http://katolaz.homeunix.net/gplv3/gplv3-it.tex";>LaTeX</a>
+</li>
+  <li><code>[nl]</code> tradução para <a
+href="http://bartbeuving.files.wordpress.com/2008/07/gpl-v3-nl-101.pdf";>holandês</a>
+da GPL (PDF)</li>
+  <li><!-- RT #1249115 -->
+<code>[pt-br]</code> tradução para português brasileiro da GPL (<a
+href="http://licencas.softwarelivre.org/gpl-3.0.pt-br.html";>HTML</a>, <a
+href="http://licencas.softwarelivre.org/gpl-3.0.pt-br.md";>Markdown</a> <a
+href="http://licencas.softwarelivre.org/gpl-3.0.pt-br.pdf";>PDF</a>, <a
+href="http://licencas.softwarelivre.org/gpl-3.0.pt-br.odt";>ODT</a>)
+  </li>
+  <li><!-- RT #1198511 -->
+<code>[ru]</code> tradução para <a
+href="http://antirao.ru/gpltrans/gplru.pdf";>russo</a> da GPL (PDF)</li>
+  <li><!-- RT #710854 -->
+<code>[sk]</code> tradução para <a
+href="http://jxself.org/translations/gpl-3.sk.shtml";>eslovaco</a> da GPL</li>
+  <li><!-- RT #339241 -->
+<code>[sr]</code> tradução para sérvio da GPL - <a
+href="http://alas.matf.bg.ac.rs/~mr99164/ojl-3.0.html";>HTML</a>, <a
+href="http://alas.matf.bg.ac.rs/~mr99164/gnu/ojl-3.0.pdf";>PDF</a>
+  </li>
+  <li>
+      <!-- RT #977716 -->
+<code>[zh-cn]</code> tradução para <a
+href="//jxself.org/translations/gpl-3.zh.shtml"> chinês (simplificado)</a>
+da GPL</li>
+  <li><!-- RT #715288 and #1198827 -->
+<code>[zh-tw]</code> tradução para <a
+href="http://www.chinasona.org/gnu/gnuv3-tc.html";> chinês (tradicional)</a>
+da GPL</li>
+</ul>
+
+<!--
+<h4>
+Translations Underway</h4>
+<p>The following translation efforts are underway, please contact the
+  person/team if you are willing to help.</p>
+
+<ul>-->
+<!-- many links, some may be problematic; the licensing terms are CC-BY-SA,
+  <li>
+<code>[ca]</code> <a 
href="http://www.softcatala.cat/wiki/GPL3";>Catalan</a></li>
+-->
+<!-- ads
+  <li>
+<code>[ko]</code> <a 
href="http://wiki.kldp.org/wiki.php/GNU/GPLV3Translation";>Korean</a></li>
+-->
+<!-- wikipedia links; the distribution terms are CC-BY-SA
+  <li>
+<code>[ro]</code> <a 
href="http://ro.wikipedia.org/wiki/GPL_(licen%C8%9Ba,_versiunea_3)">Romanian</a></li>
+-->
+<!-- </ul>
+ -->
+<h3 id="AGPL">A Licença Pública Geral Affero GNU, versão 3</h3>
+
+<ul>
+  <li><!-- RT #816657 -->
+<code>[ar]</code> tradução para <a
+href="http://fairsultan.files.wordpress.com/2013/03/agpl-3-0-ar.pdf";>árabe</a>
+da AGPL (PDF)</li>
+  <li><!-- RT #1266581 -->
+<code>[pt-br]</code> tradução para português brasileiro da AGPL (<a
+href="http://licencas.softwarelivre.org/agpl-3.0.pt-br.html";>HTML</a>, <a
+href="http://licencas.softwarelivre.org/agpl-3.0.pt-br.md";>Markdown</a> <a
+href="http://licencas.softwarelivre.org/agpl-3.0.pt-br.pdf";>PDF</a>, <a
+href="http://licencas.softwarelivre.org/agpl-3.0.pt-br.odt";>ODT</a>)
+  </li>
+  <li><!-- RT #1198511 -->
+<code>[ru]</code> tradução para <a
+href="http://antirao.ru/gpltrans/agplru.pdf";>russo</a> da AGPL (PDF)</li>
+</ul>
+
+<h3 id="LGPL">A Licença Pública Geral Menor GNU, versão 3</h3>
+
+<ul>
+
+  <!-- TODO: the page should say it is CC-BY-ND -->
+<li><code>[de]</code> tradução para <a
+href="http://www.gnu.de/documents/lgpl-3.0.de.html";>alemão</a> da LGPL</li>
+
+  <!-- TODO: the page should say it is CC-BY-ND -->
+<li><code>[hu]</code> tradução para <a
+href="http://gnu.hu/lgplv3.html";>húngaro</a> da LGPL</li> 
+
+  <!-- commercial site
+  <li>
+<code>[it]</code>
+  <a href="http://www.posterburner.com/IT_GNU_LESSER_GENERAL_PUBLIC_LICEN.htm";>
+  Italian</a> translation of the LGPL</li>
+-->
+<li><!-- RT #1198511 -->
+<code>[ru]</code> tradução para <a
+href="http://antirao.ru/gpltrans/lgplru.pdf";>russo</a> da LGPL (PDF)</li>
+  <li><code>[zh-cn]</code> tradução para <a
+href="http://www.thebigfly.com/gnu/lgpl/lgpl-v3.php";> chinês
+(simplificado)</a> da LGPL</li>
+  <li><!-- RT #715288 and #1198827-->
+<code>[zh-tw]</code> tradução para <a
+href="http://www.chinasona.org/gnu/gnulgpl-v3-tc.html";> chinês
+(tradicional)</a> da LGPL</li>
+</ul>
+<p>Esperamos que alguém escreva novas traduções não oficiais em checo e
+eslovaco. Algumas foram feitas, mas o tradutor as usou para anunciar um site
+comercial, por isso não estamos dispostos a fazer link para elas.</p>
+
+<!-- RT #716430 -->
+<!--
+<h4>
+Translations Underway</h4>
+<p>The following translation efforts are underway, please contact the
+  person/team if you are willing to help.</p>
+-->
+<h3 id="FDL">A Licença de Documentação Livre GNU, versão 1.3</h3>
+
+<!-- PLEASE DO NOT HOST TRANSLATIONS OF ANY OF OUR LICENSES ON OUR WEBSERVER 
-->
+<!-- THIS MAY LEAD THEM TO BEING CONSTRUED AS 'OFFICIAL'   -->
+<p>FDL 1.3 foi lançada em 3 de novembro de 2008 e é uma modificação
+relativamente menor do FDL 1.2; as únicas mudanças importantes são a 
revisão
+da seção 9 e a adição da seção 11. Assim, as <a
+href="/licenses/old-licenses/fdl-1.2-translations.html"> traduções de FDL
+1.2 </a> podem ajudá-lo a entender FDL 1.3 também. Você pode aprender mais
+sobre as diferenças entre essas duas versões em <a
+href="/licenses/fdl-1.3-faq.html">nosso FAQ</a>.</p>
+
+<!-- Please keep entries alphabetical by language code RT #908353. -->
+<ul>
+  <li><!-- RT #922239 -->
+<code>[fr]</code> tradução para <a
+href="https://www.april.org/files/gfdl.1.3-js.fr.html";>francês</a> da 
GFDL</li>
+
+  <!-- many links
+  <li>
+<code>[ml]</code> <a href="http://ml.wikipedia.org/wiki/WP:GFDL-ml";>
+  Malayalam</a> translation of the GFDL</li>
+-->
+<li><!-- RT #1198511 -->
+<code>[ru]</code> tradução para <a
+href="http://antirao.ru/gpltrans/fdlru.pdf";>russo</a> da GFDL (PDF)</li>
+  <li><code>[zh-cn]</code> tradução para <a
+href="http://www.thebigfly.com/gnu/FDLv1.3/";> chinês (simplificado)</a> da
+GFDL</li>
+  <li><!-- RT #715288 and 1198827 -->
+<code>[zh-tw]</code> tradução para <a
+href="http://www.chinasona.org/gnu/gnufdl-v13-tc.html";> chinês
+(tradicional)</a> da GFDL</li>
+</ul>
+<p>Esperamos que alguém escreva novas traduções não oficiais em checo e
+eslovaco. Algumas foram feitas, mas o tradutor as usou para anunciar um site
+comercial, por isso não estamos dispostos a fazer link para elas.</p>
+
+<!-- RT #716430 -->
+<h4>Traduções em andamento</h4>
+
+<p>Estão em andamento os seguintes esforços de tradução, entre em contato 
com a
+pessoa/equipe, se você estiver disposto a ajudar.</p>
+
+<ul>
+  <li><!-- contact the OP from RT #715051 -->
+<code>[id]</code> indonésio, <a href="mailto:address@hidden";>
+&lt;address@hidden&gt;</a></li>
+</ul>
+
+<h3 id="Exceptions">Traduções não oficiais das exceções das licenças 
GNU</h3>
+
+<h4>GCC Runtime Library Exception, versão 3.1</h4>
+
+<ul>
+  <li><!-- RT #1249115 -->
+<code>[pt-br]</code> tradução para português brasileiro da GCC RLE (<a
+href="http://licencas.softwarelivre.org/gcc-exception-3.1.pt-br.html";>
+HTML</a>, <a
+href="http://licencas.softwarelivre.org/gcc-exception-3.1.pt-br.md";>
+Markdown</a> <a
+href="http://licencas.softwarelivre.org/gcc-exception-3.1.pt-br.pdf";>
+PDF</a>, <a
+href="http://licencas.softwarelivre.org/gcc-exception-3.1.pt-br.odt";>
+ODT</a>)
+  </li>
+</ul>
+<p>A GCC RLE 3.1 foi lançada em 31 de março de 2009 e é uma modificação
+relativamente menor da GCC RLE 3.0. Assim, as <a
+href="/licenses/old-licenses/gcc-exception-translations.html">traduções da
+GCC RLE 3.0</a> podem lhe ajudar a entender a versão 3.1 também.</p>
+
+<p>Esperamos que alguém escreva novas traduções não oficiais em checo e
+eslovaco. Algumas foram feitas, mas o tradutor as usou para anunciar um site
+comercial, por isso não estamos dispostos a fazer link para elas.</p>
+
+<!-- RT #716430 -->
+<h4>GNU Autoconf Configure Script Exception, versão 3</h4>
+<ul>
+  <li><!-- RT #1249115 -->
+<code>[pt-br]</code> tradução para português brasileiro da GNU Autoconf
+Configure Script Exception (<a
+href="http://licencas.softwarelivre.org/autoconf-exception-3.0.pt-br.html";>
+HTML</a>, <a
+href="http://licencas.softwarelivre.org/autoconf-exception-3.0.pt-br.md";>
+Markdown</a> <a
+href="http://licencas.softwarelivre.org/autoconf-exception-3.0.pt-br.pdf";>
+PDF</a>, <a
+href="http://licencas.softwarelivre.org/autoconf-exception-3.0.pt-br.odt";>
+ODT</a>)
+  </li>
+</ul>
+<p>Esperamos que alguém escreva novas traduções não oficiais em checo e
+eslovaco. Algumas foram feitas, mas o tradutor as usou para anunciar um site
+comercial, por isso não estamos dispostos a fazer link para elas.</p>
+
+<!-- RT #716430 -->
+<div class="translators-notes">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.-->
+ </div>
+</div>
+
+<!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.pt-br.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<p>Envie perguntas em geral sobre a FSF e o GNU para <a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>. Também existem <a
+href="/contact/">outros meios de contatar</a> a FSF.  Links quebrados e
+outras correções ou sugestões podem ser enviadas para <a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>.</p>
+
+<p>
+<!-- TRANSLATORS: Ignore the original text in this paragraph,
+        replace it with the translation of these two:
+
+        We work hard and do our best to provide accurate, good quality
+        translations.  However, we are not exempt from imperfection.
+        Please send your comments and general suggestions in this regard
+        to <a href="mailto:address@hidden";>
+
+        &lt;address@hidden&gt;</a>.</p>
+
+        <p>For information on coordinating and submitting translations of
+        our web pages, see <a
+        href="/server/standards/README.translations.html">Translations
+        README</a>. -->
+A equipe de traduções para o português brasileiro se esforça para oferecer
+traduções acuradas e de boa qualidade, mas não estamos isentos de erros. Por
+favor, envie seus comentários e sugestões em geral sobre as traduções para
+<a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>.
+</p><p>Consulte o <a href="/server/standards/README.translations.html">Guia
+para as traduções</a> para mais informações sobre a coordenação e o 
envio de
+traduções das páginas desse site.</p>
+</div>
+
+<p>Copyright &copy; 1996, 1997, 1998, 1999, 2004, 2005, 2006, 2008, 2009, 2010,
+2011, 2014, 2015, 2016, 2017, 2018 Free Software Foundation, Inc.</p>
+
+<p>Esta página está licenciada sob uma licença <a rel="license"
+href="http://creativecommons.org/licenses/by-nd43.0/deed.pt_BR";>Creative
+Commons Atribuição-SemDerivações 4.0 Internacional</a>.</p>
+
+<!--#include virtual="/server/bottom-notes.pt-br.html" -->
+<div class="translators-credits">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.-->
+Traduzido por: Rafael Fontenelle
+<a href="mailto:address@hidden";>&lt;address@hidden&gt;</a>, 2018</div>
+
+<p class="unprintable"><!-- timestamp start -->
+Última atualização: 
+
+$Date: 2018/01/24 12:33:19 $
+
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>

Index: licenses/po/quick-guide-gplv3.pt-br-en.html
===================================================================
RCS file: licenses/po/quick-guide-gplv3.pt-br-en.html
diff -N licenses/po/quick-guide-gplv3.pt-br-en.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ licenses/po/quick-guide-gplv3.pt-br-en.html 24 Jan 2018 12:33:19 -0000      
1.1
@@ -0,0 +1,347 @@
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.77 -->
+<title>A Quick Guide to GPLv3
+- GNU Project - Free Software Foundation</title>
+<!--#include virtual="/licenses/po/quick-guide-gplv3.translist" -->
+<!--#include virtual="/server/banner.html" -->
+<h2>A Quick Guide to GPLv3</h2>
+
+<img class="imgright" src="/graphics/gplv3-127x51.png" alt=" [GPLv3 Logo] " />
+
+<p>by <strong>Brett Smith</strong></p>
+
+<p>[This article is also available in <a
+href="/licenses/quick-guide-gplv3.pdf">PDF</a> and <a
+href="/licenses/quick-guide-gplv3.tar.gz">reStructuredText</a>
+formats.]</p>
+
+<p>After a year and a half of public consultation, thousands of comments, and
+four drafts, version 3 of the GNU General Public License (<a class="reference 
external" href="/licenses/gpl-3.0.html">GPLv3</a>) was
+finally published on June&nbsp;29, 2007.  While there's been a lot of 
discussion about
+the license since the first draft appeared, not many people have talked
+about the benefits that it provides developers.  We've published this guide
+to fill that gap.  We'll start with a brief refresher on free software,
+copyleft, and the goals of the GPL.  We'll then review the major changes in
+the license to see how they advance those goals and benefit developers.</p>
+<div class="section" id="the-foundations-of-the-gpl">
+<h3>The Foundations of the GPL</h3>
+<p>Nobody should be restricted by the software they use.  There are four
+freedoms that every user should have:</p>
+<ul class="simple">
+<li>the freedom to use the software for any purpose,</li>
+<li>the freedom to change the software to suit your needs,</li>
+<li>the freedom to share the software with your friends and neighbors, and</li>
+<li>the freedom to share the changes you make.</li>
+</ul>
+<p>When a program offers users all of these freedoms, we call it <a 
class="reference external" href="/philosophy/free-sw.html">free
+software</a>.</p>
+<p>Developers who write software can release it under the terms of the GNU
+GPL.  When they do, it will be free software and stay free software, no
+matter who changes or distributes the program.  We call this copyleft: the
+software is copyrighted, but instead of using those rights to restrict
+users like proprietary software does, we use them to ensure that
+every user has freedom.</p>
+<p>We update the GPL to protect its copyleft from being undermined by legal or
+technological developments.  The most recent version protects users from
+three recent threats:</p>
+<ul class="simple">
+<li>Tivoization: Some companies have created various different kinds of
+devices that run GPLed software, and then rigged the hardware so that
+they can change the software that's running, but you cannot.  If a device
+can run arbitrary software, it's a general-purpose computer, and its
+owner should control what it does.  When a device thwarts you from doing
+that, we call that tivoization.</li>
+<li>Laws prohibiting free software: Legislation like the Digital Millennium
+Copyright Act and the European Union Copyright Directive make it a crime
+to write or share software that can break DRM (Digital Restrictions
+Management; see 
+<a 
href="#neutralizing-laws-that-prohibit-free-software-but-not-forbidding-drm">below</a>).
  These laws should not
+interfere with the rights the GPL grants you.</li>
+<li>Discriminatory patent deals: Microsoft has recently started
+telling people that they will not sue free software users for patent
+infringement&mdash;as long as you get the software from a vendor
+that's paying Microsoft for the privilege.  Ultimately, Microsoft is
+trying to collect royalties for the use of free software, which
+interferes with users' freedom.  No company should be able to do
+this.</li>
+</ul>
+<p>Version 3 also has a number of improvements to make the license easier for
+everyone to use and understand.  But even with all these changes, GPLv3
+isn't a radical new license; instead it's an evolution of the previous
+version.  Though a lot of text has changed, much of it simply clarifies
+what GPLv2 said.  With that in mind, let's review the major changes in
+GPLv3, and talk about how they improve the license for users and
+developers.</p>
+</div>
+<div class="section" 
id="neutralizing-laws-that-prohibit-free-software-but-not-forbidding-drm">
+<h3>Neutralizing Laws That Prohibit Free Software &mdash; But Not
+Forbidding DRM</h3>
+<p>You're probably familiar with the Digital Restrictions Management
+(DRM) on
+DVDs and other media.  You're probably also familiar with the laws that
+make it illegal to write your own tools to bypass those restrictions, like
+the Digital Millennium Copyright Act and the European Union Copyright
+Directive.  Nobody should be able to stop you from writing any code that
+you want, and GPLv3 protects this right for you.</p>
+<p>It's always possible to use GPLed code to write software that implements
+DRM.  However, if someone does that with code protected by GPLv3, section 3
+says that the system will not count as an effective technological
+&quot;protection&quot; measure.  This means that if you break the DRM, you'll 
be free
+to distribute your own software that does that, and you won't be threatened
+by the DMCA or similar laws.</p>
+<p>As usual, the GNU GPL does not restrict what people do in software; it just
+stops them from restricting others.</p>
+</div>
+<div class="section" id="protecting-your-right-to-tinker">
+<h3>Protecting Your Right to Tinker</h3>
+<p>Tivoization is a dangerous attempt to curtail users' freedom: the
+right to modify your software will become meaningless if none of your
+computers let you do it.  GPLv3 stops tivoization by requiring the
+distributor to provide you with whatever information or data is
+necessary to install modified software on the device.  This may be as
+simple as a set of instructions, or it may include special data such
+as cryptographic keys or information about how to bypass an integrity
+check in the hardware.  It will depend on how the hardware was
+designed&mdash;but no matter what information you need, you must be
+able to get it.</p>
+<p>This requirement is limited in scope.  Distributors are still allowed to
+use cryptographic keys for any purpose, and they'll only be required to
+disclose a key if you need it to modify GPLed software on the device they
+gave you.  The GNU Project itself uses GnuPG to prove the integrity of all
+the software on its FTP site, and measures like that are beneficial to
+users.  GPLv3 does not stop people from using cryptography; we wouldn't
+want it to.  It only stops people from taking away the rights that the
+license provides you&mdash;whether through patent law, technology, or any
+other means.</p>
+</div>
+<div class="section" id="stronger-protection-against-patent-threats">
+<h3>Stronger Protection Against Patent Threats</h3>
+<p>In the 17 years since GPLv2 was published, the software patent landscape
+has changed considerably, and free software licenses have developed new
+strategies to address them.  GPLv3 reflects these changes too.  Whenever
+someone conveys software covered by GPLv3 that they've written or modified,
+they must provide every recipient with any patent licenses necessary to
+exercise the rights that the GPL gives them.  In addition to that, if any
+licensee tries to use a patent suit to stop another user from exercising
+those rights, their license will be terminated.</p>
+<p>What this means for users and developers is that they'll be able to work
+with GPLv3-covered software without worrying that a desperate contributor
+will try to sue them for patent infringement later.  With these changes,
+GPLv3 affords its users more defenses against patent aggression than any
+other free software license.</p>
+</div>
+<div class="section" id="clarifying-license-compatibility">
+<h3>Clarifying License Compatibility</h3>
+<p>If you found some code and wanted to incorporate it into a GPLed project,
+GPLv2 said that the license on the other code was not allowed to have any
+restrictions that were not already in GPLv2.  As long as that was the case,
+we said the license was GPL-compatible.</p>
+<p>However, some licenses had requirements that weren't really restrictive,
+because they were so easy to comply with.  For example, some licenses say
+that they don't give you permission to use certain trademarks.  That's not
+really an additional restriction: if that clause wasn't there, you still
+wouldn't have permission to use the trademark.  We always said those
+licenses were compatible with GPLv2, too.</p>
+<p>Now, GPLv3 explicitly gives everyone permission to use code that has
+requirements like this.  These new terms should help clear up
+misunderstandings about which licenses are GPL-compatible, why that is, and
+what you can do with GPL-compatible code.</p>
+</div>
+<div class="section" id="new-compatible-licenses">
+<h3>New Compatible Licenses</h3>
+<p>In addition to clarifying the rules about licenses that are already
+GPL-compatible, GPLv3 is also newly compatible with a few other licenses.
+The Apache License 2.0 is a prime example.  Lots of great free software is
+available under this license, with strong communities surrounding it.  We
+hope that this change in GPLv3 will foster more cooperation and sharing
+within the free software community.  The chart below helps illustrate some
+common compatibility relationships between different free software
+licenses:</p>
+<!-- GNUN: localize URL /licenses/quick-guide-gplv3-compatibility.png -->
+<img alt="A chart illustrating compatibility relationships between different 
free software licenses.  For details, see the FSF's license list page." 
class="align-center" src="/licenses/quick-guide-gplv3-compatibility.png" 
style="width: 594px; height: 498px;" />
+<p>Arrows pointing from one license to another indicate that the first license
+is compatible with the second.  This is true even if you follow multiple
+arrows to get from one license to the other; so, for example, the ISC
+license is compatible with GPLv3.  GPLv2 is compatible with GPLv3 if the
+program allows you to choose &quot;any later version&quot; of the GPL, which 
is the
+case for most software released under this license.  This diagram is not
+comprehensive (see <a class="reference external" 
href="/licenses/license-list.html">our licenses page</a> for a more complete 
list of licenses
+compatible with GPLv2 and GPLv3), but plainly illustrates that GPLv3
+is compatible with just about everything GPLv2 is, and then some.</p>
+<p>The GNU Affero GPL version 3 has also been brought into the fold.  The
+original Affero GPL was designed to ensure that all users of a web
+application would be able to receive its source.  The GNU Affero GPL
+version 3 broadens this goal: it is applicable to all network-interactive
+software, so it will also work well for programs like game servers.  The
+additional provision is also more flexible, so that if someone uses AGPLed
+source in an application without a network interface, they'll only have to
+provide source in the same sort of way the GPL has always required.
+By making these two licenses compatible, developers of network-interactive
+software will be able to strengthen their copyleft while still building on
+top of the mature body of GPLed code available to them.</p>
+</div>
+<div class="section" id="more-ways-for-developers-to-provide-source">
+<h3>More Ways for Developers to Provide Source</h3>
+<p>One of the fundamental requirements of the GPL is that when you distribute
+object code to users, you must also provide them with a way to get the
+source.  GPLv2 gave you a few ways to do this, and GPLv3 keeps those intact
+with some clarification.  It also offers you new ways to provide source
+when you convey object code over a network.  For instance, when you host
+object code on a web or FTP server, you can simply provide instructions
+that tell visitors how to get the source from a third-party server.  Thanks
+to this new option, fulfilling this requirement should be easier for many
+small distributors who only make a few changes to large bodies of source.</p>
+<p>The new license also makes it much easier to convey object code via
+BitTorrent.  First, people who are merely downloading or seeding the
+torrent are exempt from the license's requirements for conveying the
+software.  Then, whoever starts the torrent can provide source by simply
+telling other torrent users where it is available on a public network
+server.</p>
+<p>These new options help keep the GPL in line with community standards for
+offering source, without making it harder for users to get.</p>
+</div>
+<div class="section" 
id="less-source-to-distribute-new-system-libraries-exception">
+<h3>Less Source to Distribute: New System Libraries Exception</h3>
+<p>Both versions of the GPL require you to provide all the source necessary to
+build the software, including supporting libraries, compilation scripts,
+and so on.  They also draw the line at System Libraries: you're not
+required to provide the source for certain core components of the operating
+system, such as the C library.</p>
+<p>GPLv3 has adjusted the definition of System Library to include software
+that may not come directly with the operating system, but that all users of
+the software can reasonably be expected to have.  For example, it now also
+includes the standard libraries of common programming languages such as
+Python and Ruby.</p>
+<p>The new definition also makes it clear that you can combine GPLed software
+with GPL-incompatible System Libraries, such as OpenSolaris' C library, and
+distribute them both together.  These changes will make life easier for
+free software distributors who want to provide these combinations to their
+users.</p>
+</div>
+<div class="section" id="a-global-license">
+<h3>A Global License</h3>
+<p>GPLv2 talks about &quot;distribution&quot; a lot&mdash;when you
+share the program with someone else, you're distributing it.  The
+license never says what distribution is, because the term was borrowed
+from United States copyright law.  We expected that judges would look
+there for the definition.  However, we later found out that copyright
+laws in other countries use the same word, but give it different
+meanings.  Because of this, a judge in such a country might analyze
+GPLv2 differently than a judge in the United States.</p>
+<p>GPLv3 uses a new term, &quot;convey,&quot; and provides a definition for 
that term.
+&quot;Convey&quot; has the same meaning we intended for 
&quot;distribute,&quot; but now that
+this is explained directly in the license, it should be easy for people
+everywhere to understand what we meant.  There are other minor changes
+throughout the license that will also help ensure it is applied
+consistently worldwide.</p>
+</div>
+<div class="section" 
id="when-the-rules-are-broken-a-smooth-path-to-compliance">
+<h3>When the Rules Are Broken: A Smooth Path to Compliance</h3>
+<p>Under GPLv2, if you violated the license in any way, your rights were
+automatically and permanently lost.  The only way to get them back was to
+petition the copyright holder.  While a strong defense against violations
+is valuable, this policy could cause a lot of headache when someone
+accidentally ran afoul of the rules.  Asking all the copyright holders for
+a formal restoration of the license could be burdensome and costly: a
+typical GNU/Linux distribution draws upon the work of thousands.</p>
+<p>GPLv3 offers a reprieve for good behavior: if you violate the license,
+you'll get your rights back once you stop the violation, unless a copyright
+holder contacts you within 60 days.  After you receive such a notice, you
+can have your rights fully restored if you're a first-time violator and
+correct the violation within 30 days.  Otherwise, you can work out the
+issue on a case-by-case basis with the copyright holders who contacted you,
+and your rights will be restored afterward.</p>
+<p>Compliance with the GPL has always been the top priority of the FSF
+Compliance Lab and other groups enforcing the license worldwide.  These
+changes ensure that compliance remains the top priority for enforcers, and
+gives violators incentive to comply.</p>
+</div>
+<div class="section" id="the-latest-and-greatest">
+<h3>The Latest and Greatest</h3>
+<p>Some of these changes probably seem less important to you than others.
+That's okay.  Every project is different, and needs different things from
+its license.  But odds are that a number of these improvements will help
+you and your work.</p>
+<p>And taken as a whole, all these upgrades represent something more:
+we made a better copyleft.  It does more to protect users' freedom,
+but it also enables more cooperation in the free software community.
+But updating the license is only part of the job: in order for people
+to get the benefits it offers, developers need to use GPLv3 for their
+projects, too.  By releasing your own software under the new license,
+everyone who deals with it&mdash;users, other developers,
+distributors, even lawyers&mdash;will benefit.  We hope you'll use
+GPLv3 for your next release.</p>
+<p>If you'd like to learn more about upgrading your project to GPLv3, the FSF
+Compliance Lab would be happy to assist you.  On <a class="reference external" 
href="http://www.fsf.org/licensing/";>our web site</a>, you can
+find <a class="reference external" 
href="http://www.fsf.org/licensing/licenses/gpl-howto.html";>basic instructions 
for using the license</a>, and an <a class="reference external" 
href="http://www.fsf.org/licensing/licenses/gpl-faq.html";>FAQ addressing
+common concerns</a> that people have about it.  If your situation is more
+complicated than that, please <a class="reference external" 
href="mailto:licensing&#64;fsf.org";>contact us</a> and we'll do what we can to
+help you with your transition.  Together, we can help protect freedom for
+all users.</p>
+</div>
+
+</div><!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<p>Please send general FSF &amp; GNU inquiries to
+<a href="mailto:address@hidden";>&lt;address@hidden&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:address@hidden";>&lt;address@hidden&gt;</a>.</p>
+
+<p><!-- TRANSLATORS: Ignore the original text in this paragraph,
+        replace it with the translation of these two:
+
+        We work hard and do our best to provide accurate, good quality
+        translations.  However, we are not exempt from imperfection.
+        Please send your comments and general suggestions in this regard
+        to <a href="mailto:address@hidden";>
+        &lt;address@hidden&gt;</a>.</p>
+
+        <p>For information on coordinating and submitting translations of
+        our web pages, see <a
+        href="/server/standards/README.translations.html">Translations
+        README</a>. -->
+Please see the <a
+href="/server/standards/README.translations.html">Translations
+README</a> for information on coordinating and submitting translations
+of this article.</p>
+</div>
+
+<!-- Regarding copyright, in general, standalone pages (as opposed to
+     files generated as part of manuals) on the GNU web server should
+     be under CC BY-ND 3.0 US.  Please do NOT change or remove this
+     without talking with the webmasters or licensing team first.
+     Please make sure the copyright date is consistent with the
+     document.  For web pages, it is ok to list just the latest year the
+     document was modified, or published.
+     
+     If you wish to list earlier years, that is ok too.
+     Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
+     years, as long as each year in the range is in fact a copyrightable
+     year, i.e., a year in which the document was published (including
+     being publicly visible on the web or in a revision control system).
+     
+     There is more detail about copyright years in the GNU Maintainers
+     Information document, www.gnu.org/prep/maintain. -->
+
+<p>Copyright &copy; 2007, 2008, 2010, 2013, 2014
+Free Software Foundation, Inc.</p>
+
+<p>This page is licensed under a <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/";>Creative
+Commons Attribution-NoDerivs 3.0 United States License</a>.</p>
+
+<!--#include virtual="/server/bottom-notes.html" -->
+
+<p class="unprintable">Updated:
+<!-- timestamp start -->
+$Date: 2018/01/24 12:33:19 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>

Index: licenses/po/translations.pt-br-en.html
===================================================================
RCS file: licenses/po/translations.pt-br-en.html
diff -N licenses/po/translations.pt-br-en.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ licenses/po/translations.pt-br-en.html      24 Jan 2018 12:33:19 -0000      
1.1
@@ -0,0 +1,376 @@
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.84 -->
+<title>Unofficial Translations
+- GNU Project - Free Software Foundation</title>
+<meta http-equiv="keywords" content="GNU, FSF, Free Software Foundation, 
Linux, Copyleft, Licenses" />
+<!--#include virtual="/licenses/po/translations.translist" -->
+<!--#include virtual="/server/banner.html" -->
+<h2>Unofficial Translations</h2>
+
+<h3 id="UnofficialTranslations">Information about unofficial
+translations</h3>
+
+<p>
+The FSF does not approve license translations as officially valid.
+The reason is that checking them would be difficult and expensive
+(needing the help of bilingual lawyers in other countries).  Even
+worse, if an error did slip through, the results could be disastrous
+for the whole free software community.  As long as the translations
+are unofficial, they can't do any legal harm.</p>
+
+<p>To underscore the fact that these translations are not officially
+valid, we do not publish translations.  To make that clear, we don't
+post them on gnu.org, only link to them.</p>
+
+<p>The purpose of linking to translations is to help more people
+understand our licenses.  In order for them to do that, translations
+need to be basically accurate even if not perfect.  To produce a good
+translation, it is essential to have fully understood fundamental
+concepts such as <a href="/licenses/copyleft.html">copyleft</a> and
+the <a href="/philosophy/free-sw.html">free software definition</a>.
+For this reason, those who wish to contribute translations should make
+sure they are well acquainted with these concepts as well as other
+philosophical principles that may appear in the document.</p>
+
+<p>We give permission to publish translations of GNU licenses
+into other languages, provided that:</p>
+
+<ol id="rules">
+
+<li>You label your translation as unofficial to inform people that
+they do not count legally as substitutes for the authentic version
+(see below for how to do this).</li>
+
+<li>You agree to install changes at our request, if we learn from other
+friends of GNU that changes are necessary to make the translation
+clearer.</li>
+
+<li>The translation is not hosted on a commercial site and does not
+refer to any company.</li>
+
+<li>The page containing the translation should have no links
+except to fsf.org and gnu.org.  We might accept links about
+other free software packages, but we prefer to avoid them.</li>
+
+<li>You permit others to copy, modify, and republish your translation (and
+modified versions of your translation) subject to these terms by placing
+the following notice: &ldquo;You may publish this translation, modified or
+unmodified, only under the terms at 
+<a href="/licenses/translations.html">
+http://www.gnu.org/licenses/translations.html</a>.&rdquo;</li>
+
+<li>We may accept small exceptions to these rules in
+legacy cases that are hard to fix.</li>
+
+</ol>
+
+<p>We do not necessarily link to all the unofficial translations that
+we know of in any given language.  For instance, if one unofficial
+translation was made by a free software organization that we know and
+have confidence in, we will link to that translation rather than others.
+We still can't make it official, but we expect it is probably mostly
+correct.</p>
+
+<p>
+To label your translations as unofficial, please add the
+following text at the beginning,
+both in English and in the language of the translation.  Replace
+<tt>language</tt> with the name of that language, and &ldquo;GNU
+General Public License&rdquo; and &ldquo;GPL&rdquo; with the name and
+abbreviation of the license you're translating, if it's not the
+GPL:</p>
+
+<blockquote><p dir="ltr" style="text-align:left">
+<!--TRANSLATORS: If you translate this paragraph, retain the English
+text and put your translation below.  The entire <blockquote> element
+has <p dir="ltr" style="text-align:left"> to work by default with RTL
+languages when the notice is not translated, so if your language is RTL,
+you *must* put your translation within
+</p><p dir="rtl" style="text-align:right">......</p><p> -->
+This is an unofficial translation of the GNU General Public License
+into <tt>language</tt>.  It was not published by the Free Software
+Foundation, and does not legally state the distribution terms for
+software that uses the GNU GPL&mdash;only the original English text of
+the GNU GPL does that.  However, we hope that this translation will
+help <tt>language</tt> speakers understand the GNU GPL better.
+</p></blockquote>
+
+<p>If you make a translation (of any license), please inform the GNU
+Translation Managers <a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>.
+They will check to make sure that your translation follows the above
+guidelines and make a link to it from this page.</p>
+
+<h3 id="GPL">The GNU General Public License, version 3</h3>
+
+<!-- Please keep entries alphabetical by language code RT #908353.         -->
+<!-- And to help users, include the language code in brackets.  -->
+
+<ul>
+  <li><code>[ar]</code> <!-- RT #816348 -->
+  <a href="http://fairsultan.files.wordpress.com/2013/03/gpl-3-0-ar1.pdf";>
+  Arabic</a> translation of the GPL (PDF)</li>
+  <li><code>[cs]</code> <!-- RT #710854 -->
+  <a href="http://jxself.org/translations/gpl-3.cz.shtml";>Czech</a>
+  translation of the GPL</li>
+  <li><code>[da]</code> <!-- RT #1184539 -->
+  Danish translation of the GPL - 
+  <a href="http://netkoder.dk/licenser/gpl-3.0.da.html";>HTML</a>,
+  <a href="http://netkoder.dk/licenser/gpl-3.0.da.txt";>plain text</a>
+  </li>
+<!-- TODO: the page should say it is CC-BY-ND -->
+  <li><code>[de]</code> <a href="http://www.gnu.de/documents/gpl-3.0.de.html";>
+  German</a> translation of the GPL</li>
+<!-- link to browsehappy.com; other links
+  <li><code>[eo]</code>
+  <a href="http://zooplah.farvista.net/eo/programado/gpl3.html";>Esperanto</a>
+  translation of the GPL</li>
+-->
+  <li><code>[fr]</code> <a href="http://dachary.org/loic/gpl-french.pdf";>
+  French</a> translation of the GPL (PDF)</li>
+<!-- TODO: the page should say it is CC-BY-ND -->
+  <li><code>[hu]</code> <a href="http://gnu.hu/gplv3.html";>Hungarian</a>
+  translation of the GPL</li> 
+  <li><code>[it]</code> Italian translation of the GPL - 
+<a href="http://katolaz.homeunix.net/gplv3/gplv3-it-final.html";>HTML</a>, 
+<a href="http://katolaz.homeunix.net/gplv3/gplv3-it-final.ps";>PS</a>, 
+<a href="http://katolaz.homeunix.net/gplv3/gplv3-it-final.pdf";>PDF</a>, 
+<a href="http://katolaz.homeunix.net/gplv3/gplv3-it.tex";>LaTeX</a>
+</li>
+  <li><code>[nl]</code> <a 
href="http://bartbeuving.files.wordpress.com/2008/07/gpl-v3-nl-101.pdf";>
+  Dutch</a> translation of the GPL (PDF)</li>
+  <li><!-- RT #1249115 --><code>[pt-br]</code>
+   Brazilian Portuguese translation of the GPL
+  (<a href="http://licencas.softwarelivre.org/gpl-3.0.pt-br.html";>HTML</a>,
+   <a href="http://licencas.softwarelivre.org/gpl-3.0.pt-br.md";>Markdown</a>
+   <a href="http://licencas.softwarelivre.org/gpl-3.0.pt-br.pdf";>PDF</a>,
+   <a href="http://licencas.softwarelivre.org/gpl-3.0.pt-br.odt";>ODT</a>)
+  </li>
+  <li><code>[ru]</code> <!-- RT #1198511 -->
+  <a href="http://antirao.ru/gpltrans/gplru.pdf";>Russian</a> translation
+  of the GPL (PDF)</li>
+  <li><code>[sk]</code> <!-- RT #710854 -->
+  <a href="http://jxself.org/translations/gpl-3.sk.shtml";>Slovak</a>
+  translation of the GPL</li>
+  <li><code>[sr]</code> <!-- RT #339241 -->
+  Serbian translation of the GPL - 
+  <a href="http://alas.matf.bg.ac.rs/~mr99164/ojl-3.0.html";>HTML</a>,
+  <a href="http://alas.matf.bg.ac.rs/~mr99164/gnu/ojl-3.0.pdf";>PDF</a>
+  </li>
+  <li><!-- RT #977716 -->
+      <code>[zh-cn]</code>
+         <a href="//jxself.org/translations/gpl-3.zh.shtml">
+         Chinese (Simplified)</a> translation of the GPL</li>
+  <li><code>[zh-tw]</code> <!-- RT #715288 and #1198827 -->
+  <a href="http://www.chinasona.org/gnu/gnuv3-tc.html";>
+  Chinese (Traditional)</a> translation of the GPL</li>
+</ul>
+<!--
+<h4>Translations Underway</h4>
+<p>The following translation efforts are underway, please contact the
+  person/team if you are willing to help.</p>
+
+<ul>-->
+<!-- many links, some may be problematic; the licensing terms are CC-BY-SA,
+  <li><code>[ca]</code> <a 
href="http://www.softcatala.cat/wiki/GPL3";>Catalan</a></li>
+-->
+<!-- ads
+  <li><code>[ko]</code> <a 
href="http://wiki.kldp.org/wiki.php/GNU/GPLV3Translation";>Korean</a></li>
+-->
+<!-- wikipedia links; the distribution terms are CC-BY-SA
+  <li><code>[ro]</code> <a 
href="http://ro.wikipedia.org/wiki/GPL_(licen%C8%9Ba,_versiunea_3)">Romanian</a></li>
+-->
+<!-- </ul> -->
+
+<h3 id="AGPL">The GNU Affero General Public License, version 3</h3>
+
+<ul>
+  <li><code>[ar]</code> <!-- RT #816657 -->
+  <a href="http://fairsultan.files.wordpress.com/2013/03/agpl-3-0-ar.pdf";>
+  Arabic</a> translation of the AGPL (PDF)</li>
+  <li><!-- RT #1266581 --><code>[pt-br]</code>
+   Brazilian Portuguese translation of the AGPL
+  (<a href="http://licencas.softwarelivre.org/agpl-3.0.pt-br.html";>HTML</a>,
+   <a href="http://licencas.softwarelivre.org/agpl-3.0.pt-br.md";>Markdown</a>
+   <a href="http://licencas.softwarelivre.org/agpl-3.0.pt-br.pdf";>PDF</a>,
+   <a href="http://licencas.softwarelivre.org/agpl-3.0.pt-br.odt";>ODT</a>)
+  </li>
+  <li><code>[ru]</code> <!-- RT #1198511 -->
+  <a href="http://antirao.ru/gpltrans/agplru.pdf";>Russian</a> translation
+  of the AGPL (PDF)</li>
+</ul>
+
+<h3 id="LGPL">The GNU Lesser General Public License, version 3</h3>
+
+<ul>
+<!-- TODO: the page should say it is CC-BY-ND -->
+  <li><code>[de]</code> <a href="http://www.gnu.de/documents/lgpl-3.0.de.html";>
+  German</a> translation of the LGPL</li>
+<!-- TODO: the page should say it is CC-BY-ND -->
+  <li><code>[hu]</code> <a href="http://gnu.hu/lgplv3.html";>Hungarian</a>
+  translation of the LGPL</li> 
+<!-- commercial site
+  <li><code>[it]</code>
+  <a href="http://www.posterburner.com/IT_GNU_LESSER_GENERAL_PUBLIC_LICEN.htm";>
+  Italian</a> translation of the LGPL</li>
+-->
+  <li><code>[ru]</code> <!-- RT #1198511 -->
+  <a href="http://antirao.ru/gpltrans/lgplru.pdf";>Russian</a> translation
+  of the LGPL (PDF)</li>
+  <li><code>[zh-cn]</code> <a 
href="http://www.thebigfly.com/gnu/lgpl/lgpl-v3.php";>
+  Chinese (Simplified)</a> translation of the LGPL</li>
+  <li><code>[zh-tw]</code> <!-- RT #715288 and #1198827-->
+  <a href="http://www.chinasona.org/gnu/gnulgpl-v3-tc.html";>
+  Chinese (Traditional)</a> translation of the LGPL</li>
+</ul>
+<p>We hope someone will write new unofficial translations in Czech and 
+Slovak. Some were made, but the translator used them to advertise a 
+commercial site, so we are not willing to link to them.</p>
+<!-- RT #716430 -->
+
+<!--
+<h4>Translations Underway</h4>
+<p>The following translation efforts are underway, please contact the
+  person/team if you are willing to help.</p>
+-->
+
+<h3 id="FDL">The GNU Free Documentation License, version 1.3</h3>
+
+<!-- PLEASE DO NOT HOST TRANSLATIONS OF ANY OF OUR LICENSES ON OUR WEBSERVER 
-->
+<!-- THIS MAY LEAD THEM TO BEING CONSTRUED AS 'OFFICIAL'   -->
+
+<p>FDL 1.3 was released on November 3, 2008, and is a relatively minor
+modification of FDL 1.2; the only major changes are the revision of
+section 9 and the addition of section 11.  Thus,
+the <a href="/licenses/old-licenses/fdl-1.2-translations.html">
+translations of FDL 1.2</a> may help you understand FDL 1.3 as well.
+You can learn more about the differences between these two versions
+in <a href="/licenses/fdl-1.3-faq.html">our FAQ</a>.</p>
+
+<!-- Please keep entries alphabetical by language code RT #908353. -->
+<ul>
+  <li><code>[fr]</code> <!-- RT #922239 -->
+  <a href="https://www.april.org/files/gfdl.1.3-js.fr.html";>
+  French</a> translation of the GFDL</li>
+<!-- many links
+  <li><code>[ml]</code> <a href="http://ml.wikipedia.org/wiki/WP:GFDL-ml";>
+  Malayalam</a> translation of the GFDL</li>
+-->
+  <li><code>[ru]</code> <!-- RT #1198511 -->
+  <a href="http://antirao.ru/gpltrans/fdlru.pdf";>Russian</a> translation
+  of the GFDL (PDF)</li>
+  <li><code>[zh-cn]</code> <a href="http://www.thebigfly.com/gnu/FDLv1.3/";>
+  Chinese (Simplified)</a> translation of the GFDL</li>
+  <li><code>[zh-tw]</code> <!-- RT #715288 and 1198827 -->
+  <a href="http://www.chinasona.org/gnu/gnufdl-v13-tc.html";>
+  Chinese (Traditional)</a> translation of the GFDL</li>
+</ul>
+<p>We hope someone will write new unofficial translations in Czech and 
+Slovak. Some were made, but the translator used them to advertise a 
+commercial site, so we are not willing to link to them.</p>
+<!-- RT #716430 -->
+
+<h4>Translations Underway</h4>
+
+<p>The following translation efforts are underway, please contact the
+  person/team if you are willing to help.</p>
+
+<ul>
+  <li><code>[id]</code> <!-- contact the OP from RT #715051 -->
+  Indonesian, <a href="mailto:address@hidden";>
+  &lt;address@hidden&gt;</a></li>
+</ul>
+
+<h3 id="Exceptions">Unofficial translations of exceptions to GNU
+licenses</h3>
+
+<h4>GCC Runtime Library Exception, version 3.1</h4>
+
+<ul>
+  <li><!-- RT #1249115 --><code>[pt-br]</code>
+   Brazilian Portuguese translation of the GCC RLE
+  (<a href="http://licencas.softwarelivre.org/gcc-exception-3.1.pt-br.html";>
+     HTML</a>,
+   <a href="http://licencas.softwarelivre.org/gcc-exception-3.1.pt-br.md";>
+     Markdown</a>
+   <a href="http://licencas.softwarelivre.org/gcc-exception-3.1.pt-br.pdf";>
+     PDF</a>,
+   <a href="http://licencas.softwarelivre.org/gcc-exception-3.1.pt-br.odt";>
+     ODT</a>)
+  </li>
+</ul>
+<p>GCC RLE 3.1 was released on March 31, 2009, and is a relatively minor
+modification of GCC RLE 3.0.  Thus, the <a
+href="/licenses/old-licenses/gcc-exception-translations.html">translations
+of GCC RLE 3.0</a> may help you understand version 3.1 as well.</p>
+
+<p>We hope someone will write new unofficial translations in Czech and 
+Slovak. Some were made, but the translator used them to advertise a 
+commercial site, so we are not willing to link to them.</p>
+<!-- RT #716430 -->
+
+<h4>GNU Autoconf Configure Script Exception, version 3</h4>
+<ul>
+  <li><!-- RT #1249115 --><code>[pt-br]</code>
+   Brazilian Portuguese translation of GNU Autoconf Configure Script Exception
+  (<a 
href="http://licencas.softwarelivre.org/autoconf-exception-3.0.pt-br.html";>
+     HTML</a>,
+   <a href="http://licencas.softwarelivre.org/autoconf-exception-3.0.pt-br.md";>
+     Markdown</a>
+   <a 
href="http://licencas.softwarelivre.org/autoconf-exception-3.0.pt-br.pdf";>
+     PDF</a>,
+   <a 
href="http://licencas.softwarelivre.org/autoconf-exception-3.0.pt-br.odt";>
+     ODT</a>)
+  </li>
+</ul>
+<p>We hope someone will write new unofficial translations in Czech and 
+Slovak. Some were made, but the translator used them to advertise a 
+commercial site, so we are not willing to link to them.</p>
+<!-- RT #716430 -->
+</div><!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<p>Please send general FSF &amp; GNU inquiries to <a
+href="mailto:address@hidden";>&lt;address@hidden&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:address@hidden";>&lt;address@hidden&gt;</a>.</p>
+
+<p><!-- TRANSLATORS: Ignore the original text in this paragraph,
+        replace it with the translation of these two:
+
+        We work hard and do our best to provide accurate, good quality
+        translations.  However, we are not exempt from imperfection.
+        Please send your comments and general suggestions in this regard
+        to <a href="mailto:address@hidden";>
+        &lt;address@hidden&gt;</a>.</p>
+
+        <p>For information on coordinating and submitting translations of
+        our web pages, see <a
+        href="/server/standards/README.translations.html">Translations
+        README</a>. -->
+Please see the <a
+href="/server/standards/README.translations.html">Translations README</a> for
+information on coordinating and submitting translations of this article.</p>
+</div>
+
+<p>Copyright &copy; 1996, 1997, 1998, 1999, 2004, 2005, 2006, 2008, 2009,
+2010, 2011, 2014, 2015, 2016, 2017, 2018 Free Software Foundation, Inc.</p>
+
+<p>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>.</p>
+
+<!--#include virtual="/server/bottom-notes.html" -->
+
+<p class="unprintable">Updated:
+<!-- timestamp start -->
+$Date: 2018/01/24 12:33:19 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>

Index: philosophy/po/dat.zh-cn-en.html
===================================================================
RCS file: philosophy/po/dat.zh-cn-en.html
diff -N philosophy/po/dat.zh-cn-en.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ philosophy/po/dat.zh-cn-en.html     24 Jan 2018 12:33:20 -0000      1.1
@@ -0,0 +1,409 @@
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.77 -->
+
+<title>The Right Way to Tax DAT - GNU Project - Free Software 
Foundation</title>
+
+<!--#include virtual="/philosophy/po/dat.translist" -->
+<!--#include virtual="/server/banner.html" -->
+
+<h2>The Right Way to Tax DAT</h2>
+
+<p>by <a href="http://www.stallman.org/";><strong>Richard
+Stallman</strong></a></p>
+
+<p><em>[This article does not concern software, not directly.  It
+concerns a parallel issue about sharing copies of music.]</em></p>
+
+<p><em>[The article was first published in Wired magazine in 1992; the
+text has not been changed; instead, I have added notes, in square
+brackets and with italics or other emphasis.]</em></p>
+
+<p><em>[The original article addressed the (then hypothetical) issue
+of sharing music using (then just appearing) digital audio tape
+recorders, since that is what the proposed US tax law was supposed to
+address.  Nowadays it could be applied to Internet file
+sharing.]</em></p>
+
+<p><em>[Another approach developed by the late Francis Muguet with my
+assistance, which includes some of these ideas, is called
+the Global Patronage
+system (in French, M&eacute;c&eacute;nat Global).  I support both
+solutions; that is to say, I favor adopting either one.]</em></p>
+
+<p>Record company magnates don't like the digital audio tape recorder
+(<acronym title="Digital Audio Tape">DAT</acronym>), which can make
+perfect copies of musical recordings.  They fear that customers will
+copy music themselves, and stop buying prerecorded music.</p>
+
+<p>Threatening lawsuits, they have obtained from the manufacturers of
+DATs an agreement to pay a fee for each DAT unit and each DAT tape
+sold to consumers.  This fee is to be divided among various
+participants in the music business: musicians, composers, music
+publishers and record companies.  In addition, DAT manufacturers have
+agreed to cripple DAT units so that they cannot make a copy of a copy
+of a prerecorded piece.</p>
+
+<p>Now the record companies have asked Congress to enact a law turning
+this fee into a tax and prohibiting manufacture of DAT tapedecks that
+function without imposed limitations.</p>
+
+<p>The stated purpose of the tax is to &ldquo;compensate&rdquo;
+musicians for copying done by individuals using DATs.  However, 57
+percent of the funds collected would go to record companies and music
+publishers&mdash;leaving less than half to the people who participate
+in the creative process.  Most of these remaining funds would go to
+musical superstars, and thus would do little to encourage musical
+creativity.  Meanwhile, DAT users would be unable to make full use of
+the power of DAT technology.</p>
+
+<p>Here is a proposal for a different system for taxing DATs and DAT
+tape&mdash;one designed to support music rather than cater to vested
+interests.</p>
+
+<ul>
+<li>Collect funds with a tax on DAT machines and DAT tapes, as the
+current proposal provides.</li>
+<li>Use a survey system to measure the extent of copying of each
+musical piece.</li>
+<li>Distribute these funds entirely to the people who create
+music.</li>
+<li>Adjust each contributor's share so that it increases more slowly
+per copy as it gets larger.  This spreads the funds more widely to
+support a larger number of musicians adequately.</li>
+<li>Make no restrictions on the functioning of DATs.</li>
+</ul>
+
+<h3>What is the purpose of copyright?</h3>
+
+<p>The record industry presents its proposal as a way to
+&ldquo;compensate&rdquo; musicians, assuming that they are entitled to
+be paid for any copy made.  Many Americans believe that copyright law
+reflects a natural right of authors or musicians&mdash;that these are
+entitled to special consideration from public policy.  However, any
+lawyer specializing in the field knows this is a misunderstanding, a
+view rejected by the American legal system.</p>
+
+<p>The stated purpose of copyright, given in the U.S. Constitution, is
+to &ldquo;promote the progress of science and the useful arts&rdquo;.
+Progress in music means new and varied music for the public to enjoy:
+copyright is supposed to promote a public good, not a private one.</p>
+
+<p>Yet copyright is often thought of as a natural right by laymen and
+politicians, which often leads to wrong decisions about copyright
+policy.  Even courts, defining the details of the copyright system,
+often let this thought creep back implicitly even though it is
+supposed to be excluded.  This is a conceptual error because it
+mistakes a means (copyright) to a larger end (progress) for an end in
+itself.</p>
+
+<p>Promoting progress in the arts does not inherently justify the idea
+that authors are entitled to any particular sort of copyright, or even
+that copyright should exist at all.  Copyright is justified if the
+benefits of progress exceeds the burden that copyright imposes on
+everyone except the copyright holder.</p>
+
+<p>How do we make this cost/benefit comparison?  It depends partly on
+facts (how does a particular law affect musical activity and music
+users) and partly on our value judgements about those results.</p>
+
+<p>Let's assume that it is worth paying a DAT tax if the result is a
+significant increase in musical activity, and investigate how we
+should arrange the details of this tax in order to maximize the
+benefit.  But first, let's review basic principles and facts which
+have a bearing on the inquiry.</p>
+
+<h3>Diminishing returns</h3>
+
+<p>The law of diminishing returns is a general principle of economics.
+It states that each additional increment of efforts or funds spent on
+a given goal typically produces a smaller and smaller increment in the
+results.  There are exceptions to this law, but they are local; if you
+keep on increasing the inputs, you eventually leave the exceptions
+behind.</p>
+
+<p>For example, you can make traffic flow more smoothly by improving
+roads.  Adding one lane to 20 miles of congested roads in a city might
+increase the average traffic speed by 15 miles an hour.  Adding a
+second lane to those roads will not give the same improvement; this
+might increase the average speed by only 5 more miles an hour.  The
+next additional lane might make no noticeable difference if the
+traffic jams are already gone.  Yet each successive lane will cause
+greater dislocation as more and more buildings must be torn down to
+make room.</p>
+
+<p>When applied to the activities of musicians, diminishing returns
+tells us that each successive increase in the income of musicians will
+have a smaller effect on the amount of creativity in music.</p>
+
+<p>Diminishing returns is the first reason to reject the idea that any
+use of music &ldquo;should&rdquo; be covered by copyright.  There is
+nothing to gain by trying to guarantee owners control of every
+possible aspect of the use of music or to give them a financial stake
+in every possible aftermarket.  Extending copyright can only
+&ldquo;promote progress&rdquo; up to a certain point.  Further
+extensions merely increase what the public pays to the owners for what
+they will do anyway.  Extending copyright beyond that point is
+certainly undesirable.</p>
+
+<h3>Trade-offs</h3>
+
+<p>Those with a vested interest in extending copyright start the
+discussion by claiming that copyright &ldquo;should&rdquo; be extended
+as far as it can go.  But the principle of diminishing returns renders
+this claim implausible.  So they fall back on the position that
+copyright should be extended to maximize the rate of progress.  But
+this too is wrong, because it ignores the existence of other
+trade-offs.  Copyright imposes costs and burdens on the public, like
+any other government project.  The benefit may not be worth the
+price.</p>
+
+<p>Government fills many important functions, but few would say that
+any one of these functions should be expanded to maximize output.  For
+example, governments build roads, and this is very useful.  But few
+leaders would advocate building every road that could be built.  Road
+construction is expensive, and citizens have other uses for their
+money.  Too much concentration on building roads means that other
+social and individual needs will be unmet.</p>
+
+<p>The same considerations apply to individual decisions.  By spending
+more money, you can buy a bigger and fancier house.  Most people would
+prefer the more expensive house, all else being equal.  But given
+finite resources, at some point spending more on a house becomes a
+poor allocation of them.</p>
+
+<p>Copyright does not directly spend public funds, but it does impose
+a cost&mdash;a loss of freedom&mdash;on every citizen.  The wider the
+scope of copyright, the more freedom we pay.  We might prefer to
+exercise some of our freedoms rather than trade them away.  We must
+judge any decision in copyright policy by comparing the benefits with
+the costs.</p>
+
+<h3>&ldquo;Incentive&rdquo; is the wrong concept</h3>
+
+<p>The idea of providing a monetary incentive for making music is
+based on a misunderstanding.  Musicians hope primarily for other kinds
+of reward; they must.  Very few musicians get rich from their music; a
+talented person whose primary goal is wealth would seek it in other
+ways.</p>
+
+<p>In fact, psychological studies show that the desire for an
+extrinsic reward (such as profit) generally hampers creative
+activities such as writing music.  The people who can do them well are
+usually those who do them mostly for their own sake.</p>
+
+<p>This is not to say that musicians don't care about being paid.
+Most hope to make a living from music so they will be free to devote
+their time to it.  As long as they earn enough to live, they will make
+music as best they can.  We might wish them to earn somewhat more than
+just enough, so they can live as well as most Americans.  But to offer
+them wealth beyond this gains the public little&mdash;it is a matter
+of diminishing returns.</p>
+
+<p>With this understanding, let's consider how a tax on DAT tape could
+be designed to serve the intended purpose of copyright.</p>
+
+<h3>Who should get the funds</h3>
+
+<p>If the purpose of the DAT tax is to better reward musicians and
+composers, then all the money collected should go to them&mdash;not
+just 43 percent.  The musicians and composers are the ones who truly
+create the music.  In principle, we could do without record companies
+entirely.</p>
+
+<p>Record companies do provide a useful service: they distribute
+prerecorded copies of music, usually of high quality.  This service is
+widely used, and will probably remain so.  And it is right that the
+purchasers of prerecorded copies should pay for this service.  But
+listeners making copies for themselves or their friends do not consume
+this service; they use only the work of the musicians and composers.
+The record companies contribute only incidentally and their role is
+not essential.</p>
+
+<h3>Dividing the funds</h3>
+
+<p>What share of the tax revenues should each musician or composer
+get?  The record company proposal would divide the money in proportion
+to record sales.</p>
+
+<p>It makes sense to distribute the funds based on how much that
+musician's work is copied, more or less.  But strict proportionality
+is not the best apportionment.  If each musician gets a share in
+strict proportion to the amount of copying of his or her music, then a
+large share will go to make a few superstars even richer than they are
+now.  This won't do much to promote musical culture or diversity.</p>
+
+<p>We can promote music more effectively by making any one musician's
+share of the tax revenues taper off as copies increase.  For example,
+we could calculate an &ldquo;adjusted number of copies&rdquo; which,
+beyond a certain point, increases more slowly than the actual
+number.</p>
+
+<p>The effect of tapering off will be to spread the money more widely,
+supporting more musicians at an adequate standard of living.  This
+encourages diversity, which is what copyright is supposed to do.</p>
+
+<p>The US government has already established a program to fund
+diversity in the arts: the 
+<acronym title="National Endowment for the Arts">NEA</acronym>.
+However, NEA grants involve discretionary power, which makes them a
+center for controversy, sometimes because a few members of the public
+strongly dislike the work, and sometimes because hardly anyone
+particularly likes it.  Spreading out DAT tax revenues will also have
+the effect of supporting less popular musicians.  However, it will not
+support musicians whose work nobody likes.  In addition, since it
+involves no discretion, no arbitrary decisions, there is little room
+for objection on account of any particular case.</p>
+
+<p><em>[I was later asked an interesting question: what organization would
+&ldquo;manage&rdquo; the distribution of these funds.  Since this is
+tax money, a government agency should collect the tax and distribute
+the funds.  Private organizations should not be involved.]</em></p>
+
+<h3>Encouraging home copying</h3>
+
+<p>The record company proposal includes a requirement to make it
+difficult for home listeners to make copies.  Specifically, it
+requires that consumer DAT machines refuse to copy a copy that was
+made on a consumer DAT machine.  The argument for this requirement is
+based on the assumption that home copying is somehow unfair.</p>
+
+<p>In the past, many people have considered it unfair, because it
+reduced the income of musicians.  The DAT tax makes this reason
+obsolete.  Once home copying does contribute to the income of
+musicians, through the DAT tax, the reason to discourage home copying
+disappears.</p>
+
+<p>Therefore, if a DAT tax is adopted, the ability to copy DAT tapes
+should not be restricted.  Home copying is more efficient than record
+companies and record stores; music lovers should be encouraged to use
+home copying as much as possible.</p>
+
+<h3>Measuring the use of each piece of music</h3>
+
+<p>Today, nearly all the recorded music in the United States is
+purchased in record stores; home copying is but a small fraction.
+This will probably remain true for a long time, because record stores
+offer a place where a person can go to find a particular piece or to
+browse a wide selection.  While this remains true, we can usually
+estimate the audience of a given piece fairly well by counting record
+sales.</p>
+
+<p>Eventually, home copying may become so widespread that estimating
+its extent from sales figures may be unsatisfactory.  This is already
+unsatisfactory for musicians who distribute independently without the
+help of record companies; and if any musicians need additional
+support, these are the ones.  We need another way to estimate usage of
+any given piece, in order to distribute the tax funds.</p>
+
+<p>We can make these estimates by survey.  From time to time, survey
+staff would ask randomly chosen members of the public to show what
+copies they have made of copyrighted music.  The citizens asked would
+not be required to answer.  But no penalty and no guilt would attach
+to having made copies, so most people will be glad to participate.
+Fans will hope to be chosen so that they can contribute to the count
+for their favorite musical groups.</p>
+
+<p>To make the survey more efficient and broader-based (and thus more
+accurate), it could be automated.  The survey bureau could mail
+read-write memory cards to the chosen participants, who would connect
+them momentarily to their DAT units and then mail them back.  With
+proper design, the survey bureau would have no way of knowing who had
+sent in any particular card, and thus no information about who had
+copied what, but they would still have an accurate total.</p>
+
+<h3>Conclusion</h3>
+
+<p>The record companies have proposed an excellent scheme for taxing
+the public to increase their own income, but this isn't a legitimate
+purpose of copyright.  Through due attention to the ends of copyright
+rather than past means, we can design a system which supports
+musicians while giving citizens full freedom to copy music as they
+wish.</p>
+
+<h3>What You Can Do</h3>
+
+<p><em>[This section is no longer applicable today; it is too late,
+because the DAT tax bill was adopted in 1992&mdash;and DAT
+recorders are obsolete nowadays.  However, the same method can support
+musicians and other artists in a world where sharing copies on the
+Internet has been legalized.]</em></p>
+
+<p>Record company lobbyists are working hard to pass their form of DAT
+tax.  There is little organized opposition, and little public debate.
+Their bill has already been sent out of committee in the Senate.</p>
+
+<p>This article proposes an alternative to the record company plan.
+In order for this alternative, or any alternative, to have a chance,
+we must first prevent the hasty adoption of the record company plan.
+To help accomplish this, please write letters to:</p>
+
+<blockquote>
+<p>Congressman Barney Frank<br />
+437 Cherry St<br />
+West Newton, MA 02165</p>
+<p>Senator Metzenbaum<br />
+United States Senate<br />
+Washington, DC 20510</p>
+<p>House Subcommittee on Intellectual Property<br />
+House of Representatives<br />
+Washington, DC 20515</p>
+</blockquote>
+
+<p>Urge Congress to reject the record company bill so that this and
+other alternatives can be properly considered.  It takes just a few
+minutes to write a short letter, but in combination with other
+people's letters it can do a great deal of good.</p>
+
+<p>If you know any musicians, composers, or songwriters, give them
+copies of this article.  Many musicians prefer this alternative to the
+record company tax plan, and they are strongly motivated to act on
+their concern.</p>
+
+</div><!-- for id="content", starts in the include above -->
+
+<!--#include virtual="/server/footer.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<p>Please send general FSF &amp; GNU inquiries to
+<a href="mailto:address@hidden";>&lt;address@hidden&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:address@hidden";>&lt;address@hidden&gt;</a>.</p>
+
+<p><!-- TRANSLATORS: Ignore the original text in this paragraph,
+        replace it with the translation of these two:
+
+        We work hard and do our best to provide accurate, good quality
+        translations.  However, we are not exempt from imperfection.
+        Please send your comments and general suggestions in this regard
+        to <a href="mailto:address@hidden";>
+        &lt;address@hidden&gt;</a>.</p>
+
+        <p>For information on coordinating and submitting translations of
+        our web pages, see <a
+        href="/server/standards/README.translations.html">Translations
+        README</a>. -->
+Please see the <a
+href="/server/standards/README.translations.html">Translations
+README</a> for information on coordinating and submitting translations
+of this article.</p>
+</div>
+
+<p>Copyright &copy; 1992, 2010, 2014 Richard M. Stallman</p>
+
+<p>This page is licensed under a <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/";>Creative
+Commons Attribution-NoDerivs 3.0 United States License</a>.</p>
+
+<!--#include virtual="/server/bottom-notes.html" -->
+
+<p class="unprintable">Updated:
+<!-- timestamp start -->
+$Date: 2018/01/24 12:33:20 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>

Index: philosophy/po/drdobbs-letter.zh-cn-en.html
===================================================================
RCS file: philosophy/po/drdobbs-letter.zh-cn-en.html
diff -N philosophy/po/drdobbs-letter.zh-cn-en.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ philosophy/po/drdobbs-letter.zh-cn-en.html  24 Jan 2018 12:33:20 -0000      
1.1
@@ -0,0 +1,144 @@
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.77 -->
+<title>Letter to the Editor of Dr. Dobb's Journal
+- GNU Project - Free Software Foundation</title>
+<!--#include virtual="/philosophy/po/drdobbs-letter.translist" -->
+<!--#include virtual="/server/banner.html" -->
+<h2>Letter to the Editor of Dr. Dobb's Journal</h2>
+
+<p>
+Dear Editor,
+</p>
+<p>
+I am sure you don't realize how ironic it is to associate me and Tim
+O'Reilly with &ldquo;open source&rdquo;.
+</p>
+<p>
+If the House Un-American Activities Committee asked me, &ldquo;Are you
+now or have you ever been a supporter of the open source
+movement,&rdquo; I could proudly and cheerfully say no.  I've been
+campaigning since 1984 for <em>free software</em>&mdash;free as in
+freedom.  (See the GNU Manifesto, Dr. Dobb's Journal, Sept. 1985.)
+</p>
+<p>
+Free software means, roughly, that you are free to study what it does,
+free to change it, free to redistribute it, and free to publish
+improved versions.
+(See <a 
href="/philosophy/free-sw.html">http://www.gnu.org/philosophy/free-sw.html</a>
+for more details.)  You deserve these freedoms; everyone deserves
+them.  I wrote the GNU General Public License (GNU GPL), the target
+of <a href="/philosophy/gpl-american-way.html">Microsoft's greatest
+ire</a>, to defend these freedoms for all users, in the spirit of the
+free software movement.
+</p>
+<p>
+Years later, in 1998, another group began operating under the term
+&ldquo;open source&rdquo;.  They have contributed to the free software
+community in practical ways, but they stand for very different views.
+They studiously avoid the issues of freedom and principle that we
+raise in the free software movement; they cite only short-term
+practical benefits as the reasons for what they do.
+</p>
+<p>
+Their stated definition for the term &ldquo;open source&rdquo; is
+somewhat broader than free software, and thus includes my work.  But
+describing the GNU GPL as an &ldquo;open source license,&rdquo; as
+Microsoft did, is more than half misleading.  The GNU GPL embodies the
+firm philosophy of the free software movement; it doesn't come from
+the open source movement.  I am not a supporter of the open source
+movement, and never have been.
+</p>
+<p>
+Tim O'Reilly, by contrast, is a pillar of the open source movement, at
+least to hear him tell it.  However, if you look at actions rather
+than words, most of the manuals published by O'Reilly Associates do
+not qualify as open source, let alone as free.  The handful of free
+titles are exceptions.  He could easily excuse himself to
+<abbr title="House Un-American Activities 
Committee">HUAC</abbr>&mdash;&ldquo;Yes, 
+I talked about open source, but I didn't really do much of it.&rdquo;
+</p>
+<p>
+If O'Reilly moves to selling free-as-in-freedom books in the future, he
+could become a true supporter of the free software movement, or at least
+the open source movement.  [Later in 2001, O'Reilly Associates published a
+couple of additional free books.  We are grateful for this contribution to
+the free software community, and we look forward to more of the same.]
+</p>
+<p>
+With the recent founding of FSF-Europe, and the coming inauguration of
+FSF-India, the free software movement is going stronger than ever.
+Please don't lump us in with the other movement in our community.
+</p>
+<p>
+Sincerely,
+</p>
+<p>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Richard Stallman
+President,
+Free Software Foundation
+</p>
+
+</div><!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<p>Please send general FSF &amp; GNU inquiries to
+<a href="mailto:address@hidden";>&lt;address@hidden&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:address@hidden";>&lt;address@hidden&gt;</a>.</p>
+
+<p><!-- TRANSLATORS: Ignore the original text in this paragraph,
+        replace it with the translation of these two:
+
+        We work hard and do our best to provide accurate, good quality
+        translations.  However, we are not exempt from imperfection.
+        Please send your comments and general suggestions in this regard
+        to <a href="mailto:address@hidden";>
+        &lt;address@hidden&gt;</a>.</p>
+
+        <p>For information on coordinating and submitting translations of
+        our web pages, see <a
+        href="/server/standards/README.translations.html">Translations
+        README</a>. -->
+Please see the <a
+href="/server/standards/README.translations.html">Translations
+README</a> for information on coordinating and submitting translations
+of this article.</p>
+</div>
+
+<!-- Regarding copyright, in general, standalone pages (as opposed to
+     files generated as part of manuals) on the GNU web server should
+     be under CC BY-ND 3.0 US.  Please do NOT change or remove this
+     without talking with the webmasters or licensing team first.
+     Please make sure the copyright date is consistent with the
+     document.  For web pages, it is ok to list just the latest year the
+     document was modified, or published.
+     
+     If you wish to list earlier years, that is ok too.
+     Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
+     years, as long as each year in the range is in fact a copyrightable
+     year, i.e., a year in which the document was published (including
+     being publicly visible on the web or in a revision control system).
+     
+     There is more detail about copyright years in the GNU Maintainers
+     Information document, www.gnu.org/prep/maintain. -->
+
+<p>Copyright &copy; 2000, 2007, 2014 Free Software Foundation, Inc.</p>
+
+<p>This page is licensed under a <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/";>Creative
+Commons Attribution-NoDerivs 3.0 United States License</a>.</p>
+
+<!--#include virtual="/server/bottom-notes.html" -->
+
+<p class="unprintable">Updated:
+<!-- timestamp start -->
+$Date: 2018/01/24 12:33:20 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>

Index: philosophy/po/university.pt-br-en.html
===================================================================
RCS file: philosophy/po/university.pt-br-en.html
diff -N philosophy/po/university.pt-br-en.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ philosophy/po/university.pt-br-en.html      24 Jan 2018 12:33:21 -0000      
1.1
@@ -0,0 +1,178 @@
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.77 -->
+<title>Releasing Free Software If You Work at a University
+- GNU Project - Free Software Foundation</title>
+<!--#include virtual="/philosophy/po/university.translist" -->
+<!--#include virtual="/server/banner.html" -->
+<h2>Releasing Free Software If You Work at a University</h2>
+
+<p>
+In the free software movement, we believe computer users should have
+the freedom to change and redistribute the software that they use.
+The &ldquo;free&rdquo; in &ldquo;free software&rdquo;
+refers to freedom: it means
+users have the freedom to run, modify and redistribute the software.
+Free software contributes to human knowledge, while nonfree software
+does not.  Universities should therefore encourage free software for
+the sake of advancing human knowledge, just as they should encourage
+scientists and other scholars to publish their work.</p>
+
+<p>
+Alas, many university administrators have a grasping attitude towards
+software (and towards science); they see programs as opportunities for
+income, not as opportunities to contribute to human knowledge.  Free
+software developers have been coping with this tendency for almost 20
+years.</p>
+
+<p>
+When I started developing the <a href="/gnu/thegnuproject.html">GNU
+operating system</a>, in 1984, my first step was to quit my job at MIT.
+I did this specifically so that the MIT licensing office would be
+unable to interfere with releasing GNU as free software.  I had
+planned an approach for licensing the programs in GNU that would ensure
+that all modified versions must be free software as well&mdash;an approach
+that developed into the <a href="/licenses/gpl.html">GNU General
+Public License</a> (GNU GPL)&mdash;and I did not want to have to beg the
+MIT administration to let me use it.</p>
+
+<p>
+Over the years, university affiliates have often come to the Free
+Software Foundation for advice on how to cope with administrators who
+see software only as something to sell.  One good method, applicable
+even for specifically funded projects, is to base your work on an
+existing program that was released under the GNU GPL.  Then you can
+tell the administrators, &ldquo;We're not allowed to release the
+modified version except under the GNU GPL&mdash;any other way would
+be copyright infringement.&rdquo; After the dollar signs fade from
+their eyes, they will usually consent to releasing it as free
+software.</p>
+
+<p>
+You can also ask your funding sponsor for help.  When a group at NYU
+developed the GNU Ada Compiler, with funding from the US Air Force,
+the contract explicitly called for donating the resulting code to the
+Free Software Foundation.  Work out the arrangement with the sponsor
+first, then politely show the university administration that it is not
+open to renegotiation.  They would rather have a contract to develop
+free software than no contract at all, so they will most likely go
+along.</p>
+
+<p>
+Whatever you do, raise the issue early&mdash;well before the
+program is half finished.  At this point, the university still needs
+you, so you can play hardball: tell the administration you will finish
+the program, make it usable, if they agree in writing to make it
+free software (and agree to your choice of free software license).
+Otherwise you will work on it only enough to write a paper about it,
+and never make a version good enough to release.  When the
+administrators know their choice is to have a free software package
+that brings credit to the university or nothing at all, they will
+usually choose the former.</p>
+<p>
+The FSF can sometimes persuade your university to accept the GNU
+General Public License, or to accept GPL version 3.  If you can't do
+it alone, please give us the chance to help.  Send mail to
address@hidden, and put &ldquo;urgent&rdquo; in the Subject
+field.</p>
+
+<p>
+Not all universities have grasping policies.  The University of Texas
+has a policy that makes it easy to release software developed there as
+free software under the GNU General Public License.  Univates in
+Brazil, and the International Institute of Information Technology in
+Hyderabad, India, both have policies in favor of releasing software
+under the GPL.  By developing faculty support first, you may be able
+to institute such a policy at your university.  Present the issue as
+one of principle: does the university have a mission to advance human
+knowledge, or is its sole purpose to perpetuate itself?</p>
+
+<p>
+In persuading the university, it helps to approach the issue with
+determination and based on an ethical perspective, as we do in the
+free software movement.  To treat the public ethically, the software
+should be free&mdash;as in freedom&mdash;for the whole public.</p>
+
+<p>
+Many developers of free software profess narrowly practical reasons
+for doing so: they advocate allowing others to share and change
+software as an expedient for making software powerful and reliable.
+If those values motivate you to develop free software, well and good,
+and thank you for your contribution.  But those values do not give you
+a good footing to stand firm when university administrators pressure
+or tempt you to make the program nonfree.</p>
+
+<p>
+For instance, they may argue that &ldquo;We could make it even more
+powerful and reliable with all the money we can get.&rdquo; This claim
+may or may not come true in the end, but it is hard to disprove in
+advance.  They may suggest a license to offer copies &ldquo;free of
+charge, for academic use only,&rdquo; which would tell the general
+public they don't deserve freedom, and argue that this will obtain the
+cooperation of academia, which is all (they say) you need.</p>
+
+<p>
+If you start from values of convenience alone, it is hard to make a
+good case for rejecting these dead-end proposals, but you can do it
+easily if you base your stand on ethical and political values.  What
+good is it to make a program powerful and reliable at the expense of
+users' freedom?  Shouldn't freedom apply outside academia as well as
+within it?  The answers are obvious if freedom and community are among
+your goals.  Free software respects the users' freedom, while nonfree
+software negates it.</p>
+
+<p>
+Nothing strengthens your resolve like knowing that the community's
+freedom depends, in one instance, on you.</p>
+
+<hr />
+<blockquote id="fsfs"><p class="big">This essay is published
+in <a href="http://shop.fsf.org/product/free-software-free-society/";><cite>Free
+Software, Free Society: The Selected Essays of Richard
+M. Stallman</cite></a>.</p></blockquote>
+
+</div><!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<p>Please send general FSF &amp; GNU inquiries to <a
+href="mailto:address@hidden";>&lt;address@hidden&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:address@hidden";>&lt;address@hidden&gt;</a>.</p>
+
+<p><!-- TRANSLATORS: Ignore the original text in this paragraph,
+        replace it with the translation of these two:
+
+        We work hard and do our best to provide accurate, good quality
+        translations.  However, we are not exempt from imperfection.
+        Please send your comments and general suggestions in this regard
+        to <a href="mailto:address@hidden";>
+        &lt;address@hidden&gt;</a>.</p>
+
+        <p>For information on coordinating and submitting translations of
+        our web pages, see <a
+        href="/server/standards/README.translations.html">Translations
+        README</a>. -->
+Please see the <a
+href="/server/standards/README.translations.html">Translations README</a> for
+information on coordinating and submitting translations of this article.</p>
+</div>
+
+<p>Copyright &copy; 2002 Richard Stallman</p>
+
+<p>This page is licensed under a <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/";>Creative
+Commons Attribution-NoDerivs 3.0 United States License</a>.</p>
+
+<!--#include virtual="/server/bottom-notes.html" -->
+
+<p class="unprintable">Updated:
+<!-- timestamp start -->
+$Date: 2018/01/24 12:33:21 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>

Index: server/irc-rules.pt-br.html
===================================================================
RCS file: server/irc-rules.pt-br.html
diff -N server/irc-rules.pt-br.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ server/irc-rules.pt-br.html 24 Jan 2018 12:33:21 -0000      1.1
@@ -0,0 +1,215 @@
+<!--#set var="ENGLISH_PAGE" value="/server/irc-rules.en.html" -->
+
+<!--#include virtual="/server/header.pt-br.html" -->
+<!-- Parent-Version: 1.84 -->
+
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>Canais IRC relacionados ao GNU e à FSF - Projeto GNU - Free Software
+Foundation</title>
+
+<!--#include virtual="/server/po/irc-rules.translist" -->
+<!--#include virtual="/server/banner.pt-br.html" -->
+<h2>Regras e diretrizes para os canais oficiais de IRC do GNU e da FSF</h2>
+
+<p>IRC (Internet Relay Chat) fornece um recurso maravilhoso para conectar
+usuários e desenvolvedores de software livre. Nossos canais tentam ser
+acolhedores tanto para as pessoas novas quanto para as regulares de longa
+data. Essas diretrizes existem com esse objetivo em mente.</p>
+
+<p>Todo mundo que usa ou contribui para o software livre é um membro valioso 
da
+comunidade de software livre. O objetivo dos canais IRC do GNU e da FSF é
+fornecer um lugar para a comunidade discutir coisas e falar sobre software
+livre e outras questões que afetam os direitos dos usuários de computador,
+como a Gestão Digital de Restrições (<cite>Digital Restrictions
+Management</cite>).</p>
+
+<p><b>Se você tiver problemas com qualquer um desses canais, com trolls ou
+membros abusivos, por favor nos contate em: <a
+href="mailto:address@hidden";>address@hidden</a>.</b></p>
+
+<h3>Lista de canais</h3>
+<p>Essa é uma lista de nossos canais.</p>
+<ul>
+<li><a href="irc://irc.gnu.org/gnu">#gnu</a> &mdash; o canal <em>oficial</em> 
do
+Projeto GNU</li>
+<li><a href="irc://irc.gnu.org/gnu-women">#gnu-women</a> &mdash; um canal para
+mulheres no GNU e em outros softwares livres.</li>
+<li><a href="irc://irc.gnu.org/gnu-es">#gnu-es</a> &mdash; GNU em espanhol</li>
+<li><a href="irc://irc.gnu.org/gnu-mx">#gnu-mx</a> &mdash; Discussão sobre o
+capítulo de GNU México</li>
+<li><a href="irc://irc.gnu.org/fsf">#fsf</a> &mdash; discussão sobre a <a
+href="http://www.fsf.org/";>FSF (Free Software Foundation) e fsf.org</a>
+</li>
+<li><a href="irc://irc.gnu.org/libreplanet">#libreplanet</a> &mdash; Discussão
+sobre o site do LibrePlanet e <a
+href="http://www.fsf.org/conference/";>conferência</a>.</li>
+<li><a href="irc://irc.gnu.org/emacs">#emacs</a> &mdash; Discussão sobre o <a
+href="/software/emacs/">Emacs</a></li>
+<li><a href="irc://irc.gnu.org/hurd">#hurd</a> &mdash; Discussão sobre o <a
+href="/software/hurd/">Hurd</a></li>
+<li><a href="irc://irc.gnu.org/grub">#grub</a> &mdash; para o sistema de
+inicialização do GNU, <a href="/software/grub/">GRUB</a>.</li>
+<li><a href="irc://irc.oftc.net/savannah">#savannah</a> &mdash; canal para
+bate-papo do <a href="http://savannah.gnu.org/";>Savannah.GNU.org</a></li>
+<li><a href="irc://irc.gnu.org/gnu-webmasters">#gnu-webmasters</a> &mdash; O
+canal de <a href="http://www.gnu.org/people/webmeisters.html";>GNU
+Webmasters</a>, para discussões sobre o www.gnu.org</li>
+<li><a href="irc://irc.gnu.org/erc">#erc</a> &mdash; Canal IRC sobre ERC, um
+cliente IRC para o Emacs</li>
+<li><a href="irc://irc.gnu.org/emacs-beginners">#emacs-beginners</a> &mdash;
+Canal IRC para ajudar iniciantes do Emacs</li>
+<li><a href="irc://irc.gnu.org/emacsconf">#emacsconf</a> &mdash; Discussão 
sobre
+a Emacs Conference</li>
+<li><a href="irc://irc.gnu.org/pspp">#pspp</a> &mdash; Discussão sobre <a
+href="/software/pspp/">PSPP</a></li>
+</ul>
+
+<h3>Regras dos canais</h3>
+
+<ol>
+<li>Respeito &mdash; não faça discurso racista ou de ódio. As pessoas têm
+direito a ter opiniões diferentes.</li>
+<li>Apropriado &mdash; pense antes de escrever: Meu comentário é apropriado? 
É
+possível que alguém interprete equivocadamente o que vou dizer como um
+discurso de ódio?</li>
+<li>Mantenha-o no tópico &mdash; ataques pessoais, “trollagem”, 
“baiting” ou
+“flooding” (publicar linhas repetitivas múltiplas vezes ou grande
+quantidades de código) no canal não será tolerado.</li>
+<li>E finalmente &mdash; cada canal do Projeto GNU e da FSF existe para 
promover
+um aspecto específico do desenvolvimento ou uso do GNU; de um modo geral,
+todos eles existem para promover o software livre e a liberdade dos usuários
+de softwares. Use o canal de forma a apoiar esses objetivos.</li>
+</ol>
+
+<h3>Abusos não serão tolerados</h3>
+
+<p>O IRC não é um parque de diversões exclusivo de alguns poucos indivíduos
+específicos e recentemente alguns usuários foram banidos de vários canais
+oficiais. Esses banimentos são infelizes, mas uma ação infelizmente
+necessária para evitar outros abusos desses usuários.</p>
+
+<p>Banimentos podem ser aplicados a um canal ou a todos canais baseados na
+segurança ou frequência dos abusos, conforme discricionariedade dos
+operadores do canal.</p>
+
+<p>Antes de ser banido, muitas vezes você será avisado por um operador, 
porém
+isso nem sempre é prático e um operador pode julgar desnecessário se um
+usuário recentemente foi chutado ou banido.</p>
+
+<p>Em um mundo ideal, não haveria necessidade dos operadores de IRC, mas em 
vez
+de tentar culpar os operadores por isso, culpe os usuários que não estão
+querendo estar em nossa comunidade.</p>
+
+<hr />
+
+<p>Regras terminam aqui, mas aqui estão algumas sugestões úteis&hellip;</p>
+
+<h3>Obtendo ajuda</h3>
+
+<p>Fale com um dos operadores. Se um operador estiver indisponível para
+ajudá-lo de imediato, por favor seja paciente. Peça a outros membros do
+canal para obter ajuda e detalhes de contato do operador.</p>
+
+<p>Você pode encontrar uma lista de operadores digitando <tt>/msg chanserv
+access #gnu list</tt> (sendo #gnu o canal pelo qual você está 
interessado).</p>
+
+<h3>Diretrizes do freenode</h3>
+
+<p>Freenode também mantém <a href="http://freenode.net/changuide";>uma lista 
de
+diretrizes de canais</a> que você também deve considerar. Certas discussões
+como GNU contra BSD, vi contra <a href="/software/emacs/">Emacs</a> são
+muitas vezes saudáveis para a discussão de software livre e nós encorajamos
+um debate saudável.</p>
+
+<h3>Lembre-se</h3>
+
+<p>O IRC está disponível para todos, e não apenas para desenvolvedores
+experientes do GNU. Não é razoável esperar que todos ignorem um usuário que
+está se comportando mal e, se você tem um manto do GNU ou da FSF, você pode
+ser reatribuído a uma capa de “não afiliado” se você continuar abusando 
de
+seus privilégios.</p>
+
+<div class="translators-notes">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.-->
+ </div>
+</div>
+
+<!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.pt-br.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<p>Envie perguntas em geral sobre a FSF e o GNU para <a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>. Também existem <a
+href="/contact/">outros meios de contatar</a> a FSF.  Links quebrados e
+outras correções ou sugestões podem ser enviadas para <a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>.</p>
+
+<p>
+<!-- TRANSLATORS: Ignore the original text in this paragraph,
+        replace it with the translation of these two:
+
+        We work hard and do our best to provide accurate, good quality
+        translations.  However, we are not exempt from imperfection.
+        Please send your comments and general suggestions in this regard
+        to <a href="mailto:address@hidden";>
+
+        &lt;address@hidden&gt;</a>.</p>
+
+        <p>For information on coordinating and submitting translations of
+        our web pages, see <a
+        href="/server/standards/README.translations.html">Translations
+        README</a>. -->
+A equipe de traduções para o português brasileiro se esforça para oferecer
+traduções acuradas e de boa qualidade, mas não estamos isentos de erros. Por
+favor, envie seus comentários e sugestões em geral sobre as traduções para
+<a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>.
+</p><p>Consulte o <a href="/server/standards/README.translations.html">Guia
+para as traduções</a> para mais informações sobre a coordenação e o 
envio de
+traduções das páginas desse site.</p>
+</div>
+
+<!-- Regarding copyright, in general, standalone pages (as opposed to
+     files generated as part of manuals) on the GNU web server should
+     be under CC BY-ND 4.0.  Please do NOT change or remove this
+     without talking with the webmasters or licensing team first.
+     Please make sure the copyright date is consistent with the
+     document.  For web pages, it is ok to list just the latest year the
+     document was modified, or published.
+
+     If you wish to list earlier years, that is ok too.
+     Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
+     years, as long as each year in the range is in fact a copyrightable
+     year, i.e., a year in which the document was published (including
+     being publicly visible on the web or in a revision control system).
+
+     There is more detail about copyright years in the GNU Maintainers
+     Information document, www.gnu.org/prep/maintain. -->
+<p>Copyright &copy; 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
+2006, 2007, 2008, 2009, 2014, 2015, 2016, 2017, 2018 Free Software
+Foundation, Inc.</p>
+
+<p>Esta página está licenciada sob uma licença <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/4.0/deed.pt_BR";>Creative
+Commons Atribuição-SemDerivações 4.0 Internacional</a>.</p>
+
+<!--#include virtual="/server/bottom-notes.pt-br.html" -->
+<div class="translators-credits">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.-->
+Traduzido por: Rafael Fontenelle <a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>, 2018</div>
+
+<p class="unprintable"><!-- timestamp start -->
+Última atualização: 
+
+$Date: 2018/01/24 12:33:21 $
+
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>

Index: server/po/irc-rules.pt-br-en.html
===================================================================
RCS file: server/po/irc-rules.pt-br-en.html
diff -N server/po/irc-rules.pt-br-en.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ server/po/irc-rules.pt-br-en.html   24 Jan 2018 12:33:21 -0000      1.1
@@ -0,0 +1,184 @@
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.84 -->
+<title>GNU and FSF related IRC channels
+- GNU Project - Free Software Foundation</title>
+
+<!--#include virtual="/server/po/irc-rules.translist" -->
+<!--#include virtual="/server/banner.html" -->
+
+<h2>Rules and guidelines for the official GNU and FSF IRC channels</h2>
+
+<p>IRC (Internet Relay Chat) provides a wonderful resource to connect
+free software users and developers together.  Our channels try to be
+welcoming to both new people and long-time regulars.  These guidelines
+exist with that goal in mind.</p>
+
+<p>Everyone who uses or contributes to free software is a valuable
+member of the free software community.  The goal of the GNU and FSF
+IRC channels is to provide a place for the community to discuss things
+and talk about free software and other issues which affect the rights
+of computer users, such as Digital Restrictions Management.</p>
+
+<p><b>If you have problems with any of these channels, with trolls or
+abusive members, please email us at: <a
+href="mailto:address@hidden";>address@hidden</a>.</b></p>
+
+<h3>List of channels</h3>
+<p>This is a list of our channels.</p>
+<ul>
+<li><a href="irc://irc.gnu.org/gnu">#gnu</a> &mdash;
+the <em>official</em> GNU Project Channel</li>
+<li><a href="irc://irc.gnu.org/gnu-women">#gnu-women</a> &mdash; a channel for 
women in GNU and other free software</li>
+<li><a href="irc://irc.gnu.org/gnu-es">#gnu-es</a> &mdash; GNU in Spanish</li>
+<li><a href="irc://irc.gnu.org/gnu-mx">#gnu-mx</a> &mdash; Discussion
+  about GNU Mexico chapter</li>
+<li><a href="irc://irc.gnu.org/fsf">#fsf</a> &mdash; Discussion about the
+<a href="http://www.fsf.org/";>FSF (Free Software Foundation) and fsf.org</a>
+</li>
+<li><a href="irc://irc.gnu.org/libreplanet">#libreplanet</a> &mdash; 
Discussion of the LibrePlanet website, and <a 
href="http://www.fsf.org/conference/";>conference</a>.</li>
+<li><a href="irc://irc.gnu.org/emacs">#emacs</a> &mdash; Discussion
+regarding <a href="/software/emacs/">Emacs</a></li>
+<li><a href="irc://irc.gnu.org/hurd">#hurd</a> &mdash; Discussion regarding
+<a href="/software/hurd/">Hurd</a></li>
+<li><a href="irc://irc.gnu.org/grub">#grub</a> &mdash; for the GNU bootloader, 
<a href="/software/grub/">GRUB</a>.</li>
+<li><a href="irc://irc.oftc.net/savannah">#savannah</a> &mdash;
+<a href="http://savannah.gnu.org/";>Savannah.GNU.org</a> hangout channel</li>
+<li><a href="irc://irc.gnu.org/gnu-webmasters">#gnu-webmasters</a> &mdash; The
+<a href="http://www.gnu.org/people/webmeisters.html";>GNU Webmasters</a>
+channel, for discussions about www.gnu.org</li>
+<li><a href="irc://irc.gnu.org/erc">#erc</a> &mdash; IRC channel about ERC, an 
IRC client for Emacs</li>
+<li><a href="irc://irc.gnu.org/emacs-beginners">#emacs-beginners</a> &mdash; 
IRC channel for helping out Emacs beginners</li>
+<li><a href="irc://irc.gnu.org/emacsconf">#emacsconf</a> &mdash; Discussion 
about the Emacs Conference</li>
+<li><a href="irc://irc.gnu.org/pspp">#pspp</a> &mdash; Discussion regarding <a 
href="/software/pspp/">PSPP</a></li>
+</ul>
+
+<h3>Channel rules</h3>
+
+<ol>
+<li>Respect &mdash; don't engage in racism or hate speech.  People are
+  entitled to different opinions.</li>
+<li>Appropriate &mdash; think before you type, is your comment appropriate?
+  Is it possible someone may misinterpret what you're saying in jest
+  as hateful speech?</li>
+<li>Keep it on topic &mdash; personal attacks, trolling/baiting or flooding
+  (posting multiple repetitive lines or large amounts of code) of the
+  channel will not be tolerated.</li>
+<li>And finally &mdash; each GNU Project and FSF channel exists to
+  promote a specific aspect of GNU development or use; more generally,
+  they all exist to promote free software and software users' freedom.
+  Use the channel in ways that support these goals.</li>
+</ol>
+
+<h3>Abuses will not be tolerated</h3>
+
+<p>IRC is not the exclusive playground of a few select individuals,
+and recently some users have been banned from various official
+channels.  These bans are an unfortunate, but unfortunately necessary
+action in order to prevent further abuses from these users.</p>
+
+<p>Bans can be applied to a channel, or to all channels based on the
+severity or frequency of the abuses, at the discretion of the channel
+operators.</p>
+
+<p>Before you are banned, you will often be warned by an operator
+first, however this is not always practical and an operator may deem
+it unnecessary if a user has recently been kicked or banned.</p>
+
+<p>In an ideal world, there would be no need for IRC operators, but
+instead of trying to blame operators for this, blame the users who are
+not willing to be in our community.</p>
+
+<hr />
+
+<p>Rules end here, but here are some helpful suggestions&hellip;</p>
+
+<h3>Getting help</h3>
+
+<p>Speak to one of the operators.  If an operator is unable to help
+you immediately, please be patient.  Ask other members of the channel
+for help and contact details for the operator.</p>
+
+<p>You can find a list of operators by typing <tt>/msg chanserv access
+#gnu list</tt> (where #gnu is the channel you are interested in).</p>
+
+<h3>Freenode guidelines</h3>
+
+<p>Freenode also
+maintains <a href="http://freenode.net/changuide";>a
+list of channel guidelines</a> which you should also consider.
+Certain discussions such as GNU vs BSD, vi
+vs <a href="/software/emacs/">Emacs</a> are often healthy to free
+software discussion and we encourage healthy debate.</p>
+
+<h3>Remember</h3>
+
+<p>IRC is there for everyone, not just seasoned GNU developers.  It is
+unreasonable to expect everyone to ignore a user who is misbehaving,
+and if you have a GNU or FSF cloak, you may be reassigned an
+&ldquo;unaffiliated&rdquo; cloak if you continue to abuse your privileges.</p>
+
+</div><!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<p>Please send general FSF &amp; GNU inquiries to
+<a href="mailto:address@hidden";>&lt;address@hidden&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:address@hidden";>&lt;address@hidden&gt;</a>.</p>
+
+<p><!-- TRANSLATORS: Ignore the original text in this paragraph,
+        replace it with the translation of these two:
+
+        We work hard and do our best to provide accurate, good quality
+        translations.  However, we are not exempt from imperfection.
+        Please send your comments and general suggestions in this regard
+        to <a href="mailto:address@hidden";>
+        &lt;address@hidden&gt;</a>.</p>
+
+        <p>For information on coordinating and submitting translations of
+        our web pages, see <a
+        href="/server/standards/README.translations.html">Translations
+        README</a>. -->
+Please see the <a
+href="/server/standards/README.translations.html">Translations
+README</a> for information on coordinating and submitting translations
+of this article.</p>
+</div>
+
+<!-- Regarding copyright, in general, standalone pages (as opposed to
+     files generated as part of manuals) on the GNU web server should
+     be under CC BY-ND 4.0.  Please do NOT change or remove this
+     without talking with the webmasters or licensing team first.
+     Please make sure the copyright date is consistent with the
+     document.  For web pages, it is ok to list just the latest year the
+     document was modified, or published.
+
+     If you wish to list earlier years, that is ok too.
+     Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
+     years, as long as each year in the range is in fact a copyrightable
+     year, i.e., a year in which the document was published (including
+     being publicly visible on the web or in a revision control system).
+
+     There is more detail about copyright years in the GNU Maintainers
+     Information document, www.gnu.org/prep/maintain. -->
+
+<p>Copyright &copy; 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004,
+2005, 2006, 2007, 2008, 2009, 2014, 2015, 2016, 2017, 2018 Free Software 
Foundation, Inc.</p>
+
+<p>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>.</p>
+
+<!--#include virtual="/server/bottom-notes.html" -->
+
+<p class="unprintable">Updated:
+<!-- timestamp start -->
+$Date: 2018/01/24 12:33:21 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>



reply via email to

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