[Top][All Lists]
[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: |
Sat, 13 Oct 2012 08:28:13 +0000 |
CVSROOT: /web/www
Module name: www
Changes by: GNUN <gnun> 12/10/13 08:28:13
Modified files:
gnu/po : rms-lisp.es.po rms-lisp.fr.po rms-lisp.pot
rms-lisp.sq.po
server/standards/po: README.translations.ca.po
README.translations.de.po
README.translations.fr.po
README.translations.pot
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.15&r2=1.16
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/rms-lisp.fr.po?cvsroot=www&r1=1.28&r2=1.29
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/rms-lisp.pot?cvsroot=www&r1=1.12&r2=1.13
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/rms-lisp.sq.po?cvsroot=www&r1=1.13&r2=1.14
http://web.cvs.savannah.gnu.org/viewcvs/www/server/standards/po/README.translations.ca.po?cvsroot=www&r1=1.56&r2=1.57
http://web.cvs.savannah.gnu.org/viewcvs/www/server/standards/po/README.translations.de.po?cvsroot=www&r1=1.36&r2=1.37
http://web.cvs.savannah.gnu.org/viewcvs/www/server/standards/po/README.translations.fr.po?cvsroot=www&r1=1.87&r2=1.88
http://web.cvs.savannah.gnu.org/viewcvs/www/server/standards/po/README.translations.pot?cvsroot=www&r1=1.48&r2=1.49
Patches:
Index: gnu/po/rms-lisp.es.po
===================================================================
RCS file: /web/www/www/gnu/po/rms-lisp.es.po,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -b -r1.15 -r1.16
--- gnu/po/rms-lisp.es.po 10 Jun 2012 09:13:21 -0000 1.15
+++ gnu/po/rms-lisp.es.po 13 Oct 2012 08:28:11 -0000 1.16
@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: rms-list.html\n"
-"POT-Creation-Date: 2012-06-10 04:26-0300\n"
+"POT-Creation-Date: 2012-10-13 04:25-0300\n"
"PO-Revision-Date: 2011-07-30 10:38+0200\n"
"Last-Translator: Xavier Reina <address@hidden>\n"
"Language-Team: Spanish <address@hidden>\n"
@@ -15,6 +15,7 @@
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"Outdated-Since: 2012-10-13 04:25-0300\n"
# type: Content of: <title>
#. type: Content of: <title>
@@ -180,12 +181,37 @@
# 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-7\">(7)</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>.
+#, 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-7\">(7)</"
+#| "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, "
"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-7\">(7)</a> added facilities to "
+"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. "
@@ -231,8 +257,31 @@
# type: Content of: <p>
#. type: Content of: <p>
+# | It was Bernie Greenberg, who discovered that it was <a
+# | [-href=\"#foot-5\">(5)</a>.-] {+href=\"#foot-2\">(2)</a>.+} He wrote a
+# | version of Emacs in Multics MacLisp, and he wrote his commands in MacLisp
+# | in a straightforward fashion. The editor itself was written entirely in
+# | Lisp. Multics Emacs proved to be a great success — programming new
+# | editing commands was so convenient that even the secretaries in his office
+# | started learning how to use it. They used a manual someone had written
+# | which showed how to extend Emacs, but didn't say it was a programming. So
+# | the secretaries, who believed they couldn't do programming, weren't scared
+# | off. They read the manual, discovered they could do useful things and they
+# | learned to program.
+#, fuzzy
+#| msgid ""
+#| "It was Bernie Greenberg, who discovered that it was <a href=\"#foot-5\">"
+#| "(5)</a>. He wrote a version of Emacs in Multics MacLisp, and he wrote "
+#| "his commands in MacLisp in a straightforward fashion. The editor itself "
+#| "was written entirely in Lisp. Multics Emacs proved to be a great success "
+#| "— programming new editing commands was so convenient that even the "
+#| "secretaries in his office started learning how to use it. They used a "
+#| "manual someone had written which showed how to extend Emacs, but didn't "
+#| "say it was a programming. So the secretaries, who believed they couldn't "
+#| "do programming, weren't scared off. They read the manual, discovered they "
+#| "could do useful things and they learned to program."
msgid ""
-"It was Bernie Greenberg, who discovered that it was <a href=\"#foot-5\">(5)</"
+"It was Bernie Greenberg, who discovered that it was <a href=\"#foot-2\">(2)</"
"a>. He wrote a version of Emacs in Multics MacLisp, and he wrote his "
"commands in MacLisp in a straightforward fashion. The editor itself was "
"written entirely in Lisp. Multics Emacs proved to be a great success — "
@@ -444,13 +493,29 @@
# type: Content of: <p>
#. type: Content of: <p>
+# | The one exception was redisplay. For a long time, redisplay was sort of an
+# | alternate world. The editor would enter the world of redisplay and things
+# | would go on with very special data structures that were not safe for
+# | garbage collection, not safe for interruption, and you couldn't run any
+# | Lisp programs during that. We've changed that since — it's now
+# | possible to run Lisp code during redisplay. It's [-a-] quite a convenient
+# | thing.
+#, fuzzy
+#| msgid ""
+#| "The one exception was redisplay. For a long time, redisplay was sort of "
+#| "an alternate world. The editor would enter the world of redisplay and "
+#| "things would go on with very special data structures that were not safe "
+#| "for garbage collection, not safe for interruption, and you couldn't run "
+#| "any Lisp programs during that. We've changed that since — it's now "
+#| "possible to run Lisp code during redisplay. It's a quite a convenient "
+#| "thing."
msgid ""
"The one exception was redisplay. For a long time, redisplay was sort of an "
"alternate world. The editor would enter the world of redisplay and things "
"would go on with very special data structures that were not safe for garbage "
"collection, not safe for interruption, and you couldn't run any Lisp "
"programs during that. We've changed that since — it's now possible to "
-"run Lisp code during redisplay. It's a quite a convenient thing."
+"run Lisp code during redisplay. It's quite a convenient thing."
msgstr ""
"La excepción fue <span style=\"font-style:italic;\">redisplay</span>. "
"Durante mucho tiempo, <span style=\"font-style:italic;\">redisplay</span> "
@@ -530,12 +595,31 @@
# type: Content of: <p>
#. type: Content of: <p>
+# | There were two different ideas about what this company should be like.
+# | Greenblatt wanted to start what he called a “hacker” company.
+# | This meant it would be a company run by hackers and would operate in a way
+# | conducive to hackers. Another goal was to maintain the AI Lab culture <a
+# | [-href=\"#foot-1\">(1)</a>.-] {+href=\"#foot-3\">(3)</a>.+}
+# | Unfortunately, Greenblatt didn't have any business experience, so other
+# | people in the Lisp machine group said they doubted whether he could
+# | succeed. They thought that his plan to avoid outside investment wouldn't
+# | work.
+#, fuzzy
+#| msgid ""
+#| "There were two different ideas about what this company should be like. "
+#| "Greenblatt wanted to start what he called a “hacker” company. "
+#| "This meant it would be a company run by hackers and would operate in a "
+#| "way conducive to hackers. Another goal was to maintain the AI Lab culture "
+#| "<a href=\"#foot-1\">(1)</a>. Unfortunately, Greenblatt didn't have any "
+#| "business experience, so other people in the Lisp machine group said they "
+#| "doubted whether he could succeed. They thought that his plan to avoid "
+#| "outside investment wouldn't work."
msgid ""
"There were two different ideas about what this company should be like. "
"Greenblatt wanted to start what he called a “hacker” company. "
"This meant it would be a company run by hackers and would operate in a way "
"conducive to hackers. Another goal was to maintain the AI Lab culture <a "
-"href=\"#foot-1\">(1)</a>. Unfortunately, Greenblatt didn't have any "
+"href=\"#foot-3\">(3)</a>. Unfortunately, Greenblatt didn't have any "
"business experience, so other people in the Lisp machine group said they "
"doubted whether he could succeed. They thought that his plan to avoid "
"outside investment wouldn't work."
@@ -695,11 +779,27 @@
# type: Content of: <p>
#. type: Content of: <p>
+# | Up until that point, I hadn't taken the side of either company, although
+# | it made me miserable to see what had happened to our community and the
+# | software. But now, Symbolics had forced the issue. So, in an effort to
+# | help keep Lisp Machines Inc. going <a [-href=\"#foot-2\">(2)</a>-]
+# | {+href=\"#foot-5\">(5)</a>+} — I began duplicating all of the
+# | improvements Symbolics had made to the Lisp machine system. I wrote the
+# | equivalent improvements again myself (i.e., the code was my own).
+#, fuzzy
+#| msgid ""
+#| "Up until that point, I hadn't taken the side of either company, although "
+#| "it made me miserable to see what had happened to our community and the "
+#| "software. But now, Symbolics had forced the issue. So, in an effort to "
+#| "help keep Lisp Machines Inc. going <a href=\"#foot-2\">(2)</a> — I "
+#| "began duplicating all of the improvements Symbolics had made to the Lisp "
+#| "machine system. I wrote the equivalent improvements again myself (i.e., "
+#| "the code was my own)."
msgid ""
"Up until that point, I hadn't taken the side of either company, although it "
"made me miserable to see what had happened to our community and the "
"software. But now, Symbolics had forced the issue. So, in an effort to "
-"help keep Lisp Machines Inc. going <a href=\"#foot-2\">(2)</a> — I "
+"help keep Lisp Machines Inc. going <a href=\"#foot-5\">(5)</a> — I "
"began duplicating all of the improvements Symbolics had made to the Lisp "
"machine system. I wrote the equivalent improvements again myself (i.e., the "
"code was my own)."
@@ -714,8 +814,21 @@
# type: Content of: <p>
#. type: Content of: <p>
+# | After a while <a [-href=\"#foot-3\">(3)</a>,-]
+# | {+href=\"#foot-6\">(6)</a>,+} I came to the conclusion that it would be
+# | best if I didn't even look at their code. When they made a beta
+# | announcement that gave the release notes, I would see what the features
+# | were and then implement them. By the time they had a real release, I did
+# | too.
+#, fuzzy
+#| msgid ""
+#| "After a while <a href=\"#foot-3\">(3)</a>, I came to the conclusion that "
+#| "it would be best if I didn't even look at their code. When they made a "
+#| "beta announcement that gave the release notes, I would see what the "
+#| "features were and then implement them. By the time they had a real "
+#| "release, I did too."
msgid ""
-"After a while <a href=\"#foot-3\">(3)</a>, I came to the conclusion that it "
+"After a while <a href=\"#foot-6\">(6)</a>, I came to the conclusion that it "
"would be best if I didn't even look at their code. When they made a beta "
"announcement that gave the release notes, I would see what the features were "
"and then implement them. By the time they had a real release, I did too."
@@ -729,13 +842,30 @@
# type: Content of: <p>
#. type: Content of: <p>
+# | In this way, for two years, I prevented them from wiping out Lisp Machines
+# | Incorporated, and the two companies went on. But, I didn't want to spend
+# | years and years punishing someone, just thwarting an evil deed. I figured
+# | they had been punished pretty thoroughly because they were stuck with
+# | competition that was not leaving or going to [-disappear<a
+# | href=\"#foot-6\">(6)</a>.-] {+disappear <a href=\"#foot-7\">(7)</a>.+}
+# | Meanwhile, it was time to start building a new community to replace the
+# | one that their actions and others had wiped out.
+#, fuzzy
+#| msgid ""
+#| "In this way, for two years, I prevented them from wiping out Lisp "
+#| "Machines Incorporated, and the two companies went on. But, I didn't want "
+#| "to spend years and years punishing someone, just thwarting an evil deed. "
+#| "I figured they had been punished pretty thoroughly because they were "
+#| "stuck with competition that was not leaving or going to disappear<a href="
+#| "\"#foot-6\">(6)</a>. Meanwhile, it was time to start building a new "
+#| "community to replace the one that their actions and others had wiped out."
msgid ""
"In this way, for two years, I prevented them from wiping out Lisp Machines "
"Incorporated, and the two companies went on. But, I didn't want to spend "
"years and years punishing someone, just thwarting an evil deed. I figured "
"they had been punished pretty thoroughly because they were stuck with "
-"competition that was not leaving or going to disappear<a href=\"#foot-6\">(6)"
-"</a>. Meanwhile, it was time to start building a new community to replace "
+"competition that was not leaving or going to disappear <a href=\"#foot-7\">"
+"(7)</a>. Meanwhile, it was time to start building a new community to replace "
"the one that their actions and others had wiped out."
msgstr ""
"De esta manera, durante dos años evité que acabaran con Lisp Machines "
@@ -1082,6 +1212,32 @@
# type: Content of: <p>
#. type: Content of: <ol><li>
msgid ""
+"Guy Steele designed the original symmetrical Emacs command set; then he and "
+"I began implementing Emacs (on top of TECO), but after one long joint "
+"development session, Steele began drifting away, so I finished Emacs. "
+"Others particularly including Eugene C. Cicciarelli and Mike McMahon "
+"contributed substantially later on."
+msgstr ""
+"Guy Steele diseñó el conjunto de órdenes simétrico original de Emacs;
luego, "
+"él y yo empezamos a implementar Emacs (sobre TECO), pero, tras una larga "
+"sesión conjunta de desarrollo, Steele empezó a distanciarse, asà que yo "
+"finalicé Emacs. Otros, entre los que destacan Eugene C. Cicciarelli y Mike "
+"McMahon, contribuyeron más tarde de forma sustancial."
+
+# type: Content of: <p>
+#. type: Content of: <ol><li>
+msgid ""
+"Bernie Greenberg says that Dan Weinreb's implementation of Emacs for the "
+"Lisp Machine came before Greenberg's implementation for Multics. I "
+"apologize for the mistake."
+msgstr ""
+"Bernie Greenberg dice que Dan Weinreb implementó Emacs para la Máquina Lisp
"
+"antes de que Greenberg lo implementara para Multics. Pido disculpas por el "
+"error. "
+
+# type: Content of: <p>
+#. type: Content of: <ol><li>
+msgid ""
"Greenblatt's plan, as I understood it, was to hire lab people part time, so "
"that they could continue working at the AI Lab. Symbolics hired them full "
"time instead, so they stopped working at MIT."
@@ -1094,6 +1250,23 @@
# type: Content of: <p>
#. type: Content of: <ol><li>
msgid ""
+"The background of this plan, which I did not state explicitly in the talk, "
+"is that during an initial period the ex-AI-Lab hackers, whether at Symbolics "
+"or LMI, continued contributing their changes to the MIT Lisp Machine system "
+"— even though the contract did not require this. Symbolics' plan was "
+"to rupture this cooperation unilaterally."
+msgstr ""
+"Las circunstancias de este plan, que no expuse explÃcitamente en la charla, "
+"fueron las siguientes: durante un periodo inicial los hackers que habÃan "
+"dejado el Laboratorio de Inteligencia Artificial, tanto los que trabajaban "
+"para Symbolics como los que lo hacÃan para LMI, continuaron aportando al "
+"sistema de la máquina Lisp del MIT sus modificaciones, a pesar de que el "
+"contrato no lo exigÃa. El plan de Symbolics era provocar unilateralmente la "
+"ruptura de esta cooperación."
+
+# type: Content of: <p>
+#. type: Content of: <ol><li>
+msgid ""
"It was not that I cared particularly about the fate of LMI, but rather I did "
"not want to let Symbolics gain through its aggression against the AI Lab."
msgstr ""
@@ -1132,55 +1305,12 @@
# type: Content of: <p>
#. type: Content of: <ol><li>
msgid ""
-"The background of this plan, which I did not state explicitly in the talk, "
-"is that during an initial period the ex-AI-Lab hackers, whether at Symbolics "
-"or LMI, continued contributing their changes to the MIT Lisp Machine system "
-"— even though the contract did not require this. Symbolics' plan was "
-"to rupture this cooperation unilaterally."
-msgstr ""
-"Las circunstancias de este plan, que no expuse explÃcitamente en la charla, "
-"fueron las siguientes: durante un periodo inicial los hackers que habÃan "
-"dejado el Laboratorio de Inteligencia Artificial, tanto los que trabajaban "
-"para Symbolics como los que lo hacÃan para LMI, continuaron aportando al "
-"sistema de la máquina Lisp del MIT sus modificaciones, a pesar de que el "
-"contrato no lo exigÃa. El plan de Symbolics era provocar unilateralmente la "
-"ruptura de esta cooperación."
-
-# type: Content of: <p>
-#. type: Content of: <ol><li>
-msgid ""
-"Bernie Greenberg says that Dan Weinreb's implementation of Emacs for the "
-"Lisp Machine came before Greenberg's implementation for Multics. I "
-"apologize for the mistake."
-msgstr ""
-"Bernie Greenberg dice que Dan Weinreb implementó Emacs para la Máquina Lisp
"
-"antes de que Greenberg lo implementara para Multics. Pido disculpas por el "
-"error. "
-
-# type: Content of: <p>
-#. type: Content of: <ol><li>
-msgid ""
"Symbolics at one point protested to MIT that my work, by thwarting their "
"plan, had cost Symbolics a million dollars."
msgstr ""
"En una ocasión Symbolics se quejó al MIT de que mi trabajo, al frustrar sus
"
"planes, le habÃa costado un millón de dólares."
-# type: Content of: <p>
-#. type: Content of: <ol><li>
-msgid ""
-"Guy Steele designed the original symmetrical Emacs command set; then he and "
-"I began implementing Emacs (on top of TECO), but after one long joint "
-"development session, Steele began drifting away, so I finished Emacs. "
-"Others particularly including Eugene C. Cicciarelli and Mike McMahon "
-"contributed substantially later on."
-msgstr ""
-"Guy Steele diseñó el conjunto de órdenes simétrico original de Emacs;
luego, "
-"él y yo empezamos a implementar Emacs (sobre TECO), pero, tras una larga "
-"sesión conjunta de desarrollo, Steele empezó a distanciarse, asà que yo "
-"finalicé Emacs. Otros, entre los que destacan Eugene C. Cicciarelli y Mike "
-"McMahon, contribuyeron más tarde de forma sustancial."
-
# type: Content of: <div>
#. TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.
#. type: Content of: <div>
Index: gnu/po/rms-lisp.fr.po
===================================================================
RCS file: /web/www/www/gnu/po/rms-lisp.fr.po,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -b -r1.28 -r1.29
--- gnu/po/rms-lisp.fr.po 9 Sep 2012 07:11:44 -0000 1.28
+++ gnu/po/rms-lisp.fr.po 13 Oct 2012 08:28:12 -0000 1.29
@@ -8,7 +8,7 @@
msgid ""
msgstr ""
"Project-Id-Version: rms-lisp.html\n"
-"POT-Creation-Date: 2012-06-10 04:26-0300\n"
+"POT-Creation-Date: 2012-10-13 04:25-0300\n"
"PO-Revision-Date: 2012-09-07 10:24+0200\n"
"Last-Translator: Thérèse Godefroy <godef.th AT free.fr>\n"
"Language-Team: French <address@hidden>\n"
@@ -16,6 +16,7 @@
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"Outdated-Since: 2012-10-13 04:25-0300\n"
"Plural-Forms: \n"
#. type: Content of: <title>
@@ -171,12 +172,37 @@
"la 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-7\">(7)</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>.
+#, 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-7\">(7)</"
+#| "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, "
"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-7\">(7)</a> added facilities to "
+"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. "
@@ -219,8 +245,31 @@
"programmation pour faire cela était Lisp."
#. type: Content of: <p>
+# | It was Bernie Greenberg, who discovered that it was <a
+# | [-href=\"#foot-5\">(5)</a>.-] {+href=\"#foot-2\">(2)</a>.+} He wrote a
+# | version of Emacs in Multics MacLisp, and he wrote his commands in MacLisp
+# | in a straightforward fashion. The editor itself was written entirely in
+# | Lisp. Multics Emacs proved to be a great success — programming new
+# | editing commands was so convenient that even the secretaries in his office
+# | started learning how to use it. They used a manual someone had written
+# | which showed how to extend Emacs, but didn't say it was a programming. So
+# | the secretaries, who believed they couldn't do programming, weren't scared
+# | off. They read the manual, discovered they could do useful things and they
+# | learned to program.
+#, fuzzy
+#| msgid ""
+#| "It was Bernie Greenberg, who discovered that it was <a href=\"#foot-5\">"
+#| "(5)</a>. He wrote a version of Emacs in Multics MacLisp, and he wrote "
+#| "his commands in MacLisp in a straightforward fashion. The editor itself "
+#| "was written entirely in Lisp. Multics Emacs proved to be a great success "
+#| "— programming new editing commands was so convenient that even the "
+#| "secretaries in his office started learning how to use it. They used a "
+#| "manual someone had written which showed how to extend Emacs, but didn't "
+#| "say it was a programming. So the secretaries, who believed they couldn't "
+#| "do programming, weren't scared off. They read the manual, discovered they "
+#| "could do useful things and they learned to program."
msgid ""
-"It was Bernie Greenberg, who discovered that it was <a href=\"#foot-5\">(5)</"
+"It was Bernie Greenberg, who discovered that it was <a href=\"#foot-2\">(2)</"
"a>. He wrote a version of Emacs in Multics MacLisp, and he wrote his "
"commands in MacLisp in a straightforward fashion. The editor itself was "
"written entirely in Lisp. Multics Emacs proved to be a great success — "
@@ -427,13 +476,29 @@
"structures de données des parties internes de l'éditeur et de les
manipuler."
#. type: Content of: <p>
+# | The one exception was redisplay. For a long time, redisplay was sort of an
+# | alternate world. The editor would enter the world of redisplay and things
+# | would go on with very special data structures that were not safe for
+# | garbage collection, not safe for interruption, and you couldn't run any
+# | Lisp programs during that. We've changed that since — it's now
+# | possible to run Lisp code during redisplay. It's [-a-] quite a convenient
+# | thing.
+#, fuzzy
+#| msgid ""
+#| "The one exception was redisplay. For a long time, redisplay was sort of "
+#| "an alternate world. The editor would enter the world of redisplay and "
+#| "things would go on with very special data structures that were not safe "
+#| "for garbage collection, not safe for interruption, and you couldn't run "
+#| "any Lisp programs during that. We've changed that since — it's now "
+#| "possible to run Lisp code during redisplay. It's a quite a convenient "
+#| "thing."
msgid ""
"The one exception was redisplay. For a long time, redisplay was sort of an "
"alternate world. The editor would enter the world of redisplay and things "
"would go on with very special data structures that were not safe for garbage "
"collection, not safe for interruption, and you couldn't run any Lisp "
"programs during that. We've changed that since — it's now possible to "
-"run Lisp code during redisplay. It's a quite a convenient thing."
+"run Lisp code during redisplay. It's quite a convenient thing."
msgstr ""
"L'unique exception était le réaffichage. Pendant longtemps, le réaffichage
a "
"été une sorte d'autre planète. L'éditeur arrivait sur cette planète, et
les "
@@ -508,12 +573,31 @@
"signifiait qu'ils allaient lancer une entreprise."
#. type: Content of: <p>
+# | There were two different ideas about what this company should be like.
+# | Greenblatt wanted to start what he called a “hacker” company.
+# | This meant it would be a company run by hackers and would operate in a way
+# | conducive to hackers. Another goal was to maintain the AI Lab culture <a
+# | [-href=\"#foot-1\">(1)</a>.-] {+href=\"#foot-3\">(3)</a>.+}
+# | Unfortunately, Greenblatt didn't have any business experience, so other
+# | people in the Lisp machine group said they doubted whether he could
+# | succeed. They thought that his plan to avoid outside investment wouldn't
+# | work.
+#, fuzzy
+#| msgid ""
+#| "There were two different ideas about what this company should be like. "
+#| "Greenblatt wanted to start what he called a “hacker” company. "
+#| "This meant it would be a company run by hackers and would operate in a "
+#| "way conducive to hackers. Another goal was to maintain the AI Lab culture "
+#| "<a href=\"#foot-1\">(1)</a>. Unfortunately, Greenblatt didn't have any "
+#| "business experience, so other people in the Lisp machine group said they "
+#| "doubted whether he could succeed. They thought that his plan to avoid "
+#| "outside investment wouldn't work."
msgid ""
"There were two different ideas about what this company should be like. "
"Greenblatt wanted to start what he called a “hacker” company. "
"This meant it would be a company run by hackers and would operate in a way "
"conducive to hackers. Another goal was to maintain the AI Lab culture <a "
-"href=\"#foot-1\">(1)</a>. Unfortunately, Greenblatt didn't have any "
+"href=\"#foot-3\">(3)</a>. Unfortunately, Greenblatt didn't have any "
"business experience, so other people in the Lisp machine group said they "
"doubted whether he could succeed. They thought that his plan to avoid "
"outside investment wouldn't work."
@@ -668,11 +752,27 @@
"exister. Donc nous ne pouvions plus rester neutres."
#. type: Content of: <p>
+# | Up until that point, I hadn't taken the side of either company, although
+# | it made me miserable to see what had happened to our community and the
+# | software. But now, Symbolics had forced the issue. So, in an effort to
+# | help keep Lisp Machines Inc. going <a [-href=\"#foot-2\">(2)</a>-]
+# | {+href=\"#foot-5\">(5)</a>+} — I began duplicating all of the
+# | improvements Symbolics had made to the Lisp machine system. I wrote the
+# | equivalent improvements again myself (i.e., the code was my own).
+#, fuzzy
+#| msgid ""
+#| "Up until that point, I hadn't taken the side of either company, although "
+#| "it made me miserable to see what had happened to our community and the "
+#| "software. But now, Symbolics had forced the issue. So, in an effort to "
+#| "help keep Lisp Machines Inc. going <a href=\"#foot-2\">(2)</a> — I "
+#| "began duplicating all of the improvements Symbolics had made to the Lisp "
+#| "machine system. I wrote the equivalent improvements again myself (i.e., "
+#| "the code was my own)."
msgid ""
"Up until that point, I hadn't taken the side of either company, although it "
"made me miserable to see what had happened to our community and the "
"software. But now, Symbolics had forced the issue. So, in an effort to "
-"help keep Lisp Machines Inc. going <a href=\"#foot-2\">(2)</a> — I "
+"help keep Lisp Machines Inc. going <a href=\"#foot-5\">(5)</a> — I "
"began duplicating all of the improvements Symbolics had made to the Lisp "
"machine system. I wrote the equivalent improvements again myself (i.e., the "
"code was my own)."
@@ -686,8 +786,21 @@
"équivalentes moi-même (c'est-à -dire avec mon propre code)."
#. type: Content of: <p>
+# | After a while <a [-href=\"#foot-3\">(3)</a>,-]
+# | {+href=\"#foot-6\">(6)</a>,+} I came to the conclusion that it would be
+# | best if I didn't even look at their code. When they made a beta
+# | announcement that gave the release notes, I would see what the features
+# | were and then implement them. By the time they had a real release, I did
+# | too.
+#, fuzzy
+#| msgid ""
+#| "After a while <a href=\"#foot-3\">(3)</a>, I came to the conclusion that "
+#| "it would be best if I didn't even look at their code. When they made a "
+#| "beta announcement that gave the release notes, I would see what the "
+#| "features were and then implement them. By the time they had a real "
+#| "release, I did too."
msgid ""
-"After a while <a href=\"#foot-3\">(3)</a>, I came to the conclusion that it "
+"After a while <a href=\"#foot-6\">(6)</a>, I came to the conclusion that it "
"would be best if I didn't even look at their code. When they made a beta "
"announcement that gave the release notes, I would see what the features were "
"and then implement them. By the time they had a real release, I did too."
@@ -700,13 +813,30 @@
"également."
#. type: Content of: <p>
+# | In this way, for two years, I prevented them from wiping out Lisp Machines
+# | Incorporated, and the two companies went on. But, I didn't want to spend
+# | years and years punishing someone, just thwarting an evil deed. I figured
+# | they had been punished pretty thoroughly because they were stuck with
+# | competition that was not leaving or going to [-disappear<a
+# | href=\"#foot-6\">(6)</a>.-] {+disappear <a href=\"#foot-7\">(7)</a>.+}
+# | Meanwhile, it was time to start building a new community to replace the
+# | one that their actions and others had wiped out.
+#, fuzzy
+#| msgid ""
+#| "In this way, for two years, I prevented them from wiping out Lisp "
+#| "Machines Incorporated, and the two companies went on. But, I didn't want "
+#| "to spend years and years punishing someone, just thwarting an evil deed. "
+#| "I figured they had been punished pretty thoroughly because they were "
+#| "stuck with competition that was not leaving or going to disappear<a href="
+#| "\"#foot-6\">(6)</a>. Meanwhile, it was time to start building a new "
+#| "community to replace the one that their actions and others had wiped out."
msgid ""
"In this way, for two years, I prevented them from wiping out Lisp Machines "
"Incorporated, and the two companies went on. But, I didn't want to spend "
"years and years punishing someone, just thwarting an evil deed. I figured "
"they had been punished pretty thoroughly because they were stuck with "
-"competition that was not leaving or going to disappear<a href=\"#foot-6\">(6)"
-"</a>. Meanwhile, it was time to start building a new community to replace "
+"competition that was not leaving or going to disappear <a href=\"#foot-7\">"
+"(7)</a>. Meanwhile, it was time to start building a new community to replace "
"the one that their actions and others had wiped out."
msgstr ""
"De cette façon, et pendant deux ans, je les ai empêchés d'écraser LMI et
les "
@@ -1041,6 +1171,31 @@
#. type: Content of: <ol><li>
msgid ""
+"Guy Steele designed the original symmetrical Emacs command set; then he and "
+"I began implementing Emacs (on top of TECO), but after one long joint "
+"development session, Steele began drifting away, so I finished Emacs. "
+"Others particularly including Eugene C. Cicciarelli and Mike McMahon "
+"contributed substantially later on."
+msgstr ""
+"Guy Steele a conçu la bibliothèque symétrique originale de commandes "
+"d'Emacs, puis lui et moi avons commencé à implémenter Emacs (au-dessus de "
+"TECO), mais après une longue session de développement conjointe, Steele a "
+"commencé à s'éloigner, donc j'ai fini Emacs. D'autres, en particulier
Eugene "
+"C. Cicciarelli et Mike McMahon, ont par la suite contribué de manière "
+"substantielle."
+
+#. type: Content of: <ol><li>
+msgid ""
+"Bernie Greenberg says that Dan Weinreb's implementation of Emacs for the "
+"Lisp Machine came before Greenberg's implementation for Multics. I "
+"apologize for the mistake."
+msgstr ""
+"Bernie Greenberg dit que l'implémentation d'Emacs de Dan Weinberg pour la "
+"machine Lisp est arrivée avant celle de Greenberg pour Multics. Je lui "
+"présente mes excuses pour cette erreur."
+
+#. type: Content of: <ol><li>
+msgid ""
"Greenblatt's plan, as I understood it, was to hire lab people part time, so "
"that they could continue working at the AI Lab. Symbolics hired them full "
"time instead, so they stopped working at MIT."
@@ -1052,6 +1207,20 @@
#. type: Content of: <ol><li>
msgid ""
+"The background of this plan, which I did not state explicitly in the talk, "
+"is that during an initial period the ex-AI-Lab hackers, whether at Symbolics "
+"or LMI, continued contributing their changes to the MIT Lisp Machine system "
+"— even though the contract did not require this. Symbolics' plan was "
+"to rupture this cooperation unilaterally."
+msgstr ""
+"L'arrière-pensée de ce plan, que je n'ai pas explicitée dans le discours, "
+"était que durant cette période initiale les ex-hackers du labo d'IA, que ce
"
+"soit chez Symbolics ou chez LMI, continuent à apporter leurs modifications "
+"au système de machine Lisp du MIT, bien que le contrat ne l'exige pas. Le "
+"plan de Symbolics était de briser cette coopération unilatéralement."
+
+#. type: Content of: <ol><li>
+msgid ""
"It was not that I cared particularly about the fate of LMI, but rather I did "
"not want to let Symbolics gain through its aggression against the AI Lab."
msgstr ""
@@ -1087,51 +1256,12 @@
#. type: Content of: <ol><li>
msgid ""
-"The background of this plan, which I did not state explicitly in the talk, "
-"is that during an initial period the ex-AI-Lab hackers, whether at Symbolics "
-"or LMI, continued contributing their changes to the MIT Lisp Machine system "
-"— even though the contract did not require this. Symbolics' plan was "
-"to rupture this cooperation unilaterally."
-msgstr ""
-"L'arrière-pensée de ce plan, que je n'ai pas explicitée dans le discours, "
-"était que durant cette période initiale les ex-hackers du labo d'IA, que ce
"
-"soit chez Symbolics ou chez LMI, continuent à apporter leurs modifications "
-"au système de machine Lisp du MIT, bien que le contrat ne l'exige pas. Le "
-"plan de Symbolics était de briser cette coopération unilatéralement."
-
-#. type: Content of: <ol><li>
-msgid ""
-"Bernie Greenberg says that Dan Weinreb's implementation of Emacs for the "
-"Lisp Machine came before Greenberg's implementation for Multics. I "
-"apologize for the mistake."
-msgstr ""
-"Bernie Greenberg dit que l'implémentation d'Emacs de Dan Weinberg pour la "
-"machine Lisp est arrivée avant celle de Greenberg pour Multics. Je lui "
-"présente mes excuses pour cette erreur."
-
-#. type: Content of: <ol><li>
-msgid ""
"Symbolics at one point protested to MIT that my work, by thwarting their "
"plan, had cost Symbolics a million dollars."
msgstr ""
"Symbolics s'est plaint au MIT que mon travail, en contrant leur plan, avait "
"coûté à Symbolics un million de dollars."
-#. type: Content of: <ol><li>
-msgid ""
-"Guy Steele designed the original symmetrical Emacs command set; then he and "
-"I began implementing Emacs (on top of TECO), but after one long joint "
-"development session, Steele began drifting away, so I finished Emacs. "
-"Others particularly including Eugene C. Cicciarelli and Mike McMahon "
-"contributed substantially later on."
-msgstr ""
-"Guy Steele a conçu la bibliothèque symétrique originale de commandes "
-"d'Emacs, puis lui et moi avons commencé à implémenter Emacs (au-dessus de "
-"TECO), mais après une longue session de développement conjointe, Steele a "
-"commencé à s'éloigner, donc j'ai fini Emacs. D'autres, en particulier
Eugene "
-"C. Cicciarelli et Mike McMahon, ont par la suite contribué de manière "
-"substantielle."
-
#. TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.
#. type: Content of: <div>
msgid "*GNUN-SLOT: TRANSLATOR'S NOTES*"
Index: gnu/po/rms-lisp.pot
===================================================================
RCS file: /web/www/www/gnu/po/rms-lisp.pot,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -b -r1.12 -r1.13
--- gnu/po/rms-lisp.pot 16 Sep 2012 05:22:37 -0000 1.12
+++ gnu/po/rms-lisp.pot 13 Oct 2012 08:28:12 -0000 1.13
@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: rms-lisp.html\n"
-"POT-Creation-Date: 2012-06-10 04:26-0300\n"
+"POT-Creation-Date: 2012-10-13 04:25-0300\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <address@hidden>\n"
"Language-Team: LANGUAGE <address@hidden>\n"
@@ -113,7 +113,7 @@
"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-7\">(7)</a> added "
+"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 "
@@ -137,7 +137,7 @@
#. type: Content of: <p>
msgid ""
"It was Bernie Greenberg, who discovered that it was <a "
-"href=\"#foot-5\">(5)</a>. He wrote a version of Emacs in Multics MacLisp, "
+"href=\"#foot-2\">(2)</a>. He wrote a version of Emacs in Multics MacLisp, "
"and he wrote his commands in MacLisp in a straightforward fashion. The "
"editor itself was written entirely in Lisp. Multics Emacs proved to be a "
"great success — programming new editing commands was so convenient "
@@ -257,7 +257,7 @@
"would go on with very special data structures that were not safe for garbage "
"collection, not safe for interruption, and you couldn't run any Lisp "
"programs during that. We've changed that since — it's now possible to "
-"run Lisp code during redisplay. It's a quite a convenient thing."
+"run Lisp code during redisplay. It's quite a convenient thing."
msgstr ""
#. type: Content of: <p>
@@ -303,7 +303,7 @@
"Greenblatt wanted to start what he called a “hacker” "
"company. This meant it would be a company run by hackers and would operate "
"in a way conducive to hackers. Another goal was to maintain the AI Lab "
-"culture <a href=\"#foot-1\">(1)</a>. Unfortunately, Greenblatt didn't have "
+"culture <a href=\"#foot-3\">(3)</a>. Unfortunately, Greenblatt didn't have "
"any business experience, so other people in the Lisp machine group said they "
"doubted whether he could succeed. They thought that his plan to avoid "
"outside investment wouldn't work."
@@ -395,7 +395,7 @@
"Up until that point, I hadn't taken the side of either company, although it "
"made me miserable to see what had happened to our community and the "
"software. But now, Symbolics had forced the issue. So, in an effort to "
-"help keep Lisp Machines Inc. going <a href=\"#foot-2\">(2)</a> — I "
+"help keep Lisp Machines Inc. going <a href=\"#foot-5\">(5)</a> — I "
"began duplicating all of the improvements Symbolics had made to the Lisp "
"machine system. I wrote the equivalent improvements again myself (i.e., the "
"code was my own)."
@@ -403,7 +403,7 @@
#. type: Content of: <p>
msgid ""
-"After a while <a href=\"#foot-3\">(3)</a>, I came to the conclusion that it "
+"After a while <a href=\"#foot-6\">(6)</a>, I came to the conclusion that it "
"would be best if I didn't even look at their code. When they made a beta "
"announcement that gave the release notes, I would see what the features were "
"and then implement them. By the time they had a real release, I did too."
@@ -415,8 +415,8 @@
"Incorporated, and the two companies went on. But, I didn't want to spend "
"years and years punishing someone, just thwarting an evil deed. I figured "
"they had been punished pretty thoroughly because they were stuck with "
-"competition that was not leaving or going to disappear<a "
-"href=\"#foot-6\">(6)</a>. Meanwhile, it was time to start building a new "
+"competition that was not leaving or going to disappear <a "
+"href=\"#foot-7\">(7)</a>. Meanwhile, it was time to start building a new "
"community to replace the one that their actions and others had wiped out."
msgstr ""
@@ -607,6 +607,22 @@
#. type: Content of: <ol><li>
msgid ""
+"Guy Steele designed the original symmetrical Emacs command set; then he and "
+"I began implementing Emacs (on top of TECO), but after one long joint "
+"development session, Steele began drifting away, so I finished Emacs. "
+"Others particularly including Eugene C. Cicciarelli and Mike McMahon "
+"contributed substantially later on."
+msgstr ""
+
+#. type: Content of: <ol><li>
+msgid ""
+"Bernie Greenberg says that Dan Weinreb's implementation of Emacs for the "
+"Lisp Machine came before Greenberg's implementation for Multics. I "
+"apologize for the mistake."
+msgstr ""
+
+#. type: Content of: <ol><li>
+msgid ""
"Greenblatt's plan, as I understood it, was to hire lab people part time, so "
"that they could continue working at the AI Lab. Symbolics hired them full "
"time instead, so they stopped working at MIT."
@@ -614,6 +630,15 @@
#. type: Content of: <ol><li>
msgid ""
+"The background of this plan, which I did not state explicitly in the talk, "
+"is that during an initial period the ex-AI-Lab hackers, whether at Symbolics "
+"or LMI, continued contributing their changes to the MIT Lisp Machine system "
+"— even though the contract did not require this. Symbolics' plan was "
+"to rupture this cooperation unilaterally."
+msgstr ""
+
+#. type: Content of: <ol><li>
+msgid ""
"It was not that I cared particularly about the fate of LMI, but rather I did "
"not want to let Symbolics gain through its aggression against the AI Lab."
msgstr ""
@@ -636,35 +661,10 @@
#. type: Content of: <ol><li>
msgid ""
-"The background of this plan, which I did not state explicitly in the talk, "
-"is that during an initial period the ex-AI-Lab hackers, whether at Symbolics "
-"or LMI, continued contributing their changes to the MIT Lisp Machine system "
-"— even though the contract did not require this. Symbolics' plan was "
-"to rupture this cooperation unilaterally."
-msgstr ""
-
-#. type: Content of: <ol><li>
-msgid ""
-"Bernie Greenberg says that Dan Weinreb's implementation of Emacs for the "
-"Lisp Machine came before Greenberg's implementation for Multics. I "
-"apologize for the mistake."
-msgstr ""
-
-#. type: Content of: <ol><li>
-msgid ""
"Symbolics at one point protested to MIT that my work, by thwarting their "
"plan, had cost Symbolics a million dollars."
msgstr ""
-#. type: Content of: <ol><li>
-msgid ""
-"Guy Steele designed the original symmetrical Emacs command set; then he and "
-"I began implementing Emacs (on top of TECO), but after one long joint "
-"development session, Steele began drifting away, so I finished Emacs. "
-"Others particularly including Eugene C. Cicciarelli and Mike McMahon "
-"contributed substantially later on."
-msgstr ""
-
#. TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.
#. type: Content of: <div>
msgid "*GNUN-SLOT: TRANSLATOR'S NOTES*"
Index: gnu/po/rms-lisp.sq.po
===================================================================
RCS file: /web/www/www/gnu/po/rms-lisp.sq.po,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -b -r1.13 -r1.14
--- gnu/po/rms-lisp.sq.po 10 Jun 2012 09:13:21 -0000 1.13
+++ gnu/po/rms-lisp.sq.po 13 Oct 2012 08:28:12 -0000 1.14
@@ -6,7 +6,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2012-06-10 04:26-0300\n"
+"POT-Creation-Date: 2012-10-13 04:25-0300\n"
"PO-Revision-Date: 2012-04-11 14:37+0200\n"
"Last-Translator: Besnik Bleta <address@hidden>\n"
"Language-Team: Shqip <address@hidden>\n"
@@ -14,6 +14,7 @@
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"Outdated-Since: 2012-10-13 04:25-0300\n"
# type: Content of: <title>
#. type: Content of: <title>
@@ -172,12 +173,25 @@
# 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-7\">(7)</"
+#| "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, "
"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-7\">(7)</a> added facilities to "
+"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. "
@@ -219,8 +233,20 @@
# type: Content of: <p>
#. type: Content of: <p>
+#, fuzzy
+#| msgid ""
+#| "It was Bernie Greenberg, who discovered that it was <a href=\"#foot-5\">"
+#| "(5)</a>. He wrote a version of Emacs in Multics MacLisp, and he wrote "
+#| "his commands in MacLisp in a straightforward fashion. The editor itself "
+#| "was written entirely in Lisp. Multics Emacs proved to be a great success "
+#| "— programming new editing commands was so convenient that even the "
+#| "secretaries in his office started learning how to use it. They used a "
+#| "manual someone had written which showed how to extend Emacs, but didn't "
+#| "say it was a programming. So the secretaries, who believed they couldn't "
+#| "do programming, weren't scared off. They read the manual, discovered they "
+#| "could do useful things and they learned to program."
msgid ""
-"It was Bernie Greenberg, who discovered that it was <a href=\"#foot-5\">(5)</"
+"It was Bernie Greenberg, who discovered that it was <a href=\"#foot-2\">(2)</"
"a>. He wrote a version of Emacs in Multics MacLisp, and he wrote his "
"commands in MacLisp in a straightforward fashion. The editor itself was "
"written entirely in Lisp. Multics Emacs proved to be a great success — "
@@ -430,13 +456,22 @@
# type: Content of: <p>
#. type: Content of: <p>
+#, fuzzy
+#| msgid ""
+#| "The one exception was redisplay. For a long time, redisplay was sort of "
+#| "an alternate world. The editor would enter the world of redisplay and "
+#| "things would go on with very special data structures that were not safe "
+#| "for garbage collection, not safe for interruption, and you couldn't run "
+#| "any Lisp programs during that. We've changed that since — it's now "
+#| "possible to run Lisp code during redisplay. It's a quite a convenient "
+#| "thing."
msgid ""
"The one exception was redisplay. For a long time, redisplay was sort of an "
"alternate world. The editor would enter the world of redisplay and things "
"would go on with very special data structures that were not safe for garbage "
"collection, not safe for interruption, and you couldn't run any Lisp "
"programs during that. We've changed that since — it's now possible to "
-"run Lisp code during redisplay. It's a quite a convenient thing."
+"run Lisp code during redisplay. It's quite a convenient thing."
msgstr ""
"Përjashtim qe rishfaqja. Për shumë kohë, rishfaqja qe njëfarë bote
tjetër. "
"Përpunuesi mund të kalonte në botën e rishfaqjeve dhe gjërat do të
vazhdonin "
@@ -512,12 +547,22 @@
# type: Content of: <p>
#. type: Content of: <p>
+#, fuzzy
+#| msgid ""
+#| "There were two different ideas about what this company should be like. "
+#| "Greenblatt wanted to start what he called a “hacker” company. "
+#| "This meant it would be a company run by hackers and would operate in a "
+#| "way conducive to hackers. Another goal was to maintain the AI Lab culture "
+#| "<a href=\"#foot-1\">(1)</a>. Unfortunately, Greenblatt didn't have any "
+#| "business experience, so other people in the Lisp machine group said they "
+#| "doubted whether he could succeed. They thought that his plan to avoid "
+#| "outside investment wouldn't work."
msgid ""
"There were two different ideas about what this company should be like. "
"Greenblatt wanted to start what he called a “hacker” company. "
"This meant it would be a company run by hackers and would operate in a way "
"conducive to hackers. Another goal was to maintain the AI Lab culture <a "
-"href=\"#foot-1\">(1)</a>. Unfortunately, Greenblatt didn't have any "
+"href=\"#foot-3\">(3)</a>. Unfortunately, Greenblatt didn't have any "
"business experience, so other people in the Lisp machine group said they "
"doubted whether he could succeed. They thought that his plan to avoid "
"outside investment wouldn't work."
@@ -676,11 +721,20 @@
# type: Content of: <p>
#. type: Content of: <p>
+#, fuzzy
+#| msgid ""
+#| "Up until that point, I hadn't taken the side of either company, although "
+#| "it made me miserable to see what had happened to our community and the "
+#| "software. But now, Symbolics had forced the issue. So, in an effort to "
+#| "help keep Lisp Machines Inc. going <a href=\"#foot-2\">(2)</a> — I "
+#| "began duplicating all of the improvements Symbolics had made to the Lisp "
+#| "machine system. I wrote the equivalent improvements again myself (i.e., "
+#| "the code was my own)."
msgid ""
"Up until that point, I hadn't taken the side of either company, although it "
"made me miserable to see what had happened to our community and the "
"software. But now, Symbolics had forced the issue. So, in an effort to "
-"help keep Lisp Machines Inc. going <a href=\"#foot-2\">(2)</a> — I "
+"help keep Lisp Machines Inc. going <a href=\"#foot-5\">(5)</a> — I "
"began duplicating all of the improvements Symbolics had made to the Lisp "
"machine system. I wrote the equivalent improvements again myself (i.e., the "
"code was my own)."
@@ -695,8 +749,15 @@
# type: Content of: <p>
#. type: Content of: <p>
+#, fuzzy
+#| msgid ""
+#| "After a while <a href=\"#foot-3\">(3)</a>, I came to the conclusion that "
+#| "it would be best if I didn't even look at their code. When they made a "
+#| "beta announcement that gave the release notes, I would see what the "
+#| "features were and then implement them. By the time they had a real "
+#| "release, I did too."
msgid ""
-"After a while <a href=\"#foot-3\">(3)</a>, I came to the conclusion that it "
+"After a while <a href=\"#foot-6\">(6)</a>, I came to the conclusion that it "
"would be best if I didn't even look at their code. When they made a beta "
"announcement that gave the release notes, I would see what the features were "
"and then implement them. By the time they had a real release, I did too."
@@ -709,13 +770,22 @@
# type: Content of: <p>
#. type: Content of: <p>
+#, fuzzy
+#| msgid ""
+#| "In this way, for two years, I prevented them from wiping out Lisp "
+#| "Machines Incorporated, and the two companies went on. But, I didn't want "
+#| "to spend years and years punishing someone, just thwarting an evil deed. "
+#| "I figured they had been punished pretty thoroughly because they were "
+#| "stuck with competition that was not leaving or going to disappear<a href="
+#| "\"#foot-6\">(6)</a>. Meanwhile, it was time to start building a new "
+#| "community to replace the one that their actions and others had wiped out."
msgid ""
"In this way, for two years, I prevented them from wiping out Lisp Machines "
"Incorporated, and the two companies went on. But, I didn't want to spend "
"years and years punishing someone, just thwarting an evil deed. I figured "
"they had been punished pretty thoroughly because they were stuck with "
-"competition that was not leaving or going to disappear<a href=\"#foot-6\">(6)"
-"</a>. Meanwhile, it was time to start building a new community to replace "
+"competition that was not leaving or going to disappear <a href=\"#foot-7\">"
+"(7)</a>. Meanwhile, it was time to start building a new community to replace "
"the one that their actions and others had wiped out."
msgstr ""
"Në këtë mënyrë, për dy vite, ua pengova ta fshinin nga faqja e dheut
Lisp "
@@ -1061,6 +1131,32 @@
# type: Content of: <ol><li>
#. type: Content of: <ol><li>
msgid ""
+"Guy Steele designed the original symmetrical Emacs command set; then he and "
+"I began implementing Emacs (on top of TECO), but after one long joint "
+"development session, Steele began drifting away, so I finished Emacs. "
+"Others particularly including Eugene C. Cicciarelli and Mike McMahon "
+"contributed substantially later on."
+msgstr ""
+"Guy Steele hartoi grupin origjinal të komandave simetrike Emacs; mandej ai "
+"dhe unë zumë të vinim në jetë Emacs-in (përsipër TECO-s), por pas një
"
+"sesioni të gjatë programimi të përbashkët, Steele-i zuri të rrëshqiste
tej, "
+"kështu që Emacs-in e përfundova unë. Të tjerë, përfshi veçanërisht
Eugene "
+"C. Cicciarelli-n dhe Mike McMahon-in, dhanë ndihmesë thelbësore më vonë."
+
+# type: Content of: <ol><li>
+#. type: Content of: <ol><li>
+msgid ""
+"Bernie Greenberg says that Dan Weinreb's implementation of Emacs for the "
+"Lisp Machine came before Greenberg's implementation for Multics. I "
+"apologize for the mistake."
+msgstr ""
+"Bernie Greenberg thotë se sendërtimi i Dan Weinreb-it për Emacs në Lisp "
+"Machine kish dal para sendërtimit të Greenberg-ut për Multics. Kërkoj "
+"ndjesë për gabimin."
+
+# type: Content of: <ol><li>
+#. type: Content of: <ol><li>
+msgid ""
"Greenblatt's plan, as I understood it, was to hire lab people part time, so "
"that they could continue working at the AI Lab. Symbolics hired them full "
"time instead, so they stopped working at MIT."
@@ -1073,6 +1169,21 @@
# type: Content of: <ol><li>
#. type: Content of: <ol><li>
msgid ""
+"The background of this plan, which I did not state explicitly in the talk, "
+"is that during an initial period the ex-AI-Lab hackers, whether at Symbolics "
+"or LMI, continued contributing their changes to the MIT Lisp Machine system "
+"— even though the contract did not require this. Symbolics' plan was "
+"to rupture this cooperation unilaterally."
+msgstr ""
+"Rrethanat e këtij plani, të cilat nuk i deklarova shprehimisht gjatë
fjalës "
+"sime, qenë që gjatë një periudhe fillestare <i>hacker</i>-at e
ish-AI-Lab-"
+"it, ata në Symbolics ose ata në LMI, vazhduan t'i jepnin ndryshimet e tyre "
+"te sistemi MIT Lisp Machine — edhe pse kontrata nuk e detyronte këtë "
+"hap. Plani i Symbolics-it qe ta thyente njëanësisht këtë bashkëpunim."
+
+# type: Content of: <ol><li>
+#. type: Content of: <ol><li>
+msgid ""
"It was not that I cared particularly about the fate of LMI, but rather I did "
"not want to let Symbolics gain through its aggression against the AI Lab."
msgstr ""
@@ -1109,53 +1220,12 @@
# type: Content of: <ol><li>
#. type: Content of: <ol><li>
msgid ""
-"The background of this plan, which I did not state explicitly in the talk, "
-"is that during an initial period the ex-AI-Lab hackers, whether at Symbolics "
-"or LMI, continued contributing their changes to the MIT Lisp Machine system "
-"— even though the contract did not require this. Symbolics' plan was "
-"to rupture this cooperation unilaterally."
-msgstr ""
-"Rrethanat e këtij plani, të cilat nuk i deklarova shprehimisht gjatë
fjalës "
-"sime, qenë që gjatë një periudhe fillestare <i>hacker</i>-at e
ish-AI-Lab-"
-"it, ata në Symbolics ose ata në LMI, vazhduan t'i jepnin ndryshimet e tyre "
-"te sistemi MIT Lisp Machine — edhe pse kontrata nuk e detyronte këtë "
-"hap. Plani i Symbolics-it qe ta thyente njëanësisht këtë bashkëpunim."
-
-# type: Content of: <ol><li>
-#. type: Content of: <ol><li>
-msgid ""
-"Bernie Greenberg says that Dan Weinreb's implementation of Emacs for the "
-"Lisp Machine came before Greenberg's implementation for Multics. I "
-"apologize for the mistake."
-msgstr ""
-"Bernie Greenberg thotë se sendërtimi i Dan Weinreb-it për Emacs në Lisp "
-"Machine kish dal para sendërtimit të Greenberg-ut për Multics. Kërkoj "
-"ndjesë për gabimin."
-
-# type: Content of: <ol><li>
-#. type: Content of: <ol><li>
-msgid ""
"Symbolics at one point protested to MIT that my work, by thwarting their "
"plan, had cost Symbolics a million dollars."
msgstr ""
"Symbolics në një rast protestoi te MIT se puna ime, duke u prishur planin,
i "
"kish kushtuar Symbolics-it një milion dollarë."
-# type: Content of: <ol><li>
-#. type: Content of: <ol><li>
-msgid ""
-"Guy Steele designed the original symmetrical Emacs command set; then he and "
-"I began implementing Emacs (on top of TECO), but after one long joint "
-"development session, Steele began drifting away, so I finished Emacs. "
-"Others particularly including Eugene C. Cicciarelli and Mike McMahon "
-"contributed substantially later on."
-msgstr ""
-"Guy Steele hartoi grupin origjinal të komandave simetrike Emacs; mandej ai "
-"dhe unë zumë të vinim në jetë Emacs-in (përsipër TECO-s), por pas një
"
-"sesioni të gjatë programimi të përbashkët, Steele-i zuri të rrëshqiste
tej, "
-"kështu që Emacs-in e përfundova unë. Të tjerë, përfshi veçanërisht
Eugene "
-"C. Cicciarelli-n dhe Mike McMahon-in, dhanë ndihmesë thelbësore më vonë."
-
# type: Content of: <div>
#. TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.
#. type: Content of: <div>
Index: server/standards/po/README.translations.ca.po
===================================================================
RCS file: /web/www/www/server/standards/po/README.translations.ca.po,v
retrieving revision 1.56
retrieving revision 1.57
diff -u -b -r1.56 -r1.57
--- server/standards/po/README.translations.ca.po 8 Oct 2012 08:30:32
-0000 1.56
+++ server/standards/po/README.translations.ca.po 13 Oct 2012 08:28:12
-0000 1.57
@@ -7,7 +7,7 @@
msgstr ""
"Project-Id-Version: README.translations.ca\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2012-10-08 04:27-0300\n"
+"POT-Creation-Date: 2012-10-13 04:25-0300\n"
"PO-Revision-Date: 2012-09-28 13:05+0200\n"
"Last-Translator: Miquel Puigpelat <address@hidden>\n"
"Language-Team: Catalan <address@hidden>\n"
@@ -663,6 +663,16 @@
msgid ".po files can be edited by using any .po file editor."
msgstr "Els fitxers .po es poden editar amb qualsevol editor de fitxers .po."
+#. type: Content of: <ul><li><p>
+msgid ""
+"Note: Some team members or occasional contributors may find it difficult or "
+"inconvenient to translate using PO files. However, contributions submitted "
+"as plain text format should not be rejected. To encourage the use of PO "
+"files, coordinators can provide those contributors with a simple guide aimed "
+"at people with little computer skills. <a href=\"/server/standards/"
+"translations/po-how-to.html\">Here is an example</a>."
+msgstr ""
+
#. type: Content of: <p>
msgid ""
"We have also implemented notification tools to keep translators informed of "
Index: server/standards/po/README.translations.de.po
===================================================================
RCS file: /web/www/www/server/standards/po/README.translations.de.po,v
retrieving revision 1.36
retrieving revision 1.37
diff -u -b -r1.36 -r1.37
--- server/standards/po/README.translations.de.po 8 Oct 2012 15:04:57
-0000 1.36
+++ server/standards/po/README.translations.de.po 13 Oct 2012 08:28:12
-0000 1.37
@@ -6,7 +6,7 @@
msgid ""
msgstr ""
"Project-Id-Version: README.translations.html\n"
-"POT-Creation-Date: 2012-10-08 04:27-0300\n"
+"POT-Creation-Date: 2012-10-13 04:25-0300\n"
"PO-Revision-Date: 2012-10-08 14:55+0200\n"
"Last-Translator: Joerg Kohne <joeko (AT) online [PUNKT] de>\n"
"Language-Team: German <address@hidden>\n"
@@ -14,6 +14,7 @@
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"Outdated-Since: 2012-10-13 04:25-0300\n"
#. type: Content of: <title>
msgid ""
@@ -682,6 +683,16 @@
msgid ".po files can be edited by using any .po file editor."
msgstr ".po-Dateien können mit jedem PO-Editor bearbeitet werden."
+#. type: Content of: <ul><li><p>
+msgid ""
+"Note: Some team members or occasional contributors may find it difficult or "
+"inconvenient to translate using PO files. However, contributions submitted "
+"as plain text format should not be rejected. To encourage the use of PO "
+"files, coordinators can provide those contributors with a simple guide aimed "
+"at people with little computer skills. <a href=\"/server/standards/"
+"translations/po-how-to.html\">Here is an example</a>."
+msgstr ""
+
#. type: Content of: <p>
msgid ""
"We have also implemented notification tools to keep translators informed of "
Index: server/standards/po/README.translations.fr.po
===================================================================
RCS file: /web/www/www/server/standards/po/README.translations.fr.po,v
retrieving revision 1.87
retrieving revision 1.88
diff -u -b -r1.87 -r1.88
--- server/standards/po/README.translations.fr.po 11 Oct 2012 17:40:08
-0000 1.87
+++ server/standards/po/README.translations.fr.po 13 Oct 2012 08:28:13
-0000 1.88
@@ -9,7 +9,7 @@
msgid ""
msgstr ""
"Project-Id-Version: README.translations.html\n"
-"POT-Creation-Date: 2012-10-08 04:27-0300\n"
+"POT-Creation-Date: 2012-10-13 04:25-0300\n"
"PO-Revision-Date: 2012-10-09 18:22+0200\n"
"Last-Translator: Thérèse Godefroy <godef.th AT free.fr>\n"
"Language-Team: French <address@hidden>\n"
@@ -17,6 +17,7 @@
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"Outdated-Since: 2012-10-13 04:25-0300\n"
"Plural-Forms: \n"
#. type: Content of: <title>
@@ -689,6 +690,16 @@
"Les fichiers .po peuvent être éditées par n'importe quel éditeur de "
"fichiers .po."
+#. type: Content of: <ul><li><p>
+msgid ""
+"Note: Some team members or occasional contributors may find it difficult or "
+"inconvenient to translate using PO files. However, contributions submitted "
+"as plain text format should not be rejected. To encourage the use of PO "
+"files, coordinators can provide those contributors with a simple guide aimed "
+"at people with little computer skills. <a href=\"/server/standards/"
+"translations/po-how-to.html\">Here is an example</a>."
+msgstr ""
+
#. type: Content of: <p>
msgid ""
"We have also implemented notification tools to keep translators informed of "
Index: server/standards/po/README.translations.pot
===================================================================
RCS file: /web/www/www/server/standards/po/README.translations.pot,v
retrieving revision 1.48
retrieving revision 1.49
diff -u -b -r1.48 -r1.49
--- server/standards/po/README.translations.pot 8 Oct 2012 08:30:33 -0000
1.48
+++ server/standards/po/README.translations.pot 13 Oct 2012 08:28:13 -0000
1.49
@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: README.translations.html\n"
-"POT-Creation-Date: 2012-10-08 04:27-0300\n"
+"POT-Creation-Date: 2012-10-13 04:25-0300\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <address@hidden>\n"
"Language-Team: LANGUAGE <address@hidden>\n"
@@ -484,6 +484,17 @@
msgid ".po files can be edited by using any .po file editor."
msgstr ""
+#. type: Content of: <ul><li><p>
+msgid ""
+"Note: Some team members or occasional contributors may find it difficult or "
+"inconvenient to translate using PO files. However, contributions submitted "
+"as plain text format should not be rejected. To encourage the use of PO "
+"files, coordinators can provide those contributors with a simple guide aimed "
+"at people with little computer skills. <a "
+"href=\"/server/standards/translations/po-how-to.html\">Here is an "
+"example</a>."
+msgstr ""
+
#. type: Content of: <p>
msgid ""
"We have also implemented notification tools to keep translators informed of "
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- www gnu/po/rms-lisp.es.po gnu/po/rms-lisp.fr.po...,
GNUN <=