[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www/philosophy linux-gnu-freedom.fr.html po/lin...
|
From: |
GNUN |
|
Subject: |
www/philosophy linux-gnu-freedom.fr.html po/lin... |
|
Date: |
Mon, 18 Oct 2021 17:32:17 -0400 (EDT) |
CVSROOT: /web/www
Module name: www
Changes by: GNUN <gnun> 21/10/18 17:32:17
Modified files:
philosophy : linux-gnu-freedom.fr.html
philosophy/po : linux-gnu-freedom.fr-en.html
rms-nyu-2001-transcript.cs.po
rms-nyu-2001-transcript.fr.po
rms-nyu-2001-transcript.pl.po
rms-nyu-2001-transcript.pot
rms-nyu-2001-transcript.ru.po
rms-nyu-2001-transcript.tr.po
Log message:
Automatic update by GNUnited Nations.
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/linux-gnu-freedom.fr.html?cvsroot=www&r1=1.72&r2=1.73
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/linux-gnu-freedom.fr-en.html?cvsroot=www&r1=1.42&r2=1.43
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/rms-nyu-2001-transcript.cs.po?cvsroot=www&r1=1.3&r2=1.4
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/rms-nyu-2001-transcript.fr.po?cvsroot=www&r1=1.18&r2=1.19
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/rms-nyu-2001-transcript.pl.po?cvsroot=www&r1=1.11&r2=1.12
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/rms-nyu-2001-transcript.pot?cvsroot=www&r1=1.5&r2=1.6
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/rms-nyu-2001-transcript.ru.po?cvsroot=www&r1=1.10&r2=1.11
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/rms-nyu-2001-transcript.tr.po?cvsroot=www&r1=1.19&r2=1.20
Patches:
Index: linux-gnu-freedom.fr.html
===================================================================
RCS file: /web/www/www/philosophy/linux-gnu-freedom.fr.html,v
retrieving revision 1.72
retrieving revision 1.73
diff -u -b -r1.72 -r1.73
--- linux-gnu-freedom.fr.html 12 Sep 2021 10:04:28 -0000 1.72
+++ linux-gnu-freedom.fr.html 18 Oct 2021 21:32:16 -0000 1.73
@@ -11,7 +11,7 @@
<meta http-equiv="Keywords"
content="GNU, FSF, Free Software Foundation, Linux, liberté, logiciel,
pouvoir,
droits, Richard Stallman, rms, SIGLINUX, Joe Barr" />
-<meta http-equiv="Description" content="Dans cet essai, « Linux, GNU et
liberté », Richard M. Stallman répond au
+<meta http-equiv="Description" content="Dans cet essai, «â¯Linux, GNU et
libertéâ¯Â», Richard M. Stallman répond au
rapport de Joe Barr sur les négociations avec le groupe d'utilisateurs Linux
de Austin." />
@@ -31,12 +31,12 @@
de Joe Barr</a> a critiqué mes négociations avec SIGLINUX, je voudrais faire
une mise au point sur ce qui s'est vraiment passé, et donner mes raisons.</p>
<p>
- Quand SIGLINUX m'a invité à parler, il s'agissait d'un « groupe
-d'utilisateurs de Linux » (LUG), un groupe d'utilisateurs du système
-GNU/Linux qui appelle l'ensemble du système d'exploitation « Linux ». J'ai
+ Quand SIGLINUX m'a invité à parler, il s'agissait d'un «â¯groupe
+d'utilisateurs de Linuxâ¯Â» (LUG), un groupe d'utilisateurs du système
+GNU/Linux qui appelle l'ensemble du système d'exploitation «â¯Linuxâ¯Â».
J'ai
alors répondu poliment que s'ils voulaient qu'une personne du projet GNU
fasse un discours pour eux, ils devaient traiter le projet GNU correctement
-et appeler le système « GNU/Linux ». Ce système est une variante de GNU
et
+et appeler le système «â¯GNU/Linuxâ¯Â». Ce système est une variante de
GNU et
le projet GNU en est le principal développeur, aussi la politesse veut-elle
qu'on lui donne le nom que nous avons choisi. à moins de raisons impérieuses
justifiant une exception, je refuse habituellement de faire des discours
@@ -47,21 +47,21 @@
Par la suite, Jeff Strunk de SIGLINUX a essayé de changer la politique du
groupe et a demandé à la FSF de l'inscrire sur notre page de groupes
d'utilisateurs GNU/Linux. Notre webmestre lui a répondu que nous ne
-l'inscririons pas sous le nom « SIGLINUX », ce nom impliquant que l'objet
de
-ce groupe était Linux. Strunk a proposé de prendre le nom de « SIGFREEÂ
», et
+l'inscririons pas sous le nom «â¯SIGLINUXâ¯Â», ce nom impliquant que
l'objet de
+ce groupe était Linux. Strunk a proposé de prendre le nom de
«â¯SIGFREEâ¯Â», et
notre webmestre a approuvé (l'article de Barr a dit que nous avions rejeté
cette proposition). Quoi qu'il en soit, le groupe décida finalement de
-garder « SIGLINUX ».</p>
+garder «â¯SIGLINUXâ¯Â».</p>
<p>
à ce moment-là , on me redemanda mon avis et je suggérai de réfléchir Ã
d'autres noms possibles. Ils ont le choix entre beaucoup de noms qui
-n'appellent pas le système « Linux » et j'espère qu'ils en trouveront un
qui
+n'appellent pas le système «â¯Linuxâ¯Â» et j'espère qu'ils en trouveront
un qui
leur plaise. Voilà où en sont les choses, pour autant que je sache.</p>
<p>
Est-il vrai, comme l'écrit Barr, que certains voient dans ces actions une
-« utilisation de la force » comparable au pouvoir du monopole de
Microsoft ?
+«â¯utilisation de la forceâ¯Â» comparable au pouvoir du monopole de
Microsoft�
Probablement. Décliner une invitation n'est pas de la coercition, mais les
-gens qui sont déterminés à croire que le système entier est « Linux »
+gens qui sont déterminés à croire que le système entier est «â¯Linuxâ¯Â»
développent parfois une vision étonnamment déformée. Pour justifier ce nom,
ils prennent des vessies pour des lanternes. Si vous pouvez ignorer les
faits et croire que Linus Torvalds a développé l'ensemble du système en
@@ -70,42 +70,42 @@
fait, il n'y a qu'un pas à faire pour croire que je vous dois un discours si
vous me le demandez.</p>
<p>
- Considérez ceci : le projet GNU commence à développer un système
+ Considérez ceciâ¯: le projet GNU commence à développer un système
d'exploitation, et des années plus tard Linus Torvalds y ajoute une partie
-importante. Le projet GNU dit « Veuillez mentionner notre projet
-équitablement », mais Linus répond, « Ne leur donnez aucune part du
mérite,
-appelez l'ensemble de mon seul nom ! » Imaginez maintenant l'état d'esprit
+importante. Le projet GNU dit «â¯Veuillez mentionner notre projet
+équitablementâ¯Â», mais Linus répond, «â¯Ne leur donnez aucune part du
mérite,
+appelez l'ensemble de mon seul nomâ¯!â¯Â» Imaginez maintenant l'état
d'esprit
d'une personne qui, à la lumière de ces événements, accuse le projet GNU
d'égoïsme. Il faut de sacrés préjugés pour se méprendre à ce point.</p>
<p>
Une personne aux préjugés aussi bien ancrés peut dire toutes sortes de
-choses injustes au sujet du projet GNU et les trouver justifiées ; ses
+choses injustes au sujet du projet GNU et les trouver justifiéesâ¯; ses
camarades la soutiendront, parce qu'ils veulent un soutien mutuel dans le
maintien de leurs préjugés. Ceux qui ne sont pas d'accord peuvent se faire
-injurier ; alors, si je refuse de participer à une activité sous la rubrique
-« Linux », ils peuvent trouver cela inexcusable et me tenir pour
responsable
+injurierâ¯; alors, si je refuse de participer à une activité sous la
rubrique
+«â¯Linuxâ¯Â», ils peuvent trouver cela inexcusable et me tenir pour
responsable
du malaise qu'ils ressentent après coup. Lorsque tant de gens veulent que
-j'appelle le système « Linux », comment puis-je, moi qui ai simplement
lancé
-son développement, ne pas obéir ? Et leur refuser carrément un discours les
+j'appelle le système «â¯Linuxâ¯Â», comment puis-je, moi qui ai simplement
lancé
+son développement, ne pas obéir� Et leur refuser carrément un discours
les
mécontente carrément. C'est de la coercition, aussi néfaste que celle de
-Microsoft !</p>
+Microsoftâ¯!</p>
<p>
Vous vous demandez peut-être pourquoi je fais tant d'histoires et me donne
tout ce mal. Quand SIGLINUX m'a convié à parler, j'aurais pu me contenter de
-dire « Non, désolé », et l'affaire en serait restée là . Pourquoi ne
l'ai-je
-pas fait ? Parce que je suis prêt à prendre le risque d'être
personnellement
+dire «â¯Non, désoléâ¯Â», et l'affaire en serait restée là . Pourquoi ne
l'ai-je
+pas fait� Parce que je suis prêt à prendre le risque d'être
personnellement
injurié afin d'avoir une chance de corriger l'erreur qui sape les efforts du
projet GNU.</p>
<p>
- Appeler cette variante du système GNU « Linux » fait le jeu de ceux qui
+ Appeler cette variante du système GNU «â¯Linuxâ¯Â» fait le jeu de ceux
qui
choisissent leur logiciel en fonction du seul critère de l'avantage
technique, sans se demander s'il respecte leur liberté. Il y a des gens
-comme Barr, qui veulent leur logiciel « libre de toute idéologie » et
+comme Barr, qui veulent leur logiciel «â¯libre de toute idéologieâ¯Â» et
critiquent ceux qui mettent en avant la liberté. Il y a des gens comme
Torvalds qui pousseront notre communauté à utiliser des programmes non
libres et défieront ceux qui s'en plaignent de fournir immédiatement un
programme (techniquement) meilleur ou de se taire. Il y a des gens pour dire
-que les décisions techniques ne doivent pas être « politisées » par la
prise
+que les décisions techniques ne doivent pas être «â¯politiséesâ¯Â» par
la prise
en compte de leurs conséquences sociétales.</p>
<p>
Dans les années 70, les utilisateurs d'ordinateurs ont perdu leurs
libertés
@@ -119,33 +119,33 @@
assurée. Elle est menacée par la <abbr title="Consumer Broadband and Digital
Television Promotion Act">CBDTPA</abbr> (anciennement <abbr title="Security
Systems Standards and Certification Act">SSSCA</abbr>), par le <i>Broadcast
-« Protection » Discussion Group</i> (voir <a
+«â¯Protectionâ¯Â» Discussion Group</i> (voir <a
href="https://www.eff.org/";>www.eff.org/</a>Â [en]) qui propose d'interdire
l'utilisation de logiciel libre pour accéder aux télédiffusions numériques,
par les brevets logiciels (l'Europe est en train d'y réfléchir), par les
clauses de confidentialité de Microsoft pour des protocoles d'importance
critique et par tous ceux qui nous incitent à utiliser des programmes non
-libres réputés « meilleurs » (techniquement) que les programmes libres
+libres réputés «â¯meilleursâ¯Â» (techniquement) que les programmes libres
disponibles. Nous pouvons perdre à nouveau notre liberté tout comme nous
l'avons perdue la première fois, si nous ne sommes pas assez concernés pour
la protéger.</p>
<p>
- Serons-nous assez nombreux à être concernés ? Cela dépend de beaucoup de
+ Serons-nous assez nombreux à être concernés� Cela dépend de beaucoup
de
choses, entre autres de l'influence qu'aura le projet GNU et de l'influence
-qu'aura Linus Torvalds. Le projet GNU dit : « Donnez du prix votre
-liberté ! » Joe Barr répond : « Choisissez entre des programmes libres
et
-non libres sur les seuls critères techniques ! » Si les gens attribuent Ã
+qu'aura Linus Torvalds. Le projet GNU ditâ¯: «â¯Donnez du prix à votre
+libertéâ¯!â¯Â» Joe Barr répondâ¯: «â¯Choisissez entre des programmes
libres et
+non libres sur les seuls critères techniquesâ¯!â¯Â» Si les gens attribuent
Ã
Torvalds le mérite d'être le développeur principal du système GNU/Linux,
non
seulement c'est inexact, mais cela donne aussi plus de poids à son
-message. Et ce message dit : « Les logiciels non libres sont bien ; je les
-utilise et les développe moi-même. » S'ils reconnaissent notre rôle, ils
-nous écouteront mieux, et le message que nous leur donnerons sera : « Ce
+message. Et ce message ditâ¯: «â¯Les logiciels non libres sont bienâ¯; je
les
+utilise et les développe moi-même.â¯Â» S'ils reconnaissent notre rôle, ils
+nous écouteront mieux, et le message que nous leur donnerons seraâ¯: «â¯Ce
système existe grâce à des gens qui se soucient de la
liberté. Rejoignez-nous, donnez du prix à votre liberté et ensemble nous
-pourrons la préserver. » Vous trouverez l'historique de notre projet dans
-« <a href="/gnu/thegnuproject.html">Le projet GNU</a> ».</p>
+pourrons la préserver.â¯Â» Vous trouverez l'historique de notre projet dans
+«â¯<a href="/gnu/thegnuproject.html">Le projet GNU</a>â¯Â».</p>
<p>
- Quand je demande aux gens d'appeler le système « GNU/Linux », certains
+ Quand je demande aux gens d'appeler le système «â¯GNU/Linuxâ¯Â», certains
donnent des <a href="/gnu/gnu-linux-faq.html">excuses farfelues et de faux
prétextes</a>. Mais il est probable que nous ne perdons rien, car au départ
ils étaient sans doute mal disposés envers nous. Pendant ce temps, d'autres
@@ -173,7 +173,7 @@
noyau qui l'ont fait. La plupart d'entre eux se convainquent petit à petit
que ce n'est pas grave d'utiliser des logiciels non libres, pour ne pas
reconnaître la dissonance cognitive qui consiste à accepter la présence de
-Bitkeeper sur leurs machines. Que pouvons-nous faire ?</p>
+Bitkeeper sur leurs machines. Que pouvons-nous faire�</p>
<p>
Une des solutions est de mettre en place un autre référentiel pour les
sources de Linux, utilisant CVS ou un autre système libre de contrôle de
@@ -192,29 +192,29 @@
utilisant des logiciels libres.</p>
<p>
Les sources de Linux ont elles-mêmes un problème de logiciel non libre bien
-plus grave : en fait, elles en contiennent. Pas mal de pilotes de
+plus graveâ¯: en fait, elles en contiennent. Pas mal de pilotes de
périphériques contiennent une série de nombres qui représentent des
micrologiciels <i>[firmware]</i> à installer dans le périphérique. Ces
programmes ne sont pas des logiciels libres. Quelques nombres à déposer dans
-les registres d'un périphérique sont une chose ; un programme binaire
+les registres d'un périphérique sont une choseâ¯; un programme binaire
conséquent en est une autre.</p>
<p>
La présence de ces programmes, uniquement binaires, dans les fichiers
-« sources » de Linux crée un problème secondaire : elle remet en
question la
+«â¯sourcesâ¯Â» de Linux crée un problème secondaireâ¯: elle remet en
question la
légalité de la redistribution des binaires de Linux. La GPL requiert le
-« code source complet correspondant », et une séquence d'entiers n'est pas
+«â¯code source complet correspondantâ¯Â», et une séquence d'entiers n'est
pas
un code source. Pour la même raison, ajouter de tels binaires aux sources de
Linux viole la GPL.</p>
<p>
Les développeurs de Linux ont prévu de placer ces micrologiciels dans des
-fichiers séparés ; cela prendra des années avant d'y arriver, mais quand ce
-sera accompli, cela résoudra le problème secondaire ; nous pourrons faire
-une version « Linux libre » qui ne contiendra aucun fichier de
micrologiciel
+fichiers séparésâ¯; cela prendra des années avant d'y arriver, mais quand
ce
+sera accompli, cela résoudra le problème secondaireâ¯; nous pourrons faire
+une version «â¯Linux libreâ¯Â» qui ne contiendra aucun fichier de
micrologiciel
non libre. Ce ne sera pas très bénéfique en soi si la plupart des gens
-utilisent la version « officielle » non libre de Linux. C'est ce qui
+utilisent la version «â¯officielleâ¯Â» non libre de Linux. C'est ce qui
pourrait bien arriver, car sur beaucoup de plateformes la version libre ne
-fonctionne pas sans rajouter de micrologiciel non libre. Le projet « Linux
-libre » devra découvrir ce que fait chaque micrologiciel et récrire son
code
+fonctionne pas sans rajouter de micrologiciel non libre. Le projet «â¯Linux
+libreâ¯Â» devra découvrir ce que fait chaque micrologiciel et récrire son
code
source, peut-être en langage assembleur, pour le processeur intégré sur
lequel il est exécuté. C'est un travail décourageant. Il aurait été moins
décourageant si nous l'avions fait petit à petit, au fil des années, plutôt
@@ -223,18 +223,18 @@
que ce travail n'est pas nécessaire.</p>
<p>
Linux, le noyau, est souvent vu comme le porte-drapeau du logiciel libre, et
-pourtant il est en partie non libre. Comment est-ce arrivé ? Ce problème,
+pourtant il est en partie non libre. Comment est-ce arrivé� Ce problème,
tout comme la décision d'utiliser Bitkeeper, reflète l'attitude du
développeur qui est à l'origine de Linux, celle d'une personne qui pense que
-« techniquement mieux » est plus important que liberté.</p>
+«â¯techniquement mieuxâ¯Â» est plus important que liberté.</p>
<p>
Donnez du prix à votre liberté ou vous la perdrez, nous apprend
-l'histoire. « Ne nous ennuyez pas avec la politique », répondent ceux qui
ne
+l'histoire. «â¯Ne nous ennuyez pas avec la politiqueâ¯Â», répondent ceux
qui ne
veulent pas s'instruire.</p>
<div class="column-limit"></div>
<p id="update">
- <strong>Mise à jour :</strong> Depuis 2005, BitKeeper n'est plus utilisé
+ <strong>Mise à jourâ¯:</strong> Depuis 2005, BitKeeper n'est plus utilisé
pour gérer l'arborescence des sources du noyau Linux. Voir l'article <a
href="/philosophy/mcvoy.html">Merci, Larry McVoy</a>. Les sources de Linux
contiennent encore des blobs de micrologiciel non libre, mais depuis janvier
@@ -311,13 +311,13 @@
<div class="translators-credits">
<!--TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.-->
-Traduction : Cédric Corazza.<br /> Révision : <a
+Traductionâ¯: Cédric Corazza.<br /> Révisionâ¯: <a
href="mailto:trad-gnu@april.org";>trad-gnu@april.org</a></div>
<p class="unprintable"><!-- timestamp start -->
Dernière mise à jour :
-$Date: 2021/09/12 10:04:28 $
+$Date: 2021/10/18 21:32:16 $
<!-- timestamp end -->
</p>
Index: po/linux-gnu-freedom.fr-en.html
===================================================================
RCS file: /web/www/www/philosophy/po/linux-gnu-freedom.fr-en.html,v
retrieving revision 1.42
retrieving revision 1.43
diff -u -b -r1.42 -r1.43
--- po/linux-gnu-freedom.fr-en.html 12 Sep 2021 10:04:29 -0000 1.42
+++ po/linux-gnu-freedom.fr-en.html 18 Oct 2021 21:32:17 -0000 1.43
@@ -129,8 +129,8 @@
Will enough of us care? That depends on many things; among them,
how much influence the GNU Project has, and how much influence Linus
Torvalds has. The GNU Project says, “Value your
- freedom!.” Joe Barr says, “Choose between nonfree and
- free programs on technical grounds alone!.” If people credit
+ freedom!” Joe Barr says, “Choose between nonfree and
+ free programs on technical grounds alone!” If people credit
Torvalds as the main developer of the GNU/Linux system, that's not
just inaccurate, it also makes his message more
influential—and that message says, “Nonfree software is
@@ -294,7 +294,7 @@
<p class="unprintable">Updated:
<!-- timestamp start -->
-$Date: 2021/09/12 10:04:29 $
+$Date: 2021/10/18 21:32:17 $
<!-- timestamp end -->
</p>
</div>
Index: po/rms-nyu-2001-transcript.cs.po
===================================================================
RCS file: /web/www/www/philosophy/po/rms-nyu-2001-transcript.cs.po,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -b -r1.3 -r1.4
--- po/rms-nyu-2001-transcript.cs.po 19 Sep 2021 15:34:13 -0000 1.3
+++ po/rms-nyu-2001-transcript.cs.po 18 Oct 2021 21:32:17 -0000 1.4
@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: rms-nyu-2001-transcript.html\n"
-"POT-Creation-Date: 2021-09-19 15:26+0000\n"
+"POT-Creation-Date: 2021-10-18 21:26+0000\n"
"PO-Revision-Date: \n"
"Last-Translator: Thérèse Godefroy <godef.th AT free.fr>\n"
"Language-Team: web-translators <web-translators@gnu.org>\n"
@@ -289,7 +289,7 @@
# | {+neophyte—of+} changing a recipe. You know, it says certain
# | things, but you don't have to do exactly that. You can leave out some
# | ingredients. Add some mushrooms, 'cause you like mushrooms. Put in less
-# | salt because your doctor said you should cut down on salt [-—
+# | salt because your doctor said you should cut down on [-salt —
# | whatever.-] {+salt—whatever.+} You can even make bigger changes
# | according to your skill. And if you've made changes in a recipe, and you
# | cook it for your friends, and they like it, one of your friends might say,
@@ -323,13 +323,13 @@
"of changing a recipe. You know, it says certain things, but you don't have "
"to do exactly that. You can leave out some ingredients. Add some "
"mushrooms, 'cause you like mushrooms. Put in less salt because your doctor "
-"said you should cut down on salt salt—whatever. You can even make "
-"bigger changes according to your skill. And if you've made changes in a "
-"recipe, and you cook it for your friends, and they like it, one of your "
-"friends might say, “Hey, could I have the recipe?” And then, "
-"what do you do? You could write down your modified version of the recipe and "
-"make a copy for your friend. These are the natural things to do with "
-"functionally useful recipes of any kind."
+"said you should cut down on salt—whatever. You can even make bigger "
+"changes according to your skill. And if you've made changes in a recipe, "
+"and you cook it for your friends, and they like it, one of your friends "
+"might say, “Hey, could I have the recipe?” And then, what do you "
+"do? You could write down your modified version of the recipe and make a copy "
+"for your friend. These are the natural things to do with functionally "
+"useful recipes of any kind."
msgstr ""
"NÄkteÅà z vás možná jeÅ¡tÄ nepsali poÄÃtaÄové programy, ale
možná vaÅÃte. A "
"jestli vaÅÃte, tak pokud nejste opravdu velmi dobÅÃ, asi použÃváte
recepty. "
@@ -5837,10 +5837,10 @@
#. type: Content of: <div><p>
# | <strong>STALLMAN</strong>: Who is here for the press conference? Not a lot
-# | of press. Oh, [-three — OK.-] {+three—OK.+} Can you afford
-# | if [-we —-] {+we…+} if I go on answering everybody's
-# | questions for another ten minutes or so? OK. So, we'll go on answering
-# | everybody's questions.
+# | of press. Oh, [-three —-] {+three…+} OK. Can you afford if
+# | [-we —-] {+we…+} if I go on answering everybody's questions
+# | for another ten minutes or so? OK. So, we'll go on answering everybody's
+# | questions.
#, fuzzy
#| msgid ""
#| "<strong>STALLMAN</strong>: Who is here for the press conference? Not a "
@@ -5849,7 +5849,7 @@
#| "So, we'll go on answering everybody's questions."
msgid ""
"<strong>STALLMAN</strong>: Who is here for the press conference? Not a lot "
-"of press. Oh, three—OK. Can you afford if we… if I go on "
+"of press. Oh, three… OK. Can you afford if we… if I go on "
"answering everybody's questions for another ten minutes or so? OK. So, "
"we'll go on answering everybody's questions."
msgstr ""
Index: po/rms-nyu-2001-transcript.fr.po
===================================================================
RCS file: /web/www/www/philosophy/po/rms-nyu-2001-transcript.fr.po,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -b -r1.18 -r1.19
--- po/rms-nyu-2001-transcript.fr.po 19 Sep 2021 17:59:51 -0000 1.18
+++ po/rms-nyu-2001-transcript.fr.po 18 Oct 2021 21:32:17 -0000 1.19
@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: rms-nyu-2001-transcript.html\n"
-"POT-Creation-Date: 2021-09-19 15:26+0000\n"
+"POT-Creation-Date: 2021-10-18 21:26+0000\n"
"PO-Revision-Date: 2021-09-19 19:58+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: 2021-10-18 21:26+0000\n"
"Plural-Forms: \n"
#. type: Content of: <title>
@@ -204,6 +205,39 @@
"et avec d'autres champs de la vie en société."
#. type: Content of: <div><p>
+# | Now, some of you may not ever write computer programs, but perhaps you
+# | cook. And if you cook, unless you're really great, you probably use
+# | recipes. And, if you use recipes, you've probably had the experience of
+# | getting a copy of a recipe from a friend who's sharing it. And you've
+# | probably also had the experience—unless you're a total
+# | neophyte—of changing a recipe. You know, it says certain things,
+# | but you don't have to do exactly that. You can leave out some
+# | ingredients. Add some mushrooms, 'cause you like mushrooms. Put in less
+# | salt because your doctor said you should cut down on [-salt-]
+# | salt—whatever. You can even make bigger changes according to your
+# | skill. And if you've made changes in a recipe, and you cook it for your
+# | friends, and they like it, one of your friends might say, “Hey,
+# | could I have the recipe?” And then, what do you do? You could write
+# | down your modified version of the recipe and make a copy for your friend.
+# | These are the natural things to do with functionally useful recipes of any
+# | kind.
+#, fuzzy
+#| msgid ""
+#| "Now, some of you may not ever write computer programs, but perhaps you "
+#| "cook. And if you cook, unless you're really great, you probably use "
+#| "recipes. And, if you use recipes, you've probably had the experience of "
+#| "getting a copy of a recipe from a friend who's sharing it. And you've "
+#| "probably also had the experience—unless you're a total "
+#| "neophyte—of changing a recipe. You know, it says certain things, "
+#| "but you don't have to do exactly that. You can leave out some "
+#| "ingredients. Add some mushrooms, 'cause you like mushrooms. Put in less "
+#| "salt because your doctor said you should cut down on salt salt—"
+#| "whatever. You can even make bigger changes according to your skill. And "
+#| "if you've made changes in a recipe, and you cook it for your friends, and "
+#| "they like it, one of your friends might say, “Hey, could I have the "
+#| "recipe?” And then, what do you do? You could write down your "
+#| "modified version of the recipe and make a copy for your friend. These "
+#| "are the natural things to do with functionally useful recipes of any kind."
msgid ""
"Now, some of you may not ever write computer programs, but perhaps you "
"cook. And if you cook, unless you're really great, you probably use "
@@ -213,13 +247,13 @@
"of changing a recipe. You know, it says certain things, but you don't have "
"to do exactly that. You can leave out some ingredients. Add some "
"mushrooms, 'cause you like mushrooms. Put in less salt because your doctor "
-"said you should cut down on salt salt—whatever. You can even make "
-"bigger changes according to your skill. And if you've made changes in a "
-"recipe, and you cook it for your friends, and they like it, one of your "
-"friends might say, “Hey, could I have the recipe?” And then, "
-"what do you do? You could write down your modified version of the recipe and "
-"make a copy for your friend. These are the natural things to do with "
-"functionally useful recipes of any kind."
+"said you should cut down on salt—whatever. You can even make bigger "
+"changes according to your skill. And if you've made changes in a recipe, "
+"and you cook it for your friends, and they like it, one of your friends "
+"might say, “Hey, could I have the recipe?” And then, what do you "
+"do? You could write down your modified version of the recipe and make a copy "
+"for your friend. These are the natural things to do with functionally "
+"useful recipes of any kind."
msgstr ""
"Certains d'entre vous n'écriront peut-être jamais de logiciels, mais vous "
"cuisinez peut-être. Et si vous cuisinez, à moins que vous ne soyez un grand
"
@@ -3958,9 +3992,19 @@
"de presse ? Ou souhaitez-vous continuer ici ?"
#. type: Content of: <div><p>
+# | <strong>STALLMAN</strong>: Who is here for the press conference? Not a lot
+# | of press. Oh, [-three—OK.-] {+three… OK.+} Can you afford
+# | if we… if I go on answering everybody's questions for another ten
+# | minutes or so? OK. So, we'll go on answering everybody's questions.
+#, fuzzy
+#| msgid ""
+#| "<strong>STALLMAN</strong>: Who is here for the press conference? Not a "
+#| "lot of press. Oh, three—OK. Can you afford if we… if I go "
+#| "on answering everybody's questions for another ten minutes or so? OK. "
+#| "So, we'll go on answering everybody's questions."
msgid ""
"<strong>STALLMAN</strong>: Who is here for the press conference? Not a lot "
-"of press. Oh, three—OK. Can you afford if we… if I go on "
+"of press. Oh, three… OK. Can you afford if we… if I go on "
"answering everybody's questions for another ten minutes or so? OK. So, "
"we'll go on answering everybody's questions."
msgstr ""
Index: po/rms-nyu-2001-transcript.pl.po
===================================================================
RCS file: /web/www/www/philosophy/po/rms-nyu-2001-transcript.pl.po,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- po/rms-nyu-2001-transcript.pl.po 30 Sep 2021 10:33:44 -0000 1.11
+++ po/rms-nyu-2001-transcript.pl.po 18 Oct 2021 21:32:17 -0000 1.12
@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: rms-nyu-2001-transcript.html\n"
-"POT-Creation-Date: 2021-09-19 15:26+0000\n"
+"POT-Creation-Date: 2021-10-18 21:26+0000\n"
"PO-Revision-Date: 2015-02-21 11:38-0600\n"
"Last-Translator: Jan Owoc <jsowoc AT gmail.com>\n"
"Language-Team: Polish <www-pl-trans@gnu.org>\n"
@@ -15,6 +15,7 @@
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"X-Outdated-Since: 2021-10-18 21:26+0000\n"
"Plural-Forms: nplurals=3; plural=(n==1 ? 0 : n%10>=2 && n%10<=4 && (n%100<10 "
"|| n%100>=20) ? 1 : 2);\n"
"X-Generator: Virtaal 0.7.0\n"
@@ -210,6 +211,39 @@
"spoÅecznego."
#. type: Content of: <div><p>
+# | Now, some of you may not ever write computer programs, but perhaps you
+# | cook. And if you cook, unless you're really great, you probably use
+# | recipes. And, if you use recipes, you've probably had the experience of
+# | getting a copy of a recipe from a friend who's sharing it. And you've
+# | probably also had the experience—unless you're a total
+# | neophyte—of changing a recipe. You know, it says certain things,
+# | but you don't have to do exactly that. You can leave out some
+# | ingredients. Add some mushrooms, 'cause you like mushrooms. Put in less
+# | salt because your doctor said you should cut down on [-salt-]
+# | salt—whatever. You can even make bigger changes according to your
+# | skill. And if you've made changes in a recipe, and you cook it for your
+# | friends, and they like it, one of your friends might say, “Hey,
+# | could I have the recipe?” And then, what do you do? You could write
+# | down your modified version of the recipe and make a copy for your friend.
+# | These are the natural things to do with functionally useful recipes of any
+# | kind.
+#, fuzzy
+#| msgid ""
+#| "Now, some of you may not ever write computer programs, but perhaps you "
+#| "cook. And if you cook, unless you're really great, you probably use "
+#| "recipes. And, if you use recipes, you've probably had the experience of "
+#| "getting a copy of a recipe from a friend who's sharing it. And you've "
+#| "probably also had the experience—unless you're a total "
+#| "neophyte—of changing a recipe. You know, it says certain things, "
+#| "but you don't have to do exactly that. You can leave out some "
+#| "ingredients. Add some mushrooms, 'cause you like mushrooms. Put in less "
+#| "salt because your doctor said you should cut down on salt salt—"
+#| "whatever. You can even make bigger changes according to your skill. And "
+#| "if you've made changes in a recipe, and you cook it for your friends, and "
+#| "they like it, one of your friends might say, “Hey, could I have the "
+#| "recipe?” And then, what do you do? You could write down your "
+#| "modified version of the recipe and make a copy for your friend. These "
+#| "are the natural things to do with functionally useful recipes of any kind."
msgid ""
"Now, some of you may not ever write computer programs, but perhaps you "
"cook. And if you cook, unless you're really great, you probably use "
@@ -219,13 +253,13 @@
"of changing a recipe. You know, it says certain things, but you don't have "
"to do exactly that. You can leave out some ingredients. Add some "
"mushrooms, 'cause you like mushrooms. Put in less salt because your doctor "
-"said you should cut down on salt salt—whatever. You can even make "
-"bigger changes according to your skill. And if you've made changes in a "
-"recipe, and you cook it for your friends, and they like it, one of your "
-"friends might say, “Hey, could I have the recipe?” And then, "
-"what do you do? You could write down your modified version of the recipe and "
-"make a copy for your friend. These are the natural things to do with "
-"functionally useful recipes of any kind."
+"said you should cut down on salt—whatever. You can even make bigger "
+"changes according to your skill. And if you've made changes in a recipe, "
+"and you cook it for your friends, and they like it, one of your friends "
+"might say, “Hey, could I have the recipe?” And then, what do you "
+"do? You could write down your modified version of the recipe and make a copy "
+"for your friend. These are the natural things to do with functionally "
+"useful recipes of any kind."
msgstr ""
"Dobrze, niektórzy z was mogÄ
nigdy nie napisaÄ Å¼adnego programu, "
"ale byÄ może gotujecie. Jako kucharze zapewne korzystacie z "
@@ -4104,9 +4138,19 @@
"na konferencjÄ prasowÄ
? Czy kontynuowaÄ z tym?"
#. type: Content of: <div><p>
+# | <strong>STALLMAN</strong>: Who is here for the press conference? Not a lot
+# | of press. Oh, [-three—OK.-] {+three… OK.+} Can you afford
+# | if we… if I go on answering everybody's questions for another ten
+# | minutes or so? OK. So, we'll go on answering everybody's questions.
+#, fuzzy
+#| msgid ""
+#| "<strong>STALLMAN</strong>: Who is here for the press conference? Not a "
+#| "lot of press. Oh, three—OK. Can you afford if we… if I go "
+#| "on answering everybody's questions for another ten minutes or so? OK. "
+#| "So, we'll go on answering everybody's questions."
msgid ""
"<strong>STALLMAN</strong>: Who is here for the press conference? Not a lot "
-"of press. Oh, three—OK. Can you afford if we… if I go on "
+"of press. Oh, three… OK. Can you afford if we… if I go on "
"answering everybody's questions for another ten minutes or so? OK. So, "
"we'll go on answering everybody's questions."
msgstr ""
Index: po/rms-nyu-2001-transcript.pot
===================================================================
RCS file: /web/www/www/philosophy/po/rms-nyu-2001-transcript.pot,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -b -r1.5 -r1.6
--- po/rms-nyu-2001-transcript.pot 19 Sep 2021 15:34:13 -0000 1.5
+++ po/rms-nyu-2001-transcript.pot 18 Oct 2021 21:32:17 -0000 1.6
@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: rms-nyu-2001-transcript.html\n"
-"POT-Creation-Date: 2021-09-19 15:26+0000\n"
+"POT-Creation-Date: 2021-10-18 21:26+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"
@@ -146,9 +146,9 @@
"neophyte—of changing a recipe. You know, it says certain things, but "
"you don't have to do exactly that. You can leave out some ingredients. Add "
"some mushrooms, 'cause you like mushrooms. Put in less salt because your "
-"doctor said you should cut down on salt salt—whatever. You can even "
-"make bigger changes according to your skill. And if you've made changes in "
-"a recipe, and you cook it for your friends, and they like it, one of your "
+"doctor said you should cut down on salt—whatever. You can even make "
+"bigger changes according to your skill. And if you've made changes in a "
+"recipe, and you cook it for your friends, and they like it, one of your "
"friends might say, “Hey, could I have the recipe?” And then, "
"what do you do? You could write down your modified version of the recipe and "
"make a copy for your friend. These are the natural things to do with "
@@ -2395,7 +2395,7 @@
#. type: Content of: <div><p>
msgid ""
"<strong>STALLMAN</strong>: Who is here for the press conference? Not a lot "
-"of press. Oh, three—OK. Can you afford if we… if I go on "
+"of press. Oh, three… OK. Can you afford if we… if I go on "
"answering everybody's questions for another ten minutes or so? OK. So, "
"we'll go on answering everybody's questions."
msgstr ""
Index: po/rms-nyu-2001-transcript.ru.po
===================================================================
RCS file: /web/www/www/philosophy/po/rms-nyu-2001-transcript.ru.po,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -b -r1.10 -r1.11
--- po/rms-nyu-2001-transcript.ru.po 19 Sep 2021 16:36:53 -0000 1.10
+++ po/rms-nyu-2001-transcript.ru.po 18 Oct 2021 21:32:17 -0000 1.11
@@ -8,7 +8,7 @@
msgid ""
msgstr ""
"Project-Id-Version: rms-nyu-2001-transcript.html\n"
-"POT-Creation-Date: 2021-09-19 15:26+0000\n"
+"POT-Creation-Date: 2021-10-18 21:26+0000\n"
"PO-Revision-Date: 2021-09-19 17:34+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: 2021-10-18 21:26+0000\n"
#. type: Content of: <title>
msgid ""
@@ -201,6 +202,39 @@
"пÑедпÑинимаÑелÑÑÑвом, а Ñакже Ñ Ð´ÑÑгими
ÑÑеÑами обÑеÑÑвенной жизни."
#. type: Content of: <div><p>
+# | Now, some of you may not ever write computer programs, but perhaps you
+# | cook. And if you cook, unless you're really great, you probably use
+# | recipes. And, if you use recipes, you've probably had the experience of
+# | getting a copy of a recipe from a friend who's sharing it. And you've
+# | probably also had the experience—unless you're a total
+# | neophyte—of changing a recipe. You know, it says certain things,
+# | but you don't have to do exactly that. You can leave out some
+# | ingredients. Add some mushrooms, 'cause you like mushrooms. Put in less
+# | salt because your doctor said you should cut down on [-salt-]
+# | salt—whatever. You can even make bigger changes according to your
+# | skill. And if you've made changes in a recipe, and you cook it for your
+# | friends, and they like it, one of your friends might say, “Hey,
+# | could I have the recipe?” And then, what do you do? You could write
+# | down your modified version of the recipe and make a copy for your friend.
+# | These are the natural things to do with functionally useful recipes of any
+# | kind.
+#, fuzzy
+#| msgid ""
+#| "Now, some of you may not ever write computer programs, but perhaps you "
+#| "cook. And if you cook, unless you're really great, you probably use "
+#| "recipes. And, if you use recipes, you've probably had the experience of "
+#| "getting a copy of a recipe from a friend who's sharing it. And you've "
+#| "probably also had the experience—unless you're a total "
+#| "neophyte—of changing a recipe. You know, it says certain things, "
+#| "but you don't have to do exactly that. You can leave out some "
+#| "ingredients. Add some mushrooms, 'cause you like mushrooms. Put in less "
+#| "salt because your doctor said you should cut down on salt salt—"
+#| "whatever. You can even make bigger changes according to your skill. And "
+#| "if you've made changes in a recipe, and you cook it for your friends, and "
+#| "they like it, one of your friends might say, “Hey, could I have the "
+#| "recipe?” And then, what do you do? You could write down your "
+#| "modified version of the recipe and make a copy for your friend. These "
+#| "are the natural things to do with functionally useful recipes of any kind."
msgid ""
"Now, some of you may not ever write computer programs, but perhaps you "
"cook. And if you cook, unless you're really great, you probably use "
@@ -210,13 +244,13 @@
"of changing a recipe. You know, it says certain things, but you don't have "
"to do exactly that. You can leave out some ingredients. Add some "
"mushrooms, 'cause you like mushrooms. Put in less salt because your doctor "
-"said you should cut down on salt salt—whatever. You can even make "
-"bigger changes according to your skill. And if you've made changes in a "
-"recipe, and you cook it for your friends, and they like it, one of your "
-"friends might say, “Hey, could I have the recipe?” And then, "
-"what do you do? You could write down your modified version of the recipe and "
-"make a copy for your friend. These are the natural things to do with "
-"functionally useful recipes of any kind."
+"said you should cut down on salt—whatever. You can even make bigger "
+"changes according to your skill. And if you've made changes in a recipe, "
+"and you cook it for your friends, and they like it, one of your friends "
+"might say, “Hey, could I have the recipe?” And then, what do you "
+"do? You could write down your modified version of the recipe and make a copy "
+"for your friend. These are the natural things to do with functionally "
+"useful recipes of any kind."
msgstr ""
"Так воÑ, кÑо-Ñо из ваÑ, Ð¼Ð¾Ð¶ÐµÑ Ð±ÑÑÑ, никогда
не пиÑал пÑогÑамм Ð´Ð»Ñ "
"компÑÑÑеÑов, но вÑ, возможно, гоÑовиÑе. Ð
Ñаз Ð²Ñ Ð³Ð¾ÑовиÑе, еÑли ÑолÑко Ð²Ñ Ð½Ðµ "
@@ -4057,9 +4091,19 @@
"Ð²Ñ Ð±ÑдеÑе пÑодолжаÑÑ Ð·Ð´ÐµÑÑ?"
#. type: Content of: <div><p>
+# | <strong>STALLMAN</strong>: Who is here for the press conference? Not a lot
+# | of press. Oh, [-three—OK.-] {+three… OK.+} Can you afford
+# | if we… if I go on answering everybody's questions for another ten
+# | minutes or so? OK. So, we'll go on answering everybody's questions.
+#, fuzzy
+#| msgid ""
+#| "<strong>STALLMAN</strong>: Who is here for the press conference? Not a "
+#| "lot of press. Oh, three—OK. Can you afford if we… if I go "
+#| "on answering everybody's questions for another ten minutes or so? OK. "
+#| "So, we'll go on answering everybody's questions."
msgid ""
"<strong>STALLMAN</strong>: Who is here for the press conference? Not a lot "
-"of press. Oh, three—OK. Can you afford if we… if I go on "
+"of press. Oh, three… OK. Can you afford if we… if I go on "
"answering everybody's questions for another ten minutes or so? OK. So, "
"we'll go on answering everybody's questions."
msgstr ""
Index: po/rms-nyu-2001-transcript.tr.po
===================================================================
RCS file: /web/www/www/philosophy/po/rms-nyu-2001-transcript.tr.po,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -b -r1.19 -r1.20
--- po/rms-nyu-2001-transcript.tr.po 25 Sep 2021 11:03:31 -0000 1.19
+++ po/rms-nyu-2001-transcript.tr.po 18 Oct 2021 21:32:17 -0000 1.20
@@ -12,7 +12,7 @@
msgid ""
msgstr ""
"Project-Id-Version: rms-nyu-2001-transcript.html\n"
-"POT-Creation-Date: 2021-09-19 15:26+0000\n"
+"POT-Creation-Date: 2021-10-18 21:26+0000\n"
"PO-Revision-Date: 2021-09-25 12:25+0200\n"
"Last-Translator: T. E. Kalayci <tekrei@member.fsf.org>\n"
"Language-Team: Turkish <www-tr-comm@gnu.org>\n"
@@ -20,6 +20,7 @@
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"X-Outdated-Since: 2021-10-18 21:26+0000\n"
"Plural-Forms: nplurals=1; plural=0;\n"
"X-Generator: Poedit 2.4.2\n"
@@ -207,6 +208,23 @@
"hakkında bir Åeyler söyleyeceÄim."
#. type: Content of: <div><p>
+#, fuzzy
+#| msgid ""
+#| "Now, some of you may not ever write computer programs, but perhaps you "
+#| "cook. And if you cook, unless you're really great, you probably use "
+#| "recipes. And, if you use recipes, you've probably had the experience of "
+#| "getting a copy of a recipe from a friend who's sharing it. And you've "
+#| "probably also had the experience—unless you're a total "
+#| "neophyte—of changing a recipe. You know, it says certain things, "
+#| "but you don't have to do exactly that. You can leave out some "
+#| "ingredients. Add some mushrooms, 'cause you like mushrooms. Put in less "
+#| "salt because your doctor said you should cut down on salt salt—"
+#| "whatever. You can even make bigger changes according to your skill. And "
+#| "if you've made changes in a recipe, and you cook it for your friends, and "
+#| "they like it, one of your friends might say, “Hey, could I have the "
+#| "recipe?” And then, what do you do? You could write down your "
+#| "modified version of the recipe and make a copy for your friend. These "
+#| "are the natural things to do with functionally useful recipes of any kind."
msgid ""
"Now, some of you may not ever write computer programs, but perhaps you "
"cook. And if you cook, unless you're really great, you probably use "
@@ -216,13 +234,13 @@
"of changing a recipe. You know, it says certain things, but you don't have "
"to do exactly that. You can leave out some ingredients. Add some "
"mushrooms, 'cause you like mushrooms. Put in less salt because your doctor "
-"said you should cut down on salt salt—whatever. You can even make "
-"bigger changes according to your skill. And if you've made changes in a "
-"recipe, and you cook it for your friends, and they like it, one of your "
-"friends might say, “Hey, could I have the recipe?” And then, "
-"what do you do? You could write down your modified version of the recipe and "
-"make a copy for your friend. These are the natural things to do with "
-"functionally useful recipes of any kind."
+"said you should cut down on salt—whatever. You can even make bigger "
+"changes according to your skill. And if you've made changes in a recipe, "
+"and you cook it for your friends, and they like it, one of your friends "
+"might say, “Hey, could I have the recipe?” And then, what do you "
+"do? You could write down your modified version of the recipe and make a copy "
+"for your friend. These are the natural things to do with functionally "
+"useful recipes of any kind."
msgstr ""
"Åimdi, bazılarınız hayatında hiç bilgisayar programı yazmamıÅ
olabilir ama "
"belki de yemek piÅirdiniz. Ve yemek piÅirdiyseniz, çok mükemmel
deÄilseniz, "
@@ -3945,9 +3963,15 @@
"musunuz? Yoksa burada mı devam etmek istiyorsunuz?"
#. type: Content of: <div><p>
+#, fuzzy
+#| msgid ""
+#| "<strong>STALLMAN</strong>: Who is here for the press conference? Not a "
+#| "lot of press. Oh, three—OK. Can you afford if we… if I go "
+#| "on answering everybody's questions for another ten minutes or so? OK. "
+#| "So, we'll go on answering everybody's questions."
msgid ""
"<strong>STALLMAN</strong>: Who is here for the press conference? Not a lot "
-"of press. Oh, three—OK. Can you afford if we… if I go on "
+"of press. Oh, three… OK. Can you afford if we… if I go on "
"answering everybody's questions for another ten minutes or so? OK. So, "
"we'll go on answering everybody's questions."
msgstr ""
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- www/philosophy linux-gnu-freedom.fr.html po/lin...,
GNUN <=