[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www/philosophy hardware-software-boundary.fr.ht...
|
From: |
Therese Godefroy |
|
Subject: |
www/philosophy hardware-software-boundary.fr.ht... |
|
Date: |
Mon, 13 Apr 2015 11:46:07 +0000 |
CVSROOT: /webcvs/www
Module name: www
Changes by: Therese Godefroy <th_g> 15/04/13 11:46:07
Removed files:
philosophy : hardware-software-boundary.fr.html
hardware-software-boundary.html
philosophy/po : hardware-software-boundary.fr-en.html
hardware-software-boundary.fr.po
hardware-software-boundary.pot
hardware-software-boundary.translist
Log message:
Remove hardware-software-boundary and its French translation (replaced
by free-hardware-designs).
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/hardware-software-boundary.fr.html?cvsroot=www&r1=1.2&r2=0
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/hardware-software-boundary.html?cvsroot=www&r1=1.3&r2=0
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/hardware-software-boundary.fr-en.html?cvsroot=www&r1=1.2&r2=0
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/hardware-software-boundary.fr.po?cvsroot=www&r1=1.4&r2=0
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/hardware-software-boundary.pot?cvsroot=www&r1=1.2&r2=0
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/hardware-software-boundary.translist?cvsroot=www&r1=1.2&r2=0
Patches:
Index: hardware-software-boundary.fr.html
===================================================================
RCS file: hardware-software-boundary.fr.html
diff -N hardware-software-boundary.fr.html
--- hardware-software-boundary.fr.html 21 Mar 2015 09:27:18 -0000 1.2
+++ /dev/null 1 Jan 1970 00:00:00 -0000
@@ -1,146 +0,0 @@
-<!--#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>Entre le matériel et le logiciel, il existe une zone grise occupée par les
-micrologiciels <cite>[firmware]</cite> qui <em>peuvent</em> être mis à jour
-ou remplacés, mais ne sont pas conçus pour être mis à jour ou remplacés
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 ces micrologiciels comme du
-matériel.</p>
-
-<p>Certaines personnes ont prétendu que préinstaller des micrologiciels 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 micrologiciel installé lors de l'utilisation est un logiciel
-ordinaire ; un micrologiciel 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 du matériel,
-mais le schéma logique de portes chargé dans ce circuit FPGA est une sorte
-de micrologiciel.</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";><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 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 © 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/21 09:27:18 $
-
-<!-- timestamp end -->
-</p>
-</div>
-</div>
-</body>
-</html>
Index: hardware-software-boundary.html
===================================================================
RCS file: hardware-software-boundary.html
diff -N hardware-software-boundary.html
--- hardware-software-boundary.html 20 Mar 2015 20:59:11 -0000 1.3
+++ /dev/null 1 Jan 1970 00:00:00 -0000
@@ -1,115 +0,0 @@
-<!--#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>Between hardware and software there is a gray area consisting of
-firmware that <em>can</em> be upgraded or replaced, but is not meant
-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) “blur the boundary
-between hardware and software,” 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 & 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 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 © 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/20 20:59:11 $
-<!-- 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
--- po/hardware-software-boundary.fr-en.html 21 Mar 2015 09:27:19 -0000
1.2
+++ /dev/null 1 Jan 1970 00:00:00 -0000
@@ -1,115 +0,0 @@
-<!--#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>Between hardware and software there is a gray area consisting of
-firmware that <em>can</em> be upgraded or replaced, but is not meant
-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) “blur the boundary
-between hardware and software,” 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 & 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 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 © 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/21 09:27:19 $
-<!-- timestamp end -->
-</p>
-</div>
-</div>
-</body>
-</html>
Index: po/hardware-software-boundary.fr.po
===================================================================
RCS file: po/hardware-software-boundary.fr.po
diff -N po/hardware-software-boundary.fr.po
--- po/hardware-software-boundary.fr.po 21 Mar 2015 09:06:42 -0000 1.4
+++ /dev/null 1 Jan 1970 00:00:00 -0000
@@ -1,201 +0,0 @@
-# French translation of
http://www.gnu.org/philosophy/hardware-software-boundary.html
-# Copyright (C) 2015 Free Software Foundation, Inc.
-# This file is distributed under the same license as the original article.
-# Sébastien Poher <address@hidden>, 2015.
-#
-msgid ""
-msgstr ""
-"Project-Id-Version: hardware-software-boundary.html\n"
-"POT-Creation-Date: 2015-03-20 21:25+0000\n"
-"PO-Revision-Date: 2015-03-21 10:04+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\n"
-
-#. type: Content of: <title>
-msgid ""
-"The Boundary Between Hardware And Software - GNU Project - Free Software "
-"Foundation"
-msgstr ""
-"La frontière entre matériel et logiciel - Projet GNU - Free Software "
-"Foundation"
-
-#. type: Content of: <h2>
-msgid "The Boundary Between Hardware And Software"
-msgstr "La frontière entre matériel et logiciel"
-
-#. type: Content of: <p>
-msgid ""
-"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."
-msgstr ""
-"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."
-
-#. type: Content of: <p>
-msgid ""
-"Between hardware and software there is a gray area consisting of firmware "
-"that <em>can</em> be upgraded or replaced, but is not meant 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."
-msgstr ""
-"Entre le matériel et le logiciel, il existe une zone grise occupée par les "
-"micrologiciels <cite>[firmware]</cite> qui <em>peuvent</em> être mis à jour
"
-"ou remplacés, mais ne sont pas conçus pour être mis à jour ou remplacés
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 ces micrologiciels comme du
"
-"matériel."
-
-#. type: Content of: <p>
-msgid ""
-"Some have said that preinstalled firmware programs and Field-Programmable "
-"Gate Array chips (FPGAs) “blur the boundary between hardware and "
-"software,” 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."
-msgstr ""
-"Certaines personnes ont prétendu que préinstaller des micrologiciels 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 micrologiciel installé lors de l'utilisation est un logiciel "
-"ordinaire ; un micrologiciel 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 du matériel, "
-"mais le schéma logique de portes chargé dans ce circuit FPGA est une sorte "
-"de micrologiciel."
-
-#. type: Content of: <p>
-msgid ""
-"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."
-msgstr ""
-"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)."
-
-#. type: Content of: <p>
-msgid ""
-"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."
-msgstr ""
-"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é."
-
-#. type: Content of: <p>
-msgid ""
-"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)."
-msgstr ""
-"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é)."
-
-#. TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.
-#. type: Content of: <div>
-msgid "*GNUN-SLOT: TRANSLATOR'S NOTES*"
-msgstr " "
-
-#. type: Content of: <div><div><p>
-msgid ""
-"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"
-"org></a>."
-msgstr ""
-"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>."
-
-#. 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>.
-#. type: Content of: <div><div><p>
-msgid ""
-"Please see the <a href=\"/server/standards/README.translations.html"
-"\">Translations README</a> for information on coordinating and submitting "
-"translations of this article."
-msgstr ""
-"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";> <web-"
-"address@hidden></a>.</p>\n"
-"<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>."
-
-#. type: Content of: <div><p>
-msgid "Copyright © 2015 Free Software Foundation, Inc."
-msgstr "Copyright © 2015 Free Software Foundation, Inc."
-
-#. type: Content of: <div><p>
-msgid ""
-"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>."
-msgstr ""
-"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>."
-
-#. TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.
-#. type: Content of: <div><div>
-msgid "*GNUN-SLOT: TRANSLATOR'S CREDITS*"
-msgstr ""
-"Traduction : Sébastien Poher<br />Révision : <a
href=\"mailto:address@hidden";
-"org\">address@hidden</a>"
-
-#. timestamp start
-#. type: Content of: <div><p>
-msgid "Updated:"
-msgstr "Dernière mise à jour :"
Index: po/hardware-software-boundary.pot
===================================================================
RCS file: po/hardware-software-boundary.pot
diff -N po/hardware-software-boundary.pot
--- po/hardware-software-boundary.pot 20 Mar 2015 21:26:55 -0000 1.2
+++ /dev/null 1 Jan 1970 00:00:00 -0000
@@ -1,140 +0,0 @@
-# LANGUAGE translation of
http://www.gnu.org/philosophy/hardware-software-boundary.html
-# Copyright (C) YEAR Free Software Foundation, Inc.
-# This file is distributed under the same license as the original article.
-# FIRST AUTHOR <address@hidden>, YEAR.
-#
-#, fuzzy
-msgid ""
-msgstr ""
-"Project-Id-Version: hardware-software-boundary.html\n"
-"POT-Creation-Date: 2015-03-20 21:25+0000\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <address@hidden>\n"
-"Language-Team: LANGUAGE <address@hidden>\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=CHARSET\n"
-"Content-Transfer-Encoding: ENCODING"
-
-#. type: Content of: <title>
-msgid ""
-"The Boundary Between Hardware And Software - GNU Project - Free Software "
-"Foundation"
-msgstr ""
-
-#. type: Content of: <h2>
-msgid "The Boundary Between Hardware And Software"
-msgstr ""
-
-#. type: Content of: <p>
-msgid ""
-"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."
-msgstr ""
-
-#. type: Content of: <p>
-msgid ""
-"Between hardware and software there is a gray area consisting of firmware "
-"that <em>can</em> be upgraded or replaced, but is not meant 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."
-msgstr ""
-
-#. type: Content of: <p>
-msgid ""
-"Some have said that preinstalled firmware programs and Field-Programmable "
-"Gate Array chips (FPGAs) “blur the boundary between hardware and "
-"software,” 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."
-msgstr ""
-
-#. type: Content of: <p>
-msgid ""
-"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."
-msgstr ""
-
-#. type: Content of: <p>
-msgid ""
-"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."
-msgstr ""
-
-#. type: Content of: <p>
-msgid ""
-"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)."
-msgstr ""
-
-#. TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.
-#. type: Content of: <div>
-msgid "*GNUN-SLOT: TRANSLATOR'S NOTES*"
-msgstr ""
-
-#. type: Content of: <div><div><p>
-msgid ""
-"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>."
-msgstr ""
-
-#. 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>.
-#. type: Content of: <div><div><p>
-msgid ""
-"Please see the <a "
-"href=\"/server/standards/README.translations.html\">Translations README</a> "
-"for information on coordinating and submitting translations of this article."
-msgstr ""
-
-#. type: Content of: <div><p>
-msgid "Copyright © 2015 Free Software Foundation, Inc."
-msgstr ""
-
-#. type: Content of: <div><p>
-msgid ""
-"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>."
-msgstr ""
-
-#. TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.
-#. type: Content of: <div><div>
-msgid "*GNUN-SLOT: TRANSLATOR'S CREDITS*"
-msgstr ""
-
-#. timestamp start
-#. type: Content of: <div><p>
-msgid "Updated:"
-msgstr ""
Index: po/hardware-software-boundary.translist
===================================================================
RCS file: po/hardware-software-boundary.translist
diff -N po/hardware-software-boundary.translist
--- po/hardware-software-boundary.translist 15 Mar 2015 12:57:00 -0000
1.2
+++ /dev/null 1 Jan 1970 00:00:00 -0000
@@ -1,14 +0,0 @@
-<!-- begin translist file -->
-<!--#set var="TRANSLATION_LIST"
-value='<div id="translations">
-<p>
-<span dir="ltr" class="original"><a lang="en" hreflang="en"
href="/philosophy/hardware-software-boundary.en.html">English</a> [en]</span>
-<span dir="ltr"><a lang="fr" hreflang="fr"
href="/philosophy/hardware-software-boundary.fr.html">français</a> [fr]</span>
-</p>
-</div>' -->
-<!--#if expr="$HTML_BODY = yes" -->
-<!-- Fallback for old position of translist; to be removed
- when translists in all translations are included before banner.html. -->
-<!--#echo encoding="none" var="TRANSLATION_LIST" -->
-<!--#endif -->
-<!-- end translist file -->
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- www/philosophy hardware-software-boundary.fr.ht...,
Therese Godefroy <=