www/gnu/po byte-interview.es.po rms-lisp.es.po ...

[Javier Fdez. Retenaga]

CVSROOT:        /web/www
Module name:    www
Changes by:     Javier Fdez. Retenaga <jfrtnaga>        20/07/03 05:33:36

Modified files:
        gnu/po         : byte-interview.es.po rms-lisp.es.po 
                         thegnuproject.es.po 

Log message:
        Update.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/byte-interview.es.po?cvsroot=www&r1=1.30&r2=1.31
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/rms-lisp.es.po?cvsroot=www&r1=1.38&r2=1.39
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/thegnuproject.es.po?cvsroot=www&r1=1.81&r2=1.82

Patches:
Index: byte-interview.es.po
===================================================================
RCS file: /web/www/www/gnu/po/byte-interview.es.po,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -b -r1.30 -r1.31
--- byte-interview.es.po        1 Jul 2020 15:35:30 -0000       1.30
+++ byte-interview.es.po        3 Jul 2020 09:33:35 -0000       1.31
@@ -1,24 +1,24 @@
 # Spanish translation of http://www.gnu.org/gnu/byte-interview.html
-# Copyright (C) 2009-2011, 2013, 2014 Free Software Foundation, Inc.
+# Copyright (C) 2009-2011, 2013, 2014, 2020 Free Software Foundation, Inc.
 # This file is distributed under the same license as the gnu.org article.
 # Rafa Pereira <rptv2003@yahoo.com>, 2009.
 # Xavier Reina <xreina@fsfe.org>, 2010, 2011.
 # Dora Scilipoti <dora AT gnu DOT org>, 2013, 2014.
+# Javier Fdez. Retenaga <jfrtnaga@gnu.org>, 2020.
 # This translation needs further review.
 #
 msgid ""
 msgstr ""
 "Project-Id-Version: byte-interview.html\n"
 "POT-Creation-Date: 2020-07-01 15:25+0000\n"
-"PO-Revision-Date: 2014-04-05 09:43+0100\n"
-"Last-Translator: Dora Scilipoti <dora AT gnu DOT org>\n"
+"PO-Revision-Date: 2020-07-03 10:55+0200\n"
+"Last-Translator: Javier Fdez. Retenaga <jfrtnaga@gnu.org>\n"
 "Language-Team: Spanish <www-es-general@gnu.org>\n"
 "Language: es\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"X-Outdated-Since: 2020-07-01 15:25+0000\n"
-"X-Poedit-Language: Spanish\n"
+"X-Generator: Poedit 2.2.1\n"
 
 # type: Content of: <title>
 #. type: Content of: <title>
@@ -158,42 +158,6 @@
 
 # type: Content of: <p>
 #. type: Content of: <p>
-# | <strong>Stallman</strong>: I'm currently planning to start with the kernel
-# | that was written at [-<abbr>MIT</abbr>-] {+MIT+} and was released to the
-# | public recently with the idea that I would use it.  This kernel is called
-# | TRIX; it's based on remote procedure call.  I still need to add
-# | compatibility for a lot of the features of Unix which it doesn't have
-# | currently.  I haven't started to work on that yet.  I'm finishing the
-# | compiler before I go to work on the kernel.  I am also going to have to
-# | rewrite the file system.  I intend to make it failsafe just by having it
-# | write blocks in the proper order so that the disk structure is always
-# | consistent.  Then I want to add version numbers.  I have a complicated
-# | scheme to reconcile version numbers with the way people usually use Unix. 
-# | You have to be able to specify filenames without version numbers, but you
-# | also have to be able to specify them with explicit version numbers, and
-# | these both need to work with ordinary Unix programs that have not been
-# | modified in any way to deal with the existence of this feature.  I think I
-# | have a scheme for doing this, and only trying it will show me whether it
-# | really does the job.
-#, fuzzy
-#| msgid ""
-#| "<strong>Stallman</strong>: I'm currently planning to start with the "
-#| "kernel that was written at <abbr>MIT</abbr> and was released to the "
-#| "public recently with the idea that I would use it.  This kernel is called "
-#| "TRIX; it's based on remote procedure call.  I still need to add "
-#| "compatibility for a lot of the features of Unix which it doesn't have "
-#| "currently.  I haven't started to work on that yet.  I'm finishing the "
-#| "compiler before I go to work on the kernel.  I am also going to have to "
-#| "rewrite the file system.  I intend to make it failsafe just by having it "
-#| "write blocks in the proper order so that the disk structure is always "
-#| "consistent.  Then I want to add version numbers.  I have a complicated "
-#| "scheme to reconcile version numbers with the way people usually use "
-#| "Unix.  You have to be able to specify filenames without version numbers, "
-#| "but you also have to be able to specify them with explicit version "
-#| "numbers, and these both need to work with ordinary Unix programs that "
-#| "have not been modified in any way to deal with the existence of this "
-#| "feature.  I think I have a scheme for doing this, and only trying it will "
-#| "show me whether it really does the job."
 msgid ""
 "<strong>Stallman</strong>: I'm currently planning to start with the kernel "
 "that was written at MIT and was released to the public recently with the "
@@ -213,23 +177,23 @@
 "whether it really does the job."
 msgstr ""
 "<strong>Stallman</strong>: En estos momentos estoy considerando empezar con "
-"el núcleo que se escribió en el <abbr>MIT</abbr> y que se ha liberado "
-"recientemente al público con la idea de que yo lo usara.  Se llama TRIX, "
-"está basado en llamadas a procedimientos remotos.  Todavía necesito 
añadirle "
-"compatibilidad para muchas de las características de Unix de las que carece "
-"actualmente.  Todavía no he empezado a trabajar en ello.  Voy a terminar el "
-"compilador antes de empezar con el núcleo.  También voy a tener que 
escribir "
-"de nuevo el sistema de archivos.  Pretendo hacerlo a prueba de fallos "
-"simplemente haciendo que escriba los bloques en el orden adecuado para que "
-"la estructura del disco sea siempre consistente.  Después quiero añadir "
-"números de versión.  Tengo un complicado plan para conciliar los números 
de "
-"versión con la forma en que la gente utiliza habitualmente Unix.  Tiene que "
-"ser capaz de especificar los nombres de fichero sin números de versión, 
pero "
-"también tiene que poder especificarlos con números de versión explícitos, 
y "
-"ambas posibilidades tienen que poder utilizarse con programas Unix normales "
-"que no hayan sido modificados de ningún modo para adaptarlos a esta "
-"funcionalidad.  Creo que tengo una idea para hacerlo, y la única forma de "
-"ver si funciona es probándola."
+"el núcleo que se escribió en el MIT y que se ha liberado recientemente al "
+"público con la idea de que yo lo usara.  Se llama TRIX, está basado en "
+"llamadas a procedimientos remotos.  Todavía necesito añadirle 
compatibilidad "
+"para muchas de las características de Unix de las que carece actualmente.  "
+"Todavía no he empezado a trabajar en ello.  Voy a terminar el compilador "
+"antes de empezar con el núcleo.  También voy a tener que escribir de nuevo "
+"el sistema de archivos.  Pretendo hacerlo a prueba de fallos simplemente "
+"haciendo que escriba los bloques en el orden adecuado para que la estructura "
+"del disco sea siempre consistente.  Después quiero añadir números de "
+"versión.  Tengo un complicado plan para conciliar los números de versión 
con "
+"la forma en que la gente utiliza habitualmente Unix.  Tiene que ser capaz de "
+"especificar los nombres de fichero sin números de versión, pero también "
+"tiene que poder especificarlos con números de versión explícitos, y ambas "
+"posibilidades tienen que poder utilizarse con programas Unix normales que no "
+"hayan sido modificados de ningún modo para adaptarlos a esta funcionalidad.  
"
+"Creo que tengo una idea para hacerlo, y la única forma de ver si funciona es 
"
+"probándola."
 
 # type: Content of: <p>
 #. type: Content of: <p>
@@ -1081,19 +1045,6 @@
 
 # type: Content of: <p>
 #. type: Content of: <p>
-# | <strong>Stallman</strong>: Right now the tape contains GNU EMACS (one
-# | version fits all computers); Bison, a program that replaces [-<acronym-]
-# | {+<abbr+} title=\"Yet Another Compiler [-Compiler\">YACC</acronym>;
-# | <abbr>MIT</abbr>-] {+Compiler\">YACC</abbr>; MIT+} Scheme, which is
-# | Professor Sussman's super-simplified dialect of LISP; and Hack, a
-# | dungeon-exploring game similar to Rogue.
-#, fuzzy
-#| msgid ""
-#| "<strong>Stallman</strong>: Right now the tape contains GNU EMACS (one "
-#| "version fits all computers); Bison, a program that replaces <acronym "
-#| "title=\"Yet Another Compiler Compiler\">YACC</acronym>; <abbr>MIT</abbr> "
-#| "Scheme, which is Professor Sussman's super-simplified dialect of LISP; "
-#| "and Hack, a dungeon-exploring game similar to Rogue."
 msgid ""
 "<strong>Stallman</strong>: Right now the tape contains GNU EMACS (one "
 "version fits all computers); Bison, a program that replaces <abbr title="
@@ -1103,10 +1054,9 @@
 msgstr ""
 "<strong>Stallman</strong>: Ahora mismo la cinta contiene EMACS de GNU (una "
 "única versión sirve para todos los ordenadores); Bison, un programa que "
-"reemplaza a <acronym title=\"Yet Another Compiler Compiler\" lang=\"en\" "
-">YACC</acronym>; Schema, del <abbr>MIT</abbr>, que es el dialecto de LISP "
-"super-simplificado del catedrático Sussman; y Hack, un juego explora-"
-"mazmorras de tipo Rogue."
+"reemplaza a <abbr title=\"Yet Another Compiler Compiler\" lang=\"en\" >YACC</"
+"abbr>; Schema, del MIT, que es el dialecto de LISP supersimplificado del "
+"catedrático Sussman; y Hack, un juego explora-mazmorras de tipo Rogue."
 
 # type: Content of: <p>
 #. type: Content of: <p>
@@ -1251,18 +1201,12 @@
 
 # type: Content of: <div><p>
 #. type: Content of: <div><p>
-# | Copyright &copy; 1999, 2000, 2001, 2002, 2007, 2013, [-2014-] {+2014,
-# | 2020+} Free Software Foundation, Inc.
-#, fuzzy
-#| msgid ""
-#| "Copyright &copy; 1999, 2000, 2001, 2002, 2007, 2013, 2014 Free Software "
-#| "Foundation, Inc."
 msgid ""
 "Copyright &copy; 1999, 2000, 2001, 2002, 2007, 2013, 2014, 2020 Free "
 "Software Foundation, Inc."
 msgstr ""
-"Copyright &copy; 1999, 2000, 2001, 2002, 2007, 2013, 2014 Free Software "
-"Foundation, Inc."
+"Copyright &copy; 1999, 2000, 2001, 2002, 2007, 2013, 2014, 2020 Free "
+"Software Foundation, Inc."
 
 #. type: Content of: <div><p>
 msgid ""

Index: rms-lisp.es.po
===================================================================
RCS file: /web/www/www/gnu/po/rms-lisp.es.po,v
retrieving revision 1.38
retrieving revision 1.39
diff -u -b -r1.38 -r1.39
--- rms-lisp.es.po      1 Jul 2020 14:31:21 -0000       1.38
+++ rms-lisp.es.po      3 Jul 2020 09:33:35 -0000       1.39
@@ -1,24 +1,23 @@
 # Spanish translation of http://www.gnu.org/gnu/rms-lisp.html
-# Copyright (C) 2009-2014 Free Software Foundation, Inc.
+# Copyright (C) 2009-2014, 2020 Free Software Foundation, Inc.
 # This file is distributed under the same license as the gnu.org article.
 # Rafa Pereira <rptv2003@yahoo.com>, 2009.
 # Xavier Reina <xreina@fsfe.org>, 2010, 2011.
 # Dora Scilipoti <dora AT gnu DOT org>, 2012-2014.
-# Javier Fdez. Retenaga <jfrtnaga@gnu.org>, 2019.
+# Javier Fdez. Retenaga <jfrtnaga@gnu.org>, 2019, 2020.
 # This translation needs further review.
 #
 msgid ""
 msgstr ""
 "Project-Id-Version: rms-list.html\n"
 "POT-Creation-Date: 2020-07-01 14:25+0000\n"
-"PO-Revision-Date: 2020-05-03 11:25+0200\n"
+"PO-Revision-Date: 2020-07-03 11:11+0200\n"
 "Last-Translator: Javier Fdez. Retenaga <jfrtnaga@gnu.org>\n"
 "Language-Team: Spanish <www-es-general@gnu.org>\n"
 "Language: es\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"X-Outdated-Since: 2020-07-01 14:25+0000\n"
 "X-Generator: Poedit 2.2.1\n"
 
 # type: Content of: <title>
@@ -157,33 +156,6 @@
 
 # type: Content of: <p>
 #. type: Content of: <p>
-# | The original Emacs did not have Lisp in it. The lower level language, the
-# | non-interpreted language &mdash; was [-<abbr>PDP</abbr>-10-] {+PDP-10+}
-# | Assembler. The interpreter we wrote in that actually wasn't written for
-# | Emacs, it was written for [-<acronym-] {+<abbr+} title=\"Text Editor and
-# | [-COrrector\">TECO</acronym>.-] {+COrrector\">TECO</abbr>.+} It was our
-# | text editor, and was an extremely ugly programming language, as ugly as
-# | could possibly be. The reason was that it wasn't designed to be a
-# | programming language, it was designed to be an editor and command
-# | language. There were commands like &lsquo;5l&rsquo;, meaning &lsquo;move
-# | five lines&rsquo;, or &lsquo;i&rsquo; and then a string and then an ESC to
-# | insert that string. You would type a string that was a series of commands,
-# | which was called a command string. You would end it with ESC ESC, and it
-# | would get executed.
-#, fuzzy
-#| msgid ""
-#| "The original Emacs did not have Lisp in it. The lower level language, the "
-#| "non-interpreted language &mdash; was <abbr>PDP</abbr>-10 Assembler. The "
-#| "interpreter we wrote in that actually wasn't written for Emacs, it was "
-#| "written for <acronym title=\"Text Editor and COrrector\">TECO</acronym>. "
-#| "It was our text editor, and was an extremely ugly programming language, "
-#| "as ugly as could possibly be. The reason was that it wasn't designed to "
-#| "be a programming language, it was designed to be an editor and command "
-#| "language. There were commands like &lsquo;5l&rsquo;, meaning &lsquo;move "
-#| "five lines&rsquo;, or &lsquo;i&rsquo; and then a string and then an ESC "
-#| "to insert that string. You would type a string that was a series of "
-#| "commands, which was called a command string. You would end it with ESC "
-#| "ESC, and it would get executed."
 msgid ""
 "The original Emacs did not have Lisp in it. The lower level language, the "
 "non-interpreted language &mdash; was PDP-10 Assembler. The interpreter we "
@@ -198,44 +170,20 @@
 "would end it with ESC ESC, and it would get executed."
 msgstr ""
 "El Emacs original no incluía Lisp. Su lenguaje, de más bajo nivel y no "
-"interpretado, era Ensamblador del <abbr>PDP</abbr>-10. El intérprete que "
-"escribimos nosotros en realidad no fue escrito para Emacs, sino para "
-"<acronym title=\"Text Editor and COrrector\" lang=\"en\">TECO</acronym>. "
-"<acronym>TECO</acronym> era nuestro editor de textos y era un lenguaje de "
-"programación extremadamente feo, no podía haber sido más feo. La razón 
era "
-"que no fue diseñado para ser un lenguaje de programación, sino como un "
-"lenguaje de órdenes y un editor de textos. Había órdenes como «5l», que "
-"significaba «mover cinco líneas», o «i» seguido de una cadena de 
caracteres "
-"y después ESC para insertar esa cadena de caracteres. Podría escribir una "
-"cadena de caracteres que fuera una secuencia de órdenes, lo que se llamaba "
-"una cadena de órdenes, terminada con ESC ESC, y sería ejecutada."
+"interpretado, era Ensamblador del PDP-10. El intérprete que escribimos "
+"nosotros en realidad no fue escrito para Emacs, sino para <abbr title=\"Text "
+"Editor and COrrector\" lang=\"en\">TECO</abbr>. <abbr>TECO</abbr> era "
+"nuestro editor de textos y era un lenguaje de programación extremadamente "
+"feo, no podía haber sido más feo. La razón era que no fue diseñado para 
ser "
+"un lenguaje de programación, sino como un lenguaje de órdenes y un editor 
de "
+"textos. Había órdenes como «5l», que significaba «mover cinco líneas», 
o «i» "
+"seguido de una cadena de caracteres y después ESC para insertar esa cadena "
+"de caracteres. Podría escribir una cadena de caracteres que fuera una "
+"secuencia de órdenes, lo que se llamaba una cadena de órdenes, terminada 
con "
+"ESC ESC, y sería ejecutada."
 
 # type: Content of: <p>
 #. type: Content of: <p>
-# | Well, people wanted to extend this language with programming facilities,
-# | so they added some. For instance, one of the first was a looping
-# | construct, which was &lt; &gt;. You would put those around things and it
-# | would loop. There were other cryptic commands that could be used to
-# | conditionally exit the loop.  To make Emacs, we <a
-# | href=\"#foot-1\">(1)</a> added facilities to have subroutines with names.
-# | Before that, it was sort of like Basic, and the subroutines could only
-# | have single letters as their names. That was hard to program big programs
-# | with, so we added code so they could have longer names. Actually, there
-# | were some rather sophisticated facilities; I think that Lisp got its
-# | unwind-protect facility from [-<acronym>TECO</acronym>.-] {+TECO.+}
-#, fuzzy
-#| msgid ""
-#| "Well, people wanted to extend this language with programming facilities, "
-#| "so they added some. For instance, one of the first was a looping "
-#| "construct, which was &lt; &gt;. You would put those around things and it "
-#| "would loop. There were other cryptic commands that could be used to "
-#| "conditionally exit the loop.  To make Emacs, we <a href=\"#foot-1\">(1)</"
-#| "a> added facilities to have subroutines with names. Before that, it was "
-#| "sort of like Basic, and the subroutines could only have single letters as "
-#| "their names. That was hard to program big programs with, so we added code "
-#| "so they could have longer names. Actually, there were some rather "
-#| "sophisticated facilities; I think that Lisp got its unwind-protect "
-#| "facility from <acronym>TECO</acronym>."
 msgid ""
 "Well, people wanted to extend this language with programming facilities, so "
 "they added some. For instance, one of the first was a looping construct, "
@@ -260,30 +208,10 @@
 "que permitió que pudieran tener nombres más largos. De hecho, había 
algunos "
 "mecanismos bastante sofisticados; creo que Lisp tomó su mecanismo <span "
 "style=\"font-style:italic;\">unwind-protect</span>, llamémosle, «de-"
-"aplicación-abierta», de <acronym>TECO</acronym>."
+"aplicación-abierta», de TECO."
 
 # type: Content of: <p>
 #. type: Content of: <p>
-# | We started putting in rather sophisticated facilities, all with the
-# | ugliest syntax you could ever think of, and it worked &mdash; people were
-# | able to write large programs in it anyway. The obvious lesson was that a
-# | language like [-<acronym>TECO</acronym>,-] {+TECO,+} which wasn't designed
-# | to be a programming language, was the wrong way to go. The language that
-# | you build your extensions on shouldn't be thought of as a programming
-# | language in afterthought; it should be designed as a programming language.
-# | In fact, we discovered that the best programming language for that purpose
-# | was Lisp.
-#, fuzzy
-#| msgid ""
-#| "We started putting in rather sophisticated facilities, all with the "
-#| "ugliest syntax you could ever think of, and it worked &mdash; people were "
-#| "able to write large programs in it anyway. The obvious lesson was that a "
-#| "language like <acronym>TECO</acronym>, which wasn't designed to be a "
-#| "programming language, was the wrong way to go. The language that you "
-#| "build your extensions on shouldn't be thought of as a programming "
-#| "language in afterthought; it should be designed as a programming "
-#| "language. In fact, we discovered that the best programming language for "
-#| "that purpose was Lisp."
 msgid ""
 "We started putting in rather sophisticated facilities, all with the ugliest "
 "syntax you could ever think of, and it worked &mdash; people were able to "
@@ -297,12 +225,12 @@
 "Empezamos a añadir otros mecanismos sofisticados, todos ellos con la "
 "sintaxis más horrible que puedan imaginar, y funcionó, por lo menos la 
gente "
 "fue capaz de escribir programas extensos con él. La lección obvia fue que "
-"utilizar un lenguaje como <acronym>TECO</acronym>, que no había sido "
-"diseñado como lenguaje de programación, fue una opción equivocada. El "
-"lenguaje sobre el que construye sus extensiones no debería ser considerado "
-"como un lenguaje de programación a posteriori, sino que debería ser 
diseñado "
-"como un lenguaje de programación desde un principio. De hecho, descubrimos "
-"que el mejor lenguaje de programación para ese propósito era Lisp."
+"utilizar un lenguaje como TECO, que no había sido diseñado como lenguaje de 
"
+"programación, fue una opción equivocada. El lenguaje sobre el que construye 
"
+"sus extensiones no debería ser considerado como un lenguaje de programación 
"
+"a posteriori, sino que debería ser diseñado como un lenguaje de 
programación "
+"desde un principio. De hecho, descubrimos que el mejor lenguaje de "
+"programación para ese propósito era Lisp."
 
 # type: Content of: <p>
 #. type: Content of: <p>
@@ -353,56 +281,6 @@
 
 # type: Content of: <p>
 #. type: Content of: <p>
-# | At that point, people began to wonder how they could get something like
-# | this on a platform where they didn't have full service Lisp
-# | implementation. Multics MacLisp had a compiler as well as an interpreter
-# | &mdash; it was a full-fledged Lisp system &mdash; but people wanted to
-# | implement something like that on other systems where they had not already
-# | written a Lisp compiler. Well, if you didn't have the Lisp compiler you
-# | couldn't write the whole editor in Lisp &mdash; it would be too slow,
-# | especially redisplay, if it had to run interpreted Lisp.  So we developed
-# | a hybrid technique. The idea was to write a Lisp interpreter and the lower
-# | level parts of the editor together, so that parts of the editor were
-# | built-in Lisp facilities. Those would be whatever parts we felt we had to
-# | optimize. This was a technique that we had already consciously practiced
-# | in the original Emacs, because there were certain fairly high level
-# | features which we re-implemented in machine language, making them into
-# | [-<acronym>TECO</acronym>-] {+TECO+} primitives. For instance, there was a
-# | [-<acronym>TECO</acronym>-] {+TECO+} primitive to fill a paragraph
-# | (actually, to do most of the work of filling a paragraph, because some of
-# | the less time-consuming parts of the job would be done at the higher level
-# | by a [-<acronym>TECO</acronym>-] {+TECO+} program). You could do the whole
-# | job by writing a [-<acronym>TECO</acronym>-] {+TECO+} program, but that
-# | was too slow, so we optimized it by putting part of it in machine
-# | language. We used the same idea here (in the hybrid technique), that most
-# | of the editor would be written in Lisp, but certain parts of it that had
-# | to run particularly fast would be written at a lower level.
-#, fuzzy
-#| msgid ""
-#| "At that point, people began to wonder how they could get something like "
-#| "this on a platform where they didn't have full service Lisp "
-#| "implementation. Multics MacLisp had a compiler as well as an interpreter "
-#| "&mdash; it was a full-fledged Lisp system &mdash; but people wanted to "
-#| "implement something like that on other systems where they had not already "
-#| "written a Lisp compiler. Well, if you didn't have the Lisp compiler you "
-#| "couldn't write the whole editor in Lisp &mdash; it would be too slow, "
-#| "especially redisplay, if it had to run interpreted Lisp.  So we developed "
-#| "a hybrid technique. The idea was to write a Lisp interpreter and the "
-#| "lower level parts of the editor together, so that parts of the editor "
-#| "were built-in Lisp facilities. Those would be whatever parts we felt we "
-#| "had to optimize. This was a technique that we had already consciously "
-#| "practiced in the original Emacs, because there were certain fairly high "
-#| "level features which we re-implemented in machine language, making them "
-#| "into <acronym>TECO</acronym> primitives. For instance, there was a "
-#| "<acronym>TECO</acronym> primitive to fill a paragraph (actually, to do "
-#| "most of the work of filling a paragraph, because some of the less time-"
-#| "consuming parts of the job would be done at the higher level by a "
-#| "<acronym>TECO</acronym> program). You could do the whole job by writing a "
-#| "<acronym>TECO</acronym> program, but that was too slow, so we optimized "
-#| "it by putting part of it in machine language. We used the same idea here "
-#| "(in the hybrid technique), that most of the editor would be written in "
-#| "Lisp, but certain parts of it that had to run particularly fast would be "
-#| "written at a lower level."
 msgid ""
 "At that point, people began to wonder how they could get something like this "
 "on a platform where they didn't have full service Lisp implementation. "
@@ -442,16 +320,15 @@
 "consideráramos que teníamos que optimizar. Ya habíamos utilizado esta "
 "técnica en el Emacs original, cuando reescribimos en lenguaje máquina "
 "algunas funciones de nivel relativamente alto, transformándolas en "
-"primitivas <acronym>TECO</acronym>. Por ejemplo, había una primitiva "
-"<acronym>TECO</acronym> para rellenar un párrafo (en realidad, para hacer "
-"casi todo el trabajo necesario para rellenar un párrafo, porque algunas de "
-"las tareas que menos tiempo consumían eran realizadas en un nivel superior "
-"por un programa <acronym>TECO</acronym>). Se podría haber hecho todo el "
-"trabajo con un programa <acronym>TECO</acronym>, pero habría resultado "
-"demasiado lento, por eso lo optimizamos escribiendo parte de él en lenguaje "
-"máquina. Esa misma idea es la que usamos aquí (en la técnica híbrida): "
-"escribimos la mayoría del editor en Lisp, pero escribimos en un nivel "
-"inferior algunas partes que tenían que ejecutarse particularmente rápido."
+"primitivas TECO. Por ejemplo, había una primitiva TECO para rellenar un "
+"párrafo (en realidad, para hacer casi todo el trabajo necesario para "
+"rellenar un párrafo, porque algunas de las tareas que menos tiempo 
consumían "
+"eran realizadas en un nivel superior por un programa TECO). Se podría haber "
+"hecho todo el trabajo con un programa TECO, pero habría resultado demasiado "
+"lento, por eso lo optimizamos escribiendo parte de él en lenguaje máquina. "
+"Esa misma idea es la que usamos aquí (en la técnica híbrida): escribimos 
la "
+"mayoría del editor en Lisp, pero escribimos en un nivel inferior algunas "
+"partes que tenían que ejecutarse particularmente rápido."
 
 # type: Content of: <p>
 #. type: Content of: <p>
@@ -477,33 +354,6 @@
 
 # type: Content of: <p>
 #. type: Content of: <p>
-# | Now, this was not the first Emacs that was written in C and ran on Unix.
-# | The first was written by James Gosling, and was referred to as GosMacs. A
-# | strange thing happened with him. In the beginning, he seemed to be
-# | influenced by the same spirit of sharing and cooperation of the original
-# | Emacs. I first released the original Emacs to people at
-# | [-<abbr>MIT</abbr>.-] {+MIT.+} Someone wanted to port it to run on Twenex
-# | &mdash; it originally only ran on the Incompatible Timesharing System we
-# | used at [-<abbr>MIT</abbr>.-] {+MIT.+} They ported it to Twenex, which
-# | meant that there were a few hundred installations around the world that
-# | could potentially use it. We started distributing it to them, with the
-# | rule that &ldquo;you had to send back all of your improvements&rdquo; so
-# | we could all benefit. No one ever tried to enforce that, but as far as I
-# | know people did cooperate.
-#, fuzzy
-#| msgid ""
-#| "Now, this was not the first Emacs that was written in C and ran on Unix. "
-#| "The first was written by James Gosling, and was referred to as GosMacs. A "
-#| "strange thing happened with him. In the beginning, he seemed to be "
-#| "influenced by the same spirit of sharing and cooperation of the original "
-#| "Emacs. I first released the original Emacs to people at <abbr>MIT</abbr>. "
-#| "Someone wanted to port it to run on Twenex &mdash; it originally only ran "
-#| "on the Incompatible Timesharing System we used at <abbr>MIT</abbr>. They "
-#| "ported it to Twenex, which meant that there were a few hundred "
-#| "installations around the world that could potentially use it. We started "
-#| "distributing it to them, with the rule that &ldquo;you had to send back "
-#| "all of your improvements&rdquo; so we could all benefit. No one ever "
-#| "tried to enforce that, but as far as I know people did cooperate."
 msgid ""
 "Now, this was not the first Emacs that was written in C and ran on Unix. The "
 "first was written by James Gosling, and was referred to as GosMacs. A "
@@ -522,16 +372,16 @@
 "Unix. El primero lo escribió James Gosling, y era conocido como GosMacs. Con 
"
 "James ocurrió algo extraño. Al principio parecía estar influido por el 
mismo "
 "espíritu de participación y cooperación del Emacs original. En primer 
lugar "
-"liberé el Emacs original para personal del <abbr>MIT</abbr>. Alguien quería 
"
-"adaptarlo para su ejecución en Twenex, inicialmente sólo se podía ejecutar 
"
-"sobre el <span style=\"font-style:italic;\">Incompatible Timesharing System</"
-"span> [sistema de tiempo compartido incompatible] que usábamos en el "
-"<abbr>MIT</abbr>. Lo adaptaron a Twenex, lo cual significaba que había unos "
-"pocos cientos de instalaciones alrededor del mundo que podían, "
-"potencialmente, usarlo. Empezamos a distribuírselo junto con la norma de que 
"
-"«usted debía enviarnos todas sus mejoras» para que así todos nos 
pudiéramos "
-"beneficiar. Nadie intentó nunca hacer cumplir esta norma pero, hasta donde "
-"yo sé, la gente cooperaba."
+"liberé el Emacs original para personal del MIT. Alguien quería adaptarlo "
+"para su ejecución en Twenex, inicialmente sólo se podía ejecutar sobre el "
+"<span style=\"font-style:italic;\">Incompatible Timesharing System</span> "
+"[sistema de tiempo compartido incompatible] que usábamos en el MIT. Lo "
+"adaptaron a Twenex, lo cual significaba que había unos pocos cientos de "
+"instalaciones alrededor del mundo que podían, potencialmente, usarlo. "
+"Empezamos a distribuírselo junto con la norma de que «usted debía 
enviarnos "
+"todas sus mejoras» para que así todos nos pudiéramos beneficiar. Nadie "
+"intentó nunca hacer cumplir esta norma pero, hasta donde yo sé, la gente "
+"cooperaba."
 
 # type: Content of: <p>
 #. type: Content of: <p>
@@ -617,27 +467,6 @@
 
 # type: Content of: <p>
 #. type: Content of: <p>
-# | This second Emacs program was &lsquo;free software&rsquo; in the modern
-# | sense of the term &mdash; it was part of an explicit political campaign to
-# | make software free. The essence of this campaign was that everybody should
-# | be free to do the things we did in the old days at [-<abbr>MIT</abbr>,-]
-# | {+MIT>,+} working together on software and working with whomever wanted to
-# | work with us.  That is the basis for the free software movement &mdash;
-# | the experience I had, the life that I've lived at the [-<abbr>MIT</abbr>-]
-# | {+MIT+} AI lab &mdash; to be working on human knowledge, and not be
-# | standing in the way of anybody's further using and further disseminating
-# | human knowledge.
-#, fuzzy
-#| msgid ""
-#| "This second Emacs program was &lsquo;free software&rsquo; in the modern "
-#| "sense of the term &mdash; it was part of an explicit political campaign "
-#| "to make software free. The essence of this campaign was that everybody "
-#| "should be free to do the things we did in the old days at <abbr>MIT</"
-#| "abbr>, working together on software and working with whomever wanted to "
-#| "work with us.  That is the basis for the free software movement &mdash; "
-#| "the experience I had, the life that I've lived at the <abbr>MIT</abbr> AI "
-#| "lab &mdash; to be working on human knowledge, and not be standing in the "
-#| "way of anybody's further using and further disseminating human knowledge."
 msgid ""
 "This second Emacs program was &lsquo;free software&rsquo; in the modern "
 "sense of the term &mdash; it was part of an explicit political campaign to "
@@ -652,12 +481,12 @@
 "Este segundo Emacs era «software libre» en el sentido moderno del término: 
"
 "formaba parte de una campaña política explícita para la elaboración de "
 "software libre. La esencia de la campaña era que todo el mundo debería 
tener "
-"la libertad de hacer lo que nosotros hacíamos en el <abbr>MIT</abbr> en los "
-"viejos tiempos: trabajar conjuntamente en el software y colaborar con todo "
-"el que quisiera trabajar con nosotros. Esta es la base del movimiento por el "
+"la libertad de hacer lo que nosotros hacíamos en el MIT en los viejos "
+"tiempos: trabajar conjuntamente en el software y colaborar con todo el que "
+"quisiera trabajar con nosotros. Esta es la base del movimiento por el "
 "software libre, la experiencia que tuve, la vida que viví en el Laboratorio "
-"de Inteligencia Artificial del <abbr>MIT</abbr>: trabajar para el "
-"conocimiento, y no obstaculizar su uso ni su expansión."
+"de Inteligencia Artificial del MIT: trabajar para el conocimiento, y no "
+"obstaculizar su uso ni su expansión."
 
 # type: Content of: <p>
 #. type: Content of: <p>
@@ -799,34 +628,6 @@
 
 # type: Content of: <p>
 #. type: Content of: <p>
-# | Thus, the abandonment of our lab was followed by &ldquo;war&rdquo; in our
-# | lab.  The abandonment happened when Symbolics hired away all the hackers,
-# | except me and the few who worked at LMI part-time. Then they invoked a
-# | rule and eliminated people who worked part-time for [-<abbr>MIT</abbr>,-]
-# | {+MIT,+} so they had to leave entirely, which left only me. The AI lab was
-# | now helpless.  And [-<abbr>MIT</abbr>-] {+MIT+} had made a very foolish
-# | arrangement with these two companies.  It was a three-way contract where
-# | both companies licensed the use of Lisp machine system sources. These
-# | companies were required to let [-<abbr>MIT</abbr>-] {+MIT+} use their
-# | changes. But it didn't say in the contract that [-<abbr>MIT</abbr>-]
-# | {+MIT+} was entitled to put them into the [-<abbr>MIT</abbr>-] {+MIT+}
-# | Lisp machine systems that both companies had licensed. Nobody had
-# | envisioned that the AI lab's hacker group would be wiped out, but it was.
-#, fuzzy
-#| msgid ""
-#| "Thus, the abandonment of our lab was followed by &ldquo;war&rdquo; in our "
-#| "lab.  The abandonment happened when Symbolics hired away all the hackers, "
-#| "except me and the few who worked at LMI part-time. Then they invoked a "
-#| "rule and eliminated people who worked part-time for <abbr>MIT</abbr>, so "
-#| "they had to leave entirely, which left only me. The AI lab was now "
-#| "helpless.  And <abbr>MIT</abbr> had made a very foolish arrangement with "
-#| "these two companies.  It was a three-way contract where both companies "
-#| "licensed the use of Lisp machine system sources. These companies were "
-#| "required to let <abbr>MIT</abbr> use their changes. But it didn't say in "
-#| "the contract that <abbr>MIT</abbr> was entitled to put them into the "
-#| "<abbr>MIT</abbr> Lisp machine systems that both companies had licensed. "
-#| "Nobody had envisioned that the AI lab's hacker group would be wiped out, "
-#| "but it was."
 msgid ""
 "Thus, the abandonment of our lab was followed by &ldquo;war&rdquo; in our "
 "lab.  The abandonment happened when Symbolics hired away all the hackers, "
@@ -844,33 +645,19 @@
 "nuestro laboratorio. El abandono tuvo lugar cuando Symbolics se llevó a "
 "todos los hackers, excepto a los pocos que trabajaban a tiempo parcial en "
 "LMI y a mí mismo. Luego apelaron a una norma y eliminaron a la gente que "
-"trabajaba a tiempo parcial para el <abbr>MIT</abbr>, que tuvo que marcharse, "
-"lo cual me dejo sólo a mí. En ese momento el Laboratorio de Inteligencia "
-"Artificial estaba indefenso. Y, además, el <abbr>MIT</abbr> había llegado a 
"
-"un acuerdo muy poco sensato con esas dos empresas. Era un contrato a tres "
-"bandas por el que ambas empresas autorizaban el uso de las fuentes del "
-"sistema de la máquina Lisp. Estas empresas debían permitir al <abbr>MIT</"
-"abbr> usar sus modificaciones. Pero el contrato no decía que el <abbr>MIT</"
-"abbr> tuviera derecho a instalarlas en las máquinas Lisp para cuyo uso le "
-"habían otorgado licencia ambas empresas. Nadie había previsto que el grupo "
-"de hackers del Laboratorio de Inteligencia Artificial sería aniquilado, pero 
"
-"lo fue."
+"trabajaba a tiempo parcial para el MIT, que tuvo que marcharse, lo cual me "
+"dejo sólo a mí. En ese momento el Laboratorio de Inteligencia Artificial "
+"estaba indefenso. Y, además, el MIT había llegado a un acuerdo muy poco "
+"sensato con esas dos empresas. Era un contrato a tres bandas por el que "
+"ambas empresas autorizaban el uso de las fuentes del sistema de la máquina "
+"Lisp. Estas empresas debían permitir al MIT usar sus modificaciones. Pero el 
"
+"contrato no decía que el MIT tuviera derecho a instalarlas en las máquinas "
+"Lisp para cuyo uso le habían otorgado licencia ambas empresas. Nadie había "
+"previsto que el grupo de hackers del Laboratorio de Inteligencia Artificial "
+"sería aniquilado, pero lo fue."
 
 # type: Content of: <p>
 #. type: Content of: <p>
-# | So Symbolics came up with a plan <a href=\"#foot-4\">(4)</a>.  They said
-# | to the lab, &ldquo;We will continue making our changes to the system
-# | available for you to use, but you can't put it into the
-# | [-<abbr>MIT</abbr>-] {+MIT+} Lisp machine system. Instead, we'll give you
-# | access to Symbolics' Lisp machine system, and you can run it, but that's
-# | all you can do.&rdquo;
-#, fuzzy
-#| msgid ""
-#| "So Symbolics came up with a plan <a href=\"#foot-4\">(4)</a>.  They said "
-#| "to the lab, &ldquo;We will continue making our changes to the system "
-#| "available for you to use, but you can't put it into the <abbr>MIT</abbr> "
-#| "Lisp machine system. Instead, we'll give you access to Symbolics' Lisp "
-#| "machine system, and you can run it, but that's all you can do.&rdquo;"
 msgid ""
 "So Symbolics came up with a plan <a href=\"#foot-4\">(4)</a>.  They said to "
 "the lab, &ldquo;We will continue making our changes to the system available "
@@ -880,32 +667,12 @@
 msgstr ""
 "A Symbolics se le ocurrió un plan <a href=\"#foot-4\">(4)</a>. Dijeron al "
 "laboratorio: «seguiremos permitiéndoles que usen nuestras modificaciones al 
"
-"sistema, pero no podrán instalarlas en la máquina Lisp del 
<abbr>MIT</abbr>. "
-"En su lugar, les daremos acceso al sistema de la máquina Lisp de Symbolics, "
-"y podrán ejecutarlo, pero eso será todo lo que podrán hacer»."
+"sistema, pero no podrán instalarlas en la máquina Lisp del MIT. En su 
lugar, "
+"les daremos acceso al sistema de la máquina Lisp de Symbolics, y podrán "
+"ejecutarlo, pero eso será todo lo que podrán hacer»."
 
 # type: Content of: <p>
 #. type: Content of: <p>
-# | This, in effect, meant that they demanded that we had to choose a side,
-# | and use either the [-<abbr>MIT</abbr>-] {+MIT+} version of the system or
-# | the Symbolics version.  Whichever choice we made determined which system
-# | our improvements went to. If we worked on and improved the Symbolics
-# | version, we would be supporting Symbolics alone. If we used and improved
-# | the [-<abbr>MIT</abbr>-] {+MIT+} version of the system, we would be doing
-# | work available to both companies, but Symbolics saw that we would be
-# | supporting LMI because we would be helping them continue to exist. So we
-# | were not allowed to be neutral anymore.
-#, fuzzy
-#| msgid ""
-#| "This, in effect, meant that they demanded that we had to choose a side, "
-#| "and use either the <abbr>MIT</abbr> version of the system or the "
-#| "Symbolics version.  Whichever choice we made determined which system our "
-#| "improvements went to. If we worked on and improved the Symbolics version, "
-#| "we would be supporting Symbolics alone. If we used and improved the "
-#| "<abbr>MIT</abbr> version of the system, we would be doing work available "
-#| "to both companies, but Symbolics saw that we would be supporting LMI "
-#| "because we would be helping them continue to exist. So we were not "
-#| "allowed to be neutral anymore."
 msgid ""
 "This, in effect, meant that they demanded that we had to choose a side, and "
 "use either the MIT version of the system or the Symbolics version.  "
@@ -917,14 +684,13 @@
 "So we were not allowed to be neutral anymore."
 msgstr ""
 "Esto, en la práctica, significaba que nos exigían posicionarnos en un bando 
"
-"y utilizar, o bien la versión del <abbr>MIT</abbr> del sistema, o bien la "
-"versión de Symbolics. Nuestra decisión determinaría a qué sistema irían "
-"nuestras mejoras. Si mejorábamos la versión de Symbolics, estaríamos "
-"apoyando a Symbolics exclusivamente. Si utilizábamos y mejorábamos la "
-"versión del sistema del <abbr>MIT</abbr>, ambas empresas tendrían acceso a "
-"nuestro trabajo. Pero Symbolics vio que estaríamos dando apoyo a LMI porque "
-"estaríamos ayudando a que siguiera existiendo. Así, no se nos permitió "
-"seguir siendo neutrales."
+"y utilizar, o bien la versión del MIT del sistema, o bien la versión de "
+"Symbolics. Nuestra decisión determinaría a qué sistema irían nuestras "
+"mejoras. Si mejorábamos la versión de Symbolics, estaríamos apoyando a "
+"Symbolics exclusivamente. Si utilizábamos y mejorábamos la versión del "
+"sistema del MIT, ambas empresas tendrían acceso a nuestro trabajo. Pero "
+"Symbolics vio que estaríamos dando apoyo a LMI porque estaríamos ayudando a 
"
+"que siguiera existiendo. Así, no se nos permitió seguir siendo neutrales."
 
 # type: Content of: <p>
 #. type: Content of: <p>
@@ -967,9 +733,9 @@
 "Incorporated, and the two companies went on. But, I didn't want to spend "
 "years and years punishing someone, just thwarting an evil deed. I figured "
 "they had been punished pretty thoroughly because they were stuck with "
-"competition that was not leaving or going to disappear <a href=\"#foot-7\">"
-"(7)</a>. Meanwhile, it was time to start building a new community to replace "
-"the one that their actions and others had wiped out."
+"competition that was not leaving or going to disappear <a href="
+"\"#foot-7\">(7)</a>. Meanwhile, it was time to start building a new "
+"community to replace the one that their actions and others had wiped out."
 msgstr ""
 "De esta manera, durante dos años evité que acabaran con Lisp Machines "
 "Incorporated, y las dos empresas siguieron adelante. Pero no quería pasarme "
@@ -981,19 +747,6 @@
 
 # type: Content of: <p>
 #. type: Content of: <p>
-# | The Lisp community in the 70s was not limited to the [-<abbr>MIT</abbr>-]
-# | {+MIT+} AI Lab, and the hackers were not all at [-<abbr>MIT</abbr>.-]
-# | {+MIT.+} The war that Symbolics started was what wiped out
-# | [-<abbr>MIT</abbr>,-] {+MIT,+} but there were other events going on then.
-# | There were people giving up on cooperation, and together this wiped out
-# | the community and there wasn't much left.
-#, fuzzy
-#| msgid ""
-#| "The Lisp community in the 70s was not limited to the <abbr>MIT</abbr> AI "
-#| "Lab, and the hackers were not all at <abbr>MIT</abbr>. The war that "
-#| "Symbolics started was what wiped out <abbr>MIT</abbr>, but there were "
-#| "other events going on then. There were people giving up on cooperation, "
-#| "and together this wiped out the community and there wasn't much left."
 msgid ""
 "The Lisp community in the 70s was not limited to the MIT AI Lab, and the "
 "hackers were not all at MIT. The war that Symbolics started was what wiped "
@@ -1002,10 +755,10 @@
 "wasn't much left."
 msgstr ""
 "La comunidad Lisp en los setenta no estaba limitada al Laboratorio de "
-"Inteligencia Artificial del <abbr>MIT</abbr>, y no todos los hackers estaban "
-"en el <abbr>MIT</abbr>. La guerra iniciada por Symbolics fue lo que aniquiló 
"
-"el <abbr>MIT</abbr>, pero había otras actividades en marcha. Había gente 
que "
-"abandonó la cooperación, y esto también contribuyó a extinguir la 
comunidad."
+"Inteligencia Artificial del MIT, y no todos los hackers estaban en el MIT. "
+"La guerra iniciada por Symbolics fue lo que aniquiló el MIT, pero había "
+"otras actividades en marcha. Había gente que abandonó la cooperación, y 
esto "
+"también contribuyó a extinguir la comunidad."
 
 # type: Content of: <p>
 #. type: Content of: <p>
@@ -1136,36 +889,6 @@
 
 # type: Content of: <p>
 #. type: Content of: <p>
-# | At the time, [-<acronym-] {+<abbr+} title=\"Tool Command
-# | [-Language\">TCL</acronym>-] {+Language\">TCL</abbr>+} was being pushed
-# | heavily for this purpose. I had a very low opinion of
-# | [-<acronym>TCL</acronym>,-] {+TCL,+} basically because it wasn't Lisp. It
-# | looks a tiny bit like Lisp, but semantically it isn't, and it's not as
-# | clean.  Then someone showed me an ad where Sun was trying to hire somebody
-# | to work on [-<acronym>TCL</acronym>-] {+TCL+} to make it the
-# | &ldquo;de-facto standard extension language&rdquo; of the world. And I
-# | thought, &ldquo;We've got to stop that from happening.&rdquo; So we
-# | started to make Scheme the standard extensibility language for GNU. Not
-# | Common Lisp, because it was too large. The idea was that we would have a
-# | Scheme interpreter designed to be linked into applications in the same way
-# | [-<acronym>TCL</acronym>-] {+TCL+} was linked into applications. We would
-# | then recommend that as the preferred extensibility package for all GNU
-# | programs.
-#, fuzzy
-#| msgid ""
-#| "At the time, <acronym title=\"Tool Command Language\">TCL</acronym> was "
-#| "being pushed heavily for this purpose. I had a very low opinion of "
-#| "<acronym>TCL</acronym>, basically because it wasn't Lisp. It looks a tiny "
-#| "bit like Lisp, but semantically it isn't, and it's not as clean.  Then "
-#| "someone showed me an ad where Sun was trying to hire somebody to work on "
-#| "<acronym>TCL</acronym> to make it the &ldquo;de-facto standard extension "
-#| "language&rdquo; of the world. And I thought, &ldquo;We've got to stop "
-#| "that from happening.&rdquo; So we started to make Scheme the standard "
-#| "extensibility language for GNU. Not Common Lisp, because it was too "
-#| "large. The idea was that we would have a Scheme interpreter designed to "
-#| "be linked into applications in the same way <acronym>TCL</acronym> was "
-#| "linked into applications. We would then recommend that as the preferred "
-#| "extensibility package for all GNU programs."
 msgid ""
 "At the time, <abbr title=\"Tool Command Language\">TCL</abbr> was being "
 "pushed heavily for this purpose. I had a very low opinion of TCL, basically "
@@ -1180,48 +903,22 @@
 "We would then recommend that as the preferred extensibility package for all "
 "GNU programs."
 msgstr ""
-"En aquel momento, <acronym title=\"Tool Command Language\" lang=\"en\">TCL</"
-"acronym> estaba recibiendo un fuerte impulso como lenguaje a utilizar para "
-"este propósito. Yo tenía una opinión muy negativa de 
<acronym>TCL</acronym>, "
-"básicamente porque no era Lisp. Tiene un ligerísimo parecido con Lisp, pero 
"
-"no semánticamente, y no es tan limpio. Después, me mostraron un anuncio en "
-"el que Sun ofrecía un puesto de trabajo para trabajar con <acronym>TCL</"
-"acronym> y hacer de él el «lenguaje de extensión estándar, de facto» en 
el "
-"mundo. Y pensé: «Tenemos que evitar que eso llegue a ocurrir.». Así que "
-"empezamos a hacer de Scheme el lenguaje para extensiones estándar para GNU. "
-"No Common Lisp, porque era demasiado voluminoso. La idea era tener un "
-"intérprete Scheme diseñado para ser enlazado en las aplicaciones de la 
misma "
-"manera que se enlazaba <acronym>TCL</acronym>. Entonces lo recomendaríamos "
-"como el paquete para extensiones prefererido para todos los programas GNU."
+"En aquel momento, <abbr title=\"Tool Command Language\" lang=\"en\">TCL</"
+"abbr> estaba recibiendo un fuerte impulso como lenguaje a utilizar para este "
+"propósito. Yo tenía una opinión muy negativa de TCL, básicamente porque 
no "
+"era Lisp. Tiene un ligerísimo parecido con Lisp, pero no semánticamente, y "
+"no es tan limpio. Después, me mostraron un anuncio en el que Sun ofrecía un 
"
+"puesto de trabajo para trabajar con TCL y hacer de él el «lenguaje de "
+"extensión estándar, de facto» en el mundo. Y pensé: «Tenemos que evitar 
que "
+"eso llegue a ocurrir.». Así que empezamos a hacer de Scheme el lenguaje 
para "
+"extensiones estándar para GNU. No Common Lisp, porque era demasiado "
+"voluminoso. La idea era tener un intérprete Scheme diseñado para ser "
+"enlazado en las aplicaciones de la misma manera que se enlazaba TCL. "
+"Entonces lo recomendaríamos como el paquete para extensiones prefererido "
+"para todos los programas GNU."
 
 # type: Content of: <p>
 #. type: Content of: <p>
-# | There's an interesting benefit you can get from using such a powerful
-# | language as a version of Lisp as your primary extensibility language.  You
-# | can implement other languages by translating them into your primary
-# | language. If your primary language is [-<acronym>TCL</acronym>,-] {+TCL,+}
-# | you can't very easily implement Lisp by translating it into
-# | [-<acronym>TCL</acronym>.-] {+TCL.+} But if your primary language is Lisp,
-# | it's not that hard to implement other things by translating them. Our idea
-# | was that if each extensible application supported Scheme, you could write
-# | an implementation of [-<acronym>TCL</acronym>-] {+TCL+} or Python or Perl
-# | in Scheme that translates that program into Scheme. Then you could load
-# | that into any application and customize it in your favorite language and
-# | it would work with other customizations as well.
-#, fuzzy
-#| msgid ""
-#| "There's an interesting benefit you can get from using such a powerful "
-#| "language as a version of Lisp as your primary extensibility language.  "
-#| "You can implement other languages by translating them into your primary "
-#| "language. If your primary language is <acronym>TCL</acronym>, you can't "
-#| "very easily implement Lisp by translating it into <acronym>TCL</acronym>. "
-#| "But if your primary language is Lisp, it's not that hard to implement "
-#| "other things by translating them. Our idea was that if each extensible "
-#| "application supported Scheme, you could write an implementation of "
-#| "<acronym>TCL</acronym> or Python or Perl in Scheme that translates that "
-#| "program into Scheme. Then you could load that into any application and "
-#| "customize it in your favorite language and it would work with other "
-#| "customizations as well."
 msgid ""
 "There's an interesting benefit you can get from using such a powerful "
 "language as a version of Lisp as your primary extensibility language.  You "
@@ -1238,14 +935,13 @@
 "Usted puede obtener un beneficio interesante del uso de un lenguaje tan "
 "potente como un dialecto de Lisp como su lenguaje primario de extensión: "
 "puede implementar otros lenguajes traduciéndolos a su lenguaje primario. Si "
-"su lenguaje primario es <acronym>TCL</acronym>, usted no podrá implementar "
-"Lisp fácilmente mediante su traducción a <acronym>TCL</acronym>. Pero si su 
"
-"lenguaje primario es Lisp, no es tan difícil implementar otros lenguajes "
-"traduciéndolos. Nuestra idea era que si cada aplicación extensible admitía 
"
-"Scheme, usted podría escribir una implementación de <acronym>TCL</acronym> 
o "
-"Python o Perl en Scheme que tradujera los programas en esos lenguajes a "
-"Scheme. Entonces, usted podría cargar su traductor en cualquier aplicación 
y "
-"extender dicha aplicación usando su lenguaje favorito."
+"su lenguaje primario es TCL, usted no podrá implementar Lisp fácilmente "
+"mediante su traducción a TCL. Pero si su lenguaje primario es Lisp, no es "
+"tan difícil implementar otros lenguajes traduciéndolos. Nuestra idea era 
que "
+"si cada aplicación extensible admitía Scheme, usted podría escribir una "
+"implementación de TCL o Python o Perl en Scheme que tradujera los programas "
+"en esos lenguajes a Scheme. Entonces, usted podría cargar su traductor en "
+"cualquier aplicación y extender dicha aplicación usando su lenguaje 
favorito."
 
 # type: Content of: <p>
 #. type: Content of: <p>
@@ -1552,14 +1248,10 @@
 
 # type: Content of: <div><p>
 #. type: Content of: <div><p>
-# | Copyright &copy; 2003, 2007, 2013, [-2014-] {+2014, 2020+} Free Software
-# | Foundation, Inc.
-#, fuzzy
-#| msgid ""
-#| "Copyright &copy; 2003, 2007, 2013, 2014 Free Software Foundation, Inc."
 msgid ""
 "Copyright &copy; 2003, 2007, 2013, 2014, 2020 Free Software Foundation, Inc."
-msgstr "Copyright &copy; 2003, 2007, 2013, 2014 Free Software Foundation, Inc."
+msgstr ""
+"Copyright &copy; 2003, 2007, 2013, 2014, 2020 Free Software Foundation, Inc."
 
 #. type: Content of: <div><p>
 msgid ""

Index: thegnuproject.es.po
===================================================================
RCS file: /web/www/www/gnu/po/thegnuproject.es.po,v
retrieving revision 1.81
retrieving revision 1.82
diff -u -b -r1.81 -r1.82
--- thegnuproject.es.po 1 Jul 2020 15:35:31 -0000       1.81
+++ thegnuproject.es.po 3 Jul 2020 09:33:35 -0000       1.82
@@ -1,5 +1,5 @@
 # Spanish translation of http://www.gnu.org/gnu/thegnuproject.html
-# Copyright (C) 1998,1999, 2003, 2009-2018 Free Software Foundation, Inc.
+# Copyright (C) 1998,1999, 2003, 2009-2018, 2020 Free Software Foundation, Inc.
 # This file is distributed under the same license as the original article.
 # César Ballardini <cballard@santafe.com.ar>, 1998. (Argentina)
 # Ramsés Morales <ramses@computer.org>, 1998. (Panamá)
@@ -10,7 +10,7 @@
 # Luis Bustamante <http://people.fluidsignal.com/~luferbu>, 2003.
 # Hernán Giovagnoli <hag@gnu.org>, 2009.
 # Xavier Reina <xreina@fsfe.org>, 2010, 2011, 2012.
-# Javier Fdez. Retenaga <jfrtnaga@gnu.org>, 2015-2018.
+# Javier Fdez. Retenaga <jfrtnaga@gnu.org>, 2015-2018, 2020.
 # Dora Scilipoti <dora AT gnu DOT org>, 2013, 2014, 2018.
 #
 msgid ""
@@ -18,17 +18,16 @@
 "Project-Id-Version: thegnuproject.es.html\n"
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2020-07-01 15:25+0000\n"
-"PO-Revision-Date: 2018-04-01 13:28+0200\n"
+"PO-Revision-Date: 2020-07-03 10:51+0200\n"
 "Last-Translator: Javier Fdez. Retenaga <jfrtnaga@gnu.org>\n"
 "Language-Team: Spanish <www-es-general@gnu.org>\n"
 "Language: es\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"X-Outdated-Since: 2020-07-01 15:25+0000\n"
 "Plural-Forms: nplurals=2; plural=(n!=1);\n"
 "X-Poedit-SourceCharset: utf-8\n"
-"X-Generator: Poedit 1.8.11\n"
+"X-Generator: Poedit 2.2.1\n"
 
 # type: Content of: <title>
 #. type: Content of: <title>
@@ -85,20 +84,6 @@
 
 # type: Content of: <p>
 #. type: Content of: <p>
-# | When I started working at the [-<acronym-] {+<abbr+} title=\"Massachusetts
-# | Institute of [-Technology\">MIT</acronym>-] {+Technology\">MIT</abbr>+}
-# | Artificial Intelligence Lab in 1971, I became part of a software-sharing
-# | community that had existed for many years.  Sharing of software was not
-# | limited to our particular community; it is as old as computers, just as
-# | sharing of recipes is as old as cooking.  But we did it more than most.
-#, fuzzy
-#| msgid ""
-#| "When I started working at the <acronym title=\"Massachusetts Institute of "
-#| "Technology\">MIT</acronym> Artificial Intelligence Lab in 1971, I became "
-#| "part of a software-sharing community that had existed for many years.  "
-#| "Sharing of software was not limited to our particular community; it is as "
-#| "old as computers, just as sharing of recipes is as old as cooking.  But "
-#| "we did it more than most."
 msgid ""
 "When I started working at the <abbr title=\"Massachusetts Institute of "
 "Technology\">MIT</abbr> Artificial Intelligence Lab in 1971, I became part "
@@ -118,23 +103,6 @@
 
 # type: Content of: <p>
 #. type: Content of: <p>
-# | The AI Lab used a timesharing operating system called [-<acronym-]
-# | {+<abbr+} title=\"Incompatible Timesharing [-System\">ITS</acronym>-]
-# | {+System\">ITS</abbr>+} (the Incompatible Timesharing System) that the
-# | lab's staff hackers (1) had designed and written in assembler language for
-# | the Digital [-<acronym-] {+<abbr+} title=\"Programmed Data
-# | [-Processor\">PDP</acronym>-10,-] {+Processor\">PDP</abbr>-10,+} one of
-# | the large computers of the era.  As a member of this community, an AI Lab
-# | staff system hacker, my job was to improve this system.
-#, fuzzy
-#| msgid ""
-#| "The AI Lab used a timesharing operating system called <acronym title="
-#| "\"Incompatible Timesharing System\">ITS</acronym> (the Incompatible "
-#| "Timesharing System) that the lab's staff hackers (1) had designed and "
-#| "written in assembler language for the Digital <acronym title=\"Programmed "
-#| "Data Processor\">PDP</acronym>-10, one of the large computers of the "
-#| "era.  As a member of this community, an AI Lab staff system hacker, my "
-#| "job was to improve this system."
 msgid ""
 "The AI Lab used a timesharing operating system called <abbr title="
 "\"Incompatible Timesharing System\">ITS</abbr> (the Incompatible Timesharing "
@@ -781,27 +749,6 @@
 
 # type: Content of: <p>
 #. type: Content of: <p>
-# | I then realized that the Pastel compiler functioned by parsing the entire
-# | input file into a syntax tree, converting the whole syntax tree into a
-# | chain of &ldquo;instructions&rdquo;, and then generating the whole output
-# | file, without ever freeing any storage.  At this point, I concluded I
-# | would have to write a new compiler from scratch.  That new compiler is now
-# | known as [-<acronym-] {+<abbr+} title=\"GNU Compiler
-# | [-Collection\">GCC</acronym>;-] {+Collection\">GCC</abbr>;+} none of the
-# | Pastel compiler is used in it, but I managed to adapt and use the C front
-# | end that I had written.  But that was some years later; first, I worked on
-# | GNU Emacs.
-#, fuzzy
-#| msgid ""
-#| "I then realized that the Pastel compiler functioned by parsing the entire "
-#| "input file into a syntax tree, converting the whole syntax tree into a "
-#| "chain of &ldquo;instructions&rdquo;, and then generating the whole output "
-#| "file, without ever freeing any storage.  At this point, I concluded I "
-#| "would have to write a new compiler from scratch.  That new compiler is "
-#| "now known as <acronym title=\"GNU Compiler Collection\">GCC</acronym>; "
-#| "none of the Pastel compiler is used in it, but I managed to adapt and use "
-#| "the C front end that I had written.  But that was some years later; "
-#| "first, I worked on GNU Emacs."
 msgid ""
 "I then realized that the Pastel compiler functioned by parsing the entire "
 "input file into a syntax tree, converting the whole syntax tree into a chain "
@@ -864,27 +811,6 @@
 
 # type: Content of: <p>
 #. type: Content of: <p>
-# | I could have said, &ldquo;Find a friend who is on the net and who will
-# | make a copy for you.&rdquo; Or I could have done what I did with the
-# | original PDP-10 Emacs: tell them, &ldquo;Mail me a tape and a [-<acronym-]
-# | {+<abbr+} title=\"Self-addressed Stamped [-Envelope\">SASE</acronym>,-]
-# | {+Envelope\">SASE</abbr>,+} and I will mail it back with Emacs on
-# | it.&rdquo; But I had no job, and I was looking for ways to make money from
-# | free software.  So I announced that I would mail a tape to whoever wanted
-# | one, for a fee of $150.  In this way, I started a free software
-# | distribution business, the precursor of the companies that today
-# | distribute entire GNU/Linux system distributions.
-#, fuzzy
-#| msgid ""
-#| "I could have said, &ldquo;Find a friend who is on the net and who will "
-#| "make a copy for you.&rdquo; Or I could have done what I did with the "
-#| "original PDP-10 Emacs: tell them, &ldquo;Mail me a tape and a <acronym "
-#| "title=\"Self-addressed Stamped Envelope\">SASE</acronym>, and I will mail "
-#| "it back with Emacs on it.&rdquo; But I had no job, and I was looking for "
-#| "ways to make money from free software.  So I announced that I would mail "
-#| "a tape to whoever wanted one, for a fee of $150.  In this way, I started "
-#| "a free software distribution business, the precursor of the companies "
-#| "that today distribute entire GNU/Linux system distributions."
 msgid ""
 "I could have said, &ldquo;Find a friend who is on the net and who will make "
 "a copy for you.&rdquo; Or I could have done what I did with the original "
@@ -1134,25 +1060,6 @@
 
 # type: Content of: <p>
 #. type: Content of: <p>
-# | As interest in using Emacs was growing, other people became involved in
-# | the GNU project, and we decided that it was time to seek funding once
-# | again.  So in 1985 we created the <a href=\"http://www.fsf.org/\";>Free
-# | Software Foundation</a> (FSF), a tax-exempt charity for free software
-# | development.  The [-<acronym-] {+<abbr+} title=\"Free Software
-# | [-Foundation\">FSF</acronym>-] {+Foundation\">FSF</abbr>+} also took over
-# | the Emacs tape distribution business; later it extended this by adding
-# | other free software (both GNU and non-GNU) to the tape, and by selling
-# | free manuals as well.
-#, fuzzy
-#| msgid ""
-#| "As interest in using Emacs was growing, other people became involved in "
-#| "the GNU project, and we decided that it was time to seek funding once "
-#| "again.  So in 1985 we created the <a href=\"http://www.fsf.org/\";>Free "
-#| "Software Foundation</a> (FSF), a tax-exempt charity for free software "
-#| "development.  The <acronym title=\"Free Software Foundation\">FSF</"
-#| "acronym> also took over the Emacs tape distribution business; later it "
-#| "extended this by adding other free software (both GNU and non-GNU) to the "
-#| "tape, and by selling free manuals as well."
 msgid ""
 "As interest in using Emacs was growing, other people became involved in the "
 "GNU project, and we decided that it was time to seek funding once again.  So "
@@ -1165,13 +1072,12 @@
 msgstr ""
 "A medida que crecía el interés por el uso de Emacs, otras personas se "
 "involucraron en el proyecto GNU, y decidimos que había llegado el momento de 
"
-"volver a conseguir fondos. Con ese objetivo, en 1985 creamos la <a href="
-"\"http://www.fsf.org/\"; ><cite>Free Software Foundation</cite></a> (FSF), "
-"una organización sin ánimo de lucro exenta de impuestos que se dedica al "
-"desarrollo de software libre. La FSF también se hizo cargo de la "
-"distribución de Emacs, y más adelante comenzó a añadir en las cintas 
otros "
-"programas libres de GNU (además de otros que no eran de GNU) y a vender "
-"manuales libres."
+"volver a conseguir fondos. Con ese objetivo, en 1985 creamos la <abbr title="
+"\"Free Software Foundation\">FSF</abbr>, una organización sin ánimo de 
lucro "
+"exenta de impuestos que se dedica al desarrollo de software libre. La FSF "
+"también se hizo cargo de la distribución de Emacs, y más adelante comenzó 
a "
+"añadir en las cintas otros programas libres de GNU (además de otros que no "
+"eran de GNU) y a vender manuales libres."
 
 # type: Content of: <p>
 #. type: Content of: <p>
@@ -1197,24 +1103,6 @@
 
 # type: Content of: <p>
 #. type: Content of: <p>
-# | Free Software Foundation employees have written and maintained a number of
-# | GNU software packages.  Two notable ones are the C library and the shell. 
-# | The GNU C library is what every program running on a GNU/Linux system uses
-# | to communicate with Linux.  It was developed by a member of the Free
-# | Software Foundation staff, Roland McGrath.  The shell used on most
-# | GNU/Linux systems is [-<acronym-] {+<abbr+} title=\"Bourne Again
-# | [-Shell\">BASH</acronym>,-] {+Shell\">BASH</abbr>,+} the Bourne Again
-# | Shell(1), which was developed by FSF employee Brian Fox.
-#, fuzzy
-#| msgid ""
-#| "Free Software Foundation employees have written and maintained a number "
-#| "of GNU software packages.  Two notable ones are the C library and the "
-#| "shell.  The GNU C library is what every program running on a GNU/Linux "
-#| "system uses to communicate with Linux.  It was developed by a member of "
-#| "the Free Software Foundation staff, Roland McGrath.  The shell used on "
-#| "most GNU/Linux systems is <acronym title=\"Bourne Again Shell\">BASH</"
-#| "acronym>, the Bourne Again Shell(1), which was developed by FSF employee "
-#| "Brian Fox."
 msgid ""
 "Free Software Foundation employees have written and maintained a number of "
 "GNU software packages.  Two notable ones are the C library and the shell.  "
@@ -1680,28 +1568,6 @@
 
 # type: Content of: <p>
 #. type: Content of: <p>
-# | Some GNU programs were developed to cope with specific threats to our
-# | freedom.  Thus, we developed gzip to replace the Compress program, which
-# | had been lost to the community because of the [-<acronym
-# | title=\"Lempel-Ziv-Welch\">LZW</acronym>-] {+<abbr
-# | title=\"Lempel-Ziv-Welch\">LZW</abbr>+} patents.  We found people to
-# | develop LessTif, and more recently started [-<acronym-] {+<abbr+}
-# | title=\"GNU Network Object Model [-Environment\">GNOME</acronym>-]
-# | {+Environment\">GNOME</abbr>+} and Harmony, to address the problems caused
-# | by certain proprietary libraries (see below).  We are developing the GNU
-# | Privacy Guard to replace popular nonfree encryption software, because
-# | users should not have to choose between privacy and freedom.
-#, fuzzy
-#| msgid ""
-#| "Some GNU programs were developed to cope with specific threats to our "
-#| "freedom.  Thus, we developed gzip to replace the Compress program, which "
-#| "had been lost to the community because of the <acronym title=\"Lempel-Ziv-"
-#| "Welch\">LZW</acronym> patents.  We found people to develop LessTif, and "
-#| "more recently started <acronym title=\"GNU Network Object Model "
-#| "Environment\">GNOME</acronym> and Harmony, to address the problems caused "
-#| "by certain proprietary libraries (see below).  We are developing the GNU "
-#| "Privacy Guard to replace popular nonfree encryption software, because "
-#| "users should not have to choose between privacy and freedom."
 msgid ""
 "Some GNU programs were developed to cope with specific threats to our "
 "freedom.  Thus, we developed gzip to replace the Compress program, which had "
@@ -2086,18 +1952,6 @@
 
 # type: Content of: <p>
 #. type: Content of: <p>
-# | Between 1996 and 1998, another nonfree [-<acronym-] {+<abbr+}
-# | title=\"Graphical User [-Interface\">GUI</acronym>-]
-# | {+Interface\">GUI</abbr>+} toolkit library, called Qt, was used in a
-# | substantial collection of free software, the desktop [-<acronym-]
-# | {+<abbr+} title=\"K Desktop [-Environment\">KDE</acronym>.-]
-# | {+Environment\">KDE</abbr>.+}
-#, fuzzy
-#| msgid ""
-#| "Between 1996 and 1998, another nonfree <acronym title=\"Graphical User "
-#| "Interface\">GUI</acronym> toolkit library, called Qt, was used in a "
-#| "substantial collection of free software, the desktop <acronym title=\"K "
-#| "Desktop Environment\">KDE</acronym>."
 msgid ""
 "Between 1996 and 1998, another nonfree <abbr title=\"Graphical User Interface"
 "\">GUI</abbr> toolkit library, called Qt, was used in a substantial "
@@ -2211,28 +2065,6 @@
 
 # type: Content of: <p>
 #. type: Content of: <p>
-# | The worst threat we face comes from software patents, which can put
-# | algorithms and features off limits to free software for up to twenty
-# | years.  The LZW compression algorithm patents were applied for in 1983,
-# | and we still cannot release free software to produce proper compressed
-# | [-<acronym-] {+<abbr+} title=\"Graphics Interchange
-# | [-Format\">GIF</acronym>s.-] {+Format\">GIF</abbr>s.+}  [As of 2009 they
-# | have expired.] In 1998, a free program to produce [-<acronym-] {+<abbr+}
-# | title=\"MPEG-1 Audio Layer [-3\">MP3</acronym>-] {+3\">MP3</abbr>+}
-# | compressed audio was removed from distribution under threat of a patent
-# | suit.  [As of 2017, these patents have expired.  Look how long we had to
-# | wait.]
-#, fuzzy
-#| msgid ""
-#| "The worst threat we face comes from software patents, which can put "
-#| "algorithms and features off limits to free software for up to twenty "
-#| "years.  The LZW compression algorithm patents were applied for in 1983, "
-#| "and we still cannot release free software to produce proper compressed "
-#| "<acronym title=\"Graphics Interchange Format\">GIF</acronym>s.  [As of "
-#| "2009 they have expired.] In 1998, a free program to produce <acronym "
-#| "title=\"MPEG-1 Audio Layer 3\">MP3</acronym> compressed audio was removed "
-#| "from distribution under threat of a patent suit.  [As of 2017, these "
-#| "patents have expired.  Look how long we had to wait.]"
 msgid ""
 "The worst threat we face comes from software patents, which can put "
 "algorithms and features off limits to free software for up to twenty years.  "
@@ -2674,18 +2506,12 @@
 "coordinación y el envío de traducciones de las páginas de este sitio web."
 
 #. type: Content of: <div><p>
-# | Copyright &copy; 1998, 2001, 2002, 2005, 2006, 2007, 2008, 2010, 2014,
-# | 2015, 2017, [-2018-] {+2018, 2020+} Richard Stallman
-#, fuzzy
-#| msgid ""
-#| "Copyright &copy; 1998, 2001, 2002, 2005, 2006, 2007, 2008, 2010, 2014, "
-#| "2015, 2017, 2018 Richard Stallman"
 msgid ""
 "Copyright &copy; 1998, 2001, 2002, 2005, 2006, 2007, 2008, 2010, 2014, 2015, "
 "2017, 2018, 2020 Richard Stallman"
 msgstr ""
 "Copyright &copy; 1998, 2001, 2002, 2005, 2006, 2007, 2008, 2010, 2014, 2015, "
-"2017, 2018 Richard Stallman"
+"2017, 2018, 2020 Richard Stallman"
 
 #. type: Content of: <div><p>
 msgid ""