[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www/philosophy/po free-hardware-designs.de.po f...
|
From: |
GNUN |
|
Subject: |
www/philosophy/po free-hardware-designs.de.po f... |
|
Date: |
Sun, 9 Apr 2023 17:30:03 -0400 (EDT) |
CVSROOT: /web/www
Module name: www
Changes by: GNUN <gnun> 23/04/09 17:30:03
Modified files:
philosophy/po : free-hardware-designs.de.po
free-hardware-designs.es.po
free-hardware-designs.fr.po
free-hardware-designs.pot
free-hardware-designs.pt-br-diff.html
free-hardware-designs.pt-br.po
free-hardware-designs.ru.po
Log message:
Automatic update by GNUnited Nations.
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/free-hardware-designs.de.po?cvsroot=www&r1=1.27&r2=1.28
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/free-hardware-designs.es.po?cvsroot=www&r1=1.24&r2=1.25
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/free-hardware-designs.fr.po?cvsroot=www&r1=1.51&r2=1.52
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/free-hardware-designs.pot?cvsroot=www&r1=1.20&r2=1.21
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/free-hardware-designs.pt-br-diff.html?cvsroot=www&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/free-hardware-designs.pt-br.po?cvsroot=www&r1=1.10&r2=1.11
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/free-hardware-designs.ru.po?cvsroot=www&r1=1.44&r2=1.45
Patches:
Index: free-hardware-designs.de.po
===================================================================
RCS file: /web/www/www/philosophy/po/free-hardware-designs.de.po,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -b -r1.27 -r1.28
--- free-hardware-designs.de.po 5 Mar 2022 14:00:32 -0000 1.27
+++ free-hardware-designs.de.po 9 Apr 2023 21:30:02 -0000 1.28
@@ -7,7 +7,7 @@
msgstr ""
"Project-Id-Version: free-hardware-designs.html\n"
"Report-Msgid-Bugs-To: Webmasters <webmasters@gnu.org>\n"
-"POT-Creation-Date: 2022-03-05 13:55+0000\n"
+"POT-Creation-Date: 2023-04-09 21:25+0000\n"
"PO-Revision-Date: 2015-07-09 22:00+0200\n"
"Last-Translator: Jоегg Kоhпе <joeko (AT) online [PUNKT] de>\n"
"Language-Team: German <www-de-translators@gnu.org>\n"
@@ -161,12 +161,25 @@
# #(part that can't be.) ??Teil mit dem dies nicht möglich ist??
#. type: Content of: <div><p>
+# | What is the boundary, in digital devices, between hardware and software?
+# | It follows from the definitions. Software is the operational part of a
+# | device that can be copied{+,+} and [-changed in-] {+modified with+} 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.
+#, fuzzy
+#| msgid ""
+#| "What is the boundary, in digital devices, between hardware and software? "
+#| "It follows from 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."
msgid ""
"What is the boundary, in digital devices, between hardware and software? It "
"follows from 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."
+"that can be copied, and modified with 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 ""
"Wo ist bei digitalen Geräten die Abgrenzung zwischen Hard- und Software? Es "
"ergibt sich aus den Definitionen. Software ist der operative Teil eines "
@@ -213,14 +226,46 @@
#. type: Content of: <div><p>
msgid ""
-"We can treat that firmware as hardware with a small stretch, but we must not "
-"try to have it both ways. If we treat certain firmware as impossible to "
-"change, since it is not realistically possible to avoid that firmware, we "
-"must also treat it as impossible to change when we might wish it could be "
-"changed. That entails refusing all upgrades or patches to that firmware. "
-"That is what I do, and this is the reason I do it. Until we can get "
-"computers with entirely free firmware, there is no feasible way to do better "
-"than this."
+"We can think of the difference between built-in firmware and equivalent "
+"hardware as a minor implementation detail, provided that we are sure in "
+"either case that it won't be changed. A hardware circuit can't be changed; "
+"that's its nature. If it's acceptable for a device to be implemented with "
+"internal circuitry that no one can alter, then an internal program that no "
+"one can alter is no worse. It would not be sensible to reject an equivalent "
+"internal software implementation, when operationally they are "
+"indistinguishable."
+msgstr ""
+
+#. type: Content of: <div><p>
+msgid ""
+"The equivalence falls apart, however, when the software implementation is "
+"not totally internal and some company can modify that code. For example, "
+"when firmware needs to be copied into the device to make the device "
+"function, or included in the system distribution that you install, that is "
+"no <em>internal</em> software implementation; rather, it is a piece of "
+"installed nonfree software. It is unjust because some manufacturer can "
+"change it but you can't."
+msgstr ""
+
+#. type: Content of: <div><p>
+msgid ""
+"In order for a firmware program to be morally equivalent to hardware, it "
+"must be unmodifiable. What about when the device can't possibly run without "
+"some firmware and it offers a way to modify that? We can make that firmware "
+"unmodifiable in practice by taking care never to let that replacement "
+"happen. This solution is not entirely clean, but no entirely clean solution "
+"has been proposed; this is the only way we know to preserve some meaning for "
+"the rejection of nonfree software while using that device. This is much "
+"better than just giving up."
+msgstr ""
+
+#. type: Content of: <div><p>
+msgid ""
+"But we can't have it both ways. To make preinstalled firmware effectively "
+"unmodifiable by not letting anyone invoke the method to change it, we must "
+"carry that out without exception even when there are changes we would wish "
+"were installed. That means rejecting all upgrades or patches to that "
+"firmware."
msgstr ""
#. type: Content of: <div><p>
@@ -881,10 +926,10 @@
"standards/README.translations\">LIESMICH für Ãbersetzungen</a>."
#. type: Content of: <div><p>
-# | Copyright © [-2015-] {+2015, 2021, 2022+} Richard Stallman
+# | Copyright © [-2015-] {+2015, 2021, 2022, 2023+} Richard Stallman
#, fuzzy
#| msgid "Copyright © 2015 Richard Stallman"
-msgid "Copyright © 2015, 2021, 2022 Richard Stallman"
+msgid "Copyright © 2015, 2021, 2022, 2023 Richard Stallman"
msgstr "Copyright © 2015 Richard Stallman."
#. type: Content of: <div><p>
Index: free-hardware-designs.es.po
===================================================================
RCS file: /web/www/www/philosophy/po/free-hardware-designs.es.po,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -b -r1.24 -r1.25
--- free-hardware-designs.es.po 9 Apr 2023 21:25:25 -0000 1.24
+++ free-hardware-designs.es.po 9 Apr 2023 21:30:02 -0000 1.25
@@ -8,7 +8,7 @@
msgid ""
msgstr ""
"Project-Id-Version: free-hardware-designs.html\n"
-"POT-Creation-Date: 2022-03-05 13:55+0000\n"
+"POT-Creation-Date: 2023-04-09 21:25+0000\n"
"PO-Revision-Date: 2022-05-26 16:15+0200\n"
"Last-Translator: Dora Scilipoti <dora AT gnu DOT org>\n"
"Language-Team: www-es-general@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: 2023-04-09 21:25+0000\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
"X-Generator: Poedit 2.4.2\n"
@@ -233,12 +234,25 @@
msgstr "La frontera entre el hardware y el software"
#. type: Content of: <div><p>
+# | What is the boundary, in digital devices, between hardware and software?
+# | It follows from the definitions. Software is the operational part of a
+# | device that can be copied{+,+} and [-changed in-] {+modified with+} 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.
+#, fuzzy
+#| msgid ""
+#| "What is the boundary, in digital devices, between hardware and software? "
+#| "It follows from 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."
msgid ""
"What is the boundary, in digital devices, between hardware and software? It "
"follows from 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."
+"that can be copied, and modified with 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 ""
"¿Dónde se sitúa el lÃmite entre el hardware y el software en los "
"dispositivos digitales? Se deduce de las definiciones. El software es la "
@@ -270,24 +284,47 @@
#. type: Content of: <div><p>
msgid ""
-"We can treat that firmware as hardware with a small stretch, but we must not "
-"try to have it both ways. If we treat certain firmware as impossible to "
-"change, since it is not realistically possible to avoid that firmware, we "
-"must also treat it as impossible to change when we might wish it could be "
-"changed. That entails refusing all upgrades or patches to that firmware. "
-"That is what I do, and this is the reason I do it. Until we can get "
-"computers with entirely free firmware, there is no feasible way to do better "
-"than this."
-msgstr ""
-"Podemos considerar ese <cite>firmware</cite> casi como hardware, pero no "
-"debemos pretender que sea ambas cosas a la vez. Si consideramos determinado "
-"<cite>firmware</cite> como imposible de modificar, porque en la práctica no "
-"es posible evitar ese <cite>firmware</cite>, entonces debemos también "
-"considerarlo como imposible de modificar cuando desearÃamos que eso fuera "
-"posible. Esto implica rechazar todas las actualizaciones o correcciones de "
-"ese <cite>firmware</cite>. Es lo que yo hago, y por eso lo hago. Mientras no "
-"dispongamos de ordenadores con <cite>firmware</cite> completamente libre, no "
-"hay manera de hacer nada mejor."
+"We can think of the difference between built-in firmware and equivalent "
+"hardware as a minor implementation detail, provided that we are sure in "
+"either case that it won't be changed. A hardware circuit can't be changed; "
+"that's its nature. If it's acceptable for a device to be implemented with "
+"internal circuitry that no one can alter, then an internal program that no "
+"one can alter is no worse. It would not be sensible to reject an equivalent "
+"internal software implementation, when operationally they are "
+"indistinguishable."
+msgstr ""
+
+#. type: Content of: <div><p>
+msgid ""
+"The equivalence falls apart, however, when the software implementation is "
+"not totally internal and some company can modify that code. For example, "
+"when firmware needs to be copied into the device to make the device "
+"function, or included in the system distribution that you install, that is "
+"no <em>internal</em> software implementation; rather, it is a piece of "
+"installed nonfree software. It is unjust because some manufacturer can "
+"change it but you can't."
+msgstr ""
+
+#. type: Content of: <div><p>
+msgid ""
+"In order for a firmware program to be morally equivalent to hardware, it "
+"must be unmodifiable. What about when the device can't possibly run without "
+"some firmware and it offers a way to modify that? We can make that firmware "
+"unmodifiable in practice by taking care never to let that replacement "
+"happen. This solution is not entirely clean, but no entirely clean solution "
+"has been proposed; this is the only way we know to preserve some meaning for "
+"the rejection of nonfree software while using that device. This is much "
+"better than just giving up."
+msgstr ""
+
+#. type: Content of: <div><p>
+msgid ""
+"But we can't have it both ways. To make preinstalled firmware effectively "
+"unmodifiable by not letting anyone invoke the method to change it, we must "
+"carry that out without exception even when there are changes we would wish "
+"were installed. That means rejecting all upgrades or patches to that "
+"firmware."
+msgstr ""
#. type: Content of: <div><p>
msgid ""
@@ -1078,8 +1115,8 @@
"coordinación y el envÃo de traducciones de las páginas de este sitio web."
#. type: Content of: <div><p>
-msgid "Copyright © 2015, 2021, 2022 Richard Stallman"
-msgstr "Copyright © 2015, 2021, 2022 Richard Stallman"
+msgid "Copyright © 2015, 2021, 2022, 2023 Richard Stallman"
+msgstr "Copyright © 2015, 2021, 2022, 2023 Richard Stallman"
#. type: Content of: <div><p>
msgid ""
@@ -1104,6 +1141,26 @@
msgid "Updated:"
msgstr "Ãltima actualización:"
-#. type: Content of: <div><p>
-msgid "Copyright © 2015, 2021, 2022, 2023 Richard Stallman"
-msgstr "Copyright © 2015, 2021, 2022, 2023 Richard Stallman"
+#~ msgid ""
+#~ "We can treat that firmware as hardware with a small stretch, but we must "
+#~ "not try to have it both ways. If we treat certain firmware as impossible "
+#~ "to change, since it is not realistically possible to avoid that firmware, "
+#~ "we must also treat it as impossible to change when we might wish it could "
+#~ "be changed. That entails refusing all upgrades or patches to that "
+#~ "firmware. That is what I do, and this is the reason I do it. Until we "
+#~ "can get computers with entirely free firmware, there is no feasible way "
+#~ "to do better than this."
+#~ msgstr ""
+#~ "Podemos considerar ese <cite>firmware</cite> casi como hardware, pero no "
+#~ "debemos pretender que sea ambas cosas a la vez. Si consideramos "
+#~ "determinado <cite>firmware</cite> como imposible de modificar, porque en "
+#~ "la práctica no es posible evitar ese <cite>firmware</cite>, entonces "
+#~ "debemos también considerarlo como imposible de modificar cuando "
+#~ "desearÃamos que eso fuera posible. Esto implica rechazar todas las "
+#~ "actualizaciones o correcciones de ese <cite>firmware</cite>. Es lo que yo "
+#~ "hago, y por eso lo hago. Mientras no dispongamos de ordenadores con "
+#~ "<cite>firmware</cite> completamente libre, no hay manera de hacer nada "
+#~ "mejor."
+
+#~ msgid "Copyright © 2015, 2021, 2022 Richard Stallman"
+#~ msgstr "Copyright © 2015, 2021, 2022 Richard Stallman"
Index: free-hardware-designs.fr.po
===================================================================
RCS file: /web/www/www/philosophy/po/free-hardware-designs.fr.po,v
retrieving revision 1.51
retrieving revision 1.52
diff -u -b -r1.51 -r1.52
--- free-hardware-designs.fr.po 9 Apr 2023 21:25:25 -0000 1.51
+++ free-hardware-designs.fr.po 9 Apr 2023 21:30:03 -0000 1.52
@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: free-hardware-designs.html\n"
-"POT-Creation-Date: 2022-03-05 13:55+0000\n"
+"POT-Creation-Date: 2023-04-09 21:25+0000\n"
"PO-Revision-Date: 2022-03-05 15:11+0100\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: 2023-04-09 21:25+0000\n"
#. type: Content of: <title>
msgid ""
@@ -231,12 +232,25 @@
msgstr "La frontière entre matériel et logiciel"
#. type: Content of: <div><p>
+# | What is the boundary, in digital devices, between hardware and software?
+# | It follows from the definitions. Software is the operational part of a
+# | device that can be copied{+,+} and [-changed in-] {+modified with+} 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.
+#, fuzzy
+#| msgid ""
+#| "What is the boundary, in digital devices, between hardware and software? "
+#| "It follows from 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."
msgid ""
"What is the boundary, in digital devices, between hardware and software? It "
"follows from 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."
+"that can be copied, and modified with 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 "
@@ -269,24 +283,47 @@
#. type: Content of: <div><p>
msgid ""
-"We can treat that firmware as hardware with a small stretch, but we must not "
-"try to have it both ways. If we treat certain firmware as impossible to "
-"change, since it is not realistically possible to avoid that firmware, we "
-"must also treat it as impossible to change when we might wish it could be "
-"changed. That entails refusing all upgrades or patches to that firmware. "
-"That is what I do, and this is the reason I do it. Until we can get "
-"computers with entirely free firmware, there is no feasible way to do better "
-"than this."
-msgstr ""
-"On peut presque considérer ces micrologiciels comme du matériel, mais il ne
"
-"faut pas essayer d'avoir le beurre et l'argent du beurre. Si l'on traite un "
-"micrologiciel comme impossible à modifier, car en pratique il est impossible
"
-"de s'en passer, on doit aussi le traiter comme impossible à modifier quand "
-"on souhaiterait qu'il le soit. Cela implique de refuser toutes les mises à "
-"niveau ou correctifs qui le concernent. C'est ce que je fais et c'est la "
-"raison pour laquelle je le fais. Tant que nous ne pourrons pas nous procurer "
-"d'ordinateurs avec des micrologiciels entièrement libres, il n'y a pas moyen
"
-"de faire mieux."
+"We can think of the difference between built-in firmware and equivalent "
+"hardware as a minor implementation detail, provided that we are sure in "
+"either case that it won't be changed. A hardware circuit can't be changed; "
+"that's its nature. If it's acceptable for a device to be implemented with "
+"internal circuitry that no one can alter, then an internal program that no "
+"one can alter is no worse. It would not be sensible to reject an equivalent "
+"internal software implementation, when operationally they are "
+"indistinguishable."
+msgstr ""
+
+#. type: Content of: <div><p>
+msgid ""
+"The equivalence falls apart, however, when the software implementation is "
+"not totally internal and some company can modify that code. For example, "
+"when firmware needs to be copied into the device to make the device "
+"function, or included in the system distribution that you install, that is "
+"no <em>internal</em> software implementation; rather, it is a piece of "
+"installed nonfree software. It is unjust because some manufacturer can "
+"change it but you can't."
+msgstr ""
+
+#. type: Content of: <div><p>
+msgid ""
+"In order for a firmware program to be morally equivalent to hardware, it "
+"must be unmodifiable. What about when the device can't possibly run without "
+"some firmware and it offers a way to modify that? We can make that firmware "
+"unmodifiable in practice by taking care never to let that replacement "
+"happen. This solution is not entirely clean, but no entirely clean solution "
+"has been proposed; this is the only way we know to preserve some meaning for "
+"the rejection of nonfree software while using that device. This is much "
+"better than just giving up."
+msgstr ""
+
+#. type: Content of: <div><p>
+msgid ""
+"But we can't have it both ways. To make preinstalled firmware effectively "
+"unmodifiable by not letting anyone invoke the method to change it, we must "
+"carry that out without exception even when there are changes we would wish "
+"were installed. That means rejecting all upgrades or patches to that "
+"firmware."
+msgstr ""
#. type: Content of: <div><p>
msgid ""
@@ -1085,8 +1122,8 @@
"traduction</a> les infos nécessaires."
#. type: Content of: <div><p>
-msgid "Copyright © 2015, 2021, 2022 Richard Stallman"
-msgstr "Copyright © 2015, 2021, 2022 Richard Stallman"
+msgid "Copyright © 2015, 2021, 2022, 2023 Richard Stallman"
+msgstr "Copyright © 2015, 2021, 2022, 2023 Richard Stallman"
#. type: Content of: <div><p>
msgid ""
@@ -1112,6 +1149,25 @@
msgid "Updated:"
msgstr "Dernière mise à jour :"
-#. type: Content of: <div><p>
-msgid "Copyright © 2015, 2021, 2022, 2023 Richard Stallman"
-msgstr "Copyright © 2015, 2021, 2022, 2023 Richard Stallman"
+#~ msgid ""
+#~ "We can treat that firmware as hardware with a small stretch, but we must "
+#~ "not try to have it both ways. If we treat certain firmware as impossible "
+#~ "to change, since it is not realistically possible to avoid that firmware, "
+#~ "we must also treat it as impossible to change when we might wish it could "
+#~ "be changed. That entails refusing all upgrades or patches to that "
+#~ "firmware. That is what I do, and this is the reason I do it. Until we "
+#~ "can get computers with entirely free firmware, there is no feasible way "
+#~ "to do better than this."
+#~ msgstr ""
+#~ "On peut presque considérer ces micrologiciels comme du matériel, mais il
"
+#~ "ne faut pas essayer d'avoir le beurre et l'argent du beurre. Si l'on "
+#~ "traite un micrologiciel comme impossible à modifier, car en pratique il "
+#~ "est impossible de s'en passer, on doit aussi le traiter comme impossible "
+#~ "Ã modifier quand on souhaiterait qu'il le soit. Cela implique de refuser "
+#~ "toutes les mises à niveau ou correctifs qui le concernent. C'est ce que "
+#~ "je fais et c'est la raison pour laquelle je le fais. Tant que nous ne "
+#~ "pourrons pas nous procurer d'ordinateurs avec des micrologiciels "
+#~ "entièrement libres, il n'y a pas moyen de faire mieux."
+
+#~ msgid "Copyright © 2015, 2021, 2022 Richard Stallman"
+#~ msgstr "Copyright © 2015, 2021, 2022 Richard Stallman"
Index: free-hardware-designs.pot
===================================================================
RCS file: /web/www/www/philosophy/po/free-hardware-designs.pot,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -b -r1.20 -r1.21
--- free-hardware-designs.pot 5 Mar 2022 14:00:32 -0000 1.20
+++ free-hardware-designs.pot 9 Apr 2023 21:30:03 -0000 1.21
@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: free-hardware-designs.html\n"
-"POT-Creation-Date: 2022-03-05 13:55+0000\n"
+"POT-Creation-Date: 2023-04-09 21:25+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"
@@ -159,9 +159,9 @@
msgid ""
"What is the boundary, in digital devices, between hardware and software? It "
"follows from 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."
+"that can be copied, and modified with 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: <div><p>
@@ -178,14 +178,46 @@
#. type: Content of: <div><p>
msgid ""
-"We can treat that firmware as hardware with a small stretch, but we must not "
-"try to have it both ways. If we treat certain firmware as impossible to "
-"change, since it is not realistically possible to avoid that firmware, we "
-"must also treat it as impossible to change when we might wish it could be "
-"changed. That entails refusing all upgrades or patches to that firmware. "
-"That is what I do, and this is the reason I do it. Until we can get "
-"computers with entirely free firmware, there is no feasible way to do better "
-"than this."
+"We can think of the difference between built-in firmware and equivalent "
+"hardware as a minor implementation detail, provided that we are sure in "
+"either case that it won't be changed. A hardware circuit can't be changed; "
+"that's its nature. If it's acceptable for a device to be implemented with "
+"internal circuitry that no one can alter, then an internal program that no "
+"one can alter is no worse. It would not be sensible to reject an equivalent "
+"internal software implementation, when operationally they are "
+"indistinguishable."
+msgstr ""
+
+#. type: Content of: <div><p>
+msgid ""
+"The equivalence falls apart, however, when the software implementation is "
+"not totally internal and some company can modify that code. For example, "
+"when firmware needs to be copied into the device to make the device "
+"function, or included in the system distribution that you install, that is "
+"no <em>internal</em> software implementation; rather, it is a piece of "
+"installed nonfree software. It is unjust because some manufacturer can "
+"change it but you can't."
+msgstr ""
+
+#. type: Content of: <div><p>
+msgid ""
+"In order for a firmware program to be morally equivalent to hardware, it "
+"must be unmodifiable. What about when the device can't possibly run without "
+"some firmware and it offers a way to modify that? We can make that firmware "
+"unmodifiable in practice by taking care never to let that replacement "
+"happen. This solution is not entirely clean, but no entirely clean solution "
+"has been proposed; this is the only way we know to preserve some meaning for "
+"the rejection of nonfree software while using that device. This is much "
+"better than just giving up."
+msgstr ""
+
+#. type: Content of: <div><p>
+msgid ""
+"But we can't have it both ways. To make preinstalled firmware effectively "
+"unmodifiable by not letting anyone invoke the method to change it, we must "
+"carry that out without exception even when there are changes we would wish "
+"were installed. That means rejecting all upgrades or patches to that "
+"firmware."
msgstr ""
#. type: Content of: <div><p>
@@ -682,7 +714,7 @@
msgstr ""
#. type: Content of: <div><p>
-msgid "Copyright © 2015, 2021, 2022 Richard Stallman"
+msgid "Copyright © 2015, 2021, 2022, 2023 Richard Stallman"
msgstr ""
#. type: Content of: <div><p>
Index: free-hardware-designs.pt-br-diff.html
===================================================================
RCS file: /web/www/www/philosophy/po/free-hardware-designs.pt-br-diff.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- free-hardware-designs.pt-br-diff.html 5 Mar 2022 14:00:32 -0000
1.4
+++ free-hardware-designs.pt-br-diff.html 9 Apr 2023 21:30:03 -0000
1.5
@@ -132,7 +132,7 @@
<p>What is the boundary, in digital devices, between hardware and
software? It follows from the definitions. Software is the
-operational part of a device that can be copied and changed in a
+operational part of a device that can be <span
class="removed"><del><strong>copied</strong></del></span> <span
class="inserted"><ins><em>copied,</em></ins></span> and <span
class="removed"><del><strong>changed in</strong></del></span> <span
class="inserted"><ins><em>modified with</em></ins></span> 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>
@@ -143,18 +143,41 @@
it is possible but unusual, or the manufacturer can release a
replacement but you can't.</em></ins></span> In conceptual terms, the gray
area is
rather narrow. In practice, it is important because many products
-fall in it. <span class="removed"><del><strong>We</strong></del></span>
<span class="inserted"><ins><em>Indeed, nowadays keyboards, cameras, disk
drives and USB
-memories typically contain an embedded nonfree program that could be
+fall in it. <span class="removed"><del><strong>We can
treat</strong></del></span> <span class="inserted"><ins><em>Indeed, nowadays
keyboards, cameras, disk drives and USB
+memories typically contain an embedded nonfree program</em></ins></span> that
<span class="inserted"><ins><em>could be
replaced by the manufacturer.</p>
-<p>We</em></ins></span> can treat that firmware as hardware with a small
<span class="removed"><del><strong>stretch.</p></strong></del></span>
<span class="inserted"><ins><em>stretch, but we
-must not try to have it both ways. If we treat certain firmware as
-impossible to change, since it is not realistically possible to avoid
-that firmware, we must also treat it as impossible to change when we
-might wish it could be changed. That entails refusing all upgrades or
-patches to that firmware. That is what I do, and this is the reason I
-do it. Until we can get computers with entirely free firmware, there
-is no feasible way to do better than this.</p></em></ins></span>
+<p>We can think of the difference between built-in</em></ins></span>
firmware <span class="inserted"><ins><em>and
+equivalent hardware</em></ins></span> as <span class="inserted"><ins><em>a
minor implementation detail, provided that we
+are sure in either case that it won't be changed. A</em></ins></span>
hardware <span class="inserted"><ins><em>circuit
+can't be changed; that's its nature. If it's acceptable for a device
+to be implemented</em></ins></span> with <span
class="inserted"><ins><em>internal circuitry that no one can alter, then
+an internal program that no one can alter is no worse. It would not
+be sensible to reject an equivalent internal software implementation,
+when operationally they are indistinguishable.</p>
+
+<p>The equivalence falls apart, however, when the software implementation
+is not totally internal and some company can modify that code. For
+example, when firmware needs to be copied into the device to make
+the device function, or included in the system distribution that you
+install, that is no <em>internal</em> software implementation;
rather,
+it is a piece of installed nonfree software. It is unjust because some
+manufacturer can change it but you can't.</p>
+
+<p>In order for a firmware program to be morally equivalent to hardware,
+it must be unmodifiable. What about when the device can't possibly run
+without some firmware and it offers</em></ins></span> a <span
class="removed"><del><strong>small stretch.</p></strong></del></span>
<span class="inserted"><ins><em>way to modify that? We can make
+that firmware unmodifiable in practice by taking care never to let that
+replacement happen. This solution is not entirely clean, but no
+entirely clean solution has been proposed; this is the only way we know
+to preserve some meaning for the rejection of nonfree software while
+using that device. This is much better than just giving up.</p>
+
+<p>But we can't have it both ways. To make preinstalled firmware
+effectively unmodifiable by not letting anyone invoke the method to
+change it, we must carry that out without exception even when there are
+changes we would wish were installed. That means rejecting all upgrades
+or patches to that firmware.</p></em></ins></span>
<p>Some have said that preinstalled firmware programs and
Field-Programmable Gate Array chips (FPGAs) “blur the boundary
@@ -559,7 +582,7 @@
There is more detail about copyright years in the GNU Maintainers
Information document, www.gnu.org/prep/maintain. -->
-<p>Copyright © 2015, <span class="removed"><del><strong>2016, 2018,
2019, 2021</strong></del></span> <span class="inserted"><ins><em>2021,
2022</em></ins></span> Richard Stallman</p>
+<p>Copyright © 2015, <span class="removed"><del><strong>2016, 2018,
2019, 2021</strong></del></span> <span class="inserted"><ins><em>2021, 2022,
2023</em></ins></span> Richard Stallman</p>
<p>This page is licensed under a <a rel="license"
href="http://creativecommons.org/licenses/by-nd/4.0/">Creative
@@ -569,7 +592,7 @@
<p class="unprintable">Updated:
<!-- timestamp start -->
-$Date: 2022/03/05 14:00:32 $
+$Date: 2023/04/09 21:30:03 $
<!-- timestamp end -->
</p>
</div>
Index: free-hardware-designs.pt-br.po
===================================================================
RCS file: /web/www/www/philosophy/po/free-hardware-designs.pt-br.po,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -b -r1.10 -r1.11
--- free-hardware-designs.pt-br.po 5 Mar 2022 14:00:32 -0000 1.10
+++ free-hardware-designs.pt-br.po 9 Apr 2023 21:30:03 -0000 1.11
@@ -6,7 +6,7 @@
msgid ""
msgstr ""
"Project-Id-Version: free-hardware-designs.html\n"
-"POT-Creation-Date: 2022-03-05 13:55+0000\n"
+"POT-Creation-Date: 2023-04-09 21:25+0000\n"
"PO-Revision-Date: 2021-05-31 11:16-0300\n"
"Last-Translator: Rafael Fontenelle <rafaelff@gnome.org>\n"
"Language-Team: Brazilian Portuguese <www-pt-br-general@gnu.org>\n"
@@ -246,12 +246,19 @@
msgstr "A fronteira entre hardware e software"
#. type: Content of: <div><p>
+#, fuzzy
+#| msgid ""
+#| "What is the boundary, in digital devices, between hardware and software? "
+#| "It follows from 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."
msgid ""
"What is the boundary, in digital devices, between hardware and software? It "
"follows from 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."
+"that can be copied, and modified with 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 ""
"Qual é o limite, em dispositivos digitais, entre hardware e software? Ele "
"segue as definições. Software é a parte operacional de um dispositivo que "
@@ -287,14 +294,46 @@
#. type: Content of: <div><p>
msgid ""
-"We can treat that firmware as hardware with a small stretch, but we must not "
-"try to have it both ways. If we treat certain firmware as impossible to "
-"change, since it is not realistically possible to avoid that firmware, we "
-"must also treat it as impossible to change when we might wish it could be "
-"changed. That entails refusing all upgrades or patches to that firmware. "
-"That is what I do, and this is the reason I do it. Until we can get "
-"computers with entirely free firmware, there is no feasible way to do better "
-"than this."
+"We can think of the difference between built-in firmware and equivalent "
+"hardware as a minor implementation detail, provided that we are sure in "
+"either case that it won't be changed. A hardware circuit can't be changed; "
+"that's its nature. If it's acceptable for a device to be implemented with "
+"internal circuitry that no one can alter, then an internal program that no "
+"one can alter is no worse. It would not be sensible to reject an equivalent "
+"internal software implementation, when operationally they are "
+"indistinguishable."
+msgstr ""
+
+#. type: Content of: <div><p>
+msgid ""
+"The equivalence falls apart, however, when the software implementation is "
+"not totally internal and some company can modify that code. For example, "
+"when firmware needs to be copied into the device to make the device "
+"function, or included in the system distribution that you install, that is "
+"no <em>internal</em> software implementation; rather, it is a piece of "
+"installed nonfree software. It is unjust because some manufacturer can "
+"change it but you can't."
+msgstr ""
+
+#. type: Content of: <div><p>
+msgid ""
+"In order for a firmware program to be morally equivalent to hardware, it "
+"must be unmodifiable. What about when the device can't possibly run without "
+"some firmware and it offers a way to modify that? We can make that firmware "
+"unmodifiable in practice by taking care never to let that replacement "
+"happen. This solution is not entirely clean, but no entirely clean solution "
+"has been proposed; this is the only way we know to preserve some meaning for "
+"the rejection of nonfree software while using that device. This is much "
+"better than just giving up."
+msgstr ""
+
+#. type: Content of: <div><p>
+msgid ""
+"But we can't have it both ways. To make preinstalled firmware effectively "
+"unmodifiable by not letting anyone invoke the method to change it, we must "
+"carry that out without exception even when there are changes we would wish "
+"were installed. That means rejecting all upgrades or patches to that "
+"firmware."
msgstr ""
#. type: Content of: <div><p>
@@ -1130,7 +1169,7 @@
#. type: Content of: <div><p>
#, fuzzy
#| msgid "Copyright © 2015, 2016, 2018, 2019 Richard Stallman"
-msgid "Copyright © 2015, 2021, 2022 Richard Stallman"
+msgid "Copyright © 2015, 2021, 2022, 2023 Richard Stallman"
msgstr "Copyright © 2015, 2016, 2018, 2019 Richard Stallman"
#. type: Content of: <div><p>
Index: free-hardware-designs.ru.po
===================================================================
RCS file: /web/www/www/philosophy/po/free-hardware-designs.ru.po,v
retrieving revision 1.44
retrieving revision 1.45
diff -u -b -r1.44 -r1.45
--- free-hardware-designs.ru.po 9 Apr 2023 21:25:25 -0000 1.44
+++ free-hardware-designs.ru.po 9 Apr 2023 21:30:03 -0000 1.45
@@ -8,7 +8,7 @@
msgid ""
msgstr ""
"Project-Id-Version: hardware-software-boundary.html\n"
-"POT-Creation-Date: 2022-03-05 13:55+0000\n"
+"POT-Creation-Date: 2023-04-09 21:25+0000\n"
"PO-Revision-Date: 2022-10-01 18:42+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: 2023-04-09 21:25+0000\n"
#. type: Content of: <title>
msgid ""
@@ -233,12 +234,25 @@
msgstr "ÐÑаниÑа Ð¼ÐµÐ¶Ð´Ñ Ð°Ð¿Ð¿Ð°ÑаÑной и
пÑогÑаммной ÑаÑÑÑÑ"
#. type: Content of: <div><p>
+# | What is the boundary, in digital devices, between hardware and software?
+# | It follows from the definitions. Software is the operational part of a
+# | device that can be copied{+,+} and [-changed in-] {+modified with+} 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.
+#, fuzzy
+#| msgid ""
+#| "What is the boundary, in digital devices, between hardware and software? "
+#| "It follows from 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."
msgid ""
"What is the boundary, in digital devices, between hardware and software? It "
"follows from 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."
+"that can be copied, and modified with 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 ""
"Ðде в ÑиÑÑовÑÑ
ÑÑÑÑойÑÑваÑ
гÑаниÑа междÑ
аппаÑаÑÑÑой и пÑогÑаммами? ÐÑо "
"ÑледÑÐµÑ Ð¸Ð· опÑеделений. ÐÑогÑÐ°Ð¼Ð¼Ñ —
ÑÑо ÑабоÑÐ°Ñ ÑаÑÑÑ ÑÑÑÑойÑÑва, "
@@ -269,24 +283,47 @@
#. type: Content of: <div><p>
msgid ""
-"We can treat that firmware as hardware with a small stretch, but we must not "
-"try to have it both ways. If we treat certain firmware as impossible to "
-"change, since it is not realistically possible to avoid that firmware, we "
-"must also treat it as impossible to change when we might wish it could be "
-"changed. That entails refusing all upgrades or patches to that firmware. "
-"That is what I do, and this is the reason I do it. Until we can get "
-"computers with entirely free firmware, there is no feasible way to do better "
-"than this."
-msgstr ""
-"ÐÑ Ð¼Ð¾Ð¶ÐµÐ¼ Ñ Ð½ÐµÐ±Ð¾Ð»ÑÑой наÑÑжкой
ÑаÑÑмаÑÑиваÑÑ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ Ð´Ð»Ñ Ð¿Ð¾Ð´ÑиÑÑем как "
-"аппаÑаÑÑÑÑ, но нам не нÑжно пÑÑаÑÑÑÑ
полÑÑиÑÑ Ð¸ Ñо, и дÑÑгое. ÐÑли Ð¼Ñ "
-"ÑаÑÑмаÑÑиваем пÑогÑÐ°Ð¼Ð¼Ñ Ð´Ð»Ñ Ð¿Ð¾Ð´ÑиÑÑем
как пÑинÑипиалÑно неизменÑемÑе "
-"вÑледÑÑвие Ñого, ÑÑо избегаÑÑ ÑÑиÑ
пÑогÑамм неÑеалÑно, Ð¼Ñ Ð´Ð¾Ð»Ð¶Ð½Ñ Ñакже "
-"ÑаÑÑмаÑÑиваÑÑ Ð¸Ñ
как неизменÑемÑе, когда
Ð´Ð»Ñ Ð½Ð°Ñ Ð¶ÐµÐ»Ð°ÑелÑно бÑло Ð±Ñ Ð¸Ñ
"
-"измениÑÑ. ÐÑо подÑазÑÐ¼ÐµÐ²Ð°ÐµÑ Ð¾Ñказ оÑ
вÑÑкиÑ
обновлений или попÑавок к ÑÑим "
-"пÑогÑаммам. Ðменно Ñак Ñ Ð¸ делаÑ, и ÑÑой
Ñамой пÑиÑине. Ðока Ð¼Ñ Ð½Ðµ можем "
-"полÑÑиÑÑ ÐºÐ¾Ð¼Ð¿ÑÑÑеÑÑ Ñ Ð¿Ð¾Ð»Ð½Ð¾ÑÑÑÑ
ÑвободнÑми пÑогÑаммами Ð´Ð»Ñ Ð¿Ð¾Ð´ÑиÑÑем,
ниÑего "
-"лÑÑÑего нам на пÑакÑике не оÑÑаеÑÑÑ."
+"We can think of the difference between built-in firmware and equivalent "
+"hardware as a minor implementation detail, provided that we are sure in "
+"either case that it won't be changed. A hardware circuit can't be changed; "
+"that's its nature. If it's acceptable for a device to be implemented with "
+"internal circuitry that no one can alter, then an internal program that no "
+"one can alter is no worse. It would not be sensible to reject an equivalent "
+"internal software implementation, when operationally they are "
+"indistinguishable."
+msgstr ""
+
+#. type: Content of: <div><p>
+msgid ""
+"The equivalence falls apart, however, when the software implementation is "
+"not totally internal and some company can modify that code. For example, "
+"when firmware needs to be copied into the device to make the device "
+"function, or included in the system distribution that you install, that is "
+"no <em>internal</em> software implementation; rather, it is a piece of "
+"installed nonfree software. It is unjust because some manufacturer can "
+"change it but you can't."
+msgstr ""
+
+#. type: Content of: <div><p>
+msgid ""
+"In order for a firmware program to be morally equivalent to hardware, it "
+"must be unmodifiable. What about when the device can't possibly run without "
+"some firmware and it offers a way to modify that? We can make that firmware "
+"unmodifiable in practice by taking care never to let that replacement "
+"happen. This solution is not entirely clean, but no entirely clean solution "
+"has been proposed; this is the only way we know to preserve some meaning for "
+"the rejection of nonfree software while using that device. This is much "
+"better than just giving up."
+msgstr ""
+
+#. type: Content of: <div><p>
+msgid ""
+"But we can't have it both ways. To make preinstalled firmware effectively "
+"unmodifiable by not letting anyone invoke the method to change it, we must "
+"carry that out without exception even when there are changes we would wish "
+"were installed. That means rejecting all upgrades or patches to that "
+"firmware."
+msgstr ""
#. type: Content of: <div><p>
msgid ""
@@ -1064,10 +1101,10 @@
# type: Content of: <div><p>
#. type: Content of: <div><p>
-msgid "Copyright © 2015, 2021, 2022 Richard Stallman"
+msgid "Copyright © 2015, 2021, 2022, 2023 Richard Stallman"
msgstr ""
-"Copyright © 2015, 2021, 2022 Richard Stallman<br />Copyright © "
-"2015, 2021, 2022 Free Software Foundation, Inc. (translation)"
+"Copyright © 2015, 2021, 2022, 2023 Richard Stallman<br />Copyright "
+"© 2015, 2021, 2022, 2023 Free Software Foundation, Inc. (translation)"
#. type: Content of: <div><p>
msgid ""
@@ -1091,9 +1128,28 @@
msgid "Updated:"
msgstr "Ðбновлено:"
+#~ msgid ""
+#~ "We can treat that firmware as hardware with a small stretch, but we must "
+#~ "not try to have it both ways. If we treat certain firmware as impossible "
+#~ "to change, since it is not realistically possible to avoid that firmware, "
+#~ "we must also treat it as impossible to change when we might wish it could "
+#~ "be changed. That entails refusing all upgrades or patches to that "
+#~ "firmware. That is what I do, and this is the reason I do it. Until we "
+#~ "can get computers with entirely free firmware, there is no feasible way "
+#~ "to do better than this."
+#~ msgstr ""
+#~ "ÐÑ Ð¼Ð¾Ð¶ÐµÐ¼ Ñ Ð½ÐµÐ±Ð¾Ð»ÑÑой наÑÑжкой
ÑаÑÑмаÑÑиваÑÑ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ Ð´Ð»Ñ Ð¿Ð¾Ð´ÑиÑÑем как "
+#~ "аппаÑаÑÑÑÑ, но нам не нÑжно пÑÑаÑÑÑÑ
полÑÑиÑÑ Ð¸ Ñо, и дÑÑгое. ÐÑли Ð¼Ñ "
+#~ "ÑаÑÑмаÑÑиваем пÑогÑÐ°Ð¼Ð¼Ñ Ð´Ð»Ñ Ð¿Ð¾Ð´ÑиÑÑем
как пÑинÑипиалÑно неизменÑемÑе "
+#~ "вÑледÑÑвие Ñого, ÑÑо избегаÑÑ ÑÑиÑ
пÑогÑамм неÑеалÑно, Ð¼Ñ Ð´Ð¾Ð»Ð¶Ð½Ñ Ñакже "
+#~ "ÑаÑÑмаÑÑиваÑÑ Ð¸Ñ
как неизменÑемÑе,
когда Ð´Ð»Ñ Ð½Ð°Ñ Ð¶ÐµÐ»Ð°ÑелÑно бÑло Ð±Ñ Ð¸Ñ
"
+#~ "измениÑÑ. ÐÑо подÑазÑÐ¼ÐµÐ²Ð°ÐµÑ Ð¾Ñказ оÑ
вÑÑкиÑ
обновлений или попÑавок к "
+#~ "ÑÑим пÑогÑаммам. Ðменно Ñак Ñ Ð¸ делаÑ, и
ÑÑой Ñамой пÑиÑине. Ðока Ð¼Ñ Ð½Ðµ "
+#~ "можем полÑÑиÑÑ ÐºÐ¾Ð¼Ð¿ÑÑÑеÑÑ Ñ Ð¿Ð¾Ð»Ð½Ð¾ÑÑÑÑ
ÑвободнÑми пÑогÑаммами Ð´Ð»Ñ "
+#~ "подÑиÑÑем, ниÑего лÑÑÑего нам на
пÑакÑике не оÑÑаеÑÑÑ."
+
# type: Content of: <div><p>
-#. type: Content of: <div><p>
-msgid "Copyright © 2015, 2021, 2022, 2023 Richard Stallman"
-msgstr ""
-"Copyright © 2015, 2021, 2022, 2023 Richard Stallman<br />Copyright "
-"© 2015, 2021, 2022, 2023 Free Software Foundation, Inc. (translation)"
+#~ msgid "Copyright © 2015, 2021, 2022 Richard Stallman"
+#~ msgstr ""
+#~ "Copyright © 2015, 2021, 2022 Richard Stallman<br />Copyright © "
+#~ "2015, 2021, 2022 Free Software Foundation, Inc. (translation)"
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- www/philosophy/po free-hardware-designs.de.po f...,
GNUN <=