www licenses/po/fdl-howto.es.po licenses/po/fdl...

[GNUN]

CVSROOT:        /web/www
Module name:    www
Changes by:     GNUN <gnun>     21/10/16 09:02:37

Modified files:
        licenses/po    : fdl-howto.es.po fdl-howto.translist 
        philosophy     : speeches-and-interview.fr.html 
        philosophy/po  : speeches-and-interview.fr-en.html 
        proprietary    : malware-microsoft.fr.html 
                         proprietary-jails.fr.html 
        proprietary/po : malware-microsoft.fr-en.html 
                         proprietary-jails.fr-en.html 
Added files:
        licenses       : fdl-howto.es.html 
        licenses/po    : fdl-howto.es-en.html 

Log message:
        Automatic update by GNUnited Nations.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/fdl-howto.es.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/fdl-howto.es.po?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/fdl-howto.translist?cvsroot=www&r1=1.19&r2=1.20
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/fdl-howto.es-en.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/speeches-and-interview.fr.html?cvsroot=www&r1=1.100&r2=1.101
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/speeches-and-interview.fr-en.html?cvsroot=www&r1=1.68&r2=1.69
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/malware-microsoft.fr.html?cvsroot=www&r1=1.119&r2=1.120
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/proprietary-jails.fr.html?cvsroot=www&r1=1.56&r2=1.57
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/malware-microsoft.fr-en.html?cvsroot=www&r1=1.109&r2=1.110
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/proprietary-jails.fr-en.html?cvsroot=www&r1=1.47&r2=1.48

Patches:
Index: licenses/po/fdl-howto.es.po
===================================================================
RCS file: /web/www/www/licenses/po/fdl-howto.es.po,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- licenses/po/fdl-howto.es.po 16 Oct 2021 12:33:44 -0000      1.1
+++ licenses/po/fdl-howto.es.po 16 Oct 2021 13:02:35 -0000      1.2
@@ -10,13 +10,13 @@
 "Project-Id-Version: fdl-howto.html\n"
 "POT-Creation-Date: 2014-04-05 00:01+0000\n"
 "PO-Revision-Date: 2021-10-16 10:41+0200\n"
+"Last-Translator: Javier Fdez. Retenaga <jfrtnaga@gnu.org>\n"
+"Language-Team: Spanish\n"
+"Language: es\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
 "Plural-Forms: nplurals=2; plural=(n!=1);\n"
-"Last-Translator: Javier Fdez. Retenaga <jfrtnaga@gnu.org>\n"
-"Language-Team: Spanish\n"
-"Language: es\n"
 "X-Generator: Poedit 2.2.1\n"
 
 #. type: Content of: <title>
@@ -27,24 +27,25 @@
 
 #. type: Content of: <h2>
 msgid "Tips on Using the GNU Free Documentation License"
-msgstr "Consejos para la utilización de la Licencia de Documentación Libre 
de GNU"
+msgstr ""
+"Consejos para la utilización de la Licencia de Documentación Libre de GNU"
 
 #. type: Content of: <p>
 msgid ""
 "This is a brief explanation of how to place a document under the <a href=\"/"
-"licenses/fdl.html\">GNU Free Documentation License</a>.  For the GNU software 
"
-"licenses, such as the GNU GPL, we have a <a href=\"/licenses/gpl-howto.html"
-"\">separate page</a>."
+"licenses/fdl.html\">GNU Free Documentation License</a>.  For the GNU "
+"software licenses, such as the GNU GPL, we have a <a href=\"/licenses/gpl-"
+"howto.html\">separate page</a>."
 msgstr ""
 "Esta es una breve explicación de cómo poner un documento bajo la <a 
href=\"/"
-"licenses/fdl.html\">Licencia de Documentación Libre de GNU</a>. De las 
licencias "
-"del software de GNU, como la GPL de GNU, nos ocupamos en una <a 
href=\"/licenses/"
-"gpl-howto.html\">página aparte</a>."
+"licenses/fdl.html\">Licencia de Documentación Libre de GNU</a>. De las "
+"licencias del software de GNU, como la GPL de GNU, nos ocupamos en una <a "
+"href=\"/licenses/gpl-howto.html\">página aparte</a>."
 
 #. type: Content of: <dl><dt>
 msgid ""
-"<a href=\"/licenses/fdl-howto-opt.html\">How does one use the optional 
features "
-"of the FDL?</a>"
+"<a href=\"/licenses/fdl-howto-opt.html\">How does one use the optional "
+"features of the FDL?</a>"
 msgstr ""
 "<a href=\"/licenses/fdl-howto-opt.html\">¿Cómo se utilizan los elementos "
 "opcionales de la <abbr title=\"Free Documentation License\">FDL</abbr>?</a>"
@@ -54,8 +55,8 @@
 "We have a <a href=\"/licenses/fdl-howto-opt.html\">separate page</a> that "
 "discusses how to use the optional features of the FDL."
 msgstr ""
-"En una <a href=\"/licenses/fdl-howto-opt.html\">página aparte</a> explicamos 
cómo "
-"utilizar los elementos opcionales de la FDL."
+"En una <a href=\"/licenses/fdl-howto-opt.html\">página aparte</a> explicamos 
"
+"cómo utilizar los elementos opcionales de la FDL."
 
 #. type: Content of: <dl><dt>
 msgid "Where must one put the license notification?"
@@ -63,15 +64,17 @@
 
 #. type: Content of: <dl><dd>
 msgid ""
-"It is sufficient to put the full license notice in the &ldquo;main&rdquo; 
file of "
-"your document.  For example, with the <cite>Emacs Lisp Reference 
Manual</cite>, "
-"we have many files included by <code>elisp.texi</code>.  We keep the full "
-"notification in <code>elisp.texi</code>, and in the other files we simply 
write:"
+"It is sufficient to put the full license notice in the &ldquo;main&rdquo; "
+"file of your document.  For example, with the <cite>Emacs Lisp Reference "
+"Manual</cite>, we have many files included by <code>elisp.texi</code>.  We "
+"keep the full notification in <code>elisp.texi</code>, and in the other "
+"files we simply write:"
 msgstr ""
 "Basta con poner la nota completa de licencia en el archivo «main» del "
-"documento. Por ejemplo, en el caso del <cite>Emacs Lisp Reference 
Manual</cite>, "
-"muchos archivos figuran en <code>elisp.texi</code>. Ponemos la nota completa 
en "
-"<code>elisp.texi</code>, y en el resto de los archivos escribimos 
simplemente:"
+"documento. Por ejemplo, en el caso del <cite>Emacs Lisp Reference Manual</"
+"cite>, muchos archivos figuran en <code>elisp.texi</code>. Ponemos la nota "
+"completa en <code>elisp.texi</code>, y en el resto de los archivos "
+"escribimos simplemente:"
 
 #. type: Content of: <dl><dd><pre>
 #, no-wrap
@@ -89,20 +92,21 @@
 "@c See the file elisp.texi for copying conditions.\n"
 
 #. type: Content of: <dl><dt>
-msgid "What do I do with scripts that are needed to render my document 
properly?"
+msgid ""
+"What do I do with scripts that are needed to render my document properly?"
 msgstr ""
-"¿Que hago con los <cite>scripts</cite> que son necesarios para poder 
visualizar "
-"el documento correctamente?"
+"¿Que hago con los <cite>scripts</cite> que son necesarios para poder "
+"visualizar el documento correctamente?"
 
 #. type: Content of: <dl><dd>
 msgid ""
-"We recommend you release these scripts under the GNU FDL as well.  Of course, 
if "
-"these scripts are generally useful for other tasks, it is a good idea to 
release "
-"them separately under the GNU GPL."
+"We recommend you release these scripts under the GNU FDL as well.  Of "
+"course, if these scripts are generally useful for other tasks, it is a good "
+"idea to release them separately under the GNU GPL."
 msgstr ""
-"Le recomendamos que publique esos <cite>scripts</cite> también bajo la FDL 
de "
-"GNU. Por supuesto, si estos <cite>scripts</cite> son útiles para otras 
tareas, es "
-"una buena idea publicarlos de forma separada bajo la GPL de GNU."
+"Le recomendamos que publique esos <cite>scripts</cite> también bajo la FDL "
+"de GNU. Por supuesto, si estos <cite>scripts</cite> son útiles para otras "
+"tareas, es una buena idea publicarlos de forma separada bajo la GPL de GNU."
 
 #. type: Content of: <dl><dt>
 msgid "Is it required for the document to have invariant sections?"
@@ -112,7 +116,8 @@
 msgid ""
 "No.  It is perfectly acceptable for a document to have no invariant sections."
 msgstr ""
-"No. Es perfectamente aceptable que el documento no tenga secciones 
invariantes."
+"No. Es perfectamente aceptable que el documento no tenga secciones "
+"invariantes."
 
 #. type: Content of: <dl><dt>
 msgid "Should I try to make sure the document has some invariant sections?"
@@ -123,8 +128,8 @@
 "Not particularly.  If a section's contents ought to be invariant, make it "
 "invariant."
 msgstr ""
-"No especialmente. Si los contenidos de una sección deben ser invariantes, 
hágalos "
-"invariantes."
+"No especialmente. Si los contenidos de una sección deben ser invariantes, "
+"hágalos invariantes."
 
 #. type: Content of: <dl><dt>
 msgid "Should I try to avoid invariant sections?"
@@ -137,61 +142,67 @@
 #. type: Content of: <dl><dd>
 msgid ""
 "First of all, keep in mind that a section that treats technical material "
-"<em>cannot</em> be invariant.  Only a secondary section can be invariant, and 
a "
-"technical section is not a secondary section."
+"<em>cannot</em> be invariant.  Only a secondary section can be invariant, "
+"and a technical section is not a secondary section."
 msgstr ""
 "En primer lugar, recuerde que una sección que trata asuntos técnicos <em>no 
"
-"puede</em> ser invariante. Solo una sección secundaria puede ser invariante, 
y "
-"una sección técnica no es una sección secundaria."
+"puede</em> ser invariante. Solo una sección secundaria puede ser invariante, 
"
+"y una sección técnica no es una sección secundaria."
 
 #. type: Content of: <dl><dd><p>
 msgid ""
-"If the section is text that you're not allowed to modify, such as a copy of 
the "
-"GNU GPL, then it <em>must</em> be invariant.  You can't give permission to 
modify "
-"it if you don't have permission to modify it."
-msgstr ""
-"Si la sección es texto que usted no está autorizado a modificar, tal como 
una "
-"copia de la GPL de GNU, entonces esa sección <em>debe</em> ser invariante. 
Si "
-"usted no tiene permiso para modificarla, tampoco puede dar permiso para 
hacerlo."
+"If the section is text that you're not allowed to modify, such as a copy of "
+"the GNU GPL, then it <em>must</em> be invariant.  You can't give permission "
+"to modify it if you don't have permission to modify it."
+msgstr ""
+"Si la sección es texto que usted no está autorizado a modificar, tal como "
+"una copia de la GPL de GNU, entonces esa sección <em>debe</em> ser "
+"invariante. Si usted no tiene permiso para modificarla, tampoco puede dar "
+"permiso para hacerlo."
 
 #. type: Content of: <dl><dd><p>
 msgid ""
-"(One consequence is that you <em>cannot use</em> preexisting text which 
covers "
-"technical material if you don't have permission to allow modification of that 
"
-"text.)"
-msgstr ""
-"(Una consecuencia de esto es que usted <em>no puede utilizar</em> texto 
previo "
-"que trate asuntos técnicos si no tiene permiso para permitir la 
modificación de "
-"dicho texto)."
+"(One consequence is that you <em>cannot use</em> preexisting text which "
+"covers technical material if you don't have permission to allow modification "
+"of that text.)"
+msgstr ""
+"(Una consecuencia de esto es que usted <em>no puede utilizar</em> texto "
+"previo que trate asuntos técnicos si no tiene permiso para permitir la "
+"modificación de dicho texto)."
 
 #. type: Content of: <dl><dd><p>
 msgid ""
-"When a section discusses the philosophy of free software, it is a good idea 
to "
-"make that section invariant.  For instance, when we put the GNU Manifesto in 
a "
-"manual, or when we include a section explaining why free documentation is "
-"important, we make that section invariant."
-msgstr ""
-"Cuando una sección aborda la filosofía del software libre, es buena idea 
hacer "
-"invariante esa sección. Cuando, por ejemplo, ponemos el Manifiesto de GNU en 
un "
-"manual, o cuando incluimos una sección para explicar por qué es importante 
la "
-"documentación libre, hacemos esa sección invariante."
+"When a section discusses the philosophy of free software, it is a good idea "
+"to make that section invariant.  For instance, when we put the GNU Manifesto "
+"in a manual, or when we include a section explaining why free documentation "
+"is important, we make that section invariant."
+msgstr ""
+"Cuando una sección aborda la filosofía del software libre, es buena idea "
+"hacer invariante esa sección. Cuando, por ejemplo, ponemos el Manifiesto de "
+"GNU en un manual, o cuando incluimos una sección para explicar por qué es "
+"importante la documentación libre, hacemos esa sección invariante."
 
 #. 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:gnu@gnu.org\";>&lt;"
-"gnu@gnu.org&gt;</a>.  There are also <a href=\"/contact/\">other ways to 
contact</"
-"a> the FSF.  Broken links and other corrections or suggestions can be sent to 
<a "
-"href=\"mailto:webmasters@gnu.org\";>&lt;webmasters@gnu.org&gt;</a>."
-msgstr " "
+"Please send general FSF &amp; GNU inquiries to <a href=\"mailto:gnu@gnu.org";
+"\">&lt;gnu@gnu.org&gt;</a>.  There are also <a href=\"/contact/\">other ways "
+"to contact</a> the FSF.  Broken links and other corrections or suggestions "
+"can be sent to <a href=\"mailto:webmasters@gnu.org\";>&lt;webmasters@gnu."
+"org&gt;</a>."
+msgstr ""
+"Envíe sus consultas acerca de la FSF y GNU a <a href=\"mailto:gnu@gnu.org";
+"\">&lt;gnu@gnu.org&gt;</a>. Existen también <a href=\"/contact/\">otros "
+"medios para contactar</a> con la FSF. <br /> Para avisar de enlaces rotos y "
+"proponer otras correcciones o sugerencias, diríjase a <a href=\"mailto:";
+"webmasters@gnu.org\">&lt;webmasters@gnu.org&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
@@ -208,28 +219,40 @@
 "Please see the <a href=\"/server/standards/README.translations.html"
 "\">Translations README</a> for information on coordinating and submitting "
 "translations of this article."
-msgstr " "
+msgstr ""
+"El equipo de traductores al español se esfuerza por ofrecer traducciones "
+"fieles al original y de buena calidad, pero no estamos libres de cometer "
+"errores.<br /> Envíe sus comentarios y sugerencias sobre las traducciones a "
+"<a  href=\"mailto:web-translators@gnu.org\";>&lt;web-translators@gnu.org&gt;</"
+"a>. </p><p>Consulte la <a href=\"/server/standards/README.translations.html"
+"\">Guía para las traducciones</a> para obtener información sobre la "
+"coordinación y el envío de traducciones de las páginas de este sitio web."
 
 #. type: Content of: <div><p>
-msgid "Copyright &copy; 2000, 2001, 2008, 2009, 2014 Free Software Foundation, 
Inc."
+msgid ""
+"Copyright &copy; 2000, 2001, 2008, 2009, 2014 Free Software Foundation, Inc."
 msgstr ""
 "Copyright &copy; 2000, 2001, 2008, 2009, 2014 Free Software Foundation, Inc."
 
 #. type: Content of: <div><p>
 msgid ""
-"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>."
-msgstr " "
+"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>."
+msgstr ""
+"Esta página está bajo licencia <a rel=\"license\" href=\"http://";
+"creativecommons.org/licenses/by-nd/3.0/us/deed.es_ES\">Creative Commons "
+"Reconocimiento-SinObraDerivada 3.0 Estados Unidos de América</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 ""
-"<strong>Traducción: Javier Fdez. Retenaga, 2021.</strong> Revisión: Equipo 
de "
-"traductores al español de GNU."
+"<strong>Traducción: Javier Fdez. Retenaga, 2021.</strong> Revisión: Equipo "
+"de traductores al español de GNU."
 
+# type: Content of: <div><p>
 #. timestamp start
 #. type: Content of: <div><p>
 msgid "Updated:"
-msgstr " "
+msgstr "Última actualización:"

Index: licenses/po/fdl-howto.translist
===================================================================
RCS file: /web/www/www/licenses/po/fdl-howto.translist,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -b -r1.19 -r1.20
--- licenses/po/fdl-howto.translist     9 Apr 2020 15:59:12 -0000       1.19
+++ licenses/po/fdl-howto.translist     16 Oct 2021 13:02:35 -0000      1.20
@@ -5,6 +5,7 @@
 <span dir="ltr" class="original">[en]&nbsp;<a lang="en" hreflang="en" 
href="/licenses/fdl-howto.en.html">English</a> &nbsp;</span>
 <span dir="ltr">[ca]&nbsp;<a lang="ca" hreflang="ca" 
href="/licenses/fdl-howto.ca.html">català </a> &nbsp;</span>
 <span dir="ltr">[de]&nbsp;<a lang="de" hreflang="de" 
href="/licenses/fdl-howto.de.html">Deutsch</a> &nbsp;</span>
+<span dir="ltr">[es]&nbsp;<a lang="es" hreflang="es" 
href="/licenses/fdl-howto.es.html">español</a> &nbsp;</span>
 <span dir="ltr">[fr]&nbsp;<a lang="fr" hreflang="fr" 
href="/licenses/fdl-howto.fr.html">français</a> &nbsp;</span>
 <span dir="ltr">[ja]&nbsp;<a lang="ja" hreflang="ja" 
href="/licenses/fdl-howto.ja.html">日本語</a> &nbsp;</span>
 <span dir="ltr">[pl]&nbsp;<a lang="pl" hreflang="pl" 
href="/licenses/fdl-howto.pl.html">polski</a> &nbsp;</span>
@@ -20,6 +21,7 @@
 <link rel="alternate" type="text/html" lang="en" hreflang="en" 
href="/licenses/fdl-howto.en.html" title="English" />
 <link rel="alternate" type="text/html" lang="ca" hreflang="ca" 
href="/licenses/fdl-howto.ca.html" title="català " />
 <link rel="alternate" type="text/html" lang="de" hreflang="de" 
href="/licenses/fdl-howto.de.html" title="Deutsch" />
+<link rel="alternate" type="text/html" lang="es" hreflang="es" 
href="/licenses/fdl-howto.es.html" title="español" />
 <link rel="alternate" type="text/html" lang="fr" hreflang="fr" 
href="/licenses/fdl-howto.fr.html" title="français" />
 <link rel="alternate" type="text/html" lang="ja" hreflang="ja" 
href="/licenses/fdl-howto.ja.html" title="日本語" />
 <link rel="alternate" type="text/html" lang="pl" hreflang="pl" 
href="/licenses/fdl-howto.pl.html" title="polski" />

Index: philosophy/speeches-and-interview.fr.html
===================================================================
RCS file: /web/www/www/philosophy/speeches-and-interview.fr.html,v
retrieving revision 1.100
retrieving revision 1.101
diff -u -b -r1.100 -r1.101
--- philosophy/speeches-and-interview.fr.html   19 Aug 2021 17:02:11 -0000      
1.100
+++ philosophy/speeches-and-interview.fr.html   16 Oct 2021 13:02:36 -0000      
1.101
@@ -278,8 +278,9 @@
 10 novembre 2004, lors d'un congrès organisé par la <i>Foundation for a 
Free
 Information Infrastructure</i> (FFII) Ã  Bruxelles, Belgique.</li>
 
-<li><a href="http://www.ariel.com.au/a/rms-unsw.html";>Résumé en anglais d'une
-conférence sur les brevets logiciels</a> donnée par <a
+<li><a
+href="https://web.archive.org/web/20210411070158/http://www.ariel.com.au/a/rms-unsw.html";>Résumé
+en anglais d'une conférence sur les brevets logiciels</a> donnée par <a
 href="http://www.stallman.org";>Richard M. Stallman</a> le 14 octobre 
2004.</li>
 
 <li><a href="/philosophy/rms-interview-edinburgh.html">Entretien</a> avec
@@ -515,7 +516,7 @@
 <p class="unprintable"><!-- timestamp start -->
 Dernière mise à jour :
 
-$Date: 2021/08/19 17:02:11 $
+$Date: 2021/10/16 13:02:36 $
 
 <!-- timestamp end -->
 </p>

Index: philosophy/po/speeches-and-interview.fr-en.html
===================================================================
RCS file: /web/www/www/philosophy/po/speeches-and-interview.fr-en.html,v
retrieving revision 1.68
retrieving revision 1.69
diff -u -b -r1.68 -r1.69
--- philosophy/po/speeches-and-interview.fr-en.html     19 Aug 2021 17:02:12 
-0000      1.68
+++ philosophy/po/speeches-and-interview.fr-en.html     16 Oct 2021 13:02:36 
-0000      1.69
@@ -226,7 +226,8 @@
     10, 2004, at a conference organized by the Foundation for a Free
     Information Infrastructure (FFII) in Brussels, Belgium</li>
 
-<li><a href="http://www.ariel.com.au/a/rms-unsw.html";>Synopsis of a
+<li><a 
href="https://web.archive.org/web/20210411070158/http://www.ariel.com.au/a/rms-unsw.html";>
+   Synopsis of a
    speech</a> given by <a href="http://www.stallman.org";>Richard
    M. Stallman</a> about software patents on 14 October 2004.</li>
 
@@ -423,7 +424,7 @@
 
 <p class="unprintable">Updated:
 <!-- timestamp start -->
-$Date: 2021/08/19 17:02:12 $
+$Date: 2021/10/16 13:02:36 $
 <!-- timestamp end -->
 </p>
 </div>

Index: proprietary/malware-microsoft.fr.html
===================================================================
RCS file: /web/www/www/proprietary/malware-microsoft.fr.html,v
retrieving revision 1.119
retrieving revision 1.120
diff -u -b -r1.119 -r1.120
--- proprietary/malware-microsoft.fr.html       4 Sep 2021 10:36:03 -0000       
1.119
+++ proprietary/malware-microsoft.fr.html       16 Oct 2021 13:02:36 -0000      
1.120
@@ -1052,7 +1052,7 @@
 
href="https://www.theverge.com/2017/6/13/15789998/microsoft-windows-10-s-upgrade-windows-10-pro-guide";>passer
 à Windows 10 Pro</a>. Le successeur de Windows 10 S est une configuration
 spéciale de Windows 10 appelée <a
-href="https://support.microsoft.com/en-us/windows/windows-10-in-s-mode-faq-851057d6-1ee9-b9e5-c30b-93baebeebc85";>modeÂ
 S</a>.
+href="https://support.microsoft.com/en-us/windows/windows-10-and-windows-11-in-s-mode-faq-851057d6-1ee9-b9e5-c30b-93baebeebc85";>modeÂ
 S</a>.
 Sa différence principale avec Windows 10 est qu'on peut facilement sortir du
 mode S.</p>
   </li>
@@ -1182,7 +1182,7 @@
 <p class="unprintable"><!-- timestamp start -->
 Dernière mise à jour :
 
-$Date: 2021/09/04 10:36:03 $
+$Date: 2021/10/16 13:02:36 $
 
 <!-- timestamp end -->
 </p>

Index: proprietary/proprietary-jails.fr.html
===================================================================
RCS file: /web/www/www/proprietary/proprietary-jails.fr.html,v
retrieving revision 1.56
retrieving revision 1.57
diff -u -b -r1.56 -r1.57
--- proprietary/proprietary-jails.fr.html       20 Sep 2021 16:33:14 -0000      
1.56
+++ proprietary/proprietary-jails.fr.html       16 Oct 2021 13:02:36 -0000      
1.57
@@ -100,8 +100,8 @@
 favorable à Navalny</a> en Russie.</p>
 
     <p>C'est impossible parce que (1) l'iPhone refuse de télécharger des 
applis qui
-ne viennent pas de chez Apple et (2) Apple a obéi à la loi russe sur la
-censure. Le premier point est mis en œuvre par le logiciel privateur
+ne viennent pas de chez Apple et (2) Apple a obéi à une loi russe sur la
+censure. Le premier point sous la dépendance d'un logiciel privateur
 d'Apple.</p>
   </li>
 
@@ -419,7 +419,7 @@
 
href="https://www.theverge.com/2017/6/13/15789998/microsoft-windows-10-s-upgrade-windows-10-pro-guide";>passer
 à Windows 10 Pro</a>. Le successeur de Windows 10 S est une configuration
 spéciale de Windows 10 appelée <a
-href="https://support.microsoft.com/en-us/windows/windows-10-in-s-mode-faq-851057d6-1ee9-b9e5-c30b-93baebeebc85";>modeÂ
 S</a>.
+href="https://support.microsoft.com/en-us/windows/windows-10-and-windows-11-in-s-mode-faq-851057d6-1ee9-b9e5-c30b-93baebeebc85";>modeÂ
 S</a>.
 Sa différence principale avec Windows 10 est qu'on peut facilement sortir du
 mode S.</p>
   </li>
@@ -519,7 +519,7 @@
 <p class="unprintable"><!-- timestamp start -->
 Dernière mise à jour :
 
-$Date: 2021/09/20 16:33:14 $
+$Date: 2021/10/16 13:02:36 $
 
 <!-- timestamp end -->
 </p>

Index: proprietary/po/malware-microsoft.fr-en.html
===================================================================
RCS file: /web/www/www/proprietary/po/malware-microsoft.fr-en.html,v
retrieving revision 1.109
retrieving revision 1.110
diff -u -b -r1.109 -r1.110
--- proprietary/po/malware-microsoft.fr-en.html 4 Sep 2021 10:36:03 -0000       
1.109
+++ proprietary/po/malware-microsoft.fr-en.html 16 Oct 2021 13:02:36 -0000      
1.110
@@ -867,7 +867,7 @@
     
href="https://www.theverge.com/2017/6/13/15789998/microsoft-windows-10-s-upgrade-windows-10-pro-guide";>
     upgrade to Windows 10 Pro</a>. The successor of Windows
     10 S is a special configuration of Windows 10 called <a
-    
href="https://support.microsoft.com/en-us/windows/windows-10-in-s-mode-faq-851057d6-1ee9-b9e5-c30b-93baebeebc85";>
+    
href="https://support.microsoft.com/en-us/windows/windows-10-and-windows-11-in-s-mode-faq-851057d6-1ee9-b9e5-c30b-93baebeebc85";>
     S mode</a>. The major difference with Windows 10 S is that there is
     an easy way to switch out of S mode.</p>
   </li>
@@ -971,7 +971,7 @@
 
 <p class="unprintable">Updated:
 <!-- timestamp start -->
-$Date: 2021/09/04 10:36:03 $
+$Date: 2021/10/16 13:02:36 $
 <!-- timestamp end -->
 </p>
 </div>

Index: proprietary/po/proprietary-jails.fr-en.html
===================================================================
RCS file: /web/www/www/proprietary/po/proprietary-jails.fr-en.html,v
retrieving revision 1.47
retrieving revision 1.48
diff -u -b -r1.47 -r1.48
--- proprietary/po/proprietary-jails.fr-en.html 20 Sep 2021 16:33:14 -0000      
1.47
+++ proprietary/po/proprietary-jails.fr-en.html 16 Oct 2021 13:02:36 -0000      
1.48
@@ -349,7 +349,7 @@
     
href="https://www.theverge.com/2017/6/13/15789998/microsoft-windows-10-s-upgrade-windows-10-pro-guide";>
     upgrade to Windows 10 Pro</a>. The successor of Windows
     10 S is a special configuration of Windows 10 called <a
-    
href="https://support.microsoft.com/en-us/windows/windows-10-in-s-mode-faq-851057d6-1ee9-b9e5-c30b-93baebeebc85";>
+    
href="https://support.microsoft.com/en-us/windows/windows-10-and-windows-11-in-s-mode-faq-851057d6-1ee9-b9e5-c30b-93baebeebc85";>
     S mode</a>. The major difference with Windows 10 S is that there is
     an easy way to switch out of S mode.</p>
   </li>
@@ -430,7 +430,7 @@
 
 <p class="unprintable">Updated:
 <!-- timestamp start -->
-$Date: 2021/09/20 16:33:14 $
+$Date: 2021/10/16 13:02:36 $
 <!-- timestamp end -->
 </p>
 </div>

Index: licenses/fdl-howto.es.html
===================================================================
RCS file: licenses/fdl-howto.es.html
diff -N licenses/fdl-howto.es.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ licenses/fdl-howto.es.html  16 Oct 2021 13:02:35 -0000      1.1
@@ -0,0 +1,167 @@
+<!--#set var="ENGLISH_PAGE" value="/licenses/fdl-howto.en.html" -->
+
+<!--#include virtual="/server/header.es.html" -->
+<!-- Parent-Version: 1.77 -->
+
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>Consejos para la utilización de la Licencia de Documentación Libre de 
GNU -
+Proyecto GNU - Free Software Foundation</title>
+
+<!--#include virtual="/licenses/po/fdl-howto.translist" -->
+<!--#include virtual="/server/banner.es.html" -->
+<h2>Consejos para la utilización de la Licencia de Documentación Libre de 
GNU</h2>
+
+<p>Esta es una breve explicación de cómo poner un documento bajo la <a
+href="/licenses/fdl.html">Licencia de Documentación Libre de GNU</a>. De las
+licencias del software de GNU, como la GPL de GNU, nos ocupamos en una <a
+href="/licenses/gpl-howto.html">página aparte</a>.</p>
+
+<dl>
+<dt><a href="/licenses/fdl-howto-opt.html">¿Cómo se utilizan los elementos
+opcionales de la <abbr title="Free Documentation License">FDL</abbr>?</a></dt>
+<dd>
+En una <a href="/licenses/fdl-howto-opt.html">página aparte</a> explicamos
+cómo utilizar los elementos opcionales de la FDL.</dd>
+
+<dt>¿Dónde hay que colocar la notificación de la licencia?</dt>
+<dd>
+Basta con poner la nota completa de licencia en el archivo «main» del
+documento. Por ejemplo, en el caso del <cite>Emacs Lisp Reference
+Manual</cite>, muchos archivos figuran en <code>elisp.texi</code>. Ponemos
+la nota completa en <code>elisp.texi</code>, y en el resto de los archivos
+escribimos simplemente:
+
+<pre>
+@c -*-texinfo-*-
+@c This is part of the GNU Emacs Lisp Reference Manual.
+@c Copyright (C) 1990, 1991, 1992, 1993, 1994, 1999
+@c   Free Software Foundation, Inc.
+@c See the file elisp.texi for copying conditions.
+</pre></dd>
+
+<dt>¿Que hago con los <cite>scripts</cite> que son necesarios para poder
+visualizar el documento correctamente?</dt>
+<dd>
+Le recomendamos que publique esos <cite>scripts</cite> también bajo la FDL
+de GNU. Por supuesto, si estos <cite>scripts</cite> son útiles para otras
+tareas, es una buena idea publicarlos de forma separada bajo la GPL de 
GNU.</dd>
+
+<dt>¿Es necesario que el documento contenga secciones invariantes?</dt>
+<dd>
+No. Es perfectamente aceptable que el documento no tenga secciones
+invariantes.</dd>
+
+<dt>¿Debo procurar que el documento tenga secciones invariantes?</dt>
+<dd>
+No especialmente. Si los contenidos de una sección deben ser invariantes,
+hágalos invariantes.</dd>
+
+<dt>¿Debo tratar de evitar las secciones invariantes?</dt>
+<dd>
+No especialmente. Si los contenidos de una sección deben ser invariantes,
+hágalos invariantes.</dd>
+
+<dt>¿Cuándo debe ser invariante una sección?</dt>
+<dd>
+En primer lugar, recuerde que una sección que trata asuntos técnicos <em>no
+puede</em> ser invariante. Solo una sección secundaria puede ser invariante,
+y una sección técnica no es una sección secundaria.
+<p>
+Si la sección es texto que usted no está autorizado a modificar, tal como
+una copia de la GPL de GNU, entonces esa sección <em>debe</em> ser
+invariante. Si usted no tiene permiso para modificarla, tampoco puede dar
+permiso para hacerlo.</p>
+<p>
+(Una consecuencia de esto es que usted <em>no puede utilizar</em> texto
+previo que trate asuntos técnicos si no tiene permiso para permitir la
+modificación de dicho texto).</p>
+<p>
+Cuando una sección aborda la filosofía del software libre, es buena idea
+hacer invariante esa sección. Cuando, por ejemplo, ponemos el Manifiesto de
+GNU en un manual, o cuando incluimos una sección para explicar por qué es
+importante la documentación libre, hacemos esa sección invariante.</p></dd>
+</dl>
+
+<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.es.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<p>Envíe sus consultas acerca de la FSF y GNU a <a
+href="mailto:gnu@gnu.org";>&lt;gnu@gnu.org&gt;</a>. Existen también <a
+href="/contact/">otros medios para contactar</a> con la FSF. <br /> Para
+avisar de enlaces rotos y proponer otras correcciones o sugerencias,
+diríjase a <a
+href="mailto:webmasters@gnu.org";>&lt;webmasters@gnu.org&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:web-translators@gnu.org";>
+
+        &lt;web-translators@gnu.org&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>. -->
+El equipo de traductores al español se esfuerza por ofrecer traducciones
+fieles al original y de buena calidad, pero no estamos libres de cometer
+errores.<br /> Envíe sus comentarios y sugerencias sobre las traducciones a
+<a
+href="mailto:web-translators@gnu.org";>&lt;web-translators@gnu.org&gt;</a>.
+</p><p>Consulte la <a href="/server/standards/README.translations.html">Guía
+para las traducciones</a> para obtener información sobre la coordinación y
+el envío de traducciones de las páginas de este sitio web.</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, 2001, 2008, 2009, 2014 Free Software Foundation, 
Inc.</p>
+
+<p>Esta página está bajo licencia <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/deed.es_ES";>Creative
+Commons Reconocimiento-SinObraDerivada 3.0 Estados Unidos de América</a>.</p>
+
+<!--#include virtual="/server/bottom-notes.es.html" -->
+<div class="translators-credits">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.-->
+<strong>Traducción: Javier Fdez. Retenaga, 2021.</strong> Revisión: Equipo
+de traductores al español de GNU.</div>
+
+<p class="unprintable"><!-- timestamp start -->
+Última actualización:
+
+$Date: 2021/10/16 13:02:35 $
+
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>

Index: licenses/po/fdl-howto.es-en.html
===================================================================
RCS file: licenses/po/fdl-howto.es-en.html
diff -N licenses/po/fdl-howto.es-en.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ licenses/po/fdl-howto.es-en.html    16 Oct 2021 13:02:35 -0000      1.1
@@ -0,0 +1,145 @@
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.77 -->
+<title>Tips on Using the GNU FDL
+- GNU Project - Free Software Foundation</title>
+<!--#include virtual="/licenses/po/fdl-howto.translist" -->
+<!--#include virtual="/server/banner.html" -->
+<h2>Tips on Using the GNU Free Documentation License</h2>
+
+<p>This is a brief explanation of how to place a document under the <a
+href="/licenses/fdl.html">GNU Free Documentation License</a>.  For the
+GNU software licenses, such as the GNU GPL, we have a <a
+href="/licenses/gpl-howto.html">separate page</a>.</p>
+
+<dl>
+<dt><a href="/licenses/fdl-howto-opt.html">How does one use the
+optional features of the FDL?</a></dt>
+<dd>
+We have a <a href="/licenses/fdl-howto-opt.html">separate page</a> that
+discusses how to use the optional features of the FDL.</dd>
+
+<dt>Where must one put the license notification?</dt>
+<dd>
+It is sufficient to put the full license notice in the
+&ldquo;main&rdquo; file of your document.  For example, with
+the <cite>Emacs Lisp Reference Manual</cite>, we have many files
+included by <code>elisp.texi</code>.  We keep the full notification
+in <code>elisp.texi</code>, and in the other files we simply write:
+
+<pre>
+@c -*-texinfo-*-
+@c This is part of the GNU Emacs Lisp Reference Manual.
+@c Copyright (C) 1990, 1991, 1992, 1993, 1994, 1999
+@c   Free Software Foundation, Inc.
+@c See the file elisp.texi for copying conditions.
+</pre></dd>
+
+<dt>What do I do with scripts that are needed to render my document
+properly?</dt>
+<dd>
+We recommend you release these scripts under the GNU FDL as well.  Of
+course, if these scripts are generally useful for other tasks, it is a
+good idea to release them separately under the GNU GPL.</dd>
+
+<dt>Is it required for the document to have invariant sections?</dt>
+<dd>
+No.  It is perfectly acceptable for a document to have no invariant
+sections.</dd>
+
+<dt>Should I try to make sure the document has some invariant
+sections?</dt>
+<dd>
+Not particularly.  If a section's contents ought to be invariant, make
+it invariant.</dd>
+
+<dt>Should I try to avoid invariant sections?</dt>
+<dd>
+Not particularly.  If a section's contents ought to be invariant, make
+it invariant.</dd>
+
+<dt>When should a section be invariant?</dt>
+<dd>
+First of all, keep in mind that a section that treats technical
+material <em>cannot</em> be invariant.  Only a secondary section can
+be invariant, and a technical section is not a secondary section.
+<p>
+If the section is text that you're not allowed to modify, such as a
+copy of the GNU GPL, then it <em>must</em> be invariant.  You can't
+give permission to modify it if you don't have permission to modify
+it.</p>
+<p>
+(One consequence is that you <em>cannot use</em> preexisting text
+which covers technical material if you don't have permission to allow
+modification of that text.)</p>
+<p>
+When a section discusses the philosophy of free software, it is a good
+idea to make that section invariant.  For instance, when we put the
+GNU Manifesto in a manual, or when we include a section explaining why
+free documentation is important, we make that section
+invariant.</p></dd>
+</dl>
+
+</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:gnu@gnu.org";>&lt;gnu@gnu.org&gt;</a>.
+There are also <a href="/contact/">other ways to contact</a>
+the FSF.  Broken links and other corrections or suggestions can be sent
+to <a href="mailto:webmasters@gnu.org";>&lt;webmasters@gnu.org&gt;</a>.</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:web-translators@gnu.org";>
+        &lt;web-translators@gnu.org&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, 2001, 2008, 2009, 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: 2021/10/16 13:02:35 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>