www/philosophy po/hardware-software-boundary.fr...

[GNUN]

CVSROOT:        /web/www
Module name:    www
Changes by:     GNUN <gnun>     15/03/15 12:57:01

Modified files:
        philosophy/po  : hardware-software-boundary.fr.po 
                         hardware-software-boundary.translist 
Added files:
        philosophy     : hardware-software-boundary.fr.html 
        philosophy/po  : hardware-software-boundary.fr-en.html 

Log message:
        Automatic update by GNUnited Nations.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/hardware-software-boundary.fr.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/hardware-software-boundary.fr.po?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/hardware-software-boundary.translist?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/hardware-software-boundary.fr-en.html?cvsroot=www&rev=1.1

Patches:
Index: po/hardware-software-boundary.fr.po
===================================================================
RCS file: /web/www/www/philosophy/po/hardware-software-boundary.fr.po,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- po/hardware-software-boundary.fr.po 15 Mar 2015 12:42:00 -0000      1.1
+++ po/hardware-software-boundary.fr.po 15 Mar 2015 12:57:00 -0000      1.2
@@ -10,9 +10,10 @@
 "PO-Revision-Date: 2015-03-15 10:15+0100\n"
 "Last-Translator: Sébastien Poher <address@hidden>\n"
 "Language-Team: French <address@hidden>\n"
+"Language: fr\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit"
+"Content-Transfer-Encoding: 8bit\n"
 
 #. type: Content of: <title>
 msgid ""

Index: po/hardware-software-boundary.translist
===================================================================
RCS file: /web/www/www/philosophy/po/hardware-software-boundary.translist,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- po/hardware-software-boundary.translist     10 Mar 2015 14:57:57 -0000      
1.1
+++ po/hardware-software-boundary.translist     15 Mar 2015 12:57:00 -0000      
1.2
@@ -3,6 +3,7 @@
 value='<div id="translations">
 <p>
 <span dir="ltr" class="original"><a lang="en" hreflang="en" 
href="/philosophy/hardware-software-boundary.en.html">English</a>&nbsp;[en]</span>
 &nbsp;
+<span dir="ltr"><a lang="fr" hreflang="fr" 
href="/philosophy/hardware-software-boundary.fr.html">français</a>&nbsp;[fr]</span>
 &nbsp;
 </p>
 </div>' -->
 <!--#if expr="$HTML_BODY = yes" -->

Index: hardware-software-boundary.fr.html
===================================================================
RCS file: hardware-software-boundary.fr.html
diff -N hardware-software-boundary.fr.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ hardware-software-boundary.fr.html  15 Mar 2015 12:56:59 -0000      1.1
@@ -0,0 +1,144 @@
+<!--#set var="ENGLISH_PAGE" 
value="/philosophy/hardware-software-boundary.en.html" -->
+
+<!--#include virtual="/server/header.fr.html" -->
+<!-- Parent-Version: 1.77 -->
+
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>La frontière entre matériel et logiciel - Projet GNU - Free Software
+Foundation</title>
+
+<!--#include virtual="/philosophy/po/hardware-software-boundary.translist" -->
+<!--#include virtual="/server/banner.fr.html" -->
+<h2>La frontière entre matériel et logiciel</h2>
+
+<p>Où se situe la frontière, dans un appareil numérique, entre matériel et
+logiciel ? Nous pouvons la déterminer en appliquant les définitions
+suivantes : le logiciel est la partie opérante d'un appareil qui peut être
+copiée et modifiée dans un ordinateur ; le matériel est la partie opérante
+qui ne peut pas l'être. C'est le meilleur moyen de faire la distinction car
+cela renvoie à des conséquences pratiques.</p>
+
+<p>Il y a une zone grise entre le matériel, d'une part, et d'autre part du
+logiciel comprenant un firmware qui <em>peut</em> être mis à jour ou
+remplacé, mais qui n'est pas conçu pour être mis à jour ou remplacé une 
fois
+le produit vendu. En termes conceptuels, la zone grise est plutôt mince. En
+pratique, ceci est important car de nombreux produits sont concernés. Nous
+pouvons donc presque considérer ce firmware comme du matériel.</p>
+
+<p>Certaines personnes ont prétendu que préinstaller des firmwares et des
+circuits logiques programmables de type « FPGA » (réseau de portes
+programmables <cite>in situ</cite>) « effacerait la frontière entre 
matériel
+et logiciel », mais je pense qu'il s'agit là d'une mauvaise interprétation
+des faits. Un firmware installé lors de l'utilisation est un logiciel ; un
+firmware intégré à un appareil et non modifiable est un logiciel par nature,
+mais nous pouvons le traiter comme si c'était un circuit. Dans le cas des
+FPGA, le circuit FPGA lui-même est un matériel, mais le schéma logique de
+portes chargé dans ce circuit FPGA est une sorte de firmware.</p>
+
+<p>Faire fonctionner des schémas de portes libres sur des FPGA pourrait être
+une méthode utile pour créer des appareils numériques libres au niveau des
+circuits. Toutefois, pour rendre ces FPGA utilisables dans le monde du
+libre, nous avons besoin d'outils de développement libres
+adaptés. L'obstacle à cela est que le format du fichier de schéma logique de
+portes chargé dans le FPGA est secret. Jusqu'à récemment, il n'existait
+<em>aucun</em> modèle de FPGA pour lequel ces fichiers pouvaient être
+reproduits sans outils non libres (privateurs).</p>
+
+<p>Grâce aux efforts de rétroingénierie, il est maintenant possible de 
compiler
+des programmes écrits en C et de les exécuter sur le circuit FPGA Xilinx
+Spartan 6 LX9. Ces outils ne gèrent pas encore le code HDL (langage de
+description matériel), cela n'offre donc pas une alternative utilisable pour
+de vrais circuits numériques. D'un autre côté, ce modèle de FPGA se fait
+vieux. Ces outils constituent une formidable avancée en comparaison de la
+situation d'il y a quelques années, mais la route est encore longue avant
+que les FPGA ne soient totalement utilisables en toute liberté.</p>
+
+<p>Quant au code HDL lui-même, il peut agir en tant que logiciel (lorsqu'il
+s'exécute dans un émulateur ou après chargement dans un FPGA) ou en tant que
+schéma de composant matériel (lorsqu'il est mis en œuvre dans des
+semiconducteurs inamovibles ou dans un circuit imprimé).</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";>&lt;address@hidden&gt;</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";>&lt;address@hidden&gt;</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";>
+
+        &lt;address@hidden&gt;</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";>
+&lt;address@hidden&gt;</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 3.0 US.  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 &copy; 2015 Free Software Foundation, Inc.</p>
+
+<p>Cette page peut être utilisée suivant les conditions de la licence <a
+rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/deed.fr";>Creative
+Commons attribution de paternité, pas de modification, 3.0 États-Unis
+(CCÂ BY-ND 3.0Â US)</a>.</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 : Sébastien Poher<br />Révision : <a
+href="mailto:address@hidden";>address@hidden</a></div>
+
+<p class="unprintable"><!-- timestamp start -->
+Dernière mise à jour :
+
+$Date: 2015/03/15 12:56:59 $
+
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>

Index: po/hardware-software-boundary.fr-en.html
===================================================================
RCS file: po/hardware-software-boundary.fr-en.html
diff -N po/hardware-software-boundary.fr-en.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ po/hardware-software-boundary.fr-en.html    15 Mar 2015 12:57:00 -0000      
1.1
@@ -0,0 +1,115 @@
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.77 -->
+<title>The Boundary Between Hardware And Software
+- GNU Project - Free Software Foundation</title>
+ <!--#include virtual="/philosophy/po/hardware-software-boundary.translist" -->
+<!--#include virtual="/server/banner.html" -->
+<h2>The Boundary Between Hardware And Software</h2>
+
+<p>What is the boundary, in digital devices, between hardware and
+software?  We can find it by applying the definitions: software is the
+operational part of a device that can be copied and changed in a
+computer; hardware is the operational part that can't be.  This is the
+right way to make the distinction because it relates to the practical
+consequences.</p>
+
+<p>There is a gray area between hardware and software that contains
+firmware that <em>can</em> be upgraded or replaced, but is not meant
+ever to be upgraded or replaced once the product is sold.  In
+conceptual terms, the gray area is rather narrow.  In practice, it is
+important because many products fall in it.  We can treat that
+firmware as hardware with a small stretch.</p>
+
+<p>Some have said that preinstalled firmware programs and
+Field-Programmable Gate Array chips (FPGAs) &ldquo;blur the boundary
+between hardware and software,&rdquo; but I think that is a
+misinterpretation of the facts.  Firmware that is installed during use
+is software; firmware that is delivered inside the device and can't be changed
+is software by nature, but we can treat it as if it were a circuit.
+As for FPGAs, the FPGA itself is hardware, but the gate pattern that
+is loaded into the FPGA is a kind of firmware.</p>
+
+<p>Running free gate patterns on FPGAs could potentially be a useful
+method for making digital devices that are free at the circuit level.
+However, to make FPGAs usable in the free world, we need free
+development tools for them.  The obstacle is that the format of the
+gate pattern file that gets loaded into the FPGA is secret.  Until
+recently there was <em>no</em> model of FPGA for which those files
+could be produced without nonfree (proprietary) tools.</p>
+
+<p>Thanks to a reverse-engineering effort, it is now possible to compile
+C programs and run them on the Xilinx Spartan 6 LX9 FPGA.  The tools
+do not yet support HDL (hardware definition language) code, though, so
+this does not offer a usable substitute for real digital chips.
+Meanwhile, that model of FPGA is starting to get old.  These tools
+constitute a tremendous advance over the situation a few years ago,
+but there's a long way to go before FPGAs are fully usable in freedom.</p>
+
+<p>As for the HDL code itself, it can act as software (when it is run on
+an emulator or loaded into an FPGA) or as a hardware design (when it
+is realized in immutable silicon or a circuit board).</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 &amp; GNU inquiries to
+<a href="mailto:address@hidden";>&lt;address@hidden&gt;</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";>&lt;address@hidden&gt;</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";>
+        &lt;address@hidden&gt;</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 3.0 US.  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 &copy; 2015 Free Software Foundation, Inc.</p>
+
+<p>This page is licensed under a <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/";>Creative
+Commons Attribution-NoDerivs 3.0 United States License</a>.</p>
+
+<!--#include virtual="/server/bottom-notes.html" -->
+
+<p class="unprintable">Updated:
+<!-- timestamp start -->
+$Date: 2015/03/15 12:57:00 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>