[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www philosophy/po/surveillance-testimony.transl...
|
From: |
GNUN |
|
Subject: |
www philosophy/po/surveillance-testimony.transl... |
|
Date: |
Mon, 26 Feb 2018 08:00:14 -0500 (EST) |
CVSROOT: /web/www
Module name: www
Changes by: GNUN <gnun> 18/02/26 08:00:14
Modified files:
philosophy/po : surveillance-testimony.translist
proprietary : malware-google.fr.html proprietary-drm.fr.html
proprietary/po : malware-appliances.fr-en.html
malware-google.fr-en.html
proprietary-drm.fr-en.html
Added files:
philosophy : surveillance-testimony.fr.html
philosophy/po : surveillance-testimony.fr-en.html
Log message:
Automatic update by GNUnited Nations.
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/surveillance-testimony.fr.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/surveillance-testimony.translist?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/surveillance-testimony.fr-en.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/malware-google.fr.html?cvsroot=www&r1=1.16&r2=1.17
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/proprietary-drm.fr.html?cvsroot=www&r1=1.16&r2=1.17
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/malware-appliances.fr-en.html?cvsroot=www&r1=1.33&r2=1.34
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/malware-google.fr-en.html?cvsroot=www&r1=1.15&r2=1.16
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/proprietary-drm.fr-en.html?cvsroot=www&r1=1.15&r2=1.16
Patches:
Index: philosophy/po/surveillance-testimony.translist
===================================================================
RCS file: /web/www/www/philosophy/po/surveillance-testimony.translist,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- philosophy/po/surveillance-testimony.translist 31 Jan 2018 16:29:51
-0000 1.1
+++ philosophy/po/surveillance-testimony.translist 26 Feb 2018 13:00:13
-0000 1.2
@@ -3,8 +3,10 @@
value='<div id="translations">
<p>
<span dir="ltr" class="original"><a lang="en" hreflang="en"
href="/philosophy/surveillance-testimony.en.html">English</a> [en]</span>
+<span dir="ltr"><a lang="fr" hreflang="fr"
href="/philosophy/surveillance-testimony.fr.html">français</a> [fr]</span>
</p>
</div>' -->
<link rel="alternate" type="text/html"
href="/philosophy/surveillance-testimony.html" hreflang="x-default" />
<link rel="alternate" type="text/html" lang="en" hreflang="en"
href="/philosophy/surveillance-testimony.en.html" title="English" />
+<link rel="alternate" type="text/html" lang="fr" hreflang="fr"
href="/philosophy/surveillance-testimony.fr.html" title="français" />
<!-- end translist file -->
Index: proprietary/malware-google.fr.html
===================================================================
RCS file: /web/www/www/proprietary/malware-google.fr.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -b -r1.16 -r1.17
--- proprietary/malware-google.fr.html 12 Feb 2018 13:37:46 -0000 1.16
+++ proprietary/malware-google.fr.html 26 Feb 2018 13:00:13 -0000 1.17
@@ -247,6 +247,12 @@
<h3 id="drm">DRM</h3>
<ul>
+<li><p>L'appli Netflix pour Android <a
+href="http://torrentfreak.com/netflix-cracks-down-on-vpn-and-proxy-pirates-150103/";>force
+la connexion à utiliser les DNS de Google</a>. C'est l'une des méthodes
+employées par Netflix pour faire appliquer les restrictions géographiques
+imposées par les studios de cinéma.</p>
+</li>
<li>
<p>Google permet maintenant aux applis Android de détecter si un appareil a
été
@@ -365,7 +371,7 @@
<p class="unprintable"><!-- timestamp start -->
Dernière mise à jour :
-$Date: 2018/02/12 13:37:46 $
+$Date: 2018/02/26 13:00:13 $
<!-- timestamp end -->
</p>
Index: proprietary/proprietary-drm.fr.html
===================================================================
RCS file: /web/www/www/proprietary/proprietary-drm.fr.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -b -r1.16 -r1.17
--- proprietary/proprietary-drm.fr.html 3 Feb 2018 10:36:20 -0000 1.16
+++ proprietary/proprietary-drm.fr.html 26 Feb 2018 13:00:13 -0000 1.17
@@ -36,6 +36,25 @@
</p>
<ul>
+<li><p>L'appli Netflix pour Android <a
+href="http://torrentfreak.com/netflix-cracks-down-on-vpn-and-proxy-pirates-150103/";>force
+la connexion à utiliser les DNS de Google</a>. C'est l'une des méthodes
+employées par Netflix pour faire appliquer les restrictions géographiques
+imposées par les studios de cinéma.</p>
+</li>
+
+<li><p><a
+href="https://fr.wikipedia.org/wiki/High-bandwidth_Digital_Content_Protection";>HDCP</a>
+est un système de gestion numérique des restrictions qui chiffre les données
+audio et vidéo entre le processeur et le moniteur. Il est essentiellement
+mis en Åuvre au niveau matériel, mais le logiciel système intervient
+également. On peut donc qualifier ce dernier de malveillant.</p>
+
+<p>Outre qu'il maintient les utilisateurs sous son contrôle, le système HDCP
+leur refuse leurs droits d'usage loyal <cite>[fair use]</cite> et entraîne
+de nombreux problèmes pratiques.</p>
+</li>
+
<li><p>Les vidéos d'iTunes ont un DRM, ce qui permet à Apple de <a
href="https://fr.wikipedia.org/wiki/FairPlay";>décider où ses clients peuvent
regarder les vidéos qu'ils ont achetées</a>.</p>
@@ -156,25 +175,6 @@
</li>
<li>
-<p><a
-href="https://www.eff.org/deeplinks/2008/11/apple-downgrades-macbook-video-drm";>Le
-DRM de MacOS</a>. Cet article porte essentiellement sur le fait qu'un
-nouveau modèle de Macbook a introduit l'obligation pour les moniteurs
-d'avoir un composant malveillant, mais le DRM logiciel de MacOS participe Ã
-son activation. Le logiciel d'accès à iTune a également une part de
-responsabilité.
-</p>
-
-<p>Un effet indirect de ce logiciel malveillant est que les utilisateurs
-peuvent avoir du mal <a
-href="http://appleinsider.com/articles/08/11/18/apples_new_macbooks_have_built_in_copy_protection_measures";>Ã
-regarder des vidéos sur un grand écran auxiliaire</a> (cet article, publié
-sur un site dont le nom suggère qu'il vénère Apple, n'émet aucune réserve
-concernant ces restrictions).
-</p>
-</li>
-
-<li>
<p><a href="https://www.eff.org/deeplinks/2008/02/adobe-pushes-drm-flash";>Le
DRM du lecteur Flash</a>.
</p>
@@ -297,7 +297,7 @@
<p class="unprintable"><!-- timestamp start -->
Dernière mise à jour :
-$Date: 2018/02/03 10:36:20 $
+$Date: 2018/02/26 13:00:13 $
<!-- timestamp end -->
</p>
Index: proprietary/po/malware-appliances.fr-en.html
===================================================================
RCS file: /web/www/www/proprietary/po/malware-appliances.fr-en.html,v
retrieving revision 1.33
retrieving revision 1.34
diff -u -b -r1.33 -r1.34
--- proprietary/po/malware-appliances.fr-en.html 25 Jan 2018 21:30:53
-0000 1.33
+++ proprietary/po/malware-appliances.fr-en.html 26 Feb 2018 13:00:13
-0000 1.34
@@ -202,7 +202,7 @@
dlink of an eye.</p>
<p>
-<a href="https://github.com/elvanderb/TCP-32764";>Many models of router
+<a href="https://github.com/elvanderb/TCP-32764";>Many models of routers
have back doors</a>.</p>
</li>
@@ -543,7 +543,7 @@
<p class="unprintable">Updated:
<!-- timestamp start -->
-$Date: 2018/01/25 21:30:53 $
+$Date: 2018/02/26 13:00:13 $
<!-- timestamp end -->
</p>
</div>
Index: proprietary/po/malware-google.fr-en.html
===================================================================
RCS file: /web/www/www/proprietary/po/malware-google.fr-en.html,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -b -r1.15 -r1.16
--- proprietary/po/malware-google.fr-en.html 12 Feb 2018 13:37:46 -0000
1.15
+++ proprietary/po/malware-google.fr-en.html 26 Feb 2018 13:00:13 -0000
1.16
@@ -219,6 +219,12 @@
<h3 id="drm">Google DRM</h3>
<ul>
+<li><p>The Netflix Android app <a
+href="http://torrentfreak.com/netflix-cracks-down-on-vpn-and-proxy-pirates-150103/";>
+forces the use of Google DNS</a>. This is one of the methods that Netflix
+uses to enforce the geolocation restrictions dictated by the movie
+studios.</p>
+</li>
<li>
<p>Google now allows Android apps to detect whether a device has been
@@ -310,7 +316,7 @@
<p class="unprintable">Updated:
<!-- timestamp start -->
-$Date: 2018/02/12 13:37:46 $
+$Date: 2018/02/26 13:00:13 $
<!-- timestamp end -->
</p>
</div>
Index: proprietary/po/proprietary-drm.fr-en.html
===================================================================
RCS file: /web/www/www/proprietary/po/proprietary-drm.fr-en.html,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -b -r1.15 -r1.16
--- proprietary/po/proprietary-drm.fr-en.html 3 Feb 2018 10:36:21 -0000
1.15
+++ proprietary/po/proprietary-drm.fr-en.html 26 Feb 2018 13:00:13 -0000
1.16
@@ -29,6 +29,24 @@
</p>
<ul>
+<li><p>The Netflix Android app <a
+href="http://torrentfreak.com/netflix-cracks-down-on-vpn-and-proxy-pirates-150103/";>
+forces the use of Google DNS</a>. This is one of the methods that Netflix
+uses to enforce the geolocation restrictions dictated by the movie
+studios.</p>
+</li>
+
+<li><p><a
+href="https://en.wikipedia.org/wiki/High-bandwidth_Digital_Content_Protection";>
+HDCP</a> is a DRM system that encrypts video and audio data from the
+processor to the monitor. It is implemented mainly in hardware, but
+the system software also participates, which makes it qualify as
+malware.</p>
+
+<p>Besides controlling users, HDCP denies their fair-use rights and
+causes numerous practical problems.</p>
+</li>
+
<li><p>iTunes videos have DRM, which allows Apple to <a
href="https://en.wikipedia.org/wiki/FairPlay";>dictate where its customers can
watch the videos they purchased</a>.</p>
@@ -139,23 +157,6 @@
</li>
<li>
-<p><a
href="https://www.eff.org/deeplinks/2008/11/apple-downgrades-macbook-video-drm";>DRM
-in MacOS</a>. This article focuses on the fact that a new model of
-Macbook introduced a requirement for monitors to have malicious
-hardware, but DRM software in MacOS is involved in activating the
-hardware. The software for accessing iTunes is also responsible.
-</p>
-
-<p>A further consequence of this malware is that users may have
-trouble
-<a
href="http://appleinsider.com/articles/08/11/18/apples_new_macbooks_have_built_in_copy_protection_measures";>playing
-videos on auxiliary large screens</a>. (The article, from a
-publication whose name suggests it idolizes Apple, treats these
-restrictions as irreproachable.)
-</p>
-</li>
-
-<li>
<p><a href="https://www.eff.org/deeplinks/2008/02/adobe-pushes-drm-flash";>
DRM in Flash Player</a>.
</p>
@@ -251,7 +252,7 @@
<p class="unprintable">Updated:
<!-- timestamp start -->
-$Date: 2018/02/03 10:36:21 $
+$Date: 2018/02/26 13:00:13 $
<!-- timestamp end -->
</p>
</div>
Index: philosophy/surveillance-testimony.fr.html
===================================================================
RCS file: philosophy/surveillance-testimony.fr.html
diff -N philosophy/surveillance-testimony.fr.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ philosophy/surveillance-testimony.fr.html 26 Feb 2018 13:00:13 -0000
1.1
@@ -0,0 +1,157 @@
+<!--#set var="ENGLISH_PAGE" value="/philosophy/surveillance-testimony.en.html"
-->
+
+<!--#include virtual="/server/header.fr.html" -->
+<!-- Parent-Version: Revision: 1.85 -->
+
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>Déclaration concernant la surveillance - GNU Project - Free Software
+Foundation</title>
+
+<!--#include virtual="/philosophy/po/surveillance-testimony.translist" -->
+<!--#include virtual="/server/banner.fr.html" -->
+<h2>Déclaration concernant la surveillance</h2>
+
+<p><em>Déclaration de Richard Stallman au Conseil municipal de Cambridge
+(Massachusetts) le 22 janvier 2018, Ã propos d'un projet d'ordonnance sur la
+surveillance.</em></p>
+<hr class="thin" />
+
+<p><strong>Le Maire, M. McGovern :</strong> Merci. Richard Stallman, suivi
+d'Elaine DeRosa.</p>
+
+<p><strong>RMSÂ :</strong> Je suis ici pour parler de la <a
+href="https://offnow.org/proposed-cambridge-ordinance-would-take-first-step-toward-limiting-surveillance-state/";>proposition
+d'ordonnance sur la surveillance</a>. J'ai une copie de ce que j'ai imprimé
+et quelques suggestions.</p>
+
+<p>Tout d'abord, il y a une définition de la « surveillance » qui, je
pense,
+est trop étroite. Outre « les mouvements, le comportement et les actionsÂ
»,
+elle devrait inclure les communications.</p>
+
+<p>Ensuite, au lieu de dire seulement « sur un sujet dont on peut
raisonnement
+s'attendre à ce qu'il suscite des inquiétudes », tout enregistrement de ce
+qui est observé doit être considéré comme suscitant des inquiétudes au
plan
+des libertés civiles.</p>
+
+<p>Il y a aussi une définition des « technologies de surveillance » qui,
à mon
+avis, est bien trop limitée.</p>
+
+<p>Je suggère que tout appareil ou système physique qui comporte des
+ordinateurs sur lesquels s'exécute du logiciel ayant une capacité de
+surveillance est une technologie de surveillance. Toute technologie qui peut
+faire de la surveillance est une technologie de surveillance.</p>
+
+<p>La définition de la « capacité de surveillance » est correcte, il me
semble.</p>
+
+<p>De plus, s'agissant de l'application des technologies de surveillance, la
+« permission en cas d'urgence » est bien trop vague. Il serait facile d'en
+donner une interprétation permettant de décider qu'il existe de nos jours un
+certain type de menace et que [cette menace] existera toujours, ce qui
+autoriserait la surveillance indéfiniment sur la base de l'urgence.</p>
+
+<p>Eh bien, c'est le genre de fausse urgence que nous ne devons pas
+accepter. Cette exigence doit être assez spécifique et assez claire pour
+qu'on ne puisse pas la contourner.</p>
+
+<p>Je suggère que ceci soit traité comme les écoutes téléphoniques et les
+perquisitions au domicile de quelqu'un.</p>
+
+<p>Cela dit, il y a des circonstances où il est possible de perquisitionner le
+domicile de quelqu'un en urgence. C'est permis. Mais en général on doit
+obtenir une ordonnance du tribunal [pour le faire].</p>
+
+<p>Et je pense que la même exigence doit s'appliquer à tout acte de
+surveillance qui ne soit pas passé par la procédure normale.</p>
+
+<p>Le [point] numéro 9 parle des « personnes blessées en violation de
+l'ordonnance », mais je ne pense pas qu'il y ait une définition de ce que
+signifie « être blessé ».</p>
+
+<p>Je voudrais suggérer qu'une personne surveillée est une personne
blessée.</p>
+
+<p>Merci.</p>
+
+<div class="translators-notes">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.-->
+ </div>
+</div>
+
+<!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.fr.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<p>Veuillez envoyer les requêtes concernant la FSF et GNU à <a
+href="mailto:address@hidden";><address@hidden></a>. Il existe aussi <a
+href="/contact/">d'autres moyens de contacter</a> la FSF. Les liens
+orphelins et autres corrections ou suggestions peuvent être signalés à <a
+href="mailto:address@hidden";><address@hidden></a>.</p>
+
+<p>
+<!-- TRANSLATORS: Ignore the original text in this paragraph,
+ replace it with the translation of these two:
+
+ We work hard and do our best to provide accurate, good quality
+ translations. However, we are not exempt from imperfection.
+ Please send your comments and general suggestions in this regard
+ to <a href="mailto:address@hidden";>
+
+ <address@hidden></a>.</p>
+
+ <p>For information on coordinating and submitting translations of
+ our web pages, see <a
+ href="/server/standards/README.translations.html">Translations
+ README</a>. -->
+Nous faisons le maximum pour proposer des traductions fidèles et de bonne
+qualité, mais nous ne sommes pas parfaits. Merci d'adresser vos commentaires
+sur cette page, ainsi que vos suggestions d'ordre général sur les
+traductions, Ã <a href="mailto:address@hidden";>
+<address@hidden></a>.</p>
+<p>Pour tout renseignement sur la coordination et la soumission des
+traductions de nos pages web, reportez-vous au <a
+href="/server/standards/README.translations.html">guide de traduction</a>.</p>
+</div>
+
+<!-- Regarding copyright, in general, standalone pages (as opposed to
+ files generated as part of manuals) on the GNU web server should
+ be under CC BY-ND 4.0. Please do NOT change or remove this
+ without talking with the webmasters or licensing team first.
+ Please make sure the copyright date is consistent with the
+ document. For web pages, it is ok to list just the latest year the
+ document was modified, or published.
+
+ If you wish to list earlier years, that is ok too.
+ Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
+ years, as long as each year in the range is in fact a copyrightable
+ year, i.e., a year in which the document was published (including
+ being publicly visible on the web or in a revision control system).
+
+ There is more detail about copyright years in the GNU Maintainers
+ Information document, www.gnu.org/prep/maintain. -->
+<p>Copyright © 2018 Richard Stallman</p>
+
+<p>Cette page peut être utilisée suivant les conditions de la licence <a
+rel="license"
+href="http://creativecommons.org/licenses/by-nd/4.0/deed.fr";>Creative
+Commons attribution, pas de modification, 4.0Â internationale (CCÂ BY-ND
+4.0)</a>.</p>
+
+<!--#include virtual="/server/bottom-notes.fr.html" -->
+<div class="translators-credits">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.-->
+Traduction : Thérèse Godefroy<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: 2018/02/26 13:00:13 $
+
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>
Index: philosophy/po/surveillance-testimony.fr-en.html
===================================================================
RCS file: philosophy/po/surveillance-testimony.fr-en.html
diff -N philosophy/po/surveillance-testimony.fr-en.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ philosophy/po/surveillance-testimony.fr-en.html 26 Feb 2018 13:00:13
-0000 1.1
@@ -0,0 +1,123 @@
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: Revision: 1.85 -->
+<title>Surveillance Testimony - GNU Project - Free Software Foundation</title>
+ <!--#include virtual="/philosophy/po/surveillance-testimony.translist" -->
+<!--#include virtual="/server/banner.html" -->
+<h2>Surveillance Testimony</h2>
+
+<p><em>Richard Stallman's statement to the Cambridge City Council, Jan 22,
2018,
+about the proposed Cambridge surveillance ordinance.</em></p>
+<hr class="thin" />
+
+<p><strong>Mayor McGovern:</strong> Thank you. Richard Stallman followed by
Elaine DeRosa.</p>
+
+<p><strong>RMS:</strong> I'm here to speak about the proposed surveillance
ordinance.
+I've got a copy of what I printed out, and I have some suggestions.</p>
+
+<p>First of all there's a Definition of “surveillance” which I
think is
+too narrow. In addition to “movements, behavior and actions,” it
+should include communications.</p>
+
+<p>Furthermore, instead of just saying “in a matter that is reasonably
+likely to raise concerns,” any recording of what is observed should be
+assumed to raise civil liberties concerns.</p>
+
+<p>There's also a definition of “surveillance technology”, which I
think is
+far too limited.</p>
+
+<p>I suggest that any physical device or system including computers running
+software that has surveillance capability is surveillance technology.
+Any technology that can do surveillance is surveillance technology.</p>
+
+<p>The definition of “surveillance capability” I think is pretty
good.</p>
+
+<p>In addition, when it comes to what to do about surveillance
+technology, the Emergency Permission seems far too loose. It would be
+easy to interpret this such that one could decide there's nowadays
+some sort of threat, and there always will be [that threat], so
+surveillance is permitted on an emergency basis forever.</p>
+
+<p>Well, that's the kind of false emergency that we shouldn't accept.
+This requirement should be specific and clear enough that that can't
+pass under it.</p>
+
+<p>I suggest treating it like a wiretap or searching people's houses.</p>
+
+<p>Now there are times when it's possible to search someone's house
+urgently. That's permitted. But in general you have to get a court
+order [to do a search].</p>
+
+<p>And I think that same requirement should apply to any kind of surveillance
+that hasn't gone through the regular process.</p>
+
+<p>[Item] number 9 talks about “persons injured in violation of the
Ordinance”,
+but I don't think there's a definition of what it means to be injured.</p>
+
+<p>I'd like to suggest that to be surveilled is to be injured.</p>
+
+<p>Thank you.</p>
+
+</div><!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<p>Please send general FSF & GNU inquiries to
+<a href="mailto:address@hidden";><address@hidden></a>.
+There are also <a href="/contact/">other ways to contact</a>
+the FSF. Broken links and other corrections or suggestions can be sent
+to <a href="mailto:address@hidden";><address@hidden></a>.</p>
+
+<p><!-- TRANSLATORS: Ignore the original text in this paragraph,
+ replace it with the translation of these two:
+
+ We work hard and do our best to provide accurate, good quality
+ translations. However, we are not exempt from imperfection.
+ Please send your comments and general suggestions in this regard
+ to <a href="mailto:address@hidden";>
+ <address@hidden></a>.</p>
+
+ <p>For information on coordinating and submitting translations of
+ our web pages, see <a
+ href="/server/standards/README.translations.html">Translations
+ README</a>. -->
+Please see the <a
+href="/server/standards/README.translations.html">Translations
+README</a> for information on coordinating and submitting translations
+of this article.</p>
+</div>
+
+<!-- Regarding copyright, in general, standalone pages (as opposed to
+ files generated as part of manuals) on the GNU web server should
+ be under CC BY-ND 4.0. Please do NOT change or remove this
+ without talking with the webmasters or licensing team first.
+ Please make sure the copyright date is consistent with the
+ document. For web pages, it is ok to list just the latest year the
+ document was modified, or published.
+
+ If you wish to list earlier years, that is ok too.
+ Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
+ years, as long as each year in the range is in fact a copyrightable
+ year, i.e., a year in which the document was published (including
+ being publicly visible on the web or in a revision control system).
+
+ There is more detail about copyright years in the GNU Maintainers
+ Information document, www.gnu.org/prep/maintain. -->
+
+<p>Copyright © 2018 Richard Stallman</p>
+
+<p>This page is licensed under a <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/4.0/";>Creative
+Commons Attribution-NoDerivatives 4.0 International License</a>.</p>
+
+<!--#include virtual="/server/bottom-notes.html" -->
+
+<p class="unprintable">Updated:
+<!-- timestamp start -->
+$Date: 2018/02/26 13:00:13 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- www philosophy/po/surveillance-testimony.transl...,
GNUN <=