[Trad Gnu] Nouvel article de RMS : The Boundary Between Hardware And Software

[Thérèse Godefroy <godef.th AT free.fr>]

Bonsoir les trad-gnusiens,

Voici un article assez court (6 petits paragraphes) qui intéressera les
amateurs de circuits logiques programmables. Comme il y en a partout, ça
devrait faire pas mal de monde.

https://www.gnu.org/philosophy/hardware-software-boundary.html

Je le mettrai sur pad si personne ne veut s'approprier le POT (en pj).

Amicalement,
Thérèse
# 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 <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: hardware-software-boundary.html\n"
"POT-Creation-Date: 2015-03-10 14:55+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL AT li.org>\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 ""
"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."
msgstr ""

#. type: Content of: <p>
msgid ""
"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."
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 &amp; GNU inquiries to <a "
"href=\"mailto:gnu AT gnu.org\";>&lt;gnu AT gnu.org&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:webmasters AT gnu.org\";>&lt;webmasters AT gnu.org&gt;</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:web-translators AT gnu.org";>
#
#.         &lt;web-translators AT gnu.org&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>. 
#. 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 &copy; 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 ""