[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www gnu/po/rms-lisp.es.po gnu/po/rms-lisp.fr.po...
|
From: |
GNUN |
|
Subject: |
www gnu/po/rms-lisp.es.po gnu/po/rms-lisp.fr.po... |
|
Date: |
Wed, 1 Jul 2020 10:31:22 -0400 (EDT) |
CVSROOT: /web/www
Module name: www
Changes by: GNUN <gnun> 20/07/01 10:31:22
Modified files:
gnu/po : rms-lisp.es.po rms-lisp.fr.po rms-lisp.ja.po
rms-lisp.pot rms-lisp.pt-br.po rms-lisp.ru.po
rms-lisp.sq.po rms-lisp.uk.po rms-lisp.zh-cn.po
philosophy/po : 15-years-of-free-software.ar.po
15-years-of-free-software.de.po
15-years-of-free-software.es.po
15-years-of-free-software.fr.po
15-years-of-free-software.hr.po
15-years-of-free-software.ja.po
15-years-of-free-software.ko.po
15-years-of-free-software.ml.po
15-years-of-free-software.nl.po
15-years-of-free-software.pl.po
15-years-of-free-software.pot
15-years-of-free-software.pt-br.po
15-years-of-free-software.ru.po
15-years-of-free-software.sq.po
15-years-of-free-software.tr.po
15-years-of-free-software.uk.po
15-years-of-free-software.zh-cn.po
Log message:
Automatic update by GNUnited Nations.
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/rms-lisp.es.po?cvsroot=www&r1=1.37&r2=1.38
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/rms-lisp.fr.po?cvsroot=www&r1=1.44&r2=1.45
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/rms-lisp.ja.po?cvsroot=www&r1=1.9&r2=1.10
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/rms-lisp.pot?cvsroot=www&r1=1.17&r2=1.18
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/rms-lisp.pt-br.po?cvsroot=www&r1=1.9&r2=1.10
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/rms-lisp.ru.po?cvsroot=www&r1=1.10&r2=1.11
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/rms-lisp.sq.po?cvsroot=www&r1=1.35&r2=1.36
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/rms-lisp.uk.po?cvsroot=www&r1=1.6&r2=1.7
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/rms-lisp.zh-cn.po?cvsroot=www&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/15-years-of-free-software.ar.po?cvsroot=www&r1=1.27&r2=1.28
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/15-years-of-free-software.de.po?cvsroot=www&r1=1.35&r2=1.36
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/15-years-of-free-software.es.po?cvsroot=www&r1=1.28&r2=1.29
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/15-years-of-free-software.fr.po?cvsroot=www&r1=1.39&r2=1.40
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/15-years-of-free-software.hr.po?cvsroot=www&r1=1.5&r2=1.6
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/15-years-of-free-software.ja.po?cvsroot=www&r1=1.10&r2=1.11
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/15-years-of-free-software.ko.po?cvsroot=www&r1=1.13&r2=1.14
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/15-years-of-free-software.ml.po?cvsroot=www&r1=1.25&r2=1.26
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/15-years-of-free-software.nl.po?cvsroot=www&r1=1.10&r2=1.11
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/15-years-of-free-software.pl.po?cvsroot=www&r1=1.21&r2=1.22
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/15-years-of-free-software.pot?cvsroot=www&r1=1.15&r2=1.16
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/15-years-of-free-software.pt-br.po?cvsroot=www&r1=1.2&r2=1.3
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/15-years-of-free-software.ru.po?cvsroot=www&r1=1.10&r2=1.11
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/15-years-of-free-software.sq.po?cvsroot=www&r1=1.40&r2=1.41
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/15-years-of-free-software.tr.po?cvsroot=www&r1=1.27&r2=1.28
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/15-years-of-free-software.uk.po?cvsroot=www&r1=1.2&r2=1.3
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/15-years-of-free-software.zh-cn.po?cvsroot=www&r1=1.1&r2=1.2
Patches:
Index: gnu/po/rms-lisp.es.po
===================================================================
RCS file: /web/www/www/gnu/po/rms-lisp.es.po,v
retrieving revision 1.37
retrieving revision 1.38
diff -u -b -r1.37 -r1.38
--- gnu/po/rms-lisp.es.po 3 May 2020 09:59:57 -0000 1.37
+++ gnu/po/rms-lisp.es.po 1 Jul 2020 14:31:21 -0000 1.38
@@ -10,7 +10,7 @@
msgid ""
msgstr ""
"Project-Id-Version: rms-list.html\n"
-"POT-Creation-Date: 2014-04-04 23:59+0000\n"
+"POT-Creation-Date: 2020-07-01 14:25+0000\n"
"PO-Revision-Date: 2020-05-03 11:25+0200\n"
"Last-Translator: Javier Fdez. Retenaga <jfrtnaga@gnu.org>\n"
"Language-Team: Spanish <www-es-general@gnu.org>\n"
@@ -18,6 +18,7 @@
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"X-Outdated-Since: 2020-07-01 14:25+0000\n"
"X-Generator: Poedit 2.2.1\n"
# type: Content of: <title>
@@ -156,19 +157,45 @@
# 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 — 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 ‘5l’, meaning ‘move
+# | five lines’, or ‘i’ 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 — 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 ‘5l’, meaning ‘move "
+#| "five lines’, or ‘i’ 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 — 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 ‘5l’, meaning ‘move five "
-"lines’, or ‘i’ 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."
+"non-interpreted language — was PDP-10 Assembler. The interpreter we "
+"wrote in that actually wasn't written for Emacs, it was written for <abbr "
+"title=\"Text Editor and 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 "
+"‘5l’, meaning ‘move five lines’, or ‘i’ "
+"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."
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 "
@@ -185,6 +212,30 @@
# 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 < >. 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 < >. 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, "
@@ -195,7 +246,7 @@
"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>."
+"got its unwind-protect facility from TECO."
msgstr ""
"Bien. La gente querÃa extender este lenguaje con elementos útiles para la "
"programación, asà que añadió algunos. Por ejemplo, uno de los primeros
fue "
@@ -213,15 +264,35 @@
# 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 — 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 — 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 — 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."
+"like 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."
msgstr ""
"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 "
@@ -282,6 +353,56 @@
# 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
+# | — it was a full-fledged Lisp system — 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 — 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 "
+#| "— it was a full-fledged Lisp system — 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 — 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. "
@@ -296,13 +417,12 @@
"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 "
+"machine language, making them into TECO primitives. For instance, there was "
+"a 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 TECO program). You could do the "
+"whole job by writing a 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."
@@ -357,19 +477,46 @@
# 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
+# | — 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 “you had to send back all of your improvements” 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 — 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 “you had to send back "
+#| "all of your improvements” 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 "
"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 — 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 “you had to send back all of your "
-"improvements” so we could all benefit. No one ever tried to enforce "
-"that, but as far as I know people did cooperate."
+"Emacs. I first released the original Emacs to people at MIT. Someone wanted "
+"to port it to run on Twenex — it originally only ran on the "
+"Incompatible Timesharing System we used at 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 “you had to send back all of your improvements” so we "
+"could all benefit. No one ever tried to enforce that, but as far as I know "
+"people did cooperate."
msgstr ""
"Ahora bien, este no fue el primer Emacs escrito en C y que se ejecutaba en "
"Unix. El primero lo escribió James Gosling, y era conocido como GosMacs. Con
"
@@ -470,16 +617,37 @@
# type: Content of: <p>
#. type: Content of: <p>
+# | This second Emacs program was ‘free software’ in the modern
+# | sense of the term — 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 —
+# | the experience I had, the life that I've lived at the [-<abbr>MIT</abbr>-]
+# | {+MIT+} AI lab — 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 ‘free software’ in the modern "
+#| "sense of the term — 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 — "
+#| "the experience I had, the life that I've lived at the <abbr>MIT</abbr> AI "
+#| "lab — 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 ‘free software’ in the modern "
"sense of the term — 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 — the experience I had, "
-"the life that I've lived at the <abbr>MIT</abbr> AI lab — to be "
-"working on human knowledge, and not be standing in the way of anybody's "
-"further using and further disseminating human knowledge."
+"be free to do the things we did in the old days at MIT>, working together on "
+"software and working with whomever wanted to work with us. That is the "
+"basis for the free software movement — the experience I had, the life "
+"that I've lived at the MIT AI lab — to be working on human knowledge, "
+"and not be standing in the way of anybody's further using and further "
+"disseminating human knowledge."
msgstr ""
"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 "
@@ -631,19 +799,46 @@
# type: Content of: <p>
#. type: Content of: <p>
+# | Thus, the abandonment of our lab was followed by “war” 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 “war” 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 “war” 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."
+"and eliminated people who worked part-time for MIT, so they had to leave "
+"entirely, which left only me. The AI lab was now helpless. And 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 MIT use their changes. But it "
+"didn't say in the contract that MIT was entitled to put them into the 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."
msgstr ""
"Por lo tanto, al abandono de nuestro laboratorio le siguió la «guerra» en
"
"nuestro laboratorio. El abandono tuvo lugar cuando Symbolics se llevó a "
@@ -663,12 +858,25 @@
# 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, “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.”
+#, fuzzy
+#| msgid ""
+#| "So Symbolics came up with a plan <a href=\"#foot-4\">(4)</a>. They said "
+#| "to the lab, “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.”"
msgid ""
"So Symbolics came up with a plan <a href=\"#foot-4\">(4)</a>. They said to "
"the lab, “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.”"
+"for you to use, but you can't put it into the 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.”"
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
"
@@ -678,15 +886,35 @@
# 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 <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."
+"use either the 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 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."
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 "
@@ -753,12 +981,25 @@
# type: Content of: <p>
#. type: Content of: <p>
-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."
+# | 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 "
+"out 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."
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 "
@@ -895,20 +1136,49 @@
# type: Content of: <p>
#. type: Content of: <p>
-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 “de-facto standard extension "
-"language” of the world. And I thought, “We've got to stop that "
-"from happening.” 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."
+# | 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
+# | “de-facto standard extension language” of the world. And I
+# | thought, “We've got to stop that from happening.” 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 “de-facto standard extension "
+#| "language” of the world. And I thought, “We've got to stop "
+#| "that from happening.” 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 "
+"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 TCL to make it the “de-facto "
+"standard extension language” of the world. And I thought, “We've "
+"got to stop that from happening.” 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 TCL was linked into applications. "
+"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 "
@@ -926,18 +1196,44 @@
# 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 "
"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."
+"language. If your primary language is TCL, you can't very easily implement "
+"Lisp by translating it into 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 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."
msgstr ""
"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: "
@@ -1256,18 +1552,24 @@
# type: Content of: <div><p>
#. type: Content of: <div><p>
-msgid "Copyright © 2003, 2007, 2013, 2014 Free Software Foundation, Inc."
+# | Copyright © 2003, 2007, 2013, [-2014-] {+2014, 2020+} Free Software
+# | Foundation, Inc.
+#, fuzzy
+#| msgid ""
+#| "Copyright © 2003, 2007, 2013, 2014 Free Software Foundation, Inc."
+msgid ""
+"Copyright © 2003, 2007, 2013, 2014, 2020 Free Software Foundation, Inc."
msgstr "Copyright © 2003, 2007, 2013, 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>."
+"creativecommons.org/licenses/by-nd/4.0/\">Creative Commons Attribution-"
+"NoDerivatives 4.0 International 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>."
+"creativecommons.org/licenses/by-nd/4.0/deed.es_ES\">Creative Commons "
+"Reconocimiento-SinObraDerivada 4.0 Internacional</a>."
# type: Content of: <div><div>
#. TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.
Index: gnu/po/rms-lisp.fr.po
===================================================================
RCS file: /web/www/www/gnu/po/rms-lisp.fr.po,v
retrieving revision 1.44
retrieving revision 1.45
diff -u -b -r1.44 -r1.45
--- gnu/po/rms-lisp.fr.po 12 Nov 2018 17:09:13 -0000 1.44
+++ gnu/po/rms-lisp.fr.po 1 Jul 2020 14:31:21 -0000 1.45
@@ -8,7 +8,7 @@
msgid ""
msgstr ""
"Project-Id-Version: rms-lisp.html\n"
-"POT-Creation-Date: 2014-04-04 23:59+0000\n"
+"POT-Creation-Date: 2020-07-01 14:25+0000\n"
"PO-Revision-Date: 2018-11-12 18:05+0100\n"
"Last-Translator: Thérèse Godefroy <godef.th AT free.fr>\n"
"Language-Team: French <trad-gnu@april.org>\n"
@@ -16,6 +16,7 @@
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"X-Outdated-Since: 2020-07-01 14:25+0000\n"
"Plural-Forms: \n"
"X-Generator: Gtranslator 2.91.5\n"
@@ -144,19 +145,45 @@
"vivre au labo d'IA qui a mené à Emacs et l'a fait devenir ce qu'il était."
#. type: Content of: <p>
+# | The original Emacs did not have Lisp in it. The lower level language, the
+# | non-interpreted language — 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 ‘5l’, meaning ‘move
+# | five lines’, or ‘i’ 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 — 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 ‘5l’, meaning ‘move "
+#| "five lines’, or ‘i’ 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 — 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 ‘5l’, meaning ‘move five "
-"lines’, or ‘i’ 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."
+"non-interpreted language — was PDP-10 Assembler. The interpreter we "
+"wrote in that actually wasn't written for Emacs, it was written for <abbr "
+"title=\"Text Editor and 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 "
+"‘5l’, meaning ‘move five lines’, or ‘i’ "
+"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."
msgstr ""
"L'Emacs original ne contenait pas de Lisp. Le langage de bas niveau, le "
"langage non interprété, était de l'assembleur PDP-10. L'interpréteur dans
"
@@ -172,6 +199,30 @@
"terminiez par Ãchap Ãchap, et elle était exécutée."
#. 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 < >. 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 < >. 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, "
@@ -182,7 +233,7 @@
"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>."
+"got its unwind-protect facility from TECO."
msgstr ""
"Certaines personnes voulaient étendre ce langage avec des méthodes de "
"programmation. Elles en ont donc ajouté quelques-unes. Par exemple, l'une "
@@ -199,15 +250,35 @@
"méthode <cite>unwind-protect</cite> de TECO."
#. type: Content of: <p>
+# | We started putting in rather sophisticated facilities, all with the
+# | ugliest syntax you could ever think of, and it worked — 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 — 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 — 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."
+"like 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."
msgstr ""
"Nous avons commencé à intégrer des méthodes plutôt sophistiquées,
toutes "
"avec la syntaxe la plus horrible que vous puissiez imaginer, et cela "
@@ -265,6 +336,56 @@
"devenus programmeurs."
#. 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
+# | — it was a full-fledged Lisp system — 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 — 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 "
+#| "— it was a full-fledged Lisp system — 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 — 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. "
@@ -279,13 +400,12 @@
"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 "
+"machine language, making them into TECO primitives. For instance, there was "
+"a 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 TECO program). You could do the "
+"whole job by writing a 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."
@@ -338,19 +458,46 @@
"la pile à l'écran, gérer les fenêtres de l'éditeur."
#. 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
+# | — 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 “you had to send back all of your improvements” 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 — 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 “you had to send back "
+#| "all of your improvements” 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 "
"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 — 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 “you had to send back all of your "
-"improvements” so we could all benefit. No one ever tried to enforce "
-"that, but as far as I know people did cooperate."
+"Emacs. I first released the original Emacs to people at MIT. Someone wanted "
+"to port it to run on Twenex — it originally only ran on the "
+"Incompatible Timesharing System we used at 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 “you had to send back all of your improvements” so we "
+"could all benefit. No one ever tried to enforce that, but as far as I know "
+"people did cooperate."
msgstr ""
"Cela dit, ce n'était pas le premier Emacs écrit en C et fonctionnant sous "
"Unix. Le premier a été écrit par James Gosling et s'appelait GosMac. Une "
@@ -446,16 +593,37 @@
"réaffichage. C'est quelque chose de très pratique."
#. type: Content of: <p>
+# | This second Emacs program was ‘free software’ in the modern
+# | sense of the term — 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 —
+# | the experience I had, the life that I've lived at the [-<abbr>MIT</abbr>-]
+# | {+MIT+} AI lab — 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 ‘free software’ in the modern "
+#| "sense of the term — 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 — "
+#| "the experience I had, the life that I've lived at the <abbr>MIT</abbr> AI "
+#| "lab — 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 ‘free software’ in the modern "
"sense of the term — 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 — the experience I had, "
-"the life that I've lived at the <abbr>MIT</abbr> AI lab — to be "
-"working on human knowledge, and not be standing in the way of anybody's "
-"further using and further disseminating human knowledge."
+"be free to do the things we did in the old days at MIT>, working together on "
+"software and working with whomever wanted to work with us. That is the "
+"basis for the free software movement — the experience I had, the life "
+"that I've lived at the MIT AI lab — to be working on human knowledge, "
+"and not be standing in the way of anybody's further using and further "
+"disseminating human knowledge."
msgstr ""
"Ce second programme Emacs était du « logiciel libre » dans le sens
moderne "
"du terme ; il faisait partie d'une campagne politique explicite pour
libérer "
@@ -604,19 +772,46 @@
"chercher des moyens de la détruire."
#. type: Content of: <p>
+# | Thus, the abandonment of our lab was followed by “war” 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 “war” 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 “war” 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."
+"and eliminated people who worked part-time for MIT, so they had to leave "
+"entirely, which left only me. The AI lab was now helpless. And 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 MIT use their changes. But it "
+"didn't say in the contract that MIT was entitled to put them into the 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."
msgstr ""
"Il y a donc eu l'abandon de notre labo, suivi par une « guerre » dans
notre "
"labo. L'abandon s'est fait quand Symbolics a débauché tous les hackers, à "
@@ -635,12 +830,25 @@
"fut le cas."
#. type: Content of: <p>
+# | So Symbolics came up with a plan <a href=\"#foot-4\">(4)</a>. They said
+# | to the lab, “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.”
+#, fuzzy
+#| msgid ""
+#| "So Symbolics came up with a plan <a href=\"#foot-4\">(4)</a>. They said "
+#| "to the lab, “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.”"
msgid ""
"So Symbolics came up with a plan <a href=\"#foot-4\">(4)</a>. They said to "
"the lab, “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.”"
+"for you to use, but you can't put it into the 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.”"
msgstr ""
"Les gens de Symbolics ont trouvé une combine <a id=\"foot-4-rev\" href="
"\"#foot-4\">(4)</a>. Ils ont dit au labo : « Nous continuerons à mettre Ã
"
@@ -650,15 +858,35 @@
"faire fonctionner, mais c'est tout ce que vous pourrez faire. »"
#. 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 <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."
+"use either the 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 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."
msgstr ""
"En pratique, cela voulait dire qu'ils nous obligeaient à choisir un camp : "
"utiliser la version du MIT, ou la version de Symbolics. Quel que soit notre "
@@ -721,12 +949,25 @@
"celle que leurs actions, ainsi que d'autres, avaient rayée de la carte."
#. type: Content of: <p>
-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."
+# | 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 "
+"out 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."
msgstr ""
"La communauté Lisp des années 70 ne se limitait pas au labo d'IA du MIT et
"
"les hackers n'étaient pas tous au MIT. La guerre lancée par Symbolics est
ce "
@@ -856,20 +1097,49 @@
"facilement extensible, comme l'éditeur. La question était lequel choisir."
#. type: Content of: <p>
-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 “de-facto standard extension "
-"language” of the world. And I thought, “We've got to stop that "
-"from happening.” 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."
+# | 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
+# | “de-facto standard extension language” of the world. And I
+# | thought, “We've got to stop that from happening.” 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 “de-facto standard extension "
+#| "language” of the world. And I thought, “We've got to stop "
+#| "that from happening.” 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 "
+"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 TCL to make it the “de-facto "
+"standard extension language” of the world. And I thought, “We've "
+"got to stop that from happening.” 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 TCL was linked into applications. "
+"We would then recommend that as the preferred extensibility package for all "
+"GNU programs."
msgstr ""
"à ce moment-là , <abbr title=\"Tool Command Language\">TCL</abbr> était "
"largement mis en avant pour ce genre d'applications. J'avais une très "
@@ -886,18 +1156,44 @@
"programmes GNU."
#. 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 "
"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."
+"language. If your primary language is TCL, you can't very easily implement "
+"Lisp by translating it into 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 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."
msgstr ""
"Il y a un avantage intéressant à utiliser comme langage d'extension
primaire "
"un langage aussi puissant qu'une version de Lisp. On peut implémenter "
@@ -1213,19 +1509,25 @@
"README.translations.html\">guide de traduction</a>."
#. type: Content of: <div><p>
-msgid "Copyright © 2003, 2007, 2013, 2014 Free Software Foundation, Inc."
+# | Copyright © 2003, 2007, 2013, [-2014-] {+2014, 2020+} Free Software
+# | Foundation, Inc.
+#, fuzzy
+#| msgid ""
+#| "Copyright © 2003, 2007, 2013, 2014 Free Software Foundation, Inc."
+msgid ""
+"Copyright © 2003, 2007, 2013, 2014, 2020 Free Software Foundation, Inc."
msgstr "Copyright © 2003, 2007, 2013, 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>."
+"creativecommons.org/licenses/by-nd/4.0/\">Creative Commons Attribution-"
+"NoDerivatives 4.0 International License</a>."
msgstr ""
"Cette page peut être utilisée suivant les conditions de la licence <a rel="
-"\"license\" href=\"http://creativecommons.org/licenses/by-nd/3.0/us/deed.fr";
-"\">Creative Commons attribution de paternité, pas de modification, 3.0Â
Ãtats-"
-"Unis (CCÂ BY-ND 3.0Â US)</a>."
+"\"license\" href=\"http://creativecommons.org/licenses/by-nd/4.0/deed.fr";
+"\">Creative Commons attribution, pas de modification, 4.0Â internationale "
+"(CCÂ BY-ND 4.0)</a>."
#. TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.
#. type: Content of: <div><div>
Index: gnu/po/rms-lisp.ja.po
===================================================================
RCS file: /web/www/www/gnu/po/rms-lisp.ja.po,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- gnu/po/rms-lisp.ja.po 3 Feb 2016 09:13:01 -0000 1.9
+++ gnu/po/rms-lisp.ja.po 1 Jul 2020 14:31:21 -0000 1.10
@@ -6,7 +6,7 @@
msgid ""
msgstr ""
"Project-Id-Version: rms-lisp.html\n"
-"POT-Creation-Date: 2014-04-04 23:59+0000\n"
+"POT-Creation-Date: 2020-07-01 14:25+0000\n"
"PO-Revision-Date: 2014-04-28 15:37+0900\n"
"Last-Translator: NIIBE Yutaka <gniibe@fsij.org>\n"
"Language-Team: Japanese <web-translators-ja@gnu.org>\n"
@@ -14,6 +14,7 @@
"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"
#. type: Content of: <title>
msgid ""
@@ -130,19 +131,32 @@
"ãã§ããããã«ããã®ã¯ãããããã¡ãæ®ãããAIã©ãã®æ¹æ³ã®æ§è³ªã
ã¨æãã¾ãã"
#. type: Content of: <p>
+#, fuzzy
+#| msgid ""
+#| "The original Emacs did not have Lisp in it. The lower level language, the "
+#| "non-interpreted language — 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 ‘5l’, meaning ‘move "
+#| "five lines’, or ‘i’ 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 — 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 ‘5l’, meaning ‘move five "
-"lines’, or ‘i’ 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."
+"non-interpreted language — was PDP-10 Assembler. The interpreter we "
+"wrote in that actually wasn't written for Emacs, it was written for <abbr "
+"title=\"Text Editor and 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 "
+"‘5l’, meaning ‘move five lines’, or ‘i’ "
+"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."
msgstr ""
"ãªãªã¸ãã«ã®Emacsã«ã¯Lispã¯ããã¾ããã§ãããä½ã¬ãã«ã®è¨èªãã¤ã³ã¿ããªã¿è¨èª"
"ã§ã¯ãªããã®ã¯ã<abbr>PDP</abbr>-10ã®ã¢ã»ã³ãã©ã§ãããããããã¡ããããã§"
@@ -157,6 +171,19 @@
"ã¨ãå®è¡ãããã®ã§ãã"
#. type: Content of: <p>
+#, 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 < >. 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, "
@@ -167,7 +194,7 @@
"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>."
+"got its unwind-protect facility from TECO."
msgstr ""
"ã¾ãã人ã
ããã®è¨èªã«ããã°ã©ãã³ã°ã®æ©è½ãæ¡å¼µãããããããã¤ã足ãã¾ã"
"ãããã¨ãã°ãæåã®ãã®ã¯ãã«ã¼ãæ§é ã§ã< >
ã§ããããããããããã®"
@@ -181,15 +208,26 @@
"æ¡ã£ãã¨æãã¾ãã"
#. type: Content of: <p>
+#, fuzzy
+#| msgid ""
+#| "We started putting in rather sophisticated facilities, all with the "
+#| "ugliest syntax you could ever think of, and it worked — 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 — 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."
+"like 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."
msgstr ""
"ããããã¡ã¯ãæ´ç·´ãããæ©è½ãè©°ãè¾¼ã¿å§ãã¾ããããã¹ã¦èãããææªã®ææ³ã§"
"ããã¾ããããåãã¾ããã人ã
ã¯ãããã§ã©ãã«ã大ããªããã°ã©ã ãæ¸ãäºãã§"
@@ -243,6 +281,32 @@
"ã¾ã§è³ã£ãã®ã§ãã"
#. type: Content of: <p>
+#, 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 "
+#| "— it was a full-fledged Lisp system — 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 — 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. "
@@ -257,13 +321,12 @@
"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 "
+"machine language, making them into TECO primitives. For instance, there was "
+"a 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 TECO program). You could do the "
+"whole job by writing a 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."
@@ -310,19 +373,33 @@
"ã管çããããªã©ã®æ©æ§ã§ãã"
#. type: Content of: <p>
+#, 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 — 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 “you had to send back "
+#| "all of your improvements” 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 "
"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 — 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 “you had to send back all of your "
-"improvements” so we could all benefit. No one ever tried to enforce "
-"that, but as far as I know people did cooperate."
+"Emacs. I first released the original Emacs to people at MIT. Someone wanted "
+"to port it to run on Twenex — it originally only ran on the "
+"Incompatible Timesharing System we used at 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 “you had to send back all of your improvements” so we "
+"could all benefit. No one ever tried to enforce that, but as far as I know "
+"people did cooperate."
msgstr ""
"ãã®æãããã¯ãCã§æ¸ããã¦Unixã§åãæåã®Emacsã§ã¯ããã¾ããã§ãããæåã®"
"ãã®ã¯ã¸ã§ã¼ã
ã¹ã»ã´ã¹ãªã³ã°ã«ãã£ã¦æ¸ãããGosMacsã¨å¼ã°ãã¾ãããããããªäº"
@@ -407,16 +484,27 @@
"ããåæç»ã®æä¸ã«Lispã®ã³ã¼ããå®è¡ã§ãã¾ããããã¯ãã¨ã¦ã便å©ãªãã¨ã§ãã"
#. type: Content of: <p>
+#, fuzzy
+#| msgid ""
+#| "This second Emacs program was ‘free software’ in the modern "
+#| "sense of the term — 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 — "
+#| "the experience I had, the life that I've lived at the <abbr>MIT</abbr> AI "
+#| "lab — 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 ‘free software’ in the modern "
"sense of the term — 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 — the experience I had, "
-"the life that I've lived at the <abbr>MIT</abbr> AI lab — to be "
-"working on human knowledge, and not be standing in the way of anybody's "
-"further using and further disseminating human knowledge."
+"be free to do the things we did in the old days at MIT>, working together on "
+"software and working with whomever wanted to work with us. That is the "
+"basis for the free software movement — the experience I had, the life "
+"that I've lived at the MIT AI lab — to be working on human knowledge, "
+"and not be standing in the way of anybody's further using and further "
+"disseminating human knowledge."
msgstr ""
"äºçªç®ã®Emacsããã°ã©ã
ã¯è¿ä»£çãªç¨èªã¨ãã¦ãèªç±ã½ããã¦ã§ã¢ãã§ããããã"
"ã¯ãã½ããã¦ã§ã¢ãèªç±ã«ããã¯ã£ããã¨ããæ¿æ²»ãã£ã³ãã¼ã³ã®ä¸é¨ã§ããããã¤"
@@ -553,19 +641,33 @@
"ãæ¢ãåºãå§ãã¾ããã"
#. type: Content of: <p>
+#, fuzzy
+#| msgid ""
+#| "Thus, the abandonment of our lab was followed by “war” 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 “war” 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."
+"and eliminated people who worked part-time for MIT, so they had to leave "
+"entirely, which left only me. The AI lab was now helpless. And 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 MIT use their changes. But it "
+"didn't say in the contract that MIT was entitled to put them into the 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."
msgstr ""
"ã§ããããããããã¡ã®ã©ãã®ç½®ãå»ãã«ç¶ãã¦ãããããã¡ã®ã©ãã®ãæ¦äºãã¨ãª"
"ãã¾ãããã·ã³ããªãã¯ã¹ãããããã¨LMIã§ãã¼ãã¿ã¤ã
ã§åãä½äººããé¤ãã¦ãã"
@@ -581,12 +683,19 @@
"ä¸æãããã¨ã¯æ³åãã¦ã¾ããã§ãããããããªã£ãã®ã§ãã"
#. type: Content of: <p>
+#, fuzzy
+#| msgid ""
+#| "So Symbolics came up with a plan <a href=\"#foot-4\">(4)</a>. They said "
+#| "to the lab, “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.”"
msgid ""
"So Symbolics came up with a plan <a href=\"#foot-4\">(4)</a>. They said to "
"the lab, “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.”"
+"for you to use, but you can't put it into the 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.”"
msgstr ""
"ãããã¦ãã·ã³ããªãã¯ã¹ã¯ãã©ã³ãåºãã¾ãã<a
href=\"#foot-4\">(4)</a>ããã"
"ãã¯ã©ãã«è¨ãã¾ããããã·ã¹ãã
ã¸ã®ããããã¡ã®å¤æ´ã使ç¨å¯è½ã¨ããããã«ç¶"
@@ -595,15 +704,26 @@
"ãããã¨ãã§ãã¾ããããããããããã¡ãã§ãããã¨ã®ãã¹ã¦ã§ããã"
#. type: Content of: <p>
+#, 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 <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."
+"use either the 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 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."
msgstr ""
"ããã¯ãå®å¹çã«ãã©ã¡ããã®å´ãé¸æãããã¨ãè¦æ±ãããã®ã§ããã<abbr>MIT</"
"abbr>çã®ã·ã¹ãã
ããã·ã³ããªãã¯ã¹ã®çããããã©ã¡ããã®ã·ã¹ãã
ã«æ±ºããã¨ã"
@@ -664,12 +784,19 @@
"ãã£ã¯ãããããã»ãã®äººã
ã®è¡åãä¸æãã¦ãã¾ã£ããã®ãç½®ãæããã®ã§ãã"
#. type: Content of: <p>
-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."
+#, 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 "
+"out 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."
msgstr ""
"70年代ã®Lispã®ã³ãã¥ããã£ã¯<abbr>MIT</abbr>AIã©ãã«éã£ããã®ã§ã¯ãªãããã"
"ã«ã¼ã¯ãã¹ã¦<abbr>MIT</abbr>ã¨ããããã§ã¯ããã¾ããã§ãããã·ã³ããªãã¯ã¹ã"
@@ -792,20 +919,34 @@
"ãã¾ãããåé¡ã¯ãã©ã®ãããªããã°ã©ãã³ã°è¨èªã§ããã¹ãããã§ãã"
#. type: Content of: <p>
-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 “de-facto standard extension "
-"language” of the world. And I thought, “We've got to stop that "
-"from happening.” 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."
+#, 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 “de-facto standard extension "
+#| "language” of the world. And I thought, “We've got to stop "
+#| "that from happening.” 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 "
+"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 TCL to make it the “de-facto "
+"standard extension language” of the world. And I thought, “We've "
+"got to stop that from happening.” 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 TCL was linked into applications. "
+"We would then recommend that as the preferred extensibility package for all "
+"GNU programs."
msgstr ""
"å½æã<acronym title=\"Tool Command
Language\">TCL</acronym>ããã®ç®çã«å¼·ã"
"æ¼ããã¦ãã¾ããããããã¯<acronym>TCL</acronym>ã«å¯¾ãã¦ã¨ã¦ãä½ãè©ä¾¡ããã"
@@ -821,18 +962,32 @@
"ãã°ã©ã
ã«å¯¾ãã¦ãããã好ãã¹ãæ¡å¼µããã±ã¼ã¸ã¨ãã¦æ¨å¥¨ããã®ã§ãã"
#. type: Content of: <p>
+#, 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 "
"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."
+"language. If your primary language is TCL, you can't very easily implement "
+"Lisp by translating it into 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 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."
msgstr ""
"åºæ¬ã®æ¡å¼µè¨èªã¨ãã¦Lispç³»ã®å¼·åãªè¨èªã使ããã¨ã§ãå¾ããã¨ãã§ããèå³æ·±ã"
"æ©æµãããã¾ããåºæ¬ã®è¨èªã¸ã¨ç¿»è¨³ãããã¨ã§ãã»ãã®è¨èªãå®è£
ãããã¨ãã§ã"
@@ -1109,17 +1264,21 @@
"README.translations.html\">翻訳 README</a>ãã覧ãã ããã"
#. type: Content of: <div><p>
-msgid "Copyright © 2003, 2007, 2013, 2014 Free Software Foundation, Inc."
+#, fuzzy
+#| msgid ""
+#| "Copyright © 2003, 2007, 2013, 2014 Free Software Foundation, Inc."
+msgid ""
+"Copyright © 2003, 2007, 2013, 2014, 2020 Free Software Foundation, Inc."
msgstr "Copyright © 2003, 2007, 2013, 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>."
+"creativecommons.org/licenses/by-nd/4.0/\">Creative Commons Attribution-"
+"NoDerivatives 4.0 International License</a>."
msgstr ""
"ãã®ãã¼ã¸ã¯<a rel=\"license\"
href=\"http://creativecommons.org/licenses/by-";
-"nd/3.0/us/deed.ja\">Creative Commons Attribution-NoDerivs 3.0 United States "
+"nd/4.0/deed.ja\">Creative Commons Attribution-NoDerivs 4.0 International "
"License</a>ã®æ¡ä»¶ã§è¨±è«¾ããã¾ãã"
#. TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.
Index: gnu/po/rms-lisp.pot
===================================================================
RCS file: /web/www/www/gnu/po/rms-lisp.pot,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -b -r1.17 -r1.18
--- gnu/po/rms-lisp.pot 5 Apr 2014 00:39:40 -0000 1.17
+++ gnu/po/rms-lisp.pot 1 Jul 2020 14:31:21 -0000 1.18
@@ -1,4 +1,4 @@
-# LANGUAGE translation of http://www.gnu.org/gnu/rms-lisp.html
+# LANGUAGE translation of https://www.gnu.org/gnu/rms-lisp.html
# Copyright (C) YEAR Free Software Foundation, Inc.
# This file is distributed under the same license as the original article.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
@@ -7,13 +7,14 @@
msgid ""
msgstr ""
"Project-Id-Version: rms-lisp.html\n"
-"POT-Creation-Date: 2014-04-04 23:59+0000\n"
+"POT-Creation-Date: 2020-07-01 14:25+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=CHARSET\n"
-"Content-Transfer-Encoding: ENCODING"
+"Content-Transfer-Encoding: 8bit\n"
#. type: Content of: <title>
msgid ""
@@ -94,17 +95,16 @@
#. type: Content of: <p>
msgid ""
"The original Emacs did not have Lisp in it. The lower level language, the "
-"non-interpreted language — 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 ‘5l’, meaning ‘move "
-"five lines’, or ‘i’ 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."
+"non-interpreted language — was PDP-10 Assembler. The interpreter we "
+"wrote in that actually wasn't written for Emacs, it was written for <abbr "
+"title=\"Text Editor and 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 "
+"‘5l’, meaning ‘move five lines’, or ‘i’ "
+"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."
msgstr ""
#. type: Content of: <p>
@@ -118,8 +118,7 @@
"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>."
+"facilities; I think that Lisp got its unwind-protect facility from TECO."
msgstr ""
#. type: Content of: <p>
@@ -127,11 +126,11 @@
"We started putting in rather sophisticated facilities, all with the ugliest "
"syntax you could ever think of, and it worked — 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."
+"like 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."
msgstr ""
#. type: Content of: <p>
@@ -175,17 +174,15 @@
"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."
+"which we re-implemented in machine language, making them into TECO "
+"primitives. For instance, there was a 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 TECO program). You could do the whole job by writing a 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."
msgstr ""
#. type: Content of: <p>
@@ -206,14 +203,14 @@
"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 — 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 “you had to send "
-"back all of your improvements” so we could all benefit. No one ever "
-"tried to enforce that, but as far as I know people did cooperate."
+"Emacs. I first released the original Emacs to people at MIT. Someone wanted "
+"to port it to run on Twenex — it originally only ran on the "
+"Incompatible Timesharing System we used at 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 “you had to send back all of your improvements” so we "
+"could all benefit. No one ever tried to enforce that, but as far as I know "
+"people did cooperate."
msgstr ""
#. type: Content of: <p>
@@ -265,12 +262,12 @@
"This second Emacs program was ‘free software’ in the modern "
"sense of the term — 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 — the experience I had, "
-"the life that I've lived at the <abbr>MIT</abbr> AI lab — to be "
-"working on human knowledge, and not be standing in the way of anybody's "
-"further using and further disseminating human knowledge."
+"be free to do the things we did in the old days at MIT>, working together on "
+"software and working with whomever wanted to work with us. That is the "
+"basis for the free software movement — the experience I had, the life "
+"that I've lived at the MIT AI lab — to be working on human knowledge, "
+"and not be standing in the way of anybody's further using and further "
+"disseminating human knowledge."
msgstr ""
#. type: Content of: <p>
@@ -357,22 +354,21 @@
"Thus, the abandonment of our lab was followed by “war” 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."
+"and eliminated people who worked part-time for MIT, so they had to leave "
+"entirely, which left only me. The AI lab was now helpless. And 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 MIT use their changes. But it "
+"didn't say in the contract that MIT was entitled to put them into the 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."
msgstr ""
#. type: Content of: <p>
msgid ""
"So Symbolics came up with a plan <a href=\"#foot-4\">(4)</a>. They said to "
"the lab, “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 "
+"for you to use, but you can't put it into the 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.”"
msgstr ""
@@ -380,14 +376,13 @@
#. type: Content of: <p>
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."
+"use either the 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 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."
msgstr ""
#. type: Content of: <p>
@@ -422,11 +417,11 @@
#. type: Content of: <p>
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."
+"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 "
+"out 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."
msgstr ""
#. type: Content of: <p>
@@ -502,19 +497,18 @@
#. type: Content of: <p>
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 “de-facto standard extension "
-"language” of the world. And I thought, “We've got to stop that "
-"from happening.” So we started to make Scheme the standard "
-"extensibility language for GNU. Not Common Lisp, because it was too "
+"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 "
+"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 TCL to make it the “de-facto "
+"standard extension language” of the world. And I thought, “We've "
+"got to stop that from happening.” 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."
+"linked into applications in the same way TCL was linked into "
+"applications. We would then recommend that as the preferred extensibility "
+"package for all GNU programs."
msgstr ""
#. type: Content of: <p>
@@ -522,12 +516,11 @@
"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 "
+"language. If your primary language is TCL, you can't very easily implement "
+"Lisp by translating it into 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 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."
@@ -708,14 +701,14 @@
msgstr ""
#. type: Content of: <div><p>
-msgid "Copyright © 2003, 2007, 2013, 2014 Free Software Foundation, Inc."
+msgid "Copyright © 2003, 2007, 2013, 2014, 2020 Free Software Foundation,
Inc."
msgstr ""
#. type: Content of: <div><p>
msgid ""
"This page is licensed under a <a rel=\"license\" "
-"href=\"http://creativecommons.org/licenses/by-nd/3.0/us/\";>Creative Commons "
-"Attribution-NoDerivs 3.0 United States License</a>."
+"href=\"http://creativecommons.org/licenses/by-nd/4.0/\";>Creative Commons "
+"Attribution-NoDerivatives 4.0 International License</a>."
msgstr ""
#. TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.
Index: gnu/po/rms-lisp.pt-br.po
===================================================================
RCS file: /web/www/www/gnu/po/rms-lisp.pt-br.po,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- gnu/po/rms-lisp.pt-br.po 22 May 2020 22:05:12 -0000 1.9
+++ gnu/po/rms-lisp.pt-br.po 1 Jul 2020 14:31:21 -0000 1.10
@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: rms-lisp.html\n"
-"POT-Creation-Date: 2014-04-04 23:59+0000\n"
+"POT-Creation-Date: 2020-07-01 14:25+0000\n"
"PO-Revision-Date: 2019-01-03 13:12-0200\n"
"Last-Translator: Cassiano R Novais dos Santos <caco@member.fsf.org>\n"
"Language-Team: Brazilian Portuguese <www-pt-br-general@gnu.org>\n"
@@ -15,6 +15,7 @@
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"X-Outdated-Since: 2020-07-01 14:25+0000\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
"X-Generator: Virtaal 1.0.0-beta1\n"
@@ -139,19 +140,32 @@
"vivemos no AI Lab que levou ao Emacs e fez dele o que se tornou."
#. type: Content of: <p>
+#, fuzzy
+#| msgid ""
+#| "The original Emacs did not have Lisp in it. The lower level language, the "
+#| "non-interpreted language — 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 ‘5l’, meaning ‘move "
+#| "five lines’, or ‘i’ 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 — 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 ‘5l’, meaning ‘move five "
-"lines’, or ‘i’ 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."
+"non-interpreted language — was PDP-10 Assembler. The interpreter we "
+"wrote in that actually wasn't written for Emacs, it was written for <abbr "
+"title=\"Text Editor and 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 "
+"‘5l’, meaning ‘move five lines’, or ‘i’ "
+"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."
msgstr ""
"O Emacs original não tinha Lisp nele. A linguagem de baixo nÃvel, a "
"linguagem ṇo interpretada Рera o Assembler de <abbr>PDP</abbr>-10. O
"
@@ -167,6 +181,19 @@
"ESC ESC, e o comando seria executado."
#. type: Content of: <p>
+#, 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 < >. 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, "
@@ -177,7 +204,7 @@
"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>."
+"got its unwind-protect facility from TECO."
msgstr ""
"Bem, as pessoas queriam estender essa linguagem com recursos de
programação, "
"então elas adicionaram alguns. Por exemplo, um dos primeiros foi uma "
@@ -193,15 +220,26 @@
"protect</i> do <abbr>TECO</abbr>."
#. type: Content of: <p>
+#, fuzzy
+#| msgid ""
+#| "We started putting in rather sophisticated facilities, all with the "
+#| "ugliest syntax you could ever think of, and it worked — 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 — 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."
+"like 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."
msgstr ""
"Começamos a colocar instalações bastante sofisticadas, todas com a sintaxe
"
"mais feia que voc̻ poderia imaginar, e funcionou Рas pessoas eram "
@@ -258,6 +296,32 @@
"até chegarem ao ponto em que são programadores."
#. type: Content of: <p>
+#, 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 "
+#| "— it was a full-fledged Lisp system — 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 — 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. "
@@ -272,13 +336,12 @@
"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 "
+"machine language, making them into TECO primitives. For instance, there was "
+"a 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 TECO program). You could do the "
+"whole job by writing a 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."
@@ -329,19 +392,33 @@
"tela, gerenciamento de janelas do editor."
#. type: Content of: <p>
+#, 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 — 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 “you had to send back "
+#| "all of your improvements” 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 "
"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 — 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 “you had to send back all of your "
-"improvements” so we could all benefit. No one ever tried to enforce "
-"that, but as far as I know people did cooperate."
+"Emacs. I first released the original Emacs to people at MIT. Someone wanted "
+"to port it to run on Twenex — it originally only ran on the "
+"Incompatible Timesharing System we used at 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 “you had to send back all of your improvements” so we "
+"could all benefit. No one ever tried to enforce that, but as far as I know "
+"people did cooperate."
msgstr ""
"Agora, este não foi o primeiro Emacs que foi escrito em C e rodou no Unix. O
"
"primeiro foi escrito por James Gosling e foi referido como GosMacs. Uma "
@@ -432,16 +509,27 @@
"reexibição. à uma coisa bastante conveniente."
#. type: Content of: <p>
+#, fuzzy
+#| msgid ""
+#| "This second Emacs program was ‘free software’ in the modern "
+#| "sense of the term — 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 — "
+#| "the experience I had, the life that I've lived at the <abbr>MIT</abbr> AI "
+#| "lab — 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 ‘free software’ in the modern "
"sense of the term — 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 — the experience I had, "
-"the life that I've lived at the <abbr>MIT</abbr> AI lab — to be "
-"working on human knowledge, and not be standing in the way of anybody's "
-"further using and further disseminating human knowledge."
+"be free to do the things we did in the old days at MIT>, working together on "
+"software and working with whomever wanted to work with us. That is the "
+"basis for the free software movement — the experience I had, the life "
+"that I've lived at the MIT AI lab — to be working on human knowledge, "
+"and not be standing in the way of anybody's further using and further "
+"disseminating human knowledge."
msgstr ""
"Este segundo programa Emacs era âsoftware livreâ no sentido moderno do
termo "
"– foi parte de uma campanha polÃtica explÃcita para desenvolver "
@@ -586,19 +674,33 @@
"de cara no chão, eles começaram a procurar maneiras de destruÃ-la."
#. type: Content of: <p>
+#, fuzzy
+#| msgid ""
+#| "Thus, the abandonment of our lab was followed by “war” 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 “war” 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."
+"and eliminated people who worked part-time for MIT, so they had to leave "
+"entirely, which left only me. The AI lab was now helpless. And 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 MIT use their changes. But it "
+"didn't say in the contract that MIT was entitled to put them into the 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."
msgstr ""
"Assim, o abandono do nosso laboratório foi seguido por uma âguerraâ em
nosso "
"laboratório. O abandono aconteceu quando a Symbolics contratou todos os "
@@ -615,12 +717,19 @@
"seria aniquilado, mas foi."
#. type: Content of: <p>
+#, fuzzy
+#| msgid ""
+#| "So Symbolics came up with a plan <a href=\"#foot-4\">(4)</a>. They said "
+#| "to the lab, “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.”"
msgid ""
"So Symbolics came up with a plan <a href=\"#foot-4\">(4)</a>. They said to "
"the lab, “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.”"
+"for you to use, but you can't put it into the 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.”"
msgstr ""
"Então, a Symbolics criou um plano <a href=\"#foot-4\">(4)</a>. Eles disseram
"
"para o laboratório, âContinuaremos a disponibilizar nossas alterações no
"
@@ -630,15 +739,26 @@
"fazer.â"
#. type: Content of: <p>
+#, 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 <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."
+"use either the 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 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."
msgstr ""
"Isso, na verdade, significava que eles precisavam escolher um lado e, ou "
"usar a versão <abbr>MIT</abbr> do sistema ou a versão da Symbolics. A "
@@ -700,12 +820,19 @@
"as ações da Symbolics e outros haviam eliminado."
#. type: Content of: <p>
-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."
+#, 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 "
+"out 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."
msgstr ""
"A comunidade Lisp nos anos 70 não se limitou ao AI Lab do <abbr>MIT</abbr>, "
"e os hackers não estavam todos no <abbr>MIT</abbr>. A guerra que a Symbolics
"
@@ -830,20 +957,34 @@
"facilmente extensÃvel, como o editor. A questão era o que deveria ser."
#. type: Content of: <p>
-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 “de-facto standard extension "
-"language” of the world. And I thought, “We've got to stop that "
-"from happening.” 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."
+#, 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 “de-facto standard extension "
+#| "language” of the world. And I thought, “We've got to stop "
+#| "that from happening.” 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 "
+"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 TCL to make it the “de-facto "
+"standard extension language” of the world. And I thought, “We've "
+"got to stop that from happening.” 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 TCL was linked into applications. "
+"We would then recommend that as the preferred extensibility package for all "
+"GNU programs."
msgstr ""
"Na época, a <abbr title=\"Tool Command Language\">TCL</abbr> estava sendo "
"intensamente utilizada para essa finalidade. Eu tinha uma opinião muito ruim
"
@@ -860,18 +1001,32 @@
"programas GNU."
#. type: Content of: <p>
+#, 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 "
"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."
+"language. If your primary language is TCL, you can't very easily implement "
+"Lisp by translating it into 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 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."
msgstr ""
"Há um benefÃcio interessante que você pode obter usando uma linguagem tão
"
"poderosa quanto uma versão do Lisp como sua principal linguagem de "
@@ -1158,18 +1313,22 @@
"envio de traduções das páginas deste site."
#. type: Content of: <div><p>
-msgid "Copyright © 2003, 2007, 2013, 2014 Free Software Foundation, Inc."
+#, fuzzy
+#| msgid ""
+#| "Copyright © 2003, 2007, 2013, 2014 Free Software Foundation, Inc."
+msgid ""
+"Copyright © 2003, 2007, 2013, 2014, 2020 Free Software Foundation, Inc."
msgstr "Copyright © 2003, 2007, 2013, 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>."
+"creativecommons.org/licenses/by-nd/4.0/\">Creative Commons Attribution-"
+"NoDerivatives 4.0 International License</a>."
msgstr ""
"Esta página está licenciada sob uma licença <a rel=\"license\"
href=\"http://";
-"creativecommons.org/licenses/by-nd/3.0/us/deed.pt_BR\">Creative Commons "
-"Atribuição-SemDerivações 3.0 Estados Unidos</a>."
+"creativecommons.org/licenses/by-nd/4.0/deed.pt_BR\">Creative Commons "
+"Atribuição-SemDerivações 4.0 Internacional</a>."
#. TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.
#. type: Content of: <div><div>
Index: gnu/po/rms-lisp.ru.po
===================================================================
RCS file: /web/www/www/gnu/po/rms-lisp.ru.po,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -b -r1.10 -r1.11
--- gnu/po/rms-lisp.ru.po 14 Apr 2015 13:28:50 -0000 1.10
+++ gnu/po/rms-lisp.ru.po 1 Jul 2020 14:31:22 -0000 1.11
@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: rms-lisp.html\n"
-"POT-Creation-Date: 2014-04-04 23:59+0000\n"
+"POT-Creation-Date: 2020-07-01 14:25+0000\n"
"PO-Revision-Date: 2014-04-05 17:34+0000\n"
"Last-Translator: Ineiev <ineiev@gnu.org>\n"
"Language-Team: Russian <www-ru-list@gnu.org>\n"
@@ -15,6 +15,7 @@
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"X-Outdated-Since: 2020-07-01 14:25+0000\n"
#. type: Content of: <title>
msgid ""
@@ -138,19 +139,45 @@
"инÑеллекÑа пÑивела к ÑÐ¾Ð·Ð´Ð°Ð½Ð¸Ñ Emacs и
Ñделала его Ñаким, каким он бÑл."
#. type: Content of: <p>
+# | The original Emacs did not have Lisp in it. The lower level language, the
+# | non-interpreted language — 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 ‘5l’, meaning ‘move
+# | five lines’, or ‘i’ 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 — 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 ‘5l’, meaning ‘move "
+#| "five lines’, or ‘i’ 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 — 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 ‘5l’, meaning ‘move five "
-"lines’, or ‘i’ 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."
+"non-interpreted language — was PDP-10 Assembler. The interpreter we "
+"wrote in that actually wasn't written for Emacs, it was written for <abbr "
+"title=\"Text Editor and 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 "
+"‘5l’, meaning ‘move five lines’, or ‘i’ "
+"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."
msgstr ""
"РпеÑвонаÑалÑном Emacs ÐиÑпа не бÑло. ЯзÑком
низкого ÑÑÐ¾Ð²Ð½Ñ — "
"неинÑеÑпÑеÑиÑÑемÑм ÑзÑком — бÑл
аÑÑÐµÐ¼Ð±Ð»ÐµÑ PDP-10. ÐнÑеÑпÑеÑаÑоÑ, "
@@ -167,6 +194,30 @@
"вÑполнÑлаÑÑ."
#. 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 < >. 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 < >. 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, "
@@ -177,7 +228,7 @@
"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>."
+"got its unwind-protect facility from TECO."
msgstr ""
"ÐÑ, лÑди Ñ
оÑели дополниÑÑ ÑÑÐ¾Ñ ÑзÑк
ÑÑедÑÑвами пÑогÑаммиÑованиÑ, Ñак ÑÑо они "
"добавили некоÑоÑÑе Ñакие ÑÑедÑÑва.
ÐапÑимеÑ, одной из пеÑвÑÑ
бÑла добавлена "
@@ -192,15 +243,35 @@
"unwind-protect” ÐиÑп заимÑÑвовал из TECO."
#. type: Content of: <p>
+# | We started putting in rather sophisticated facilities, all with the
+# | ugliest syntax you could ever think of, and it worked — 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 — 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 — 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."
+"like 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."
msgstr ""
"ÐÑ Ð½Ð°Ñали закладÑваÑÑ Ð´Ð¾Ð²Ð¾Ð»Ñно
замÑÑловаÑÑе ÑÑедÑÑва, и Ñ Ð²ÑеÑ
Ñ Ð½Ð¸Ñ
бÑл "
"ÑÑодливейÑий ÑинÑакÑиÑ, какой ÑолÑко
можно пÑидÑмаÑÑ, и ÑÑо ÑабоÑало "
@@ -258,6 +329,56 @@
"коÑоÑой они Ñже ÑÑали пÑогÑаммиÑÑами."
#. 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
+# | — it was a full-fledged Lisp system — 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 — 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 "
+#| "— it was a full-fledged Lisp system — 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 — 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. "
@@ -272,13 +393,12 @@
"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 "
+"machine language, making them into TECO primitives. For instance, there was "
+"a 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 TECO program). You could do the "
+"whole job by writing a 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."
@@ -328,19 +448,46 @@
"бÑÑеÑа на ÑкÑане, ÑпÑавление окнами
ÑедакÑоÑа."
#. 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
+# | — 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 “you had to send back all of your improvements” 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 — 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 “you had to send back "
+#| "all of your improvements” 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 "
"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 — 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 “you had to send back all of your "
-"improvements” so we could all benefit. No one ever tried to enforce "
-"that, but as far as I know people did cooperate."
+"Emacs. I first released the original Emacs to people at MIT. Someone wanted "
+"to port it to run on Twenex — it originally only ran on the "
+"Incompatible Timesharing System we used at 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 “you had to send back all of your improvements” so we "
+"could all benefit. No one ever tried to enforce that, but as far as I know "
+"people did cooperate."
msgstr ""
"Так воÑ, ÑÑо бÑл не пеÑвÑй Emacs, напиÑаннÑй
на Си и ÑабоÑавÑий в Unix. "
"ÐеÑвÑй бÑл напиÑан ÐжеймÑом ÐоÑлингом,
его назÑвали GosMacs. С ним вÑÑла "
@@ -431,16 +578,37 @@
"пеÑеÑиÑовки. ÐÑо оÑÐµÐ½Ñ Ñдобно."
#. type: Content of: <p>
+# | This second Emacs program was ‘free software’ in the modern
+# | sense of the term — 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 —
+# | the experience I had, the life that I've lived at the [-<abbr>MIT</abbr>-]
+# | {+MIT+} AI lab — 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 ‘free software’ in the modern "
+#| "sense of the term — 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 — "
+#| "the experience I had, the life that I've lived at the <abbr>MIT</abbr> AI "
+#| "lab — 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 ‘free software’ in the modern "
"sense of the term — 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 — the experience I had, "
-"the life that I've lived at the <abbr>MIT</abbr> AI lab — to be "
-"working on human knowledge, and not be standing in the way of anybody's "
-"further using and further disseminating human knowledge."
+"be free to do the things we did in the old days at MIT>, working together on "
+"software and working with whomever wanted to work with us. That is the "
+"basis for the free software movement — the experience I had, the life "
+"that I've lived at the MIT AI lab — to be working on human knowledge, "
+"and not be standing in the way of anybody's further using and further "
+"disseminating human knowledge."
msgstr ""
"ÐÑа вÑоÑÐ°Ñ Ð¿ÑогÑамма Emacs бÑла
“Ñвободной пÑогÑаммой” в "
"ÑовÑеменном ÑмÑÑле ÑÑого Ñлова — она
бÑла ÑаÑÑÑÑ Ð¾ÑкÑÑÑой "
@@ -586,19 +754,46 @@
"ÑÑали иÑкаÑÑ ÑпоÑÐ¾Ð±Ñ ÑазÑÑÑиÑÑ ÐµÐµ."
#. type: Content of: <p>
+# | Thus, the abandonment of our lab was followed by “war” 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 “war” 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 “war” 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."
+"and eliminated people who worked part-time for MIT, so they had to leave "
+"entirely, which left only me. The AI lab was now helpless. And 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 MIT use their changes. But it "
+"didn't say in the contract that MIT was entitled to put them into the 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."
msgstr ""
"Таким обÑазом, за ÑÑ
одом из наÑей
лабоÑаÑоÑии поÑледовала “"
"война” в наÑей лабоÑаÑоÑии. УÑ
од
пÑоизоÑел, когда ÐºÐ¾Ð¼Ð¿Ð°Ð½Ð¸Ñ Symbolics "
@@ -615,12 +810,25 @@
"ÐабоÑаÑоÑии иÑкÑÑÑÑвенного инÑеллекÑа
ÑазгонÑÑ, но Ñак и ÑлÑÑилоÑÑ."
#. type: Content of: <p>
+# | So Symbolics came up with a plan <a href=\"#foot-4\">(4)</a>. They said
+# | to the lab, “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.”
+#, fuzzy
+#| msgid ""
+#| "So Symbolics came up with a plan <a href=\"#foot-4\">(4)</a>. They said "
+#| "to the lab, “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.”"
msgid ""
"So Symbolics came up with a plan <a href=\"#foot-4\">(4)</a>. They said to "
"the lab, “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.”"
+"for you to use, but you can't put it into the 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.”"
msgstr ""
"ÐÑак, в Symbolics ÑозÑел план <a
href=\"#foot-4\">(4)</a>. Ðни Ñказали "
"лабоÑаÑоÑии: “ÐÑ Ð¿Ñодолжим
пÑедоÑÑавлÑÑÑ Ð² ваÑе полÑзование Ñвои "
@@ -629,15 +837,35 @@
"Symbolics, и Ð²Ñ ÑможеÑе ÑабоÑаÑÑ Ð½Ð° ней, но ÑÑо
вÑе, ÑÑо Ð²Ñ Ð¼Ð¾Ð¶ÐµÑе делаÑÑ."
#. 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 <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."
+"use either the 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 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."
msgstr ""
"ÐÑо ÑакÑиÑеÑки ознаÑало, ÑÑо они
поÑÑебовали Ð¾Ñ Ð½Ð°Ñ Ð²ÑÑаÑÑ Ð½Ð° ÑÑ Ð¸Ð»Ð¸ дÑÑгÑÑ "
"ÑÑоÑÐ¾Ð½Ñ Ð¸ полÑзоваÑÑÑÑ Ð»Ð¸Ð±Ð¾ веÑÑией
инÑÑиÑÑÑа, либо веÑÑией Symbolics. ЧÑо "
@@ -700,12 +928,25 @@
"коÑоÑое бÑло ÑниÑÑожено иÑ
дейÑÑвиÑми и
дейÑÑвиÑми дÑÑгиÑ
."
#. type: Content of: <p>
-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."
+# | 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 "
+"out 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."
msgstr ""
"Ð ÑемидеÑÑÑÑÑ
годаÑ
ÑообÑеÑÑво ÐиÑпа не
огÑаниÑивалоÑÑ ÐабоÑаÑоÑией "
"иÑкÑÑÑÑвенного инÑеллекÑа
ÐаÑÑаÑÑÑеÑÑкого ÑеÑ
ниÑеÑкого инÑÑиÑÑÑа, и
не вÑе "
@@ -836,20 +1077,49 @@
"бÑÑÑ ÑзÑк."
#. type: Content of: <p>
-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 “de-facto standard extension "
-"language” of the world. And I thought, “We've got to stop that "
-"from happening.” 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."
+# | 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
+# | “de-facto standard extension language” of the world. And I
+# | thought, “We've got to stop that from happening.” 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 “de-facto standard extension "
+#| "language” of the world. And I thought, “We've got to stop "
+#| "that from happening.” 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 "
+"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 TCL to make it the “de-facto "
+"standard extension language” of the world. And I thought, “We've "
+"got to stop that from happening.” 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 TCL was linked into applications. "
+"We would then recommend that as the preferred extensibility package for all "
+"GNU programs."
msgstr ""
"Ð Ñо вÑÐµÐ¼Ñ Ð´Ð»Ñ ÑÑиÑ
Ñелей ÑÑиленно
пÑодвигалÑÑ TCL <a href=\"#tf2\">[2]"
"</a>. Я бÑл оÑÐµÐ½Ñ Ð½ÐµÐ²ÑÑокого Ð¼Ð½ÐµÐ½Ð¸Ñ Ð¾ TCL, в
оÑновном поÑомÑ, ÑÑо ÑÑо бÑл не "
@@ -865,18 +1135,44 @@
"Ð´Ð»Ñ Ð²ÑеÑ
пÑогÑамм GNU."
#. 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 "
"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."
+"language. If your primary language is TCL, you can't very easily implement "
+"Lisp by translating it into 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 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."
msgstr ""
"ÐÑÑÑ Ð¾Ð´Ð½Ð° инÑеÑеÑÐ½Ð°Ñ Ð²Ñгода, коÑоÑÑÑ
можно извлеÑÑ Ð¸Ð· пÑÐ¸Ð¼ÐµÐ½ÐµÐ½Ð¸Ñ Ñакого "
"моÑного ÑзÑка, как ваÑÐ¸Ð°Ð½Ñ ÐиÑпа, в
каÑеÑÑве пеÑвиÑного ÑзÑка ÑаÑÑиÑений. ÐÑ "
@@ -1173,19 +1469,31 @@
# type: Content of: <div><p>
#. type: Content of: <div><p>
-msgid "Copyright © 2003, 2007, 2013, 2014 Free Software Foundation, Inc."
+# | Copyright © 2003, 2007, 2013, [-2014-] {+2014, 2020+} Free Software
+# | Foundation, Inc.
+#, fuzzy
+#| msgid ""
+#| "Copyright © 2003, 2007, 2013, 2014 Free Software Foundation, Inc."
+msgid ""
+"Copyright © 2003, 2007, 2013, 2014, 2020 Free Software Foundation, Inc."
msgstr "Copyright © 2003, 2007, 2013, 2014 Free Software Foundation, Inc."
#. type: Content of: <div><p>
+# || No change detected. The change might only be in amounts of spaces.
+#, fuzzy
+#| msgid ""
+#| "This page is licensed under a <a rel=\"license\" href=\"http://";
+#| "creativecommons.org/licenses/by-nd/4.0/\">Creative Commons Attribution-"
+#| "NoDerivatives 4.0 International License</a>."
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>."
+"creativecommons.org/licenses/by-nd/4.0/\">Creative Commons Attribution-"
+"NoDerivatives 4.0 International License</a>."
msgstr ""
"ÐÑо пÑоизведение доÑÑÑпно по <a rel=\"license\"
href=\"http://";
-"creativecommons.org/licenses/by-nd/3.0/us/deed.ru\">лиÑензии Creative
"
-"Commons Attribution-NoDerivs (<em>ÐÑÑибÑÑÐ¸Ñ — Ðез
пÑоизводнÑÑ
"
-"пÑоизведений</em>) 3.0 СШÐ</a>."
+"creativecommons.org/licenses/by-nd/4.0/deed.ru\">лиÑензии Creative
Commons "
+"Attribution-NoDerivs (<em>ÐÑÑибÑÑÐ¸Ñ — Ðез
пÑоизводнÑÑ
"
+"пÑоизведений</em>) 4.0 ÐÑемиÑнаÑ</a>."
# type: Content of: <div><div>
#. TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.
Index: gnu/po/rms-lisp.sq.po
===================================================================
RCS file: /web/www/www/gnu/po/rms-lisp.sq.po,v
retrieving revision 1.35
retrieving revision 1.36
diff -u -b -r1.35 -r1.36
--- gnu/po/rms-lisp.sq.po 13 Feb 2015 16:57:39 -0000 1.35
+++ gnu/po/rms-lisp.sq.po 1 Jul 2020 14:31:22 -0000 1.36
@@ -6,7 +6,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2014-04-04 23:59+0000\n"
+"POT-Creation-Date: 2020-07-01 14:25+0000\n"
"PO-Revision-Date: 2014-11-28 23:29+0200\n"
"Last-Translator: Besnik Bleta <besnik@programeshqip.org>\n"
"Language-Team: Shqip <besnik@programeshqip.org>\n"
@@ -14,6 +14,7 @@
"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"
# type: Content of: <title>
#. type: Content of: <title>
@@ -144,19 +145,32 @@
# type: Content of: <p>
#. type: Content of: <p>
+#, fuzzy
+#| msgid ""
+#| "The original Emacs did not have Lisp in it. The lower level language, the "
+#| "non-interpreted language — 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 ‘5l’, meaning ‘move "
+#| "five lines’, or ‘i’ 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 — 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 ‘5l’, meaning ‘move five "
-"lines’, or ‘i’ 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."
+"non-interpreted language — was PDP-10 Assembler. The interpreter we "
+"wrote in that actually wasn't written for Emacs, it was written for <abbr "
+"title=\"Text Editor and 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 "
+"‘5l’, meaning ‘move five lines’, or ‘i’ "
+"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."
msgstr ""
"Emacs-i origjinal nuk përmbante Lisp. Gjuha e nivelit të ulët, gjuha e "
"painterpretueshme — qe <abbr>PDP</abbr>-10 Assembler. Interpretuesi që
"
@@ -172,6 +186,19 @@
# type: Content of: <p>
#. type: Content of: <p>
+#, 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 < >. 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, "
@@ -182,7 +209,7 @@
"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>."
+"got its unwind-protect facility from TECO."
msgstr ""
"Njerëzit donin ta zgjeronin këtë gjuhë me aftësi programimi, ndaj edhe "
"shtuan ca syresh. Për shembull, nga të parat qe një mekanizëm
përsëritjeje, "
@@ -198,15 +225,26 @@
# type: Content of: <p>
#. type: Content of: <p>
+#, fuzzy
+#| msgid ""
+#| "We started putting in rather sophisticated facilities, all with the "
+#| "ugliest syntax you could ever think of, and it worked — 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 — 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."
+"like 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."
msgstr ""
"Filluam duke shtuar aftësi pak a shumë të sofistikuara, krejt me
sintaksën "
"më të shpifur që mund të mendoni, dhe funksionoi — njerëzit "
@@ -266,6 +304,32 @@
# type: Content of: <p>
#. type: Content of: <p>
+#, 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 "
+#| "— it was a full-fledged Lisp system — 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 — 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. "
@@ -280,13 +344,12 @@
"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 "
+"machine language, making them into TECO primitives. For instance, there was "
+"a 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 TECO program). You could do the "
+"whole job by writing a 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."
@@ -339,19 +402,33 @@
# type: Content of: <p>
#. type: Content of: <p>
+#, 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 — 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 “you had to send back "
+#| "all of your improvements” 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 "
"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 — 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 “you had to send back all of your "
-"improvements” so we could all benefit. No one ever tried to enforce "
-"that, but as far as I know people did cooperate."
+"Emacs. I first released the original Emacs to people at MIT. Someone wanted "
+"to port it to run on Twenex — it originally only ran on the "
+"Incompatible Timesharing System we used at 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 “you had to send back all of your improvements” so we "
+"could all benefit. No one ever tried to enforce that, but as far as I know "
+"people did cooperate."
msgstr ""
"Tani, ky nuk qe Emacs-i i parë i shkruar në C dhe që xhironte nën Unix. I
"
"pari qe shkruar nga James Gosling, dhe i referoheshin si GosMacs. I ndodhi "
@@ -446,16 +523,27 @@
# type: Content of: <p>
#. type: Content of: <p>
+#, fuzzy
+#| msgid ""
+#| "This second Emacs program was ‘free software’ in the modern "
+#| "sense of the term — 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 — "
+#| "the experience I had, the life that I've lived at the <abbr>MIT</abbr> AI "
+#| "lab — 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 ‘free software’ in the modern "
"sense of the term — 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 — the experience I had, "
-"the life that I've lived at the <abbr>MIT</abbr> AI lab — to be "
-"working on human knowledge, and not be standing in the way of anybody's "
-"further using and further disseminating human knowledge."
+"be free to do the things we did in the old days at MIT>, working together on "
+"software and working with whomever wanted to work with us. That is the "
+"basis for the free software movement — the experience I had, the life "
+"that I've lived at the MIT AI lab — to be working on human knowledge, "
+"and not be standing in the way of anybody's further using and further "
+"disseminating human knowledge."
msgstr ""
"Ky program i dytë Emacs qe ‘<em>software</em> i lirë’ në "
"kuptimin modern të fjalës — qe pjesë e një fushate të deklaruar "
@@ -606,19 +694,33 @@
# type: Content of: <p>
#. type: Content of: <p>
+#, fuzzy
+#| msgid ""
+#| "Thus, the abandonment of our lab was followed by “war” 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 “war” 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."
+"and eliminated people who worked part-time for MIT, so they had to leave "
+"entirely, which left only me. The AI lab was now helpless. And 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 MIT use their changes. But it "
+"didn't say in the contract that MIT was entitled to put them into the 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."
msgstr ""
"Kështu që, në laboratorin tonë, braktisja u pasua nga
“lufta”. "
"Braktisja erdhi kur Symbolics punësoi krejt <i>hacker</i>-ët, hiq mua dhe "
@@ -637,12 +739,19 @@
# type: Content of: <p>
#. type: Content of: <p>
+#, fuzzy
+#| msgid ""
+#| "So Symbolics came up with a plan <a href=\"#foot-4\">(4)</a>. They said "
+#| "to the lab, “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.”"
msgid ""
"So Symbolics came up with a plan <a href=\"#foot-4\">(4)</a>. They said to "
"the lab, “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.”"
+"for you to use, but you can't put it into the 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.”"
msgstr ""
"Kështu që Symbolics hartoi një plan <a href=\"#foot-4\">(4)</a>. I thanë
"
"laboratorit, “Do të vazhdojmë tâju lejojmë përdorimin e
ndryshimeve "
@@ -653,15 +762,26 @@
# type: Content of: <p>
#. type: Content of: <p>
+#, 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 <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."
+"use either the 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 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."
msgstr ""
"Kjo, praktikisht, do të thoshte që na kërkuan të zgjidhnim me kë palë
do të "
"ishim, dhe të përdornim ose versionin <abbr>MIT</abbr> të sistemit, ose "
@@ -727,12 +847,19 @@
# type: Content of: <p>
#. type: Content of: <p>
-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."
+#, 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 "
+"out 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."
msgstr ""
"Bashkësia Lisp në vitet â70 nuk kufizohej te <abbr>MIT</abbr> AI Lab, dhe
"
"<i>hacker</i>-ët nuk qenë vetëm në <abbr>MIT</abbr>. Lufta e nisur nga "
@@ -867,20 +994,34 @@
# type: Content of: <p>
#. type: Content of: <p>
-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 “de-facto standard extension "
-"language” of the world. And I thought, “We've got to stop that "
-"from happening.” 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."
+#, 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 “de-facto standard extension "
+#| "language” of the world. And I thought, “We've got to stop "
+#| "that from happening.” 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 "
+"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 TCL to make it the “de-facto "
+"standard extension language” of the world. And I thought, “We've "
+"got to stop that from happening.” 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 TCL was linked into applications. "
+"We would then recommend that as the preferred extensibility package for all "
+"GNU programs."
msgstr ""
"Në atë kohë, <acronym title=\"Tool Command Language\">TCL</acronym> po "
"reklamohej rëndshëm për këtë qëllim. Kisha vlerësim shumë të ulët
për "
@@ -898,18 +1039,32 @@
# type: Content of: <p>
#. type: Content of: <p>
+#, 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 "
"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."
+"language. If your primary language is TCL, you can't very easily implement "
+"Lisp by translating it into 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 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."
msgstr ""
"Ka një përfitim interesant që ju vjen nga përdorimi si gjuhë tuajën
parësore "
"për zgjerime i një gjuhe kaq të fuqishme siç do të ishte një version
Lisp-"
@@ -1214,16 +1369,25 @@
# type: Content of: <div><p>
#. type: Content of: <div><p>
-msgid "Copyright © 2003, 2007, 2013, 2014 Free Software Foundation, Inc."
+#, fuzzy
+#| msgid ""
+#| "Copyright © 2003, 2007, 2013, 2014 Free Software Foundation, Inc."
+msgid ""
+"Copyright © 2003, 2007, 2013, 2014, 2020 Free Software Foundation, Inc."
msgstr ""
"Të drejta kopjimi © 2003, 2007, 2013, 2014 Free Software Foundation, "
"Inc."
#. type: Content of: <div><p>
+#, fuzzy
+#| 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>."
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>."
+"creativecommons.org/licenses/by-nd/4.0/\">Creative Commons Attribution-"
+"NoDerivatives 4.0 International License</a>."
msgstr ""
"Kjo faqe mund të përdoret sipas një licence <a rel=\"license\"
href=\"http://";
"creativecommons.org/licenses/by-nd/3.0/us/\">Creative Commons Attribution-"
Index: gnu/po/rms-lisp.uk.po
===================================================================
RCS file: /web/www/www/gnu/po/rms-lisp.uk.po,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -b -r1.6 -r1.7
--- gnu/po/rms-lisp.uk.po 4 Aug 2016 05:57:33 -0000 1.6
+++ gnu/po/rms-lisp.uk.po 1 Jul 2020 14:31:22 -0000 1.7
@@ -6,7 +6,7 @@
msgid ""
msgstr ""
"Project-Id-Version: rms-lisp.html\n"
-"POT-Creation-Date: 2014-04-04 23:59+0000\n"
+"POT-Creation-Date: 2020-07-01 14:25+0000\n"
"PO-Revision-Date: 2016-08-04 08:20+0200\n"
"Last-Translator: Andriy Bandura <andriykopanytsia@gmail.com>\n"
"Language-Team: Ukrainian <>\n"
@@ -14,6 +14,7 @@
"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"
"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
"X-Generator: Lokalize 2.0\n"
@@ -139,19 +140,32 @@
"зÑобила його Ñаким, Ñким вÑн бÑв."
#. type: Content of: <p>
+#, fuzzy
+#| msgid ""
+#| "The original Emacs did not have Lisp in it. The lower level language, the "
+#| "non-interpreted language — 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 ‘5l’, meaning ‘move "
+#| "five lines’, or ‘i’ 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 — 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 ‘5l’, meaning ‘move five "
-"lines’, or ‘i’ 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."
+"non-interpreted language — was PDP-10 Assembler. The interpreter we "
+"wrote in that actually wasn't written for Emacs, it was written for <abbr "
+"title=\"Text Editor and 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 "
+"‘5l’, meaning ‘move five lines’, or ‘i’ "
+"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."
msgstr ""
"У пеÑвÑÑÐ½Ð¾Ð¼Ñ Emacs ÐÑÑпа не бÑло. ÐовоÑ
низÑкого ÑÑÐ²Ð½Ñ — "
"неÑÑеÑпÑеÑÐ¾Ð²Ð°Ð½Ð¾Ñ Ð¼Ð¾Ð²Ð¾Ñ Ð±Ñв
аÑÐµÐ¼Ð±Ð»ÐµÑ PDP-10. ÐнÑеÑпÑеÑаÑоÑ, Ñкий "
@@ -167,6 +181,19 @@
"поÑлÑдовнÑÑÑÑ Ð²Ð¸ÐºÐ¾Ð½ÑвалаÑÑ."
#. type: Content of: <p>
+#, 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 < >. 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, "
@@ -177,7 +204,7 @@
"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>."
+"got its unwind-protect facility from TECO."
msgstr ""
"ÐÑÑм лÑди Ñ
оÑÑли доповниÑи ÑÑ Ð¼Ð¾Ð²Ñ
заÑобами пÑогÑамÑваннÑ, ÑÐ¾Ð¼Ñ Ð²Ð¾Ð½Ð¸ додали "
"деÑÐºÑ Ð·Ð°Ñоби. ÐапÑиклад, однÑÑÑ Ð· пеÑÑиÑ
бÑла додана конÑÑÑÑкÑÑÑ ÑиклÑ, Ñе "
@@ -191,15 +218,26 @@
"unwind-protect” ÐÑÑп запозиÑив з TECO."
#. type: Content of: <p>
+#, fuzzy
+#| msgid ""
+#| "We started putting in rather sophisticated facilities, all with the "
+#| "ugliest syntax you could ever think of, and it worked — 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 — 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."
+"like 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."
msgstr ""
"Ðи поÑали закладаÑи доÑиÑÑ Ñ
иÑÑомÑдÑÑ
заÑоби, Ñ Ñ Ð²ÑÑÑ
Ñ Ð½Ð¸Ñ
бÑв поÑвоÑний "
"ÑинÑакÑиÑ, Ñкий ÑÑлÑки-но можна пÑидÑмаÑи,
Ñ Ñе пÑаÑÑвало лÑди "
@@ -256,6 +294,32 @@
"пÑогÑамÑÑÑами."
#. type: Content of: <p>
+#, 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 "
+#| "— it was a full-fledged Lisp system — 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 — 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. "
@@ -270,13 +334,12 @@
"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 "
+"machine language, making them into TECO primitives. For instance, there was "
+"a 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 TECO program). You could do the "
+"whole job by writing a 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."
@@ -325,19 +388,33 @@
"екÑанÑ, ÑпÑавлÑÐ½Ð½Ñ Ð²Ñкнами ÑедакÑоÑа."
#. type: Content of: <p>
+#, 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 — 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 “you had to send back "
+#| "all of your improvements” 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 "
"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 — 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 “you had to send back all of your "
-"improvements” so we could all benefit. No one ever tried to enforce "
-"that, but as far as I know people did cooperate."
+"Emacs. I first released the original Emacs to people at MIT. Someone wanted "
+"to port it to run on Twenex — it originally only ran on the "
+"Incompatible Timesharing System we used at 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 “you had to send back all of your improvements” so we "
+"could all benefit. No one ever tried to enforce that, but as far as I know "
+"people did cooperate."
msgstr ""
"ÐоÑеÑÑ Ñе бÑв не пеÑÑий Emacs, напиÑаний на
Ð¡Ñ Ñ Ð¿ÑаÑÑвав в Unix. ÐеÑÑий бÑв "
"напиÑаний ÐжеймÑом ÐоÑлÑнгом, його
називали GosMacs. РниÑ
вийÑла дивна "
@@ -428,16 +505,27 @@
"дÑже зÑÑÑно."
#. type: Content of: <p>
+#, fuzzy
+#| msgid ""
+#| "This second Emacs program was ‘free software’ in the modern "
+#| "sense of the term — 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 — "
+#| "the experience I had, the life that I've lived at the <abbr>MIT</abbr> AI "
+#| "lab — 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 ‘free software’ in the modern "
"sense of the term — 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 — the experience I had, "
-"the life that I've lived at the <abbr>MIT</abbr> AI lab — to be "
-"working on human knowledge, and not be standing in the way of anybody's "
-"further using and further disseminating human knowledge."
+"be free to do the things we did in the old days at MIT>, working together on "
+"software and working with whomever wanted to work with us. That is the "
+"basis for the free software movement — the experience I had, the life "
+"that I've lived at the MIT AI lab — to be working on human knowledge, "
+"and not be standing in the way of anybody's further using and further "
+"disseminating human knowledge."
msgstr ""
"Ð¦Ñ Ð´ÑÑга пÑогÑама Emacs бÑла “вÑлÑноÑ
пÑогÑамоє ÑÑÑаÑÐ½Ð¾Ð¼Ñ "
"ÑозÑмÑÐ½Ð½Ñ ÑÑого Ñлова — вона бÑла
ÑаÑÑÐ¸Ð½Ð¾Ñ Ð²ÑдкÑиÑÐ¾Ñ Ð¿Ð¾Ð»ÑÑиÑÐ½Ð¾Ñ "
@@ -579,19 +667,33 @@
"зÑÑйнÑваÑи ÑÑ."
#. type: Content of: <p>
+#, fuzzy
+#| msgid ""
+#| "Thus, the abandonment of our lab was followed by “war” 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 “war” 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."
+"and eliminated people who worked part-time for MIT, so they had to leave "
+"entirely, which left only me. The AI lab was now helpless. And 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 MIT use their changes. But it "
+"didn't say in the contract that MIT was entitled to put them into the 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."
msgstr ""
"Таким Ñином, за вÑдÑ
одом з наÑоÑ
лабоÑаÑоÑÑÑ Ð½Ð°ÑÑала “вÑйна” в "
"наÑÑй лабоÑаÑоÑÑÑ. ÐÑдÑ
Ñд ÑÑавÑÑ, коли
компанÑÑ Symbolics пеÑеманила вÑÑÑ
"
@@ -607,12 +709,19 @@
"Ñ
акеÑÑв ÐабоÑаÑоÑÑÑ ÑÑÑÑного ÑнÑелекÑÑ
ÑозженÑÑÑ, але Ñак Ñ ÑÑалоÑÑ."
#. type: Content of: <p>
+#, fuzzy
+#| msgid ""
+#| "So Symbolics came up with a plan <a href=\"#foot-4\">(4)</a>. They said "
+#| "to the lab, “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.”"
msgid ""
"So Symbolics came up with a plan <a href=\"#foot-4\">(4)</a>. They said to "
"the lab, “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.”"
+"for you to use, but you can't put it into the 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.”"
msgstr ""
"ÐÑже, в Symbolics дозÑÑв план <a
href=\"#foot-4\">(4)</a>. Ðони Ñказали "
"лабоÑаÑоÑÑÑ: “Ðи пÑодовжимо надаваÑи Ñ
ваÑе коÑиÑÑÑÐ²Ð°Ð½Ð½Ñ ÑÐ²Ð¾Ñ Ð·Ð¼Ñни в "
@@ -621,15 +730,26 @@
"зможеÑе пÑаÑÑваÑи на нÑй, але Ñе вÑе, Ñо ви
можеÑе ÑобиÑи."
#. type: Content of: <p>
+#, 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 <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."
+"use either the 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 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."
msgstr ""
"Це ÑакÑиÑно ознаÑало, Ñо вони зажадали вÑд
Ð½Ð°Ñ ÑÑаÑи на ÑÑ Ñи ÑнÑÑ Ð±Ñк Ñ "
"коÑиÑÑÑваÑиÑÑ Ð°Ð±Ð¾ веÑÑÑÑÑ ÑнÑÑиÑÑÑÑ, або
веÑÑÑÑÑ Symbolics. Що б ми не "
@@ -690,12 +810,19 @@
"ÑÑ
нÑми дÑÑми Ñа дÑÑми ÑнÑиÑ
."
#. type: Content of: <p>
-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."
+#, 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 "
+"out 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."
msgstr ""
"У ÑÑмдеÑÑÑиÑ
ÑокаÑ
ÑпÑвÑоваÑиÑÑво ÐÑÑпа
не обмежÑвалоÑÑ ÐабоÑаÑоÑÑÑÑ "
"ÑÑÑÑного ÑнÑелекÑÑ ÐаÑÑаÑÑÑеÑÑÑкого ÑеÑ
нологÑÑного ÑнÑÑиÑÑÑÑ, Ñ Ð½Ðµ вÑÑ "
@@ -824,20 +951,34 @@
"мова."
#. type: Content of: <p>
-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 “de-facto standard extension "
-"language” of the world. And I thought, “We've got to stop that "
-"from happening.” 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."
+#, 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 “de-facto standard extension "
+#| "language” of the world. And I thought, “We've got to stop "
+#| "that from happening.” 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 "
+"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 TCL to make it the “de-facto "
+"standard extension language” of the world. And I thought, “We've "
+"got to stop that from happening.” 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 TCL was linked into applications. "
+"We would then recommend that as the preferred extensibility package for all "
+"GNU programs."
msgstr ""
"У Ñой ÑÐ°Ñ Ð´Ð»Ñ ÑиÑ
ÑÑлей поÑилено
пÑоÑÑвавÑÑ TCL <a href=\"#tf2\">[2]</"
"a>. Я бÑв дÑже невиÑÐ¾ÐºÐ¾Ñ Ð´Ñмки пÑо TCL, в
оÑÐ½Ð¾Ð²Ð½Ð¾Ð¼Ñ ÑомÑ, Ñо Ñе бÑв не ÐÑÑп. "
@@ -852,18 +993,32 @@
"ми ÑÑали б ÑекомендÑваÑи Ñе Ñк бажаний
Ð¿Ð°ÐºÐµÑ ÑозÑиÑÐµÐ½Ñ Ð´Ð»Ñ Ð²ÑÑÑ
пÑогÑам GNU."
#. type: Content of: <p>
+#, 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 "
"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."
+"language. If your primary language is TCL, you can't very easily implement "
+"Lisp by translating it into 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 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."
msgstr ""
"Родна ÑÑкава вигода, ÑÐºÑ Ð¼Ð¾Ð¶Ð½Ð° оÑÑимаÑи з
заÑÑоÑÑÐ²Ð°Ð½Ð½Ñ Ñакого поÑÑÐ¶Ð½Ð¾Ñ "
"мови, Ñк ваÑÑÐ°Ð½Ñ ÐÑÑпа, в ÑкоÑÑÑ Ð¿ÐµÑвинноÑ
мови ÑозÑиÑенÑ. Ðи можеÑе "
@@ -1153,16 +1308,25 @@
"translations.html\">“ÐоÑÑÐ±Ð½Ð¸ÐºÑ Ð·
пеÑекладє</a>."
#. type: Content of: <div><p>
-msgid "Copyright © 2003, 2007, 2013, 2014 Free Software Foundation, Inc."
+#, fuzzy
+#| msgid ""
+#| "Copyright © 2003, 2007, 2013, 2014 Free Software Foundation, Inc."
+msgid ""
+"Copyright © 2003, 2007, 2013, 2014, 2020 Free Software Foundation, Inc."
msgstr ""
"Copyright © 2003, 2007, 2013, 2014 Фонд вÑлÑного
пÑогÑамного "
"забезпеÑеннÑ, Inc."
#. type: Content of: <div><p>
+#, fuzzy
+#| 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>."
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>."
+"creativecommons.org/licenses/by-nd/4.0/\">Creative Commons Attribution-"
+"NoDerivatives 4.0 International License</a>."
msgstr ""
"Ð¦Ñ ÑÑоÑÑнка доÑÑÑпна на ÑмоваÑ
<a rel=\"license\"
href=\"http://";
"creativecommons.org/licenses/by-nd/3.0/us/deed.uk\"> лÑÑензÑÑ
Creative "
Index: gnu/po/rms-lisp.zh-cn.po
===================================================================
RCS file: /web/www/www/gnu/po/rms-lisp.zh-cn.po,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- gnu/po/rms-lisp.zh-cn.po 5 Aug 2018 13:29:13 -0000 1.4
+++ gnu/po/rms-lisp.zh-cn.po 1 Jul 2020 14:31:22 -0000 1.5
@@ -6,7 +6,7 @@
msgid ""
msgstr ""
"Project-Id-Version: rms-lisp.html\n"
-"POT-Creation-Date: 2014-04-04 23:59+0000\n"
+"POT-Creation-Date: 2020-07-01 14:25+0000\n"
"PO-Revision-Date: 2018-08-05 20:17+0800\n"
"Last-Translator: Wensheng Xie <wxie@member.fsf.org>\n"
"Language-Team: Chinese <www-zh-cn-translators@gnu.org>\n"
@@ -14,6 +14,7 @@
"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"
#. type: Content of: <title>
msgid ""
@@ -116,19 +117,32 @@
"Emacsçè¯ç并使ä¹åå±ã"
#. type: Content of: <p>
+#, fuzzy
+#| msgid ""
+#| "The original Emacs did not have Lisp in it. The lower level language, the "
+#| "non-interpreted language — 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 ‘5l’, meaning ‘move "
+#| "five lines’, or ‘i’ 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 — 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 ‘5l’, meaning ‘move five "
-"lines’, or ‘i’ 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."
+"non-interpreted language — was PDP-10 Assembler. The interpreter we "
+"wrote in that actually wasn't written for Emacs, it was written for <abbr "
+"title=\"Text Editor and 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 "
+"‘5l’, meaning ‘move five lines’, or ‘i’ "
+"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."
msgstr ""
"æåçEmacsä¸å¸¦Lispãå
¶åºå±è¯è¨ãä¸ä¸ªé解éæ§è¯è¨—æ¯<abbr>PDP</abbr>-10"
"æ±ç¼è¯è¨ãæ们ç¼åç解éå¨å®é
ä¸ä¸æ¯ä¸ºEmacsåçï¼å®æ¯ä¸º<acronym title=\"Text "
@@ -140,6 +154,19 @@
"å°¾ï¼è¿æ ·è¯¥ä¸²å½ä»¤å°±æ§è¡äºã"
#. type: Content of: <p>
+#, 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 < >. 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, "
@@ -150,7 +177,7 @@
"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>."
+"got its unwind-protect facility from TECO."
msgstr ""
"ä¸è¿ï¼äººä»¬æ³è¦æ©å±è¯¥è¯è¨ä½¿ä¹å¸¦ä¸ç¼ç¨è½åï¼æ以人们就添å
äºä¸äºåè½ãä¾å¦ï¼æ"
"æ©æ·»å çå°±æ循ç¯ç»æï¼å°±æ¯< >ãä½
æä¸è¥¿æ¾å¨è¿ä¸¤ä¸ªç¬¦å·ä¹é´ï¼å®ä»¬å°±å¾ªç¯"
@@ -161,15 +188,26 @@
"å°±æ¥èª<acronym>TECO</acronym>ã"
#. type: Content of: <p>
+#, fuzzy
+#| msgid ""
+#| "We started putting in rather sophisticated facilities, all with the "
+#| "ugliest syntax you could ever think of, and it worked — 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 — 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."
+"like 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."
msgstr ""
"æ们å¼å§æ·»å
ä¸äºç¸å½å¤æçåè½ï¼é½æ¯ç¨æ们æç¥çé£ä¸ªæä¸éçè¯æ³å®æçï¼èå®"
"æ¯å¯è¡ç—人们ç»ç©¶è½å¤ä½¿ç¨å®æ¥å®æ大åç¨åºãè¿éï¼ææ¾çæè®å°±æ¯ä½¿ç¨è¯¸å¦"
@@ -215,6 +253,32 @@
"çæ¶åï¼ç´å°ä»ä»¬æåæ为ç¨åºåã"
#. type: Content of: <p>
+#, 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 "
+#| "— it was a full-fledged Lisp system — 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 — 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. "
@@ -229,13 +293,12 @@
"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 "
+"machine language, making them into TECO primitives. For instance, there was "
+"a 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 TECO program). You could do the "
+"whole job by writing a 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."
@@ -272,19 +335,33 @@
"ç¼åãæå
¥èµ·å§ææ¬ã读åæ件ãå·æ°å±å¹æ¾ç¤ºä»¥å管çç¼è¾çªå£ã"
#. type: Content of: <p>
+#, 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 — 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 “you had to send back "
+#| "all of your improvements” 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 "
"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 — 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 “you had to send back all of your "
-"improvements” so we could all benefit. No one ever tried to enforce "
-"that, but as far as I know people did cooperate."
+"Emacs. I first released the original Emacs to people at MIT. Someone wanted "
+"to port it to run on Twenex — it originally only ran on the "
+"Incompatible Timesharing System we used at 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 “you had to send back all of your improvements” so we "
+"could all benefit. No one ever tried to enforce that, but as far as I know "
+"people did cooperate."
msgstr ""
"å½æ¶ï¼å®ä¸åæ¯ç¬¬ä¸ä¸ªç¨Cç¼å并è¿è¡å¨Unixä¸çEmacsäºã第ä¸ä¸ªæ¯ç±James
Goslingå®"
"æçï¼å°±æ¯GosMacsãä»æäºå¥æªãä¸å¼å§ï¼ä»çæ¥è¿æ¯åå°äºåå§Emacsçåä½åå享"
@@ -358,16 +435,27 @@
"ç°å¨ä½ å¨æ¾ç¤ºå·æ°æ¶ä¹å¯ä»¥è¿è¡Lisp代ç
ãè¿æ¯ä¸ä»¶å¾ä¾¿å©çäºã"
#. type: Content of: <p>
+#, fuzzy
+#| msgid ""
+#| "This second Emacs program was ‘free software’ in the modern "
+#| "sense of the term — 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 — "
+#| "the experience I had, the life that I've lived at the <abbr>MIT</abbr> AI "
+#| "lab — 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 ‘free software’ in the modern "
"sense of the term — 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 — the experience I had, "
-"the life that I've lived at the <abbr>MIT</abbr> AI lab — to be "
-"working on human knowledge, and not be standing in the way of anybody's "
-"further using and further disseminating human knowledge."
+"be free to do the things we did in the old days at MIT>, working together on "
+"software and working with whomever wanted to work with us. That is the "
+"basis for the free software movement — the experience I had, the life "
+"that I've lived at the MIT AI lab — to be working on human knowledge, "
+"and not be standing in the way of anybody's further using and further "
+"disseminating human knowledge."
msgstr ""
"è¿ä¸ªç¬¬äºççEmacs毑èªç±è½¯ä»¶’以该è¯æ±çå½ä»æä¹æ¥è¯´—å®æ¯å"
"äºè½¯ä»¶èªç±çæ¿æ²»è¿å¨çä¸é¨åã该è¿å¨çç²¾é«å°±æ¯æ¯ä¸ªäººé½åºè¯¥æèªç±åæ们å¨"
@@ -485,19 +573,33 @@
"çµèå
¬å¸ãå½Symbolicsçå°LMIä¸æ¯èµ°å失败æ¶ï¼ä»ä»¬å¼å§å¯»æºæç
´åã"
#. type: Content of: <p>
+#, fuzzy
+#| msgid ""
+#| "Thus, the abandonment of our lab was followed by “war” 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 “war” 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."
+"and eliminated people who worked part-time for MIT, so they had to leave "
+"entirely, which left only me. The AI lab was now helpless. And 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 MIT use their changes. But it "
+"didn't say in the contract that MIT was entitled to put them into the 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."
msgstr ""
"å
æ¤ï¼å®éªå®¤ç被离å¼æ¥çæ¯å®éªå®¤ç“æ五ã离å¼æ¯å
为Symbolicsæèµ°"
"äºå®éªå®¤çææé»å®¢ï¼åªå©ä¸æåå 个å¨LMIå
¼èç人ãç¶åï¼ä»ä»¬åæ´å¼æ¡ä¾æå¨"
@@ -509,12 +611,19 @@
"ç»ä¼è¢«å½»åºæ¯çï¼ä½æ¯å®å°±æ¯è¢«æ¯çäºã"
#. type: Content of: <p>
+#, fuzzy
+#| msgid ""
+#| "So Symbolics came up with a plan <a href=\"#foot-4\">(4)</a>. They said "
+#| "to the lab, “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.”"
msgid ""
"So Symbolics came up with a plan <a href=\"#foot-4\">(4)</a>. They said to "
"the lab, “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.”"
+"for you to use, but you can't put it into the 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.”"
msgstr ""
"äºæ¯ï¼Symbolicså¯å¨äºä¸ä¸ªè®¡å<a
href=\"#foot-4\">(4)</a>ãä»ä»¬å¯¹å®éªå®¤è¯´ï¼"
"“æ们ä¼æç»è®©ä½ 们使ç¨æ们çç³»ç»æ¹è¿ï¼ä½æ¯ä½
们ä¸è½æè¿äºæ¹è¿è£
å°"
@@ -522,15 +631,26 @@
"ç»ï¼ä½ 们å¯ä»¥å¨è¿äºç³»ç»ä¸è¿è¡æ¹è¿çï¼ä½æ¯ä»
æ¤èå·²ã”"
#. type: Content of: <p>
+#, 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 <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."
+"use either the 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 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."
msgstr ""
"è¿å®é
ä¸æ¯è¦æ±æ们åªè½éæ©ä¸è¾¹ï¼è¦ä¹ä½¿ç¨<abbr>MIT</abbr>çç³»ç»çæ¬ï¼è¦ä¹ä½¿ç¨"
"Symbolicsççæ¬ãæ们éæ©åªä¸è¾¹ï¼å°±å³å®äºæ们çç³»ç»æ¹è¿ä¼è¿å
¥å°åªä¸è¾¹ãå¦ææ"
@@ -582,12 +702,19 @@
"ç社åºäºã"
#. type: Content of: <p>
-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."
+#, 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 "
+"out 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."
msgstr ""
"70年代çLisp社åºä¸éäº<abbr>MIT</abbr>人工æºè½å®éªå®¤ï¼å¹¶ä¸æ¯ææçé»å®¢é½å¨"
"<abbr>MIT</abbr>ãSymbolicsåèµ·çæäºæ¯çäº<abbr>MIT</abbr>社åºï¼ä½æ¯åæ¶è¿æ"
@@ -694,20 +821,34 @@
"çç¼è¾å¨ä¸æ ·ãé®é¢å¨äºè¿åºè¯¥æ¯ä¸ä¸ªä»ä¹è¯è¨ã"
#. type: Content of: <p>
-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 “de-facto standard extension "
-"language” of the world. And I thought, “We've got to stop that "
-"from happening.” 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."
+#, 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 “de-facto standard extension "
+#| "language” of the world. And I thought, “We've got to stop "
+#| "that from happening.” 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 "
+"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 TCL to make it the “de-facto "
+"standard extension language” of the world. And I thought, “We've "
+"got to stop that from happening.” 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 TCL was linked into applications. "
+"We would then recommend that as the preferred extensibility package for all "
+"GNU programs."
msgstr ""
"æ¤æ¶ï¼<acronym title=\"Tool Command
Language\">TCL</acronym>ä½ä¸ºåéè¯è¨çå¼"
"声å¾é«ãæé常çä¸ä¸<acronym>TCL</acronym>ï¼åºæ¬ä¸å
为å®ä¸æ¯Lispè¯è¨ãå®ç¨ç¨"
@@ -719,18 +860,32 @@
"æ¯ææGNUç¨åºé¦éçæ©å±å
ã"
#. type: Content of: <p>
+#, 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 "
"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."
+"language. If your primary language is TCL, you can't very easily implement "
+"Lisp by translating it into 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 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."
msgstr ""
"使ç¨è¿ä¸ªå¼ºå¤§çLispåæ¯è¯è¨ä½ä¸ºåºæ¬æ©å±è¯è¨ä¼ç»ä½
带æ¥ä¸ä¸ªæ趣ç好å¤ãä½ å°è½å¤"
"æå
¶ä»è¯è¨ç¿»è¯æåºæ¬æ©å±è¯è¨æ¥å®ç°å
¶ä»è¯è¨ãå¦æä½
çåºæ¬è¯è¨æ¯<acronym>TCL</"
@@ -981,18 +1136,27 @@
"ç¿»è¯é¡»ç¥</a>ã"
#. type: Content of: <div><p>
-msgid "Copyright © 2003, 2007, 2013, 2014 Free Software Foundation, Inc."
+#, fuzzy
+#| msgid ""
+#| "Copyright © 2003, 2007, 2013, 2014 Free Software Foundation, Inc."
+msgid ""
+"Copyright © 2003, 2007, 2013, 2014, 2020 Free Software Foundation, Inc."
msgstr "Copyright © 2003, 2007, 2013, 2014 Free Software Foundation, Inc."
#. type: Content of: <div><p>
+#, fuzzy
+#| 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>."
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>."
+"creativecommons.org/licenses/by-nd/4.0/\">Creative Commons Attribution-"
+"NoDerivatives 4.0 International License</a>."
msgstr ""
-"æ¬é¡µé¢ä½¿ç¨<a rel=\"license\"
href=\"http://creativecommons.org/licenses/by-";
+"æ¬é¡µé¢éç¨ <a rel=\"license\"
href=\"http://creativecommons.org/licenses/by-";
"nd/3.0/us/\">Creative Commons Attribution-NoDerivs 3.0 United States "
-"License</a>ææã"
+"License</a> 许å¯è¯ææã"
#. TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.
#. type: Content of: <div><div>
@@ -1007,3 +1171,12 @@
#. type: Content of: <div><p>
msgid "Updated:"
msgstr "æåæ´æ°ï¼"
+
+#~ 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 ""
+#~ "æ¬é¡µé¢ä½¿ç¨<a rel=\"license\"
href=\"http://creativecommons.org/licenses/";
+#~ "by-nd/3.0/us/\">Creative Commons Attribution-NoDerivs 3.0 United States "
+#~ "License</a>ææã"
Index: philosophy/po/15-years-of-free-software.ar.po
===================================================================
RCS file: /web/www/www/philosophy/po/15-years-of-free-software.ar.po,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -b -r1.27 -r1.28
--- philosophy/po/15-years-of-free-software.ar.po 10 Dec 2014 15:28:07
-0000 1.27
+++ philosophy/po/15-years-of-free-software.ar.po 1 Jul 2020 14:31:22
-0000 1.28
@@ -9,7 +9,7 @@
msgstr ""
"Project-Id-Version: 15-years-of-free-software.html\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2014-04-05 15:25+0000\n"
+"POT-Creation-Date: 2020-07-01 14:25+0000\n"
"PO-Revision-Date: 2014-12-09 19:15+0100\n"
"Last-Translator: faycal <faycal_alami@hotmail.com>\n"
"Language-Team: Arabic\n"
@@ -17,6 +17,7 @@
"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"
"Plural-Forms: nplurals=6; plural=n==0 ? 0 : n==1 ? 1 : n==2 ? 2 : n%100>=3 "
"&& n%100<=10 ? 3 : n%100>=11 && n%100<=99 ? 4 : 5;\n"
"X-Generator: Lokalize 1.0\n"
@@ -114,14 +115,31 @@
# type: Content of: <p>
#. type: Content of: <p>
+# | In 1991, the last major essential component of a Unix-like system was
+# | developed: Linux, the free kernel written by Linus Torvalds. Today, the
+# | combination of GNU and Linux is used by millions of people around the
+# | world, and its popularity is growing. This month, we announced release 1.0
+# | of [-<acronym-] {+<abbr+} title=\"GNU Network Object Model
+# | [-Environment\">GNOME</acronym>,-] {+Environment\">GNOME</abbr>,+} the GNU
+# | graphical desktop, which we hope will make the GNU/Linux system as easy to
+# | use as any other operating system.
+#, fuzzy
+#| msgid ""
+#| "In 1991, the last major essential component of a Unix-like system was "
+#| "developed: Linux, the free kernel written by Linus Torvalds. Today, the "
+#| "combination of GNU and Linux is used by millions of people around the "
+#| "world, and its popularity is growing. This month, we announced release "
+#| "1.0 of <acronym title=\"GNU Network Object Model Environment\">GNOME</"
+#| "acronym>, the GNU graphical desktop, which we hope will make the GNU/"
+#| "Linux system as easy to use as any other operating system."
msgid ""
"In 1991, the last major essential component of a Unix-like system was "
"developed: Linux, the free kernel written by Linus Torvalds. Today, the "
"combination of GNU and Linux is used by millions of people around the world, "
-"and its popularity is growing. This month, we announced release 1.0 of "
-"<acronym title=\"GNU Network Object Model Environment\">GNOME</acronym>, the "
-"GNU graphical desktop, which we hope will make the GNU/Linux system as easy "
-"to use as any other operating system."
+"and its popularity is growing. This month, we announced release 1.0 of <abbr "
+"title=\"GNU Network Object Model Environment\">GNOME</abbr>, the GNU "
+"graphical desktop, which we hope will make the GNU/Linux system as easy to "
+"use as any other operating system."
msgstr ""
"Ù٠عاÙ
1991Ø ØªÙ
تطÙÙر آخر اÙعÙاصر اÙأساسÙØ©
ÙÙظاÙ
شبÙ٠بÙÙÙÙس: ÙÙÙÙØ³Ø Ø§ÙÙÙاة "
"اÙØرÙØ© اÙت٠ÙتبÙا ÙÙÙÙس تÙرÙاÙدس. Ùذا
اÙÙظاÙ
اÙÙ
ÙرÙب Ù
٠غÙÙ ÙÙÙÙÙس ÙÙستخدÙÙ
"
@@ -206,14 +224,27 @@
"href=\"/server/standards/README.translations.html\">دÙÙ٠اÙترجÙ
Ø©</a>."
#. type: Content of: <div><p>
-msgid "Copyright © 1999, 2014 Richard M. Stallman"
+# | Copyright © 1999, [-2014-] {+2014, 2020+} Richard M. Stallman
+#, fuzzy
+#| msgid "Copyright © 1999, 2014 Richard M. Stallman"
+msgid "Copyright © 1999, 2014, 2020 Richard M. Stallman"
msgstr "Copyright © 1999, 2014 Richard M. Stallman"
#. type: Content of: <div><p>
+# | This page is licensed under a <a rel=\"license\"
+# | [-href=\"http://creativecommons.org/licenses/by-nd/3.0/us/\";>Creative-]
+# | {+href=\"http://creativecommons.org/licenses/by-nd/4.0/\";>Creative+}
+# | Commons [-Attribution-NoDerivs 3.0 United States-]
+# | {+Attribution-NoDerivatives 4.0 International+} License</a>.
+#, fuzzy
+#| 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>."
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>."
+"creativecommons.org/licenses/by-nd/4.0/\">Creative Commons Attribution-"
+"NoDerivatives 4.0 International License</a>."
msgstr ""
"Ùذا اÙÙ
ÙصÙÙÙÙ Ù
رخص بÙ
Ùجب <a rel=\"license\"
href=\"http://creativecommons.org/";
"licenses/by-nd/3.0/us/deed.ar\">رخصة اÙÙ
شاع اÙإبداع٠Ùسب
اÙÙ
صÙÙ - Ù
Ùع "
@@ -232,3 +263,12 @@
#. type: Content of: <div><p>
msgid "Updated:"
msgstr "تØدÙØ«:"
+
+#~ 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 ""
+#~ "Ùذا اÙÙ
ÙصÙÙÙÙ Ù
رخص بÙ
Ùجب <a rel=\"license\"
href=\"http://creativecommons.";
+#~ "org/licenses/by-nd/3.0/us/deed.ar\">رخصة اÙÙ
شاع اÙإبداعÙ
Ùسب اÙÙ
صÙÙ - Ù
Ùع "
+#~ "اÙاشتÙا٠3.0 اÙÙÙاÙات اÙÙ
تØدة</a>."
Index: philosophy/po/15-years-of-free-software.de.po
===================================================================
RCS file: /web/www/www/philosophy/po/15-years-of-free-software.de.po,v
retrieving revision 1.35
retrieving revision 1.36
diff -u -b -r1.35 -r1.36
--- philosophy/po/15-years-of-free-software.de.po 3 Dec 2016 23:45:11
-0000 1.35
+++ philosophy/po/15-years-of-free-software.de.po 1 Jul 2020 14:31:22
-0000 1.36
@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 15-years-of-free-software.html\n"
-"POT-Creation-Date: 2014-04-05 15:25+0000\n"
+"POT-Creation-Date: 2020-07-01 14:25+0000\n"
"PO-Revision-Date: 2014-04-18 02:20+0200\n"
"Last-Translator: Joerg Kohne <joeko (AT) online [PUNKT] de>\n"
"Language-Team: German <www-de-translators@gnu.org>\n"
@@ -15,6 +15,7 @@
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"X-Outdated-Since: 2020-07-01 14:25+0000\n"
#. type: Content of: <title>
msgid "15 Years of Free Software - GNU Project - Free Software Foundation"
@@ -106,14 +107,31 @@
"die gesamte Menschheit zu befreien."
#. type: Content of: <p>
+# | In 1991, the last major essential component of a Unix-like system was
+# | developed: Linux, the free kernel written by Linus Torvalds. Today, the
+# | combination of GNU and Linux is used by millions of people around the
+# | world, and its popularity is growing. This month, we announced release 1.0
+# | of [-<acronym-] {+<abbr+} title=\"GNU Network Object Model
+# | [-Environment\">GNOME</acronym>,-] {+Environment\">GNOME</abbr>,+} the GNU
+# | graphical desktop, which we hope will make the GNU/Linux system as easy to
+# | use as any other operating system.
+#, fuzzy
+#| msgid ""
+#| "In 1991, the last major essential component of a Unix-like system was "
+#| "developed: Linux, the free kernel written by Linus Torvalds. Today, the "
+#| "combination of GNU and Linux is used by millions of people around the "
+#| "world, and its popularity is growing. This month, we announced release "
+#| "1.0 of <acronym title=\"GNU Network Object Model Environment\">GNOME</"
+#| "acronym>, the GNU graphical desktop, which we hope will make the GNU/"
+#| "Linux system as easy to use as any other operating system."
msgid ""
"In 1991, the last major essential component of a Unix-like system was "
"developed: Linux, the free kernel written by Linus Torvalds. Today, the "
"combination of GNU and Linux is used by millions of people around the world, "
-"and its popularity is growing. This month, we announced release 1.0 of "
-"<acronym title=\"GNU Network Object Model Environment\">GNOME</acronym>, the "
-"GNU graphical desktop, which we hope will make the GNU/Linux system as easy "
-"to use as any other operating system."
+"and its popularity is growing. This month, we announced release 1.0 of <abbr "
+"title=\"GNU Network Object Model Environment\">GNOME</abbr>, the GNU "
+"graphical desktop, which we hope will make the GNU/Linux system as easy to "
+"use as any other operating system."
msgstr ""
"Im Jahr 1991 wurde die letzte groÃe wesentliche Komponente eines unixartigen
"
"Systems entwickelt: Linux, der von Linus Torvalds geschriebene freie "
@@ -204,19 +222,27 @@
"standards/README.translations\">LIESMICH für Ãbersetzungen</a>."
#. type: Content of: <div><p>
-msgid "Copyright © 1999, 2014 Richard M. Stallman"
+# | Copyright © 1999, [-2014-] {+2014, 2020+} Richard M. Stallman
+#, fuzzy
+#| msgid "Copyright © 1999, 2014 Richard M. Stallman"
+msgid "Copyright © 1999, 2014, 2020 Richard M. Stallman"
msgstr "Copyright © 1999, 2014 Richard M. Stallman."
#. type: Content of: <div><p>
+# || No change detected. The change might only be in amounts of spaces.
+#, fuzzy
+#| msgid ""
+#| "This page is licensed under a <a rel=\"license\" href=\"http://";
+#| "creativecommons.org/licenses/by-nd/4.0/\">Creative Commons Attribution-"
+#| "NoDerivatives 4.0 International License</a>."
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>."
+"creativecommons.org/licenses/by-nd/4.0/\">Creative Commons Attribution-"
+"NoDerivatives 4.0 International License</a>."
msgstr ""
-"Dieses Werk steht unter einer <a rel=\"license\" href=\"http://";
-"creativecommons.org/licenses/by-nd/3.0/us/deed.de\">Creative Commons "
-"Namensnennung-Keine Bearbeitung 3.0 Vereinigte Staaten von Amerika Lizenz</"
-"a>."
+"Dieses Werk ist lizenziert unter einer <a rel=\"license\" href=\"//"
+"creativecommons.org/licenses/by-nd/4.0/deed.de\">Creative Commons "
+"Namensnennung-Keine Bearbeitungen 4.0 International</a>-Lizenz."
#. TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.
#. type: Content of: <div><div>
@@ -231,6 +257,16 @@
msgid "Updated:"
msgstr "Letzte Ãnderung:"
+#~ 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 ""
+#~ "Dieses Werk steht unter einer <a rel=\"license\" href=\"http://";
+#~ "creativecommons.org/licenses/by-nd/3.0/us/deed.de\">Creative Commons "
+#~ "Namensnennung-Keine Bearbeitung 3.0 Vereinigte Staaten von Amerika "
+#~ "Lizenz</a>."
+
#~ msgid "Copyright © 1999 Richard M. Stallman"
#~ msgstr "Copyright © 1999 Richard M. Stallman."
Index: philosophy/po/15-years-of-free-software.es.po
===================================================================
RCS file: /web/www/www/philosophy/po/15-years-of-free-software.es.po,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -b -r1.28 -r1.29
--- philosophy/po/15-years-of-free-software.es.po 15 Sep 2019 21:06:04
-0000 1.28
+++ philosophy/po/15-years-of-free-software.es.po 1 Jul 2020 14:31:22
-0000 1.29
@@ -9,7 +9,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 15-years-of-free-software.html\n"
-"POT-Creation-Date: 2014-04-05 15:25+0000\n"
+"POT-Creation-Date: 2020-07-01 14:25+0000\n"
"PO-Revision-Date: 2015-11-30 15:03+0100\n"
"Last-Translator: Dora Scilipoti <dora AT gnu DOT org>\n"
"Language-Team: Spanish <www-es-general@gnu.org>\n"
@@ -17,6 +17,7 @@
"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-Poedit-Language: Spanish\n"
# type: Content of: <title>
@@ -122,14 +123,31 @@
# type: Content of: <p>
#. type: Content of: <p>
+# | In 1991, the last major essential component of a Unix-like system was
+# | developed: Linux, the free kernel written by Linus Torvalds. Today, the
+# | combination of GNU and Linux is used by millions of people around the
+# | world, and its popularity is growing. This month, we announced release 1.0
+# | of [-<acronym-] {+<abbr+} title=\"GNU Network Object Model
+# | [-Environment\">GNOME</acronym>,-] {+Environment\">GNOME</abbr>,+} the GNU
+# | graphical desktop, which we hope will make the GNU/Linux system as easy to
+# | use as any other operating system.
+#, fuzzy
+#| msgid ""
+#| "In 1991, the last major essential component of a Unix-like system was "
+#| "developed: Linux, the free kernel written by Linus Torvalds. Today, the "
+#| "combination of GNU and Linux is used by millions of people around the "
+#| "world, and its popularity is growing. This month, we announced release "
+#| "1.0 of <acronym title=\"GNU Network Object Model Environment\">GNOME</"
+#| "acronym>, the GNU graphical desktop, which we hope will make the GNU/"
+#| "Linux system as easy to use as any other operating system."
msgid ""
"In 1991, the last major essential component of a Unix-like system was "
"developed: Linux, the free kernel written by Linus Torvalds. Today, the "
"combination of GNU and Linux is used by millions of people around the world, "
-"and its popularity is growing. This month, we announced release 1.0 of "
-"<acronym title=\"GNU Network Object Model Environment\">GNOME</acronym>, the "
-"GNU graphical desktop, which we hope will make the GNU/Linux system as easy "
-"to use as any other operating system."
+"and its popularity is growing. This month, we announced release 1.0 of <abbr "
+"title=\"GNU Network Object Model Environment\">GNOME</abbr>, the GNU "
+"graphical desktop, which we hope will make the GNU/Linux system as easy to "
+"use as any other operating system."
msgstr ""
"En 1991 se desarrolló el último de los componentes esenciales de todo "
"sistema de tipo Unix, el kernel libro escrito por Linus Torvalds. Hoy en "
@@ -225,18 +243,21 @@
"coordinación y el envÃo de traducciones de las páginas de este sitio web."
#. type: Content of: <div><p>
-msgid "Copyright © 1999, 2014 Richard M. Stallman"
+# | Copyright © 1999, [-2014-] {+2014, 2020+} Richard M. Stallman
+#, fuzzy
+#| msgid "Copyright © 1999, 2014 Richard M. Stallman"
+msgid "Copyright © 1999, 2014, 2020 Richard M. Stallman"
msgstr "Copyright © 1999, 2014 Richard M. Stallman"
#. 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>."
+"creativecommons.org/licenses/by-nd/4.0/\">Creative Commons Attribution-"
+"NoDerivatives 4.0 International 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>."
+"creativecommons.org/licenses/by-nd/4.0/deed.es_ES\">Creative Commons "
+"Reconocimiento-SinObraDerivada 4.0 Internacional</a>."
# type: Content of: <div><div>
#. TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.
Index: philosophy/po/15-years-of-free-software.fr.po
===================================================================
RCS file: /web/www/www/philosophy/po/15-years-of-free-software.fr.po,v
retrieving revision 1.39
retrieving revision 1.40
diff -u -b -r1.39 -r1.40
--- philosophy/po/15-years-of-free-software.fr.po 3 Feb 2017 14:08:46
-0000 1.39
+++ philosophy/po/15-years-of-free-software.fr.po 1 Jul 2020 14:31:22
-0000 1.40
@@ -8,7 +8,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 15-years-of-free-software.html\n"
-"POT-Creation-Date: 2014-04-05 15:25+0000\n"
+"POT-Creation-Date: 2020-07-01 14:25+0000\n"
"PO-Revision-Date: 2017-02-03 14:56+0100\n"
"Last-Translator: Thérèse Godefroy <godef.th AT free.fr>\n"
"Language-Team: French <trad-gnu@april.org>\n"
@@ -16,6 +16,7 @@
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"X-Outdated-Since: 2020-07-01 14:25+0000\n"
"Plural-Forms: \n"
#. type: Content of: <title>
@@ -110,14 +111,31 @@
"libérer le potentiel du réseau informatique pour toute l'humanité."
#. type: Content of: <p>
+# | In 1991, the last major essential component of a Unix-like system was
+# | developed: Linux, the free kernel written by Linus Torvalds. Today, the
+# | combination of GNU and Linux is used by millions of people around the
+# | world, and its popularity is growing. This month, we announced release 1.0
+# | of [-<acronym-] {+<abbr+} title=\"GNU Network Object Model
+# | [-Environment\">GNOME</acronym>,-] {+Environment\">GNOME</abbr>,+} the GNU
+# | graphical desktop, which we hope will make the GNU/Linux system as easy to
+# | use as any other operating system.
+#, fuzzy
+#| msgid ""
+#| "In 1991, the last major essential component of a Unix-like system was "
+#| "developed: Linux, the free kernel written by Linus Torvalds. Today, the "
+#| "combination of GNU and Linux is used by millions of people around the "
+#| "world, and its popularity is growing. This month, we announced release "
+#| "1.0 of <acronym title=\"GNU Network Object Model Environment\">GNOME</"
+#| "acronym>, the GNU graphical desktop, which we hope will make the GNU/"
+#| "Linux system as easy to use as any other operating system."
msgid ""
"In 1991, the last major essential component of a Unix-like system was "
"developed: Linux, the free kernel written by Linus Torvalds. Today, the "
"combination of GNU and Linux is used by millions of people around the world, "
-"and its popularity is growing. This month, we announced release 1.0 of "
-"<acronym title=\"GNU Network Object Model Environment\">GNOME</acronym>, the "
-"GNU graphical desktop, which we hope will make the GNU/Linux system as easy "
-"to use as any other operating system."
+"and its popularity is growing. This month, we announced release 1.0 of <abbr "
+"title=\"GNU Network Object Model Environment\">GNOME</abbr>, the GNU "
+"graphical desktop, which we hope will make the GNU/Linux system as easy to "
+"use as any other operating system."
msgstr ""
"En 1991, le dernier élément essentiel à un système de type Unix a été "
"développé : Linux, le noyau libre écrit par Linus Torvalds. Aujourd'hui,
la "
@@ -204,19 +222,22 @@
"README.translations.html\">guide de traduction</a>."
#. type: Content of: <div><p>
-msgid "Copyright © 1999, 2014 Richard M. Stallman"
+# | Copyright © 1999, [-2014-] {+2014, 2020+} Richard M. Stallman
+#, fuzzy
+#| msgid "Copyright © 1999, 2014 Richard M. Stallman"
+msgid "Copyright © 1999, 2014, 2020 Richard M. Stallman"
msgstr "Copyright © 1999, 2014 Richard M. Stallman"
#. 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>."
+"creativecommons.org/licenses/by-nd/4.0/\">Creative Commons Attribution-"
+"NoDerivatives 4.0 International License</a>."
msgstr ""
"Cette page peut être utilisée suivant les conditions de la licence <a rel="
-"\"license\" href=\"http://creativecommons.org/licenses/by-nd/3.0/us/deed.fr";
-"\">Creative Commons attribution de paternité, pas de modification, 3.0Â
Ãtats-"
-"Unis (CCÂ BY-ND 3.0Â US)</a>."
+"\"license\" href=\"http://creativecommons.org/licenses/by-nd/4.0/deed.fr";
+"\">Creative Commons attribution, pas de modification, 4.0Â internationale "
+"(CCÂ BY-ND 4.0)</a>."
#. TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.
#. type: Content of: <div><div>
Index: philosophy/po/15-years-of-free-software.hr.po
===================================================================
RCS file: /web/www/www/philosophy/po/15-years-of-free-software.hr.po,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -b -r1.5 -r1.6
--- philosophy/po/15-years-of-free-software.hr.po 14 Apr 2017 14:53:12
-0000 1.5
+++ philosophy/po/15-years-of-free-software.hr.po 1 Jul 2020 14:31:22
-0000 1.6
@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 15-years-of-free-software.html\n"
-"POT-Creation-Date: 2014-04-05 15:25+0000\n"
+"POT-Creation-Date: 2020-07-01 14:25+0000\n"
"PO-Revision-Date: 2013-05-30 21:54+0100\n"
"Last-Translator: Martina Bebek <martinaporec@gmail.com>\n"
"Language-Team: www-hr <www-hr-lista@gnu.org>\n"
@@ -15,6 +15,7 @@
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"X-Outdated-Since: 2020-07-01 14:25+0000\n"
"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
"X-Generator: Poedit 1.5.4\n"
@@ -110,14 +111,31 @@
"osloboditi potencijal raÄunalne mreže za cijelo ÄovjeÄanstvo."
#. type: Content of: <p>
+# | In 1991, the last major essential component of a Unix-like system was
+# | developed: Linux, the free kernel written by Linus Torvalds. Today, the
+# | combination of GNU and Linux is used by millions of people around the
+# | world, and its popularity is growing. This month, we announced release 1.0
+# | of [-<acronym-] {+<abbr+} title=\"GNU Network Object Model
+# | [-Environment\">GNOME</acronym>,-] {+Environment\">GNOME</abbr>,+} the GNU
+# | graphical desktop, which we hope will make the GNU/Linux system as easy to
+# | use as any other operating system.
+#, fuzzy
+#| msgid ""
+#| "In 1991, the last major essential component of a Unix-like system was "
+#| "developed: Linux, the free kernel written by Linus Torvalds. Today, the "
+#| "combination of GNU and Linux is used by millions of people around the "
+#| "world, and its popularity is growing. This month, we announced release "
+#| "1.0 of <acronym title=\"GNU Network Object Model Environment\">GNOME</"
+#| "acronym>, the GNU graphical desktop, which we hope will make the GNU/"
+#| "Linux system as easy to use as any other operating system."
msgid ""
"In 1991, the last major essential component of a Unix-like system was "
"developed: Linux, the free kernel written by Linus Torvalds. Today, the "
"combination of GNU and Linux is used by millions of people around the world, "
-"and its popularity is growing. This month, we announced release 1.0 of "
-"<acronym title=\"GNU Network Object Model Environment\">GNOME</acronym>, the "
-"GNU graphical desktop, which we hope will make the GNU/Linux system as easy "
-"to use as any other operating system."
+"and its popularity is growing. This month, we announced release 1.0 of <abbr "
+"title=\"GNU Network Object Model Environment\">GNOME</abbr>, the GNU "
+"graphical desktop, which we hope will make the GNU/Linux system as easy to "
+"use as any other operating system."
msgstr ""
"Godine 1991. razvijena je i posljednja kljuÄna komponenta sustava nalik "
"Unixu, slobodna jezgra, koju je napisao Linus Torvalds. Danas kombinaciju "
@@ -204,18 +222,31 @@
"prijevode</a>."
#. type: Content of: <div><p>
-msgid "Copyright © 1999, 2014 Richard M. Stallman"
+# | Copyright © 1999, [-2014-] {+2014, 2020+} Richard M. Stallman
+#, fuzzy
+#| msgid "Copyright © 1999, 2014 Richard M. Stallman"
+msgid "Copyright © 1999, 2014, 2020 Richard M. Stallman"
msgstr "Copyright © 1999, 2014 Richard M. Stallman"
#. type: Content of: <div><p>
+# | This page is licensed under a <a rel=\"license\"
+# | [-href=\"http://creativecommons.org/licenses/by-nd/3.0/us/\";>Creative-]
+# | {+href=\"http://creativecommons.org/licenses/by-nd/4.0/\";>Creative+}
+# | Commons [-Attribution-NoDerivs 3.0 United States-]
+# | {+Attribution-NoDerivatives 4.0 International+} License</a>.
+#, fuzzy
+#| 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>."
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>."
+"creativecommons.org/licenses/by-nd/4.0/\">Creative Commons Attribution-"
+"NoDerivatives 4.0 International License</a>."
msgstr ""
-"Ovo djelo dano je na korištenje pod <a rel=\"license\" href=\"http://";
-"creativecommons.org/licenses/by-nd/3.0/us/deed.hr\"> Creative Commons "
-"Imenovanje-Bez prerada 3.0 SAD licencom</a>."
+"Ovo djelo je dano na korištenje pod licencom <a rel=\"license\" href="
+"\"http://creativecommons.org/licenses/by-nd/3.0/us/deed.hr\";> Creative "
+"Commons Imenovanje-Bez prerada 3.0 SAD</a>."
#. TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.
#. type: Content of: <div><div>
@@ -226,3 +257,12 @@
#. type: Content of: <div><p>
msgid "Updated:"
msgstr "Vrijeme zadnje izmjene:"
+
+#~ 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 ""
+#~ "Ovo djelo dano je na korištenje pod <a rel=\"license\" href=\"http://";
+#~ "creativecommons.org/licenses/by-nd/3.0/us/deed.hr\"> Creative Commons "
+#~ "Imenovanje-Bez prerada 3.0 SAD licencom</a>."
Index: philosophy/po/15-years-of-free-software.ja.po
===================================================================
RCS file: /web/www/www/philosophy/po/15-years-of-free-software.ja.po,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -b -r1.10 -r1.11
--- philosophy/po/15-years-of-free-software.ja.po 3 Feb 2016 09:13:54
-0000 1.10
+++ philosophy/po/15-years-of-free-software.ja.po 1 Jul 2020 14:31:22
-0000 1.11
@@ -6,7 +6,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 15-years-of-free-software.html\n"
-"POT-Creation-Date: 2014-04-05 15:25+0000\n"
+"POT-Creation-Date: 2020-07-01 14:25+0000\n"
"PO-Revision-Date: 2014-12-16 11:19+0900\n"
"Last-Translator: NIIBE Yutaka <gniibe@fsij.org>\n"
"Language-Team: Japanese <web-translators-ja@gnu.org>\n"
@@ -14,6 +14,7 @@
"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"
#. type: Content of: <title>
msgid "15 Years of Free Software - GNU Project - Free Software Foundation"
@@ -107,14 +108,23 @@
"ããã"
#. type: Content of: <p>
+#, fuzzy
+#| msgid ""
+#| "In 1991, the last major essential component of a Unix-like system was "
+#| "developed: Linux, the free kernel written by Linus Torvalds. Today, the "
+#| "combination of GNU and Linux is used by millions of people around the "
+#| "world, and its popularity is growing. This month, we announced release "
+#| "1.0 of <acronym title=\"GNU Network Object Model Environment\">GNOME</"
+#| "acronym>, the GNU graphical desktop, which we hope will make the GNU/"
+#| "Linux system as easy to use as any other operating system."
msgid ""
"In 1991, the last major essential component of a Unix-like system was "
"developed: Linux, the free kernel written by Linus Torvalds. Today, the "
"combination of GNU and Linux is used by millions of people around the world, "
-"and its popularity is growing. This month, we announced release 1.0 of "
-"<acronym title=\"GNU Network Object Model Environment\">GNOME</acronym>, the "
-"GNU graphical desktop, which we hope will make the GNU/Linux system as easy "
-"to use as any other operating system."
+"and its popularity is growing. This month, we announced release 1.0 of <abbr "
+"title=\"GNU Network Object Model Environment\">GNOME</abbr>, the GNU "
+"graphical desktop, which we hope will make the GNU/Linux system as easy to "
+"use as any other operating system."
msgstr ""
"1991å¹´ã«ã¯ãUnixã©ã¤ã¯ãªã·ã¹ãã
ã®æå¾ã®éè¦ãªã³ã³ãã¼ãã³ããéçºããã¾ã"
"ãããªã¼ãã¹ã»ãã¼ãã«ãºã«ãã£ã¦æ¸ãããèªç±ã®ã«ã¼ãã«ãLinuxã§ããä»æ¥ãGNU"
@@ -196,17 +206,19 @@
"README.translations.html\">翻訳 README</a>ãã覧ãã ããã"
#. type: Content of: <div><p>
-msgid "Copyright © 1999, 2014 Richard M. Stallman"
+#, fuzzy
+#| msgid "Copyright © 1999, 2014 Richard M. Stallman"
+msgid "Copyright © 1999, 2014, 2020 Richard M. Stallman"
msgstr "Copyright © 1999, 2014 Richard M. Stallman"
#. 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>."
+"creativecommons.org/licenses/by-nd/4.0/\">Creative Commons Attribution-"
+"NoDerivatives 4.0 International License</a>."
msgstr ""
"ãã®ãã¼ã¸ã¯<a rel=\"license\"
href=\"http://creativecommons.org/licenses/by-";
-"nd/3.0/us/deed.ja\">Creative Commons Attribution-NoDerivs 3.0 United States "
+"nd/4.0/deed.ja\">Creative Commons Attribution-NoDerivs 4.0 International "
"License</a>ã®æ¡ä»¶ã§è¨±è«¾ããã¾ãã"
#. TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.
Index: philosophy/po/15-years-of-free-software.ko.po
===================================================================
RCS file: /web/www/www/philosophy/po/15-years-of-free-software.ko.po,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -b -r1.13 -r1.14
--- philosophy/po/15-years-of-free-software.ko.po 5 Jul 2014 04:58:42
-0000 1.13
+++ philosophy/po/15-years-of-free-software.ko.po 1 Jul 2020 14:31:22
-0000 1.14
@@ -9,7 +9,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 15-years-of-free-software.html\n"
-"POT-Creation-Date: 2014-04-05 15:25+0000\n"
+"POT-Creation-Date: 2020-07-01 14:25+0000\n"
"PO-Revision-Date: 2012-04-27 15:55+0900\n"
"Last-Translator: Chang-hun Song <chsong@gnu.org>\n"
"Language-Team: Korean <www-ko-translators@gnu.org>\n"
@@ -17,6 +17,7 @@
"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"
#. type: Content of: <title>
msgid "15 Years of Free Software - GNU Project - Free Software Foundation"
@@ -104,14 +105,31 @@
"ì¬í를 ìí´ ì»´í¨í° ë¤í¸ìí¬ì ì ì¬ì±ì í´ë°©ìí¤ë
ê²ì ëììµëë¤."
#. type: Content of: <p>
+# | In 1991, the last major essential component of a Unix-like system was
+# | developed: Linux, the free kernel written by Linus Torvalds. Today, the
+# | combination of GNU and Linux is used by millions of people around the
+# | world, and its popularity is growing. This month, we announced release 1.0
+# | of [-<acronym-] {+<abbr+} title=\"GNU Network Object Model
+# | [-Environment\">GNOME</acronym>,-] {+Environment\">GNOME</abbr>,+} the GNU
+# | graphical desktop, which we hope will make the GNU/Linux system as easy to
+# | use as any other operating system.
+#, fuzzy
+#| msgid ""
+#| "In 1991, the last major essential component of a Unix-like system was "
+#| "developed: Linux, the free kernel written by Linus Torvalds. Today, the "
+#| "combination of GNU and Linux is used by millions of people around the "
+#| "world, and its popularity is growing. This month, we announced release "
+#| "1.0 of <acronym title=\"GNU Network Object Model Environment\">GNOME</"
+#| "acronym>, the GNU graphical desktop, which we hope will make the GNU/"
+#| "Linux system as easy to use as any other operating system."
msgid ""
"In 1991, the last major essential component of a Unix-like system was "
"developed: Linux, the free kernel written by Linus Torvalds. Today, the "
"combination of GNU and Linux is used by millions of people around the world, "
-"and its popularity is growing. This month, we announced release 1.0 of "
-"<acronym title=\"GNU Network Object Model Environment\">GNOME</acronym>, the "
-"GNU graphical desktop, which we hope will make the GNU/Linux system as easy "
-"to use as any other operating system."
+"and its popularity is growing. This month, we announced release 1.0 of <abbr "
+"title=\"GNU Network Object Model Environment\">GNOME</abbr>, the GNU "
+"graphical desktop, which we hope will make the GNU/Linux system as easy to "
+"use as any other operating system."
msgstr ""
"1991ë
, ì ëì¤ í¸í ìì¤í
ìì ë§ì§ë§ì¼ë¡ 주ìí íì
êµ¬ì± ììê° ê°ë°ëìµë"
"ë¤. ë°ë¡ 리ë
ì¤ë¼ë ê²ì¼ë¡ 리ëì¤ í ë°ì¦ê° ë§ë ìì
커ëì
ëë¤. ì¤ëë GNU"
@@ -187,18 +205,21 @@
"standards/README.translations.html\">ë²ì ìë´</a>를 ì°¸ê³ í´
주ì¸ì."
#. type: Content of: <div><p>
-msgid "Copyright © 1999, 2014 Richard M. Stallman"
+# | Copyright © 1999, [-2014-] {+2014, 2020+} Richard M. Stallman
+#, fuzzy
+#| msgid "Copyright © 1999, 2014 Richard M. Stallman"
+msgid "Copyright © 1999, 2014, 2020 Richard M. Stallman"
msgstr "Copyright © 1999, 2014 Richard M. Stallman"
#. 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>."
+"creativecommons.org/licenses/by-nd/4.0/\">Creative Commons Attribution-"
+"NoDerivatives 4.0 International License</a>."
msgstr ""
"ì´ íì´ì§ë <a rel=\"license\"
href=\"http://creativecommons.org/licenses/by-";
-"nd/3.0/us/deed.ko\">í¬ë¦¬ìì´í°ë¸ ì»¤ë¨¼ì¤ ì ììíì-ë³ê²½ê¸ì§
3.0 ë¯¸êµ ì´ì©íë½"
-"ì</a>ì ë°ë¼ ì´ì©í ì ììµëë¤."
+"nd/4.0/deed.ko\">í¬ë¦¬ìì´í°ë¸ ì»¤ë¨¼ì¤ ì ììíì-ë³ê²½ê¸ì§
4.0 êµì ì´ì©íë½ì"
+"</a>ì ë°ë¼ ì´ì©í ì ììµëë¤."
#. TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.
#. type: Content of: <div><div>
Index: philosophy/po/15-years-of-free-software.ml.po
===================================================================
RCS file: /web/www/www/philosophy/po/15-years-of-free-software.ml.po,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -b -r1.25 -r1.26
--- philosophy/po/15-years-of-free-software.ml.po 3 May 2020 17:32:42
-0000 1.25
+++ philosophy/po/15-years-of-free-software.ml.po 1 Jul 2020 14:31:22
-0000 1.26
@@ -9,7 +9,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 15-years-of-free-software.html\n"
-"POT-Creation-Date: 2014-04-05 15:25+0000\n"
+"POT-Creation-Date: 2020-07-01 14:25+0000\n"
"PO-Revision-Date: 2014-05-06 18:23+0530\n"
"Last-Translator: Navaneeth <navaneeth@gnu.org>\n"
"Language-Team: Swathanthra Malayalam Computing <smc-discuss@googlegroups."
@@ -18,6 +18,7 @@
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"X-Outdated-Since: 2020-07-01 14:25+0000\n"
#. type: Content of: <title>
msgid "15 Years of Free Software - GNU Project - Free Software Foundation"
@@ -107,14 +108,31 @@
"à´à´®àµà´ªàµà´¯àµà´àµà´à´°àµâ à´¶àµà´°à´à´à´²à´¯àµà´àµ
സാധàµà´¯à´¤à´à´³àµâ മാനവരാശിയàµà´àµà´àµàµ
à´µàµà´£àµà´à´¿ സമരàµâà´ªàµà´ªà´¿à´àµà´àµ."
#. type: Content of: <p>
+# | In 1991, the last major essential component of a Unix-like system was
+# | developed: Linux, the free kernel written by Linus Torvalds. Today, the
+# | combination of GNU and Linux is used by millions of people around the
+# | world, and its popularity is growing. This month, we announced release 1.0
+# | of [-<acronym-] {+<abbr+} title=\"GNU Network Object Model
+# | [-Environment\">GNOME</acronym>,-] {+Environment\">GNOME</abbr>,+} the GNU
+# | graphical desktop, which we hope will make the GNU/Linux system as easy to
+# | use as any other operating system.
+#, fuzzy
+#| msgid ""
+#| "In 1991, the last major essential component of a Unix-like system was "
+#| "developed: Linux, the free kernel written by Linus Torvalds. Today, the "
+#| "combination of GNU and Linux is used by millions of people around the "
+#| "world, and its popularity is growing. This month, we announced release "
+#| "1.0 of <acronym title=\"GNU Network Object Model Environment\">GNOME</"
+#| "acronym>, the GNU graphical desktop, which we hope will make the GNU/"
+#| "Linux system as easy to use as any other operating system."
msgid ""
"In 1991, the last major essential component of a Unix-like system was "
"developed: Linux, the free kernel written by Linus Torvalds. Today, the "
"combination of GNU and Linux is used by millions of people around the world, "
-"and its popularity is growing. This month, we announced release 1.0 of "
-"<acronym title=\"GNU Network Object Model Environment\">GNOME</acronym>, the "
-"GNU graphical desktop, which we hope will make the GNU/Linux system as easy "
-"to use as any other operating system."
+"and its popularity is growing. This month, we announced release 1.0 of <abbr "
+"title=\"GNU Network Object Model Environment\">GNOME</abbr>, the GNU "
+"graphical desktop, which we hope will make the GNU/Linux system as easy to "
+"use as any other operating system."
msgstr ""
"1991-à´²àµâ à´¯àµà´£à´¿à´àµà´¸à´¿à´¨àµ സമാനമായ
à´ªàµà´°à´µà´°àµâà´¤àµà´¤à´ à´¸à´à´µà´¿à´§à´¾à´¨à´¤àµà´¤à´¿à´¨àµà´±àµ
à´
വസാനതàµà´¤àµ à´
à´¤àµà´¯à´¾à´µà´¶àµà´¯à´à´à´à´®à´¾à´¯
à´àµà´°àµâണലàµâ "
"വിà´à´¸à´¿à´ªàµà´ªà´¿à´àµà´àµ. ലിനസàµ
à´àµà´°àµâവാളàµâà´¡àµà´¸àµ à´à´¯à´¿à´°àµà´¨àµà´¨àµ à´
à´¸àµà´µà´¤à´¨àµà´¤àµà´°à´à´à´à´
വിà´à´¸à´¿à´ªàµà´ªà´¿à´àµà´à´¤àµ. à´à´¨àµà´¨àµàµ,
à´àµà´¨àµà´µà´¿à´¨àµà´±àµà´¯àµà´ "
@@ -197,17 +215,20 @@
"README.translations.html\">Translations README</a> à´¨àµà´àµà´àµà´."
#. type: Content of: <div><p>
-msgid "Copyright © 1999, 2014 Richard M. Stallman"
+# | Copyright © 1999, [-2014-] {+2014, 2020+} Richard M. Stallman
+#, fuzzy
+#| msgid "Copyright © 1999, 2014 Richard M. Stallman"
+msgid "Copyright © 1999, 2014, 2020 Richard M. Stallman"
msgstr "Copyright © 1999, 2014 Richard M. Stallman |
റിà´àµà´à´¾à´°àµâഡൠസàµà´±àµà´±à´¾à´³àµâമാനàµâ"
#. 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>."
+"creativecommons.org/licenses/by-nd/4.0/\">Creative Commons Attribution-"
+"NoDerivatives 4.0 International License</a>."
msgstr ""
"ഠതാളàµàµ <a rel=\"license\"
href=\"http://creativecommons.org/licenses/by-";
-"nd/3.0/us/\">à´àµà´°à´¿à´¯àµà´±àµà´±àµà´µàµ à´àµà´®à´£àµâà´¸àµ
à´à´àµà´°à´¿à´¬àµà´¯àµà´·à´¨àµâ-à´¨àµà´¡àµà´±à´¿à´µàµà´¸àµ 3.0
à´¯àµà´¨àµà´±àµà´±à´¡àµ à´¸àµà´±àµà´±àµà´±àµà´±àµà´¸àµ
à´²àµà´¸àµ»à´¸àµ</a> "
+"nd/4.0/\">à´àµà´°à´¿à´¯àµà´±àµà´±àµà´µàµ à´àµà´®à´£àµâà´¸àµ
à´à´àµà´°à´¿à´¬àµà´¯àµà´·à´¨àµâ-à´¨àµà´¡àµà´±à´¿à´µàµà´±àµà´±àµà´µàµà´¸àµ
4.0 à´à´¨àµà´±àµ¼à´¨à´¾à´·à´£àµ½ à´²àµà´¸àµ»à´¸àµ</a> "
"à´
à´à´¿à´¸àµà´¥à´¾à´¨à´¤àµà´¤à´¿à´²àµâ
à´ªàµà´°à´¸à´¿à´¦àµà´§àµà´à´°à´¿à´àµà´à´¤à´¾à´£àµàµ."
#. TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.
Index: philosophy/po/15-years-of-free-software.nl.po
===================================================================
RCS file: /web/www/www/philosophy/po/15-years-of-free-software.nl.po,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -b -r1.10 -r1.11
--- philosophy/po/15-years-of-free-software.nl.po 9 Feb 2015 20:30:30
-0000 1.10
+++ philosophy/po/15-years-of-free-software.nl.po 1 Jul 2020 14:31:22
-0000 1.11
@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 15-years-of-free-software.html\n"
-"POT-Creation-Date: 2014-04-05 15:25+0000\n"
+"POT-Creation-Date: 2020-07-01 14:25+0000\n"
"PO-Revision-Date: \n"
"Last-Translator: Tom Uijldert <tom.uijldert@gmail.com>\n"
"Language-Team: Dutch\n"
@@ -15,6 +15,7 @@
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"X-Outdated-Since: 2020-07-01 14:25+0000\n"
#. type: Content of: <title>
msgid "15 Years of Free Software - GNU Project - Free Software Foundation"
@@ -109,14 +110,31 @@
"mensheid."
#. type: Content of: <p>
+# | In 1991, the last major essential component of a Unix-like system was
+# | developed: Linux, the free kernel written by Linus Torvalds. Today, the
+# | combination of GNU and Linux is used by millions of people around the
+# | world, and its popularity is growing. This month, we announced release 1.0
+# | of [-<acronym-] {+<abbr+} title=\"GNU Network Object Model
+# | [-Environment\">GNOME</acronym>,-] {+Environment\">GNOME</abbr>,+} the GNU
+# | graphical desktop, which we hope will make the GNU/Linux system as easy to
+# | use as any other operating system.
+#, fuzzy
+#| msgid ""
+#| "In 1991, the last major essential component of a Unix-like system was "
+#| "developed: Linux, the free kernel written by Linus Torvalds. Today, the "
+#| "combination of GNU and Linux is used by millions of people around the "
+#| "world, and its popularity is growing. This month, we announced release "
+#| "1.0 of <acronym title=\"GNU Network Object Model Environment\">GNOME</"
+#| "acronym>, the GNU graphical desktop, which we hope will make the GNU/"
+#| "Linux system as easy to use as any other operating system."
msgid ""
"In 1991, the last major essential component of a Unix-like system was "
"developed: Linux, the free kernel written by Linus Torvalds. Today, the "
"combination of GNU and Linux is used by millions of people around the world, "
-"and its popularity is growing. This month, we announced release 1.0 of "
-"<acronym title=\"GNU Network Object Model Environment\">GNOME</acronym>, the "
-"GNU graphical desktop, which we hope will make the GNU/Linux system as easy "
-"to use as any other operating system."
+"and its popularity is growing. This month, we announced release 1.0 of <abbr "
+"title=\"GNU Network Object Model Environment\">GNOME</abbr>, the GNU "
+"graphical desktop, which we hope will make the GNU/Linux system as easy to "
+"use as any other operating system."
msgstr ""
"In 1991 werd de laatste belangrijke component van een Unix-achtig systeem "
"ontwikkeld: Linux, de vrije kernel, geschreven door Linus Torvalds. "
@@ -200,14 +218,27 @@
"voor informatie over het onderhoud van vertalingen op deze website."
#. type: Content of: <div><p>
-msgid "Copyright © 1999, 2014 Richard M. Stallman"
+# | Copyright © 1999, [-2014-] {+2014, 2020+} Richard M. Stallman
+#, fuzzy
+#| msgid "Copyright © 1999, 2014 Richard M. Stallman"
+msgid "Copyright © 1999, 2014, 2020 Richard M. Stallman"
msgstr "Copyright © 1999, 2014 Richard M. Stallman"
#. type: Content of: <div><p>
+# | This page is licensed under a <a rel=\"license\"
+# | [-href=\"http://creativecommons.org/licenses/by-nd/3.0/us/\";>Creative-]
+# | {+href=\"http://creativecommons.org/licenses/by-nd/4.0/\";>Creative+}
+# | Commons [-Attribution-NoDerivs 3.0 United States-]
+# | {+Attribution-NoDerivatives 4.0 International+} License</a>.
+#, fuzzy
+#| 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>."
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>."
+"creativecommons.org/licenses/by-nd/4.0/\">Creative Commons Attribution-"
+"NoDerivatives 4.0 International License</a>."
msgstr ""
"Deze pagina valt onder de <a rel=\"license\" href=\"http://creativecommons.";
"org/licenses/by-nd/3.0/us/deed.nl\">Creative Commons Attribution-NoDerivs "
Index: philosophy/po/15-years-of-free-software.pl.po
===================================================================
RCS file: /web/www/www/philosophy/po/15-years-of-free-software.pl.po,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -b -r1.21 -r1.22
--- philosophy/po/15-years-of-free-software.pl.po 16 Jan 2016 00:05:03
-0000 1.21
+++ philosophy/po/15-years-of-free-software.pl.po 1 Jul 2020 14:31:22
-0000 1.22
@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 15-years-of-free-software.html\n"
-"POT-Creation-Date: 2014-04-05 15:25+0000\n"
+"POT-Creation-Date: 2020-07-01 14:25+0000\n"
"PO-Revision-Date: 2014-04-26 22:13-0600\n"
"Last-Translator: Jan Owoc <jsowoc AT gmail.com>\n"
"Language-Team: Polish <www-pl-trans@gnu.org>\n"
@@ -15,6 +15,7 @@
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"X-Outdated-Since: 2020-07-01 14:25+0000\n"
"Plural-Forms: nplurals=3; plural=(n==1 ? 0 : n%10>=2 && n%10<=4 && (n%100<10 "
"|| n%100>=20) ? 1 : 2);\n"
"X-Generator: Virtaal 0.7.0\n"
@@ -114,14 +115,31 @@
"ludzkoÅci."
#. type: Content of: <p>
+# | In 1991, the last major essential component of a Unix-like system was
+# | developed: Linux, the free kernel written by Linus Torvalds. Today, the
+# | combination of GNU and Linux is used by millions of people around the
+# | world, and its popularity is growing. This month, we announced release 1.0
+# | of [-<acronym-] {+<abbr+} title=\"GNU Network Object Model
+# | [-Environment\">GNOME</acronym>,-] {+Environment\">GNOME</abbr>,+} the GNU
+# | graphical desktop, which we hope will make the GNU/Linux system as easy to
+# | use as any other operating system.
+#, fuzzy
+#| msgid ""
+#| "In 1991, the last major essential component of a Unix-like system was "
+#| "developed: Linux, the free kernel written by Linus Torvalds. Today, the "
+#| "combination of GNU and Linux is used by millions of people around the "
+#| "world, and its popularity is growing. This month, we announced release "
+#| "1.0 of <acronym title=\"GNU Network Object Model Environment\">GNOME</"
+#| "acronym>, the GNU graphical desktop, which we hope will make the GNU/"
+#| "Linux system as easy to use as any other operating system."
msgid ""
"In 1991, the last major essential component of a Unix-like system was "
"developed: Linux, the free kernel written by Linus Torvalds. Today, the "
"combination of GNU and Linux is used by millions of people around the world, "
-"and its popularity is growing. This month, we announced release 1.0 of "
-"<acronym title=\"GNU Network Object Model Environment\">GNOME</acronym>, the "
-"GNU graphical desktop, which we hope will make the GNU/Linux system as easy "
-"to use as any other operating system."
+"and its popularity is growing. This month, we announced release 1.0 of <abbr "
+"title=\"GNU Network Object Model Environment\">GNOME</abbr>, the GNU "
+"graphical desktop, which we hope will make the GNU/Linux system as easy to "
+"use as any other operating system."
msgstr ""
"W 1991 roku zaprojektowany zostaÅ ostatni gÅówny i niezbÄdny "
"element systemu uniksopodobnego: Linux, wolne jÄ
dro stworzone przez Linusa "
@@ -209,18 +227,22 @@
"tÅumaczeÅ</a>."
#. type: Content of: <div><p>
-msgid "Copyright © 1999, 2014 Richard M. Stallman"
+# | Copyright © 1999, [-2014-] {+2014, 2020+} Richard M. Stallman
+#, fuzzy
+#| msgid "Copyright © 1999, 2014 Richard M. Stallman"
+msgid "Copyright © 1999, 2014, 2020 Richard M. Stallman"
msgstr "Copyright © 1999, 2014 Richard M. Stallman"
#. 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>."
+"creativecommons.org/licenses/by-nd/4.0/\">Creative Commons Attribution-"
+"NoDerivatives 4.0 International License</a>."
msgstr ""
"Ta strona jest dostÄpna na <a rel=\"license\" href=\"http://";
-"creativecommons.org/licenses/by-nd/3.0/us/\">licencji Creative Commons "
-"Uznanie autorstwa-Bez utworów zależnych 3.0 Stany Zjednoczone</a>."
+"creativecommons.org/licenses/by-nd/4.0/deed.pl\">licencji Creative Commons "
+"Uznanie autorstwa – Bez utworów zależnych 4.0 "
+"MiÄdzynarodowe</a>."
#. TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.
#. type: Content of: <div><div>
Index: philosophy/po/15-years-of-free-software.pot
===================================================================
RCS file: /web/www/www/philosophy/po/15-years-of-free-software.pot,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -b -r1.15 -r1.16
--- philosophy/po/15-years-of-free-software.pot 5 Apr 2014 15:43:01 -0000
1.15
+++ philosophy/po/15-years-of-free-software.pot 1 Jul 2020 14:31:22 -0000
1.16
@@ -1,4 +1,4 @@
-# LANGUAGE translation of
http://www.gnu.org/philosophy/15-years-of-free-software.html
+# LANGUAGE translation of
https://www.gnu.org/philosophy/15-years-of-free-software.html
# Copyright (C) YEAR Free Software Foundation, Inc.
# This file is distributed under the same license as the original article.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
@@ -7,13 +7,14 @@
msgid ""
msgstr ""
"Project-Id-Version: 15-years-of-free-software.html\n"
-"POT-Creation-Date: 2014-04-05 15:25+0000\n"
+"POT-Creation-Date: 2020-07-01 14:25+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=CHARSET\n"
-"Content-Transfer-Encoding: ENCODING"
+"Content-Transfer-Encoding: 8bit\n"
#. type: Content of: <title>
msgid "15 Years of Free Software - GNU Project - Free Software Foundation"
@@ -83,10 +84,10 @@
"In 1991, the last major essential component of a Unix-like system was "
"developed: Linux, the free kernel written by Linus Torvalds. Today, the "
"combination of GNU and Linux is used by millions of people around the world, "
-"and its popularity is growing. This month, we announced release 1.0 of "
-"<acronym title=\"GNU Network Object Model Environment\">GNOME</acronym>, the "
-"GNU graphical desktop, which we hope will make the GNU/Linux system as easy "
-"to use as any other operating system."
+"and its popularity is growing. This month, we announced release 1.0 of <abbr "
+"title=\"GNU Network Object Model Environment\">GNOME</abbr>, the GNU "
+"graphical desktop, which we hope will make the GNU/Linux system as easy to "
+"use as any other operating system."
msgstr ""
#. type: Content of: <p>
@@ -143,14 +144,14 @@
msgstr ""
#. type: Content of: <div><p>
-msgid "Copyright © 1999, 2014 Richard M. Stallman"
+msgid "Copyright © 1999, 2014, 2020 Richard M. Stallman"
msgstr ""
#. 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>."
+"href=\"http://creativecommons.org/licenses/by-nd/4.0/\";>Creative Commons "
+"Attribution-NoDerivatives 4.0 International License</a>."
msgstr ""
#. TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.
Index: philosophy/po/15-years-of-free-software.pt-br.po
===================================================================
RCS file: /web/www/www/philosophy/po/15-years-of-free-software.pt-br.po,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- philosophy/po/15-years-of-free-software.pt-br.po 22 May 2020 22:05:26
-0000 1.2
+++ philosophy/po/15-years-of-free-software.pt-br.po 1 Jul 2020 14:31:22
-0000 1.3
@@ -5,7 +5,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 15-years-of-free-software.html\n"
-"POT-Creation-Date: 2014-04-05 15:25+0000\n"
+"POT-Creation-Date: 2020-07-01 14:25+0000\n"
"PO-Revision-Date: 2019-12-27 11:06-0300\n"
"Last-Translator: Rafael Fontenelle <rafaelff@gnome.org>\n"
"Language-Team: Brazilian Portuguese <www-pt-br-general@gnu.org>\n"
@@ -13,6 +13,7 @@
"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"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
"X-Generator: Virtaal 1.0.0-beta1\n"
@@ -107,14 +108,23 @@
"humanidade."
#. type: Content of: <p>
+#, fuzzy
+#| msgid ""
+#| "In 1991, the last major essential component of a Unix-like system was "
+#| "developed: Linux, the free kernel written by Linus Torvalds. Today, the "
+#| "combination of GNU and Linux is used by millions of people around the "
+#| "world, and its popularity is growing. This month, we announced release "
+#| "1.0 of <acronym title=\"GNU Network Object Model Environment\">GNOME</"
+#| "acronym>, the GNU graphical desktop, which we hope will make the GNU/"
+#| "Linux system as easy to use as any other operating system."
msgid ""
"In 1991, the last major essential component of a Unix-like system was "
"developed: Linux, the free kernel written by Linus Torvalds. Today, the "
"combination of GNU and Linux is used by millions of people around the world, "
-"and its popularity is growing. This month, we announced release 1.0 of "
-"<acronym title=\"GNU Network Object Model Environment\">GNOME</acronym>, the "
-"GNU graphical desktop, which we hope will make the GNU/Linux system as easy "
-"to use as any other operating system."
+"and its popularity is growing. This month, we announced release 1.0 of <abbr "
+"title=\"GNU Network Object Model Environment\">GNOME</abbr>, the GNU "
+"graphical desktop, which we hope will make the GNU/Linux system as easy to "
+"use as any other operating system."
msgstr ""
"Em 1991, o último grande componente essencial de um sistema similar ao Unix "
"foi desenvolvido: Linux, o kernel livre escrito por Linus Torvalds. Hoje, a "
@@ -199,18 +209,20 @@
"envio de traduções das páginas deste site."
#. type: Content of: <div><p>
-msgid "Copyright © 1999, 2014 Richard M. Stallman"
+#, fuzzy
+#| msgid "Copyright © 1999, 2014 Richard M. Stallman"
+msgid "Copyright © 1999, 2014, 2020 Richard M. Stallman"
msgstr "Copyright © 1999, 2014 Richard M. Stallman"
#. 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>."
+"creativecommons.org/licenses/by-nd/4.0/\">Creative Commons Attribution-"
+"NoDerivatives 4.0 International License</a>."
msgstr ""
"Esta página está licenciada sob uma licença <a rel=\"license\"
href=\"http://";
-"creativecommons.org/licenses/by-nd/3.0/us/deed.pt_BR\">Creative Commons "
-"Atribuição-SemDerivações 3.0 Estados Unidos</a>."
+"creativecommons.org/licenses/by-nd/4.0/deed.pt_BR\">Creative Commons "
+"Atribuição-SemDerivações 4.0 Internacional</a>."
#. TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.
#. type: Content of: <div><div>
Index: philosophy/po/15-years-of-free-software.ru.po
===================================================================
RCS file: /web/www/www/philosophy/po/15-years-of-free-software.ru.po,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -b -r1.10 -r1.11
--- philosophy/po/15-years-of-free-software.ru.po 23 Mar 2019 17:32:00
-0000 1.10
+++ philosophy/po/15-years-of-free-software.ru.po 1 Jul 2020 14:31:22
-0000 1.11
@@ -9,7 +9,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 15-years-of-free-software.html\n"
-"POT-Creation-Date: 2014-04-05 15:25+0000\n"
+"POT-Creation-Date: 2020-07-01 14:25+0000\n"
"PO-Revision-Date: 2019-03-23 09:17+0000\n"
"Last-Translator: Ineiev <ineiev@gnu.org>\n"
"Language-Team: Russian <www-ru-list@gnu.org>\n"
@@ -17,6 +17,7 @@
"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"
#. type: Content of: <title>
msgid "15 Years of Free Software - GNU Project - Free Software Foundation"
@@ -113,14 +114,31 @@
"оÑвободиÑÑ Ð¿Ð¾ÑенÑиал компÑÑÑеÑной ÑеÑи
Ð´Ð»Ñ Ð²Ñего ÑеловеÑеÑÑва."
#. type: Content of: <p>
+# | In 1991, the last major essential component of a Unix-like system was
+# | developed: Linux, the free kernel written by Linus Torvalds. Today, the
+# | combination of GNU and Linux is used by millions of people around the
+# | world, and its popularity is growing. This month, we announced release 1.0
+# | of [-<acronym-] {+<abbr+} title=\"GNU Network Object Model
+# | [-Environment\">GNOME</acronym>,-] {+Environment\">GNOME</abbr>,+} the GNU
+# | graphical desktop, which we hope will make the GNU/Linux system as easy to
+# | use as any other operating system.
+#, fuzzy
+#| msgid ""
+#| "In 1991, the last major essential component of a Unix-like system was "
+#| "developed: Linux, the free kernel written by Linus Torvalds. Today, the "
+#| "combination of GNU and Linux is used by millions of people around the "
+#| "world, and its popularity is growing. This month, we announced release "
+#| "1.0 of <acronym title=\"GNU Network Object Model Environment\">GNOME</"
+#| "acronym>, the GNU graphical desktop, which we hope will make the GNU/"
+#| "Linux system as easy to use as any other operating system."
msgid ""
"In 1991, the last major essential component of a Unix-like system was "
"developed: Linux, the free kernel written by Linus Torvalds. Today, the "
"combination of GNU and Linux is used by millions of people around the world, "
-"and its popularity is growing. This month, we announced release 1.0 of "
-"<acronym title=\"GNU Network Object Model Environment\">GNOME</acronym>, the "
-"GNU graphical desktop, which we hope will make the GNU/Linux system as easy "
-"to use as any other operating system."
+"and its popularity is growing. This month, we announced release 1.0 of <abbr "
+"title=\"GNU Network Object Model Environment\">GNOME</abbr>, the GNU "
+"graphical desktop, which we hope will make the GNU/Linux system as easy to "
+"use as any other operating system."
msgstr ""
"Ð 1991 Ð³Ð¾Ð´Ñ Ð±Ñл ÑазÑабоÑан поÑледний
кÑÑпнÑй ÑÑÑеÑÑвеннÑй ÐºÐ¾Ð¼Ð¿Ð¾Ð½ÐµÐ½Ñ ÑиÑÑÐµÐ¼Ñ "
"Ñипа Unix: Linux, Ñвободное ÑдÑо, напиÑанное
ÐинÑÑом ТоÑвалÑдÑом. Ð¡ÐµÐ³Ð¾Ð´Ð½Ñ "
@@ -206,21 +224,30 @@
# type: Content of: <div><p>
#. type: Content of: <div><p>
-msgid "Copyright © 1999, 2014 Richard M. Stallman"
+# | Copyright © 1999, [-2014-] {+2014, 2020+} Richard M. Stallman
+#, fuzzy
+#| msgid "Copyright © 1999, 2014 Richard M. Stallman"
+msgid "Copyright © 1999, 2014, 2020 Richard M. Stallman"
msgstr ""
"Copyright © 1999, 2014 Richard Stallman<br />Copyright © 2014 Free "
"Software Foundation, Inc. (translation)"
#. type: Content of: <div><p>
+# || No change detected. The change might only be in amounts of spaces.
+#, fuzzy
+#| msgid ""
+#| "This page is licensed under a <a rel=\"license\" href=\"http://";
+#| "creativecommons.org/licenses/by-nd/4.0/\">Creative Commons Attribution-"
+#| "NoDerivatives 4.0 International License</a>."
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>."
+"creativecommons.org/licenses/by-nd/4.0/\">Creative Commons Attribution-"
+"NoDerivatives 4.0 International License</a>."
msgstr ""
"ÐÑо пÑоизведение доÑÑÑпно по <a rel=\"license\"
href=\"http://";
-"creativecommons.org/licenses/by-nd/3.0/us/deed.ru\">лиÑензии Creative
"
-"Commons Attribution-NoDerivs (<em>ÐÑÑибÑÑÐ¸Ñ — Ðез
пÑоизводнÑÑ
"
-"пÑоизведений</em>) 3.0 СШÐ</a>."
+"creativecommons.org/licenses/by-nd/4.0/deed.ru\">лиÑензии Creative
Commons "
+"Attribution-NoDerivs (<em>ÐÑÑибÑÑÐ¸Ñ — Ðез
пÑоизводнÑÑ
"
+"пÑоизведений</em>) 4.0 ÐÑемиÑнаÑ</a>."
# type: Content of: <div><div>
#. TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.
Index: philosophy/po/15-years-of-free-software.sq.po
===================================================================
RCS file: /web/www/www/philosophy/po/15-years-of-free-software.sq.po,v
retrieving revision 1.40
retrieving revision 1.41
diff -u -b -r1.40 -r1.41
--- philosophy/po/15-years-of-free-software.sq.po 13 Feb 2015 16:57:40
-0000 1.40
+++ philosophy/po/15-years-of-free-software.sq.po 1 Jul 2020 14:31:22
-0000 1.41
@@ -6,7 +6,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2014-04-05 15:25+0000\n"
+"POT-Creation-Date: 2020-07-01 14:25+0000\n"
"PO-Revision-Date: 2014-11-28 23:36+0200\n"
"Last-Translator: Besnik Bleta <besnik@programeshqip.org>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@@ -14,6 +14,7 @@
"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"
# type: Content of: <title>
#. type: Content of: <title>
@@ -117,14 +118,23 @@
# type: Content of: <p>
#. type: Content of: <p>
+#, fuzzy
+#| msgid ""
+#| "In 1991, the last major essential component of a Unix-like system was "
+#| "developed: Linux, the free kernel written by Linus Torvalds. Today, the "
+#| "combination of GNU and Linux is used by millions of people around the "
+#| "world, and its popularity is growing. This month, we announced release "
+#| "1.0 of <acronym title=\"GNU Network Object Model Environment\">GNOME</"
+#| "acronym>, the GNU graphical desktop, which we hope will make the GNU/"
+#| "Linux system as easy to use as any other operating system."
msgid ""
"In 1991, the last major essential component of a Unix-like system was "
"developed: Linux, the free kernel written by Linus Torvalds. Today, the "
"combination of GNU and Linux is used by millions of people around the world, "
-"and its popularity is growing. This month, we announced release 1.0 of "
-"<acronym title=\"GNU Network Object Model Environment\">GNOME</acronym>, the "
-"GNU graphical desktop, which we hope will make the GNU/Linux system as easy "
-"to use as any other operating system."
+"and its popularity is growing. This month, we announced release 1.0 of <abbr "
+"title=\"GNU Network Object Model Environment\">GNOME</abbr>, the GNU "
+"graphical desktop, which we hope will make the GNU/Linux system as easy to "
+"use as any other operating system."
msgstr ""
"Më 1991, përbërësi i fundit i thelbësor i një sistemi të ngjashëm me
Unix-in "
"u ndërtua: Linux, kerneli i lirë i shkruar nga Linus Torvalds. Sot, "
@@ -212,14 +222,21 @@
"standards/README.translations.html\">README për përkthimet</a>."
#. type: Content of: <div><p>
-msgid "Copyright © 1999, 2014 Richard M. Stallman"
+#, fuzzy
+#| msgid "Copyright © 1999, 2014 Richard M. Stallman"
+msgid "Copyright © 1999, 2014, 2020 Richard M. Stallman"
msgstr "Të drejta kopjimi © 1999, 2014 Richard M. Stallman"
#. type: Content of: <div><p>
+#, fuzzy
+#| 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>."
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>."
+"creativecommons.org/licenses/by-nd/4.0/\">Creative Commons Attribution-"
+"NoDerivatives 4.0 International License</a>."
msgstr ""
"Kjo faqe mund të përdoret sipas një licence <a rel=\"license\"
href=\"http://";
"creativecommons.org/licenses/by-nd/3.0/us/\">Creative Commons Attribution-"
Index: philosophy/po/15-years-of-free-software.tr.po
===================================================================
RCS file: /web/www/www/philosophy/po/15-years-of-free-software.tr.po,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -b -r1.27 -r1.28
--- philosophy/po/15-years-of-free-software.tr.po 5 Mar 2020 18:03:59
-0000 1.27
+++ philosophy/po/15-years-of-free-software.tr.po 1 Jul 2020 14:31:22
-0000 1.28
@@ -11,7 +11,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 15-years-of-free-software.html\n"
-"POT-Creation-Date: 2014-04-05 15:25+0000\n"
+"POT-Creation-Date: 2020-07-01 14:25+0000\n"
"PO-Revision-Date: 2020-01-18 18:02+0300\n"
"Last-Translator: The FLOSS Information <theflossinformation@gmail.com>\n"
"Language-Team: Turkish <www-tr-comm@gnu.org>\n"
@@ -19,6 +19,7 @@
"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"
"Plural-Forms: nplurals=1; plural=0;\n"
"X-Generator: Lokalize 19.12.1\n"
@@ -113,14 +114,23 @@
"çıkmasına katkıda bulunmuÅlardır."
#. type: Content of: <p>
+#, fuzzy
+#| msgid ""
+#| "In 1991, the last major essential component of a Unix-like system was "
+#| "developed: Linux, the free kernel written by Linus Torvalds. Today, the "
+#| "combination of GNU and Linux is used by millions of people around the "
+#| "world, and its popularity is growing. This month, we announced release "
+#| "1.0 of <acronym title=\"GNU Network Object Model Environment\">GNOME</"
+#| "acronym>, the GNU graphical desktop, which we hope will make the GNU/"
+#| "Linux system as easy to use as any other operating system."
msgid ""
"In 1991, the last major essential component of a Unix-like system was "
"developed: Linux, the free kernel written by Linus Torvalds. Today, the "
"combination of GNU and Linux is used by millions of people around the world, "
-"and its popularity is growing. This month, we announced release 1.0 of "
-"<acronym title=\"GNU Network Object Model Environment\">GNOME</acronym>, the "
-"GNU graphical desktop, which we hope will make the GNU/Linux system as easy "
-"to use as any other operating system."
+"and its popularity is growing. This month, we announced release 1.0 of <abbr "
+"title=\"GNU Network Object Model Environment\">GNOME</abbr>, the GNU "
+"graphical desktop, which we hope will make the GNU/Linux system as easy to "
+"use as any other operating system."
msgstr ""
"1991âde, Unix benzeri bir sistemin büyük önem taÅıyan son bileÅeni "
"geliÅtirildi: Linux, Linus Torvalds tarafından yazılmıŠözgür
çekirdek. "
@@ -207,17 +217,19 @@
"\">çalıÅma sayfamızı</a> ziyaret edebilirsiniz."
#. type: Content of: <div><p>
-msgid "Copyright © 1999, 2014 Richard M. Stallman"
+#, fuzzy
+#| msgid "Copyright © 1999, 2014 Richard M. Stallman"
+msgid "Copyright © 1999, 2014, 2020 Richard M. Stallman"
msgstr "Copyright © 1999, 2014 Richard M. Stallman"
#. 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>."
+"creativecommons.org/licenses/by-nd/4.0/\">Creative Commons Attribution-"
+"NoDerivatives 4.0 International License</a>."
msgstr ""
"Bu sayfa <a rel=\"license\" href=\"http://creativecommons.org/licenses/by-";
-"nd/3.0/us/deed.tr\">Creative Commons Atıf-Türetilemez 3.0 BirleÅik
Devletler "
+"nd/4.0/deed.tr\">Creative Commons Alıntı-Türetilemez 4.0 Uluslararası "
"Lisansı</a> altında lisanslanmıÅtır."
#. TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.
Index: philosophy/po/15-years-of-free-software.uk.po
===================================================================
RCS file: /web/www/www/philosophy/po/15-years-of-free-software.uk.po,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- philosophy/po/15-years-of-free-software.uk.po 10 Dec 2017 14:58:10
-0000 1.2
+++ philosophy/po/15-years-of-free-software.uk.po 1 Jul 2020 14:31:22
-0000 1.3
@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 15-years-of-free-software.html\n"
-"POT-Creation-Date: 2014-04-05 15:25+0000\n"
+"POT-Creation-Date: 2020-07-01 14:25+0000\n"
"PO-Revision-Date: 2017-12-10 16:03+0200\n"
"Last-Translator: Andriy Bandura <andriykopanytsia@gmail.com>\n"
"Language-Team: Ukrainian <>\n"
@@ -15,6 +15,7 @@
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"X-Outdated-Since: 2020-07-01 14:25+0000\n"
"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
"X-Generator: Lokalize 2.0\n"
@@ -112,14 +113,23 @@
"лÑбеÑалÑзÑваÑи поÑенÑÑал комп'ÑÑеÑноÑ
меÑÐµÐ¶Ñ Ð´Ð»Ñ Ð²ÑÑого лÑдÑÑва."
#. type: Content of: <p>
+#, fuzzy
+#| msgid ""
+#| "In 1991, the last major essential component of a Unix-like system was "
+#| "developed: Linux, the free kernel written by Linus Torvalds. Today, the "
+#| "combination of GNU and Linux is used by millions of people around the "
+#| "world, and its popularity is growing. This month, we announced release "
+#| "1.0 of <acronym title=\"GNU Network Object Model Environment\">GNOME</"
+#| "acronym>, the GNU graphical desktop, which we hope will make the GNU/"
+#| "Linux system as easy to use as any other operating system."
msgid ""
"In 1991, the last major essential component of a Unix-like system was "
"developed: Linux, the free kernel written by Linus Torvalds. Today, the "
"combination of GNU and Linux is used by millions of people around the world, "
-"and its popularity is growing. This month, we announced release 1.0 of "
-"<acronym title=\"GNU Network Object Model Environment\">GNOME</acronym>, the "
-"GNU graphical desktop, which we hope will make the GNU/Linux system as easy "
-"to use as any other operating system."
+"and its popularity is growing. This month, we announced release 1.0 of <abbr "
+"title=\"GNU Network Object Model Environment\">GNOME</abbr>, the GNU "
+"graphical desktop, which we hope will make the GNU/Linux system as easy to "
+"use as any other operating system."
msgstr ""
"1991-го ÑÐ¾ÐºÑ Ð±Ñло ÑозÑоблено оÑÑаннÑй
важливий ÐºÐ¾Ð¼Ð¿Ð¾Ð½ÐµÐ½Ñ UNIX-подÑÐ±Ð½Ð¾Ñ "
"ÑиÑÑеми: Linux, вÑлÑне ÑдÑо, напиÑане ÐÑнÑÑом
ТоÑвалÑдÑом. ÐÐ¸Ð½Ñ Ð¶ комбÑнаÑÑÑ "
@@ -206,14 +216,21 @@
"translations.html\">“ÐоÑÑÐ±Ð½Ð¸ÐºÑ Ð·
пеÑекладє</a>."
#. type: Content of: <div><p>
-msgid "Copyright © 1999, 2014 Richard M. Stallman"
+#, fuzzy
+#| msgid "Copyright © 1999, 2014 Richard M. Stallman"
+msgid "Copyright © 1999, 2014, 2020 Richard M. Stallman"
msgstr "Copyright © 1999, 2014 Ð ÑÑаÑд Ð. СÑолмен"
#. type: Content of: <div><p>
+#, fuzzy
+#| 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>."
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>."
+"creativecommons.org/licenses/by-nd/4.0/\">Creative Commons Attribution-"
+"NoDerivatives 4.0 International License</a>."
msgstr ""
"Ð¦Ñ ÑÑоÑÑнка доÑÑÑпна на ÑмоваÑ
<a rel=\"license\"
href=\"http://";
"creativecommons.org/licenses/by-nd/3.0/us/deed.uk\"> лÑÑензÑÑ
Creative "
Index: philosophy/po/15-years-of-free-software.zh-cn.po
===================================================================
RCS file: /web/www/www/philosophy/po/15-years-of-free-software.zh-cn.po,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- philosophy/po/15-years-of-free-software.zh-cn.po 19 Jul 2018 12:51:54
-0000 1.1
+++ philosophy/po/15-years-of-free-software.zh-cn.po 1 Jul 2020 14:31:22
-0000 1.2
@@ -6,7 +6,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 15-years-of-free-software.html\n"
-"POT-Creation-Date: 2014-04-05 15:25+0000\n"
+"POT-Creation-Date: 2020-07-01 14:25+0000\n"
"PO-Revision-Date: 2018-07-19 20:26+0800\n"
"Last-Translator: Wensheng Xie <wxie@member.fsf.org>\n"
"Language-Team: Chinese <www-zh-cn-translators@gnu.org>\n"
@@ -14,6 +14,7 @@
"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"
#. type: Content of: <title>
msgid "15 Years of Free Software - GNU Project - Free Software Foundation"
@@ -91,14 +92,23 @@
"æç¥ã被å
¶ä»ä½¿ç¨å
¶ä»£ç çé»å®¢æç¥ã大家ä¸èµ·ä¸ºå
¨äººç±»è§£æ¾äºçµèç½ç»çæ½åã"
#. type: Content of: <p>
+#, fuzzy
+#| msgid ""
+#| "In 1991, the last major essential component of a Unix-like system was "
+#| "developed: Linux, the free kernel written by Linus Torvalds. Today, the "
+#| "combination of GNU and Linux is used by millions of people around the "
+#| "world, and its popularity is growing. This month, we announced release "
+#| "1.0 of <acronym title=\"GNU Network Object Model Environment\">GNOME</"
+#| "acronym>, the GNU graphical desktop, which we hope will make the GNU/"
+#| "Linux system as easy to use as any other operating system."
msgid ""
"In 1991, the last major essential component of a Unix-like system was "
"developed: Linux, the free kernel written by Linus Torvalds. Today, the "
"combination of GNU and Linux is used by millions of people around the world, "
-"and its popularity is growing. This month, we announced release 1.0 of "
-"<acronym title=\"GNU Network Object Model Environment\">GNOME</acronym>, the "
-"GNU graphical desktop, which we hope will make the GNU/Linux system as easy "
-"to use as any other operating system."
+"and its popularity is growing. This month, we announced release 1.0 of <abbr "
+"title=\"GNU Network Object Model Environment\">GNOME</abbr>, the GNU "
+"graphical desktop, which we hope will make the GNU/Linux system as easy to "
+"use as any other operating system."
msgstr ""
"å¨1991å¹´ï¼æåä¸ä¸ªç±»Unixç³»ç»ç主è¦é¨ä»¶è¢«å¼åäºåºæ¥ï¼Linuxï¼ç±Linus
Torvaldsç¼"
"åçå
æ ¸ãä»å¤©ï¼å
¨ä¸çææ°ç¾ä¸äººä½¿ç¨GNUåLinuxçç»åï¼èä¸å
¶ç度è¿å¨æåãæ¬"
@@ -172,18 +182,25 @@
"ç¿»è¯é¡»ç¥</a>ã"
#. type: Content of: <div><p>
-msgid "Copyright © 1999, 2014 Richard M. Stallman"
+#, fuzzy
+#| msgid "Copyright © 1999, 2014 Richard M. Stallman"
+msgid "Copyright © 1999, 2014, 2020 Richard M. Stallman"
msgstr "Copyright © 1999, 2014 Richard M. Stallman"
#. type: Content of: <div><p>
+#, fuzzy
+#| 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>."
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>."
+"creativecommons.org/licenses/by-nd/4.0/\">Creative Commons Attribution-"
+"NoDerivatives 4.0 International License</a>."
msgstr ""
-"æ¬é¡µé¢ä½¿ç¨<a rel=\"license\"
href=\"http://creativecommons.org/licenses/by-";
+"æ¬é¡µé¢éç¨ <a rel=\"license\"
href=\"http://creativecommons.org/licenses/by-";
"nd/3.0/us/\">Creative Commons Attribution-NoDerivs 3.0 United States "
-"License</a>ææã"
+"License</a> 许å¯è¯ææã"
#. TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.
#. type: Content of: <div><div>
@@ -196,3 +213,12 @@
#. type: Content of: <div><p>
msgid "Updated:"
msgstr "æåæ´æ°ï¼"
+
+#~ 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 ""
+#~ "æ¬é¡µé¢ä½¿ç¨<a rel=\"license\"
href=\"http://creativecommons.org/licenses/";
+#~ "by-nd/3.0/us/\">Creative Commons Attribution-NoDerivs 3.0 United States "
+#~ "License</a>ææã"
- www gnu/po/rms-lisp.es.po gnu/po/rms-lisp.fr.po...,
GNUN <=