[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www gnu/rms-lisp.fr.html gnu/rms-lisp.ja.html g...
|
From: |
GNUN |
|
Subject: |
www gnu/rms-lisp.fr.html gnu/rms-lisp.ja.html g... |
|
Date: |
Tue, 7 Jul 2020 08:30:00 -0400 (EDT) |
CVSROOT: /web/www
Module name: www
Changes by: GNUN <gnun> 20/07/07 08:30:00
Modified files:
gnu : rms-lisp.fr.html rms-lisp.ja.html
gnu/po : rms-lisp.fr-en.html rms-lisp.ja-en.html
rms-lisp.ja.po rms-lisp.ru-en.html
rms-lisp.ru.po rms-lisp.uk-en.html
rms-lisp.uk.po
philosophy : words-to-avoid.fr.html words-to-avoid.ru.html
philosophy/po : danger-of-software-patents.es.po
danger-of-software-patents.fr.po
danger-of-software-patents.pot
danger-of-software-patents.ru.po
words-to-avoid.fr-en.html
words-to-avoid.ru-en.html words-to-avoid.ru.po
Log message:
Automatic update by GNUnited Nations.
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/rms-lisp.fr.html?cvsroot=www&r1=1.57&r2=1.58
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/rms-lisp.ja.html?cvsroot=www&r1=1.8&r2=1.9
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/rms-lisp.fr-en.html?cvsroot=www&r1=1.38&r2=1.39
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/rms-lisp.ja-en.html?cvsroot=www&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/rms-lisp.ja.po?cvsroot=www&r1=1.14&r2=1.15
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/rms-lisp.ru-en.html?cvsroot=www&r1=1.12&r2=1.13
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/rms-lisp.ru.po?cvsroot=www&r1=1.15&r2=1.16
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/rms-lisp.uk-en.html?cvsroot=www&r1=1.2&r2=1.3
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/rms-lisp.uk.po?cvsroot=www&r1=1.11&r2=1.12
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/words-to-avoid.fr.html?cvsroot=www&r1=1.194&r2=1.195
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/words-to-avoid.ru.html?cvsroot=www&r1=1.102&r2=1.103
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/danger-of-software-patents.es.po?cvsroot=www&r1=1.10&r2=1.11
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/danger-of-software-patents.fr.po?cvsroot=www&r1=1.31&r2=1.32
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/danger-of-software-patents.pot?cvsroot=www&r1=1.22&r2=1.23
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/danger-of-software-patents.ru.po?cvsroot=www&r1=1.18&r2=1.19
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/words-to-avoid.fr-en.html?cvsroot=www&r1=1.111&r2=1.112
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/words-to-avoid.ru-en.html?cvsroot=www&r1=1.85&r2=1.86
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/words-to-avoid.ru.po?cvsroot=www&r1=1.231&r2=1.232
Patches:
Index: gnu/rms-lisp.fr.html
===================================================================
RCS file: /web/www/www/gnu/rms-lisp.fr.html,v
retrieving revision 1.57
retrieving revision 1.58
diff -u -b -r1.57 -r1.58
--- gnu/rms-lisp.fr.html 1 Jul 2020 16:32:17 -0000 1.57
+++ gnu/rms-lisp.fr.html 7 Jul 2020 12:30:00 -0000 1.58
@@ -226,17 +226,17 @@
vérification complète de type. Les ordinateurs ordinaires vous forçaient
typiquement à choisir entre vitesse d'exécution et bonne vérification de
type. Donc oui, vous pouviez avoir un compilateur Lisp et faire fonctionner
-vos programmes rapidement, mais quand ils essayaient d'exécuter <tt>car</tt>
-sur un nombre, ils sortaient des résultats insensés et finissaient par
-planter au bout d'un moment.</p>
+vos programmes rapidement, mais quand ils essayaient d'exécuter
+<code>car</code> sur un nombre, ils sortaient des résultats insensés et
+finissaient par planter au bout d'un moment.</p>
<p>La machine Lisp était capable d'exécuter des instructions presque aussi
vite
que ces autres machines, mais à chaque instruction une instruction
-<tt>car</tt> faisait une vérification de type ; par conséquent, lorsque vous
-essayiez d'obtenir le <tt>car</tt> d'un nombre dans un programme compilé,
-vous obteniez immédiatement une erreur. Nous avons construit la machine et
-fait un système d'exploitation Lisp pour elle. Il était presque entièrement
-écrit en Lisp, à la seule exception des parties écrites dans le
+<code>car</code> faisait une vérification de type ; par conséquent, lorsque
+vous essayiez d'obtenir le <code>car</code> d'un nombre dans un programme
+compilé, vous obteniez immédiatement une erreur. Nous avons construit la
+machine et fait un système d'exploitation Lisp pour elle. Il était presque
+entièrement écrit en Lisp, à la seule exception des parties écrites dans le
microcode. Certaines personnes ont porté de l'intérêt à la fabrication de
la
machine Lisp, ce qui voulait dire qu'elles allaient lancer une entreprise.</p>
@@ -381,17 +381,17 @@
possible.</p>
<p>Par exemple, à ce moment-là , la seule construction de boucle était
-<tt>while</tt>, et elle était extrêmement simple. Il n'existait aucun moyen
-de sortir de cette boucle <tt>while</tt>Â ; vous ne pouviez faire qu'un
-<tt>catch</tt> et un <tt>throw</tt>, ou tester une variable dans la
-boucle. Cela montre à quel point j'essayais de réduire le programme. Nous
-n'avions pas de <tt>caar</tt>, de <tt>cadr</tt>, etc. ; simplifier au
-maximum était l'esprit de GNU Emacs, l'esprit du Lisp d'Emacs, depuis
-l'origine.</p>
+<code>while</code>, et elle était extrêmement simple. Il n'existait aucun
+moyen de sortir de cette boucle <code>while</code>Â ; vous ne pouviez faire
+qu'un <code>catch</code> et un <code>throw</code>, ou tester une variable
+dans la boucle. Cela montre à quel point j'essayais de réduire le
+programme. Nous n'avions pas de <code>caar</code>, de <code>cadr</code>,
+etc. ; simplifier au maximum était l'esprit de GNU Emacs, l'esprit du Lisp
+d'Emacs, depuis l'origine.</p>
<p>Ãvidemment les machines sont plus grosses maintenant et nous ne travaillons
-plus de cette façon. Nous utilisons <tt>caar</tt> et <tt>cadr</tt>, etc., et
-nous pourrions intégrer une autre construction de boucle un de ces
+plus de cette façon. Nous utilisons <code>caar</code> et <code>cadr</code>,
+etc., et nous pourrions intégrer une autre construction de boucle un de ces
jours. Nous avons envie de l'étendre un peu maintenant, mais nous ne voulons
pas l'étendre au niveau du Common Lisp. Il m'est arrivé une fois
d'implémenter le Common Lisp sur la machine Lisp, mais je n'en ai pas été
@@ -639,7 +639,7 @@
<p class="unprintable"><!-- timestamp start -->
Dernière mise à jour :
-$Date: 2020/07/01 16:32:17 $
+$Date: 2020/07/07 12:30:00 $
<!-- timestamp end -->
</p>
Index: gnu/rms-lisp.ja.html
===================================================================
RCS file: /web/www/www/gnu/rms-lisp.ja.html,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- gnu/rms-lisp.ja.html 4 Jul 2020 09:00:35 -0000 1.8
+++ gnu/rms-lisp.ja.html 7 Jul 2020 12:30:00 -0000 1.9
@@ -61,7 +61,7 @@
<p>äºçªç®ã®Emacsããã°ã©ã
ã¯è¿ä»£çãªç¨èªã¨ãã¦ãèªç±ã½ããã¦ã§ã¢ãã§ãããããã¯ãã½ããã¦ã§ã¢ãèªç±ã«ããã¯ã£ããã¨ããæ¿æ²»ãã£ã³ãã¼ã³ã®ä¸é¨ã§ããããã¤ã¦ã®MITã®æ¥ã
ã«ããããã¡ãããããã«ãå
¨å¡ãèªç±ã«ãã®ãã¨ãè¡ãã¹ãã§ãããã¨ããã®ããã®ãã£ã³ãã¼ã³ã®æ¬è³ªã§ãããã½ããã¦ã§ã¢ã§ååããããããã¡ã¨åããã誰ã¨ã§ãä¸ç·ã«åãã®ã§ãããããèªç±ã½ããã¦ã§ã¢éåã®åºç¤ã§ãããããã®çµé¨ãMITã®AIã©ãã§éãããæ®ãããã§ãã人é¡ã®ç¥èã«ã¤ãã¦åãã誰ããããã«ä½¿ããã¨ãããã«äººé¡ã®ç¥èãåºãããã¨ã«ã¤ãã¦é»ãã§åæ¢ããã®ã§ãªãã¦ã</p>
-<p>å½æãLispç¨ã§ã¯ãªãã»ãã®ã³ã³ãã¥ã¼ã¿ã¨ã
ãããåæ§ãªå¤æ®µã®ç¯å²ã®ã³ã³ãã¥ã¼ã¿ã製ä½ãããã¹ã¦ã®å½ä»¤ã§å®å
¨ãªåãã§ãã¯ããã¤ã¤ããLispãã»ãã®ã³ã³ãã¥ã¼ã¿ãããã
ãã¶éãå®è¡ããäºãå¯è½ã§ãããé常ã®ã³ã³ãã¥ã¼ã¿ã§ã¯ãå®è¡é度ã¨è¯ãåãã§ãã¯ã®ã©ã¡ããã®é¸æãè¿«ããã¾ããã§ããããLispã³ã³ãã¤ã©ã§ããã°ã©ã
ãéãå®è¡ãããã¨ã¯ã§ãã¾ãããæ°ã«å¯¾ãã¦<tt>car</tt>ãåããã¨ããã¨ãã¯ãæå³ã®ãªãçµæãåºããçµå±ã¯ã©ããã§ã¯ã©ãã·ã¥ãã¾ãã</p>
+<p>å½æãLispç¨ã§ã¯ãªãã»ãã®ã³ã³ãã¥ã¼ã¿ã¨ã
ãããåæ§ãªå¤æ®µã®ç¯å²ã®ã³ã³ãã¥ã¼ã¿ã製ä½ãããã¹ã¦ã®å½ä»¤ã§å®å
¨ãªåãã§ãã¯ããã¤ã¤ããLispãã»ãã®ã³ã³ãã¥ã¼ã¿ãããã
ãã¶éãå®è¡ããäºãå¯è½ã§ãããé常ã®ã³ã³ãã¥ã¼ã¿ã§ã¯ãå®è¡é度ã¨è¯ãåãã§ãã¯ã®ã©ã¡ããã®é¸æãè¿«ããã¾ããã§ããããLispã³ã³ãã¤ã©ã§ããã°ã©ã
ãéãå®è¡ãããã¨ã¯ã§ãã¾ãããæ°ã«å¯¾ãã¦<code>car</code>ãåããã¨ããã¨ãã¯ãæå³ã®ãªãçµæãåºããçµå±ã¯ã©ããã§ã¯ã©ãã·ã¥ãã¾ãã</p>
<p>Lispãã·ã³ã¯ãã»ãã®ãã·ã³ã¨åããããéãå½ä»¤ãå®è¡ã§ãã¾ããããããããã®å½ä»¤(ãã¨ãã°ãcarå½ä»¤)ã¯ãã¼ã¿ã®åãã§ãã¯ãããã®ã§ãã³ã³ãã¤ã«ãããããã°ã©ã
ã§æ°ã«å¯¾ãã¦carãåããã¨ããã¨ãå³åº§ã«ã¨ã©ã¼ã¨ãªãã¾ããããããã¡ã¯ãã·ã³ãæ§ç¯ããããã«Lispãªãã¬ã¼ãã£ã³ã°ã»ã·ã¹ãã
ãè¼ãã¾ãããããã¯ã»ã¨ãã©å
¨ä½ãLispã§æ¸ããã¦ãã¾ãããä¸é¨ããã¤ã¯ãã³ã¼ãã§æ¸ããããã®ãä¾å¤ã¨ãã¦ããã
ãã§ãã人ã
ã¯ããã製é
ããäºã«é¢å¿ã示ããããã¯ãä¼ç¤¾ãéå§ããã¹ããã¨ãæå³ãã¾ããã</p>
@@ -225,7 +225,7 @@
<p class="unprintable"><!-- timestamp start -->
æçµæ´æ°:
-$Date: 2020/07/04 09:00:35 $
+$Date: 2020/07/07 12:30:00 $
<!-- timestamp end -->
</p>
Index: gnu/po/rms-lisp.fr-en.html
===================================================================
RCS file: /web/www/www/gnu/po/rms-lisp.fr-en.html,v
retrieving revision 1.38
retrieving revision 1.39
diff -u -b -r1.38 -r1.39
--- gnu/po/rms-lisp.fr-en.html 1 Jul 2020 16:32:17 -0000 1.38
+++ gnu/po/rms-lisp.fr-en.html 7 Jul 2020 12:30:00 -0000 1.39
@@ -215,7 +215,7 @@
in every operation as well. Ordinary computers typically forced you to
choose between execution speed and good typechecking. So yes, you could
have a Lisp compiler and run your programs fast, but when they tried to
-take <tt>car</tt> of a number, it got nonsensical results and eventually
+take <code>car</code> of a number, it got nonsensical results and eventually
crashed at some point.</p>
<p>The Lisp machine was able to execute instructions about as fast as
@@ -583,7 +583,7 @@
<p class="unprintable">Updated:
<!-- timestamp start -->
-$Date: 2020/07/01 16:32:17 $
+$Date: 2020/07/07 12:30:00 $
<!-- timestamp end -->
</p>
</div>
Index: gnu/po/rms-lisp.ja-en.html
===================================================================
RCS file: /web/www/www/gnu/po/rms-lisp.ja-en.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- gnu/po/rms-lisp.ja-en.html 4 Jul 2020 09:00:36 -0000 1.4
+++ gnu/po/rms-lisp.ja-en.html 7 Jul 2020 12:30:00 -0000 1.5
@@ -215,7 +215,7 @@
in every operation as well. Ordinary computers typically forced you to
choose between execution speed and good typechecking. So yes, you could
have a Lisp compiler and run your programs fast, but when they tried to
-take <tt>car</tt> of a number, it got nonsensical results and eventually
+take <code>car</code> of a number, it got nonsensical results and eventually
crashed at some point.</p>
<p>The Lisp machine was able to execute instructions about as fast as
@@ -583,7 +583,7 @@
<p class="unprintable">Updated:
<!-- timestamp start -->
-$Date: 2020/07/04 09:00:36 $
+$Date: 2020/07/07 12:30:00 $
<!-- timestamp end -->
</p>
</div>
Index: gnu/po/rms-lisp.ja.po
===================================================================
RCS file: /web/www/www/gnu/po/rms-lisp.ja.po,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -b -r1.14 -r1.15
--- gnu/po/rms-lisp.ja.po 7 Jul 2020 12:08:30 -0000 1.14
+++ gnu/po/rms-lisp.ja.po 7 Jul 2020 12:30:00 -0000 1.15
@@ -15,7 +15,6 @@
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
-"X-Outdated-Since: 2020-07-07 11:55+0000\n"
#. type: Content of: <title>
msgid ""
@@ -438,8 +437,8 @@
"ã¿ã製ä½ãããã¹ã¦ã®å½ä»¤ã§å®å
¨ãªåãã§ãã¯ããã¤ã¤ããLispãã»ãã®ã³ã³ãã¥ã¼"
"ã¿ãããã
ãã¶éãå®è¡ããäºãå¯è½ã§ãããé常ã®ã³ã³ãã¥ã¼ã¿ã§ã¯ãå®è¡é度ã¨"
"è¯ãåãã§ãã¯ã®ã©ã¡ããã®é¸æãè¿«ããã¾ããã§ããããLispã³ã³ãã¤ã©ã§ããã°"
-"ã©ã
ãéãå®è¡ãããã¨ã¯ã§ãã¾ãããæ°ã«å¯¾ãã¦<code>car</code>ãåããã¨ããã¨ã"
-"ã¯ãæå³ã®ãªãçµæãåºããçµå±ã¯ã©ããã§ã¯ã©ãã·ã¥ãã¾ãã"
+"ã©ã
ãéãå®è¡ãããã¨ã¯ã§ãã¾ãããæ°ã«å¯¾ãã¦<code>car</code>ãåããã¨ãã"
+"ã¨ãã¯ãæå³ã®ãªãçµæãåºããçµå±ã¯ã©ããã§ã¯ã©ãã·ã¥ãã¾ãã"
#. type: Content of: <p>
msgid ""
Index: gnu/po/rms-lisp.ru-en.html
===================================================================
RCS file: /web/www/www/gnu/po/rms-lisp.ru-en.html,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -b -r1.12 -r1.13
--- gnu/po/rms-lisp.ru-en.html 1 Jul 2020 17:02:57 -0000 1.12
+++ gnu/po/rms-lisp.ru-en.html 7 Jul 2020 12:30:00 -0000 1.13
@@ -215,7 +215,7 @@
in every operation as well. Ordinary computers typically forced you to
choose between execution speed and good typechecking. So yes, you could
have a Lisp compiler and run your programs fast, but when they tried to
-take <tt>car</tt> of a number, it got nonsensical results and eventually
+take <code>car</code> of a number, it got nonsensical results and eventually
crashed at some point.</p>
<p>The Lisp machine was able to execute instructions about as fast as
@@ -583,7 +583,7 @@
<p class="unprintable">Updated:
<!-- timestamp start -->
-$Date: 2020/07/01 17:02:57 $
+$Date: 2020/07/07 12:30:00 $
<!-- timestamp end -->
</p>
</div>
Index: gnu/po/rms-lisp.ru.po
===================================================================
RCS file: /web/www/www/gnu/po/rms-lisp.ru.po,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -b -r1.15 -r1.16
--- gnu/po/rms-lisp.ru.po 7 Jul 2020 12:02:32 -0000 1.15
+++ gnu/po/rms-lisp.ru.po 7 Jul 2020 12:30:00 -0000 1.16
@@ -15,7 +15,6 @@
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
-"X-Outdated-Since: 2020-07-07 11:55+0000\n"
#. type: Content of: <title>
msgid ""
@@ -453,23 +452,6 @@
"и далÑнейÑÐµÐ¼Ñ ÑаÑпÑоÑÑÑанениÑ
ÑеловеÑеÑкого знаниÑ."
#. type: Content of: <p>
-# | At the time, you could make a computer that was about the same price range
-# | as other computers that weren't meant for Lisp, except that it would run
-# | Lisp much faster than they would, and with full type checking in every
-# | operation as well. Ordinary computers typically forced you to choose
-# | between execution speed and good typechecking. So yes, you could have a
-# | Lisp compiler and run your programs fast, but when they tried to take
-# | [-<tt>car</tt>-] {+<code>car</code>+} of a number, it got nonsensical
-# | results and eventually crashed at some point.
-#| msgid ""
-#| "At the time, you could make a computer that was about the same price "
-#| "range as other computers that weren't meant for Lisp, except that it "
-#| "would run Lisp much faster than they would, and with full type checking "
-#| "in every operation as well. Ordinary computers typically forced you to "
-#| "choose between execution speed and good typechecking. So yes, you could "
-#| "have a Lisp compiler and run your programs fast, but when they tried to "
-#| "take <tt>car</tt> of a number, it got nonsensical results and eventually "
-#| "crashed at some point."
msgid ""
"At the time, you could make a computer that was about the same price range "
"as other computers that weren't meant for Lisp, except that it would run "
Index: gnu/po/rms-lisp.uk-en.html
===================================================================
RCS file: /web/www/www/gnu/po/rms-lisp.uk-en.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- gnu/po/rms-lisp.uk-en.html 4 Jul 2020 09:00:36 -0000 1.2
+++ gnu/po/rms-lisp.uk-en.html 7 Jul 2020 12:30:00 -0000 1.3
@@ -215,7 +215,7 @@
in every operation as well. Ordinary computers typically forced you to
choose between execution speed and good typechecking. So yes, you could
have a Lisp compiler and run your programs fast, but when they tried to
-take <tt>car</tt> of a number, it got nonsensical results and eventually
+take <code>car</code> of a number, it got nonsensical results and eventually
crashed at some point.</p>
<p>The Lisp machine was able to execute instructions about as fast as
@@ -583,7 +583,7 @@
<p class="unprintable">Updated:
<!-- timestamp start -->
-$Date: 2020/07/04 09:00:36 $
+$Date: 2020/07/07 12:30:00 $
<!-- timestamp end -->
</p>
</div>
Index: gnu/po/rms-lisp.uk.po
===================================================================
RCS file: /web/www/www/gnu/po/rms-lisp.uk.po,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- gnu/po/rms-lisp.uk.po 7 Jul 2020 12:08:30 -0000 1.11
+++ gnu/po/rms-lisp.uk.po 7 Jul 2020 12:30:00 -0000 1.12
@@ -15,7 +15,6 @@
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
-"X-Outdated-Since: 2020-07-07 11:55+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"
Index: philosophy/words-to-avoid.fr.html
===================================================================
RCS file: /web/www/www/philosophy/words-to-avoid.fr.html,v
retrieving revision 1.194
retrieving revision 1.195
diff -u -b -r1.194 -r1.195
--- philosophy/words-to-avoid.fr.html 7 Jul 2020 09:59:54 -0000 1.194
+++ philosophy/words-to-avoid.fr.html 7 Jul 2020 12:30:00 -0000 1.195
@@ -1082,8 +1082,8 @@
d'un programme privateur particulier servant à faire des présentations. Dans
l'intérêt de votre liberté, vous ne devez utiliser que du logiciel libre
pour les vôtres â qui par conséquent ne seront pas des « PowerPoint ».
Parmi
-les choix recommandés, il y a la classe <code>beamer</code> de LaTeX, et
-« Impress » de LibreOffice.</p>
+les choix recommandés, il y a la classe <code>beamer</code> de LaTeX et
+LibreOffice Impress.</p>
<!-- GNUN-SORT-NEXT-ITEM -->
<!-- GNUN-SORT-BEGIN-KEY -->
@@ -1482,7 +1482,7 @@
<p class="unprintable"><!-- timestamp start -->
Dernière mise à jour :
-$Date: 2020/07/07 09:59:54 $
+$Date: 2020/07/07 12:30:00 $
<!-- timestamp end -->
</p>
Index: philosophy/words-to-avoid.ru.html
===================================================================
RCS file: /web/www/www/philosophy/words-to-avoid.ru.html,v
retrieving revision 1.102
retrieving revision 1.103
diff -u -b -r1.102 -r1.103
--- philosophy/words-to-avoid.ru.html 7 Jul 2020 09:59:54 -0000 1.102
+++ philosophy/words-to-avoid.ru.html 7 Jul 2020 12:30:00 -0000 1.103
@@ -1171,7 +1171,7 @@
ÑÐ²Ð¾Ð±Ð¾Ð´Ñ Ð²Ð°Ð¼ Ð´Ð»Ñ Ð¿Ð¾Ð´Ð³Ð¾Ñовки ÑвоиÑ
докладов
ÑледÑÐµÑ Ð¿ÑименÑÑÑ ÑолÑко ÑвободнÑе
пÑогÑÐ°Ð¼Ð¼Ñ — Ñо еÑÑÑ <em>не PowerPoint</em>. Ð
екомендÑÑÑÑÑ Ñакие
ваÑианÑÑ, как клаÑÑ <code>beamer</code> из ÑиÑÑемÑ
LaTeX или пÑогÑамма
-Impress из пакеÑа LibreOffice.org.</p>
+Impress из пакеÑа LibreOffice.</p>
<!-- GNUN-SORT-NEXT-ITEM -->
<!-- GNUN-SORT-BEGIN-KEY -->
@@ -1558,7 +1558,7 @@
<p class="unprintable"><!-- timestamp start -->
Ðбновлено:
-$Date: 2020/07/07 09:59:54 $
+$Date: 2020/07/07 12:30:00 $
<!-- timestamp end -->
</p>
Index: philosophy/po/danger-of-software-patents.es.po
===================================================================
RCS file: /web/www/www/philosophy/po/danger-of-software-patents.es.po,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -b -r1.10 -r1.11
--- philosophy/po/danger-of-software-patents.es.po 7 Jul 2020 09:49:13
-0000 1.10
+++ philosophy/po/danger-of-software-patents.es.po 7 Jul 2020 12:30:00
-0000 1.11
@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: danger-of-software-patents.html\n"
-"POT-Creation-Date: 2020-07-01 15:25+0000\n"
+"POT-Creation-Date: 2020-07-07 12:25+0000\n"
"PO-Revision-Date: 2020-07-07 11:32+0200\n"
"Last-Translator: Javier Fdez. Retenaga <jfrtnaga@gnu.org>\n"
"Language-Team: Spanish <www-es-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-07 12:25+0000\n"
"Plural-Forms: nplurals=2; plural=(n!=1);\n"
"X-Generator: Poedit 2.2.1\n"
@@ -1103,13 +1104,36 @@
"resultado."
#. type: Content of: <dl><dd><p>
+# | You see, if somebody has made a machine that does something once, and
+# | somebody else designs a machine that will do the same thing, but N times,
+# | for us that's a [-<tt>for</tt>-loop,-] {+<code>for</code>-loop,+} but for
+# | the Patent Office that's an invention. If there are machines that can do
+# | A, and there are machines that can do B, and somebody designs a machine
+# | that can do A or B, for us that's an [-<tt>if-then-else</tt>-]
+# | {+<code>if-then-else</code>+} statement, but for the Patent Office that's
+# | an invention. So they have very low standards, and they follow those
+# | standards; and the result is patents that look absurd and trivial to us.
+# | Whether they're legally valid I can't say. But every programmer who sees
+# | them laughs.
+#, fuzzy
+#| msgid ""
+#| "You see, if somebody has made a machine that does something once, and "
+#| "somebody else designs a machine that will do the same thing, but N times, "
+#| "for us that's a <tt>for</tt>-loop, but for the Patent Office that's an "
+#| "invention. If there are machines that can do A, and there are machines "
+#| "that can do B, and somebody designs a machine that can do A or B, for us "
+#| "that's an <tt>if-then-else</tt> statement, but for the Patent Office "
+#| "that's an invention. So they have very low standards, and they follow "
+#| "those standards; and the result is patents that look absurd and trivial "
+#| "to us. Whether they're legally valid I can't say. But every programmer "
+#| "who sees them laughs."
msgid ""
"You see, if somebody has made a machine that does something once, and "
"somebody else designs a machine that will do the same thing, but N times, "
-"for us that's a <tt>for</tt>-loop, but for the Patent Office that's an "
+"for us that's a <code>for</code>-loop, but for the Patent Office that's an "
"invention. If there are machines that can do A, and there are machines that "
"can do B, and somebody designs a machine that can do A or B, for us that's "
-"an <tt>if-then-else</tt> statement, but for the Patent Office that's an "
+"an <code>if-then-else</code> statement, but for the Patent Office that's an "
"invention. So they have very low standards, and they follow those "
"standards; and the result is patents that look absurd and trivial to us. "
"Whether they're legally valid I can't say. But every programmer who sees "
Index: philosophy/po/danger-of-software-patents.fr.po
===================================================================
RCS file: /web/www/www/philosophy/po/danger-of-software-patents.fr.po,v
retrieving revision 1.31
retrieving revision 1.32
diff -u -b -r1.31 -r1.32
--- philosophy/po/danger-of-software-patents.fr.po 1 Jul 2020 16:13:45
-0000 1.31
+++ philosophy/po/danger-of-software-patents.fr.po 7 Jul 2020 12:30:00
-0000 1.32
@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: danger-of-software-patents.html\n"
-"POT-Creation-Date: 2020-07-01 15:25+0000\n"
+"POT-Creation-Date: 2020-07-07 12:25+0000\n"
"PO-Revision-Date: 2020-07-01 18:13+0200\n"
"Last-Translator: Thérèse Godefroy <godef.th AT free.fr>\n"
"Language-Team: French <trad-gnu@april.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-07 12:25+0000\n"
"Plural-Forms: \n"
"X-Generator: Gtranslator 2.91.5\n"
@@ -1124,13 +1125,36 @@
"et que ces règles aboutissent à ce résultat."
#. type: Content of: <dl><dd><p>
+# | You see, if somebody has made a machine that does something once, and
+# | somebody else designs a machine that will do the same thing, but N times,
+# | for us that's a [-<tt>for</tt>-loop,-] {+<code>for</code>-loop,+} but for
+# | the Patent Office that's an invention. If there are machines that can do
+# | A, and there are machines that can do B, and somebody designs a machine
+# | that can do A or B, for us that's an [-<tt>if-then-else</tt>-]
+# | {+<code>if-then-else</code>+} statement, but for the Patent Office that's
+# | an invention. So they have very low standards, and they follow those
+# | standards; and the result is patents that look absurd and trivial to us.
+# | Whether they're legally valid I can't say. But every programmer who sees
+# | them laughs.
+#, fuzzy
+#| msgid ""
+#| "You see, if somebody has made a machine that does something once, and "
+#| "somebody else designs a machine that will do the same thing, but N times, "
+#| "for us that's a <tt>for</tt>-loop, but for the Patent Office that's an "
+#| "invention. If there are machines that can do A, and there are machines "
+#| "that can do B, and somebody designs a machine that can do A or B, for us "
+#| "that's an <tt>if-then-else</tt> statement, but for the Patent Office "
+#| "that's an invention. So they have very low standards, and they follow "
+#| "those standards; and the result is patents that look absurd and trivial "
+#| "to us. Whether they're legally valid I can't say. But every programmer "
+#| "who sees them laughs."
msgid ""
"You see, if somebody has made a machine that does something once, and "
"somebody else designs a machine that will do the same thing, but N times, "
-"for us that's a <tt>for</tt>-loop, but for the Patent Office that's an "
+"for us that's a <code>for</code>-loop, but for the Patent Office that's an "
"invention. If there are machines that can do A, and there are machines that "
"can do B, and somebody designs a machine that can do A or B, for us that's "
-"an <tt>if-then-else</tt> statement, but for the Patent Office that's an "
+"an <code>if-then-else</code> statement, but for the Patent Office that's an "
"invention. So they have very low standards, and they follow those "
"standards; and the result is patents that look absurd and trivial to us. "
"Whether they're legally valid I can't say. But every programmer who sees "
Index: philosophy/po/danger-of-software-patents.pot
===================================================================
RCS file: /web/www/www/philosophy/po/danger-of-software-patents.pot,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -b -r1.22 -r1.23
--- philosophy/po/danger-of-software-patents.pot 1 Jul 2020 15:35:34
-0000 1.22
+++ philosophy/po/danger-of-software-patents.pot 7 Jul 2020 12:30:00
-0000 1.23
@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: danger-of-software-patents.html\n"
-"POT-Creation-Date: 2020-07-01 15:25+0000\n"
+"POT-Creation-Date: 2020-07-07 12: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"
@@ -695,10 +695,10 @@
msgid ""
"You see, if somebody has made a machine that does something once, and "
"somebody else designs a machine that will do the same thing, but N times, "
-"for us that's a <tt>for</tt>-loop, but for the Patent Office that's an "
+"for us that's a <code>for</code>-loop, but for the Patent Office that's an "
"invention. If there are machines that can do A, and there are machines that "
"can do B, and somebody designs a machine that can do A or B, for us that's "
-"an <tt>if-then-else</tt> statement, but for the Patent Office that's an "
+"an <code>if-then-else</code> statement, but for the Patent Office that's an "
"invention. So they have very low standards, and they follow those "
"standards; and the result is patents that look absurd and trivial to us. "
"Whether they're legally valid I can't say. But every programmer who sees "
Index: philosophy/po/danger-of-software-patents.ru.po
===================================================================
RCS file: /web/www/www/philosophy/po/danger-of-software-patents.ru.po,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -b -r1.18 -r1.19
--- philosophy/po/danger-of-software-patents.ru.po 1 Jul 2020 17:03:01
-0000 1.18
+++ philosophy/po/danger-of-software-patents.ru.po 7 Jul 2020 12:30:00
-0000 1.19
@@ -8,7 +8,7 @@
msgid ""
msgstr ""
"Project-Id-Version: danger-of-software-patents.html\n"
-"POT-Creation-Date: 2020-07-01 15:25+0000\n"
+"POT-Creation-Date: 2020-07-07 12:25+0000\n"
"PO-Revision-Date: 2020-07-01 17:51+0000\n"
"Last-Translator: Ineiev <ineiev@gnu.org>\n"
"Language-Team: Russian <www-ru-list@gnu.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-07 12:25+0000\n"
#. type: Content of: <title>
msgid "The Danger of Software Patents - GNU Project - Free Software Foundation"
@@ -1111,13 +1112,36 @@
"ÑезÑлÑÑаÑÑ."
#. type: Content of: <dl><dd><p>
+# | You see, if somebody has made a machine that does something once, and
+# | somebody else designs a machine that will do the same thing, but N times,
+# | for us that's a [-<tt>for</tt>-loop,-] {+<code>for</code>-loop,+} but for
+# | the Patent Office that's an invention. If there are machines that can do
+# | A, and there are machines that can do B, and somebody designs a machine
+# | that can do A or B, for us that's an [-<tt>if-then-else</tt>-]
+# | {+<code>if-then-else</code>+} statement, but for the Patent Office that's
+# | an invention. So they have very low standards, and they follow those
+# | standards; and the result is patents that look absurd and trivial to us.
+# | Whether they're legally valid I can't say. But every programmer who sees
+# | them laughs.
+#, fuzzy
+#| msgid ""
+#| "You see, if somebody has made a machine that does something once, and "
+#| "somebody else designs a machine that will do the same thing, but N times, "
+#| "for us that's a <tt>for</tt>-loop, but for the Patent Office that's an "
+#| "invention. If there are machines that can do A, and there are machines "
+#| "that can do B, and somebody designs a machine that can do A or B, for us "
+#| "that's an <tt>if-then-else</tt> statement, but for the Patent Office "
+#| "that's an invention. So they have very low standards, and they follow "
+#| "those standards; and the result is patents that look absurd and trivial "
+#| "to us. Whether they're legally valid I can't say. But every programmer "
+#| "who sees them laughs."
msgid ""
"You see, if somebody has made a machine that does something once, and "
"somebody else designs a machine that will do the same thing, but N times, "
-"for us that's a <tt>for</tt>-loop, but for the Patent Office that's an "
+"for us that's a <code>for</code>-loop, but for the Patent Office that's an "
"invention. If there are machines that can do A, and there are machines that "
"can do B, and somebody designs a machine that can do A or B, for us that's "
-"an <tt>if-then-else</tt> statement, but for the Patent Office that's an "
+"an <code>if-then-else</code> statement, but for the Patent Office that's an "
"invention. So they have very low standards, and they follow those "
"standards; and the result is patents that look absurd and trivial to us. "
"Whether they're legally valid I can't say. But every programmer who sees "
Index: philosophy/po/words-to-avoid.fr-en.html
===================================================================
RCS file: /web/www/www/philosophy/po/words-to-avoid.fr-en.html,v
retrieving revision 1.111
retrieving revision 1.112
diff -u -b -r1.111 -r1.112
--- philosophy/po/words-to-avoid.fr-en.html 7 Jul 2020 09:59:54 -0000
1.111
+++ philosophy/po/words-to-avoid.fr-en.html 7 Jul 2020 12:30:00 -0000
1.112
@@ -1065,7 +1065,7 @@
one particular proprietary program to make presentations. For your
freedom's sake, you should use only free software to make your
presentations—which means, <em>not PowerPoint</em>. Recommended
-options include LaTeX's <code>beamer</code> class and LibreOffice.org's
+options include LaTeX's <code>beamer</code> class and LibreOffice
Impress.</p>
<!-- GNUN-SORT-NEXT-ITEM -->
@@ -1410,7 +1410,7 @@
<p class="unprintable">Updated:
<!-- timestamp start -->
-$Date: 2020/07/07 09:59:54 $
+$Date: 2020/07/07 12:30:00 $
<!-- timestamp end -->
</p>
</div>
Index: philosophy/po/words-to-avoid.ru-en.html
===================================================================
RCS file: /web/www/www/philosophy/po/words-to-avoid.ru-en.html,v
retrieving revision 1.85
retrieving revision 1.86
diff -u -b -r1.85 -r1.86
--- philosophy/po/words-to-avoid.ru-en.html 7 Jul 2020 09:59:54 -0000
1.85
+++ philosophy/po/words-to-avoid.ru-en.html 7 Jul 2020 12:30:00 -0000
1.86
@@ -1065,7 +1065,7 @@
one particular proprietary program to make presentations. For your
freedom's sake, you should use only free software to make your
presentations—which means, <em>not PowerPoint</em>. Recommended
-options include LaTeX's <code>beamer</code> class and LibreOffice.org's
+options include LaTeX's <code>beamer</code> class and LibreOffice
Impress.</p>
<!-- GNUN-SORT-NEXT-ITEM -->
@@ -1410,7 +1410,7 @@
<p class="unprintable">Updated:
<!-- timestamp start -->
-$Date: 2020/07/07 09:59:54 $
+$Date: 2020/07/07 12:30:00 $
<!-- timestamp end -->
</p>
</div>
Index: philosophy/po/words-to-avoid.ru.po
===================================================================
RCS file: /web/www/www/philosophy/po/words-to-avoid.ru.po,v
retrieving revision 1.231
retrieving revision 1.232
diff -u -b -r1.231 -r1.232
--- philosophy/po/words-to-avoid.ru.po 7 Jul 2020 12:02:32 -0000 1.231
+++ philosophy/po/words-to-avoid.ru.po 7 Jul 2020 12:30:00 -0000 1.232
@@ -15,7 +15,6 @@
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
-"X-Outdated-Since: 2020-07-07 11:55+0000\n"
#. type: Content of: <title>
msgid ""
@@ -2172,20 +2171,6 @@
msgstr "“<span xml:lang=\"en\" lang=\"en\">PowerPoint</span>”"
#. type: Content of: <p>
-# | Please avoid using the term “PowerPoint” to mean any kind of
-# | slide presentation. “PowerPoint” is just the name of one
-# | particular proprietary program to make presentations. For your freedom's
-# | sake, you should use only free software to make your
-# | presentations—which means, <em>not PowerPoint</em>. Recommended
-# | options include LaTeX's <code>beamer</code> class and
-# | [-LibreOffice.org's-] {+LibreOffice+} Impress.
-#| msgid ""
-#| "Please avoid using the term “PowerPoint” to mean any kind of "
-#| "slide presentation. “PowerPoint” is just the name of one "
-#| "particular proprietary program to make presentations. For your freedom's "
-#| "sake, you should use only free software to make your presentations—"
-#| "which means, <em>not PowerPoint</em>. Recommended options include "
-#| "LaTeX's <code>beamer</code> class and LibreOffice.org's Impress."
msgid ""
"Please avoid using the term “PowerPoint” to mean any kind of "
"slide presentation. “PowerPoint” is just the name of one "
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- www gnu/rms-lisp.fr.html gnu/rms-lisp.ja.html g...,
GNUN <=