www/philosophy free-hardware-designs.es.html po...

[GNUN]

CVSROOT:        /web/www
Module name:    www
Changes by:     GNUN <gnun>     23/04/13 07:59:49

Modified files:
        philosophy     : free-hardware-designs.es.html 
        philosophy/po  : free-hardware-designs.es-en.html 
                         free-hardware-designs.es.po 

Log message:
        Automatic update by GNUnited Nations.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/free-hardware-designs.es.html?cvsroot=www&r1=1.9&r2=1.10
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/free-hardware-designs.es-en.html?cvsroot=www&r1=1.6&r2=1.7
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/free-hardware-designs.es.po?cvsroot=www&r1=1.26&r2=1.27

Patches:
Index: free-hardware-designs.es.html
===================================================================
RCS file: /web/www/www/philosophy/free-hardware-designs.es.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- free-hardware-designs.es.html       26 May 2022 14:30:26 -0000      1.9
+++ free-hardware-designs.es.html       13 Apr 2023 11:59:47 -0000      1.10
@@ -115,7 +115,7 @@
 
 <p>¿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
-parte operante del dispositivo que se puede copiar y modificar en un
+parte operante del dispositivo que se puede copiar y modificar con un
 ordenador, mientras que el hardware es la parte operante que no se puede
 copiar ni modificar. Esta es la forma correcta de hacer la distinción,
 porque alude a las consecuencias prácticas.</p>
@@ -130,15 +130,38 @@
 habitual que teclados, cámaras, discos duros y memorias USB contengan un
 programa privativo que el fabricante podría reemplazar.</p>
 
-<p>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.</p>
+<p>Podemos considerar la diferencia entre el <cite>firmware</cite> integrado y
+el hardware equivalente como un detalle menor de implementación, siempre que
+estemos seguros de que no cambiarán en ninguno de los dos casos. Un circuito
+de hardware no se puede modificar, es su naturaleza. Si es aceptable que un
+dispositivo se implemente con circuitos internos que nadie puede modificar,
+no es menos aceptable un programa interno que nadie puede modificar. No
+sería sensato rechazar una implementación equivalente con software interno
+cuando ambas son operativamente indistinguibles.</p>
+
+<p>Sin embargo, dejan de ser equivalentes si la implementación del software no
+es totalmente interna y alguna compañía puede modificar ese código. Por
+ejemplo, cuando para que el dispositivo funcione hay que copiar en él el
+<cite>firmware</cite> o este debe ir incluido en la distribución del sistema
+que se instale, eso no es una implementación <em>interna</em> del software;
+es más bien un software no libre instalado. Es injusto porque un fabricante
+puede cambiarlo, pero el usuario no.</p>
+
+<p>Para que un <cite>firmware</cite> sea moralmente equivalente al hardware
+debe ser inmodificable. ¿Qué sucede cuando el dispositivo no puede funcionar
+sin cierto <cite>firmware</cite> y permite modificarlo de alguna manera?
+Podemos hacer que ese <cite>firmware</cite> sea inmodificable en la práctica
+no permitiendo que se produzca nunca ningún cambio. Esta solución no es
+totalmente limpia, pero aún no se ha propuesto ninguna solución que lo sea,
+y es la única manera que conocemos de que el rechazo del software no libre
+continúe teniendo algún sentido mientras utilizamos ese dispositivo. Es
+mucho mejor que darse por vencido.</p>
+
+<p>Pero no podemos tener ambas cosas. Para hacer que el <cite>firmware</cite>
+preinstalado sea efectivamente inmodificable no permitiendo que nadie
+recurra al método para modificarlo, debemos hacerlo así sin excepciones, aun
+cuando haya cambios que quisiéramos tener instalados. Eso implica rechazar
+toda actualización o parche para ese <cite>firmware</cite>.</p>
 
 <p>Algunos opinan que los programas de <cite>firmware</cite> preinstalados y
 los circuitos lógicos programables (<abbr title="Field-Programmable Gate
@@ -559,7 +582,7 @@
      
      There is more detail about copyright years in the GNU Maintainers
      Information document, www.gnu.org/prep/maintain. -->
-<p>Copyright &copy; 2015, 2021, 2022 Richard Stallman</p>
+<p>Copyright &copy; 2015, 2021, 2022, 2023 Richard Stallman</p>
 
 <p>Esta página está bajo licencia <a rel="license"
 href="http://creativecommons.org/licenses/by-nd/4.0/deed.es_ES";>Creative
@@ -575,7 +598,7 @@
 <p class="unprintable"><!-- timestamp start -->
 Última actualización:
 
-$Date: 2022/05/26 14:30:26 $
+$Date: 2023/04/13 11:59:47 $
 
 <!-- timestamp end -->
 </p>

Index: po/free-hardware-designs.es-en.html
===================================================================
RCS file: /web/www/www/philosophy/po/free-hardware-designs.es-en.html,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -b -r1.6 -r1.7
--- po/free-hardware-designs.es-en.html 6 Mar 2022 10:30:37 -0000       1.6
+++ po/free-hardware-designs.es-en.html 13 Apr 2023 11:59:49 -0000      1.7
@@ -109,7 +109,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 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.</p>
@@ -124,14 +124,37 @@
 memories typically contain an embedded nonfree program that could be
 replaced by the manufacturer.</p>
 
-<p>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.</p>
+<p>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.</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 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.</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>
 
 <p>Some have said that preinstalled firmware programs and
 Field-Programmable Gate Array chips (FPGAs) &ldquo;blur the boundary
@@ -515,7 +538,7 @@
      There is more detail about copyright years in the GNU Maintainers
      Information document, www.gnu.org/prep/maintain. -->
 
-<p>Copyright &copy; 2015, 2021, 2022 Richard Stallman</p>
+<p>Copyright &copy; 2015, 2021, 2022, 2023 Richard Stallman</p>
 
 <p>This page is licensed under a <a rel="license"
 href="http://creativecommons.org/licenses/by-nd/4.0/";>Creative
@@ -525,7 +548,7 @@
 
 <p class="unprintable">Updated:
 <!-- timestamp start -->
-$Date: 2022/03/06 10:30:37 $
+$Date: 2023/04/13 11:59:49 $
 <!-- timestamp end -->
 </p>
 </div>

Index: po/free-hardware-designs.es.po
===================================================================
RCS file: /web/www/www/philosophy/po/free-hardware-designs.es.po,v
retrieving revision 1.26
retrieving revision 1.27
diff -u -b -r1.26 -r1.27
--- po/free-hardware-designs.es.po      13 Apr 2023 11:40:58 -0000      1.26
+++ po/free-hardware-designs.es.po      13 Apr 2023 11:59:49 -0000      1.27
@@ -70,8 +70,8 @@
 "\"/philosophy/free-sw.html\">las cuatro libertades esenciales</a>. Para "
 "poner de relieve que «<cite>free</cite>» hace referencia a la libertad y no 
"
 "al precio, a menudo ponemos junto a «<cite>free</cite>» la palabra francesa 
"
-"o española «libre»&#8239;<a href=\"#TransNote1\" id=\"TransNote1-rev"
-"\"><sup>[1]</sup></a>."
+"o española «libre»&#8239;<a href=\"#TransNote1\" 
id=\"TransNote1-rev\"><sup>"
+"[1]</sup></a>."
 
 #. type: Content of: <div><p>
 msgid ""
@@ -232,12 +232,6 @@
 msgid "The Boundary between Hardware and Software"
 msgstr "La frontera entre el hardware y el software"
 
-# | 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.
 #. type: Content of: <div><p>
 msgid ""
 "What is the boundary, in digital devices, between hardware and software? It "