www/philosophy po/is-ever-good-use-nonfree-prog...

[GNUN]

CVSROOT:        /web/www
Module name:    www
Changes by:     GNUN <gnun>     15/06/27 09:28:16

Modified files:
        philosophy/po  : is-ever-good-use-nonfree-program.translist 
Added files:
        philosophy     : is-ever-good-use-nonfree-program.es.html 
        philosophy/po  : is-ever-good-use-nonfree-program.es-en.html 

Log message:
        Automatic update by GNUnited Nations.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/is-ever-good-use-nonfree-program.es.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/is-ever-good-use-nonfree-program.translist?cvsroot=www&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/is-ever-good-use-nonfree-program.es-en.html?cvsroot=www&rev=1.1

Patches:
Index: po/is-ever-good-use-nonfree-program.translist
===================================================================
RCS file: 
/web/www/www/philosophy/po/is-ever-good-use-nonfree-program.translist,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- po/is-ever-good-use-nonfree-program.translist       23 May 2015 05:09:30 
-0000      1.4
+++ po/is-ever-good-use-nonfree-program.translist       27 Jun 2015 09:28:16 
-0000      1.5
@@ -3,12 +3,14 @@
 value='<div id="translations">
 <p>
 <span dir="ltr" class="original"><a lang="en" hreflang="en" 
href="/philosophy/is-ever-good-use-nonfree-program.en.html">English</a>&nbsp;[en]</span>
 &nbsp;
+<span dir="ltr"><a lang="es" hreflang="es" 
href="/philosophy/is-ever-good-use-nonfree-program.es.html">español</a>&nbsp;[es]</span>
 &nbsp;
 <span dir="ltr"><a lang="fr" hreflang="fr" 
href="/philosophy/is-ever-good-use-nonfree-program.fr.html">français</a>&nbsp;[fr]</span>
 &nbsp;
 <span dir="ltr"><a lang="ru" hreflang="ru" 
href="/philosophy/is-ever-good-use-nonfree-program.ru.html">русский</a>&nbsp;[ru]</span>
 &nbsp;
 </p>
 </div>' -->
 <link rel="alternate" type="text/html" 
href="/philosophy/is-ever-good-use-nonfree-program.html" hreflang="x-default" />
 <link rel="alternate" type="text/html" lang="en" hreflang="en" 
href="/philosophy/is-ever-good-use-nonfree-program.en.html" title="English" />
+<link rel="alternate" type="text/html" lang="es" hreflang="es" 
href="/philosophy/is-ever-good-use-nonfree-program.es.html" title="español" />
 <link rel="alternate" type="text/html" lang="fr" hreflang="fr" 
href="/philosophy/is-ever-good-use-nonfree-program.fr.html" title="français" />
 <link rel="alternate" type="text/html" lang="ru" hreflang="ru" 
href="/philosophy/is-ever-good-use-nonfree-program.ru.html" 
title="русский" />
 <!-- end translist file -->

Index: is-ever-good-use-nonfree-program.es.html
===================================================================
RCS file: is-ever-good-use-nonfree-program.es.html
diff -N is-ever-good-use-nonfree-program.es.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ is-ever-good-use-nonfree-program.es.html    27 Jun 2015 09:28:14 -0000      
1.1
@@ -0,0 +1,189 @@
+<!--#set var="ENGLISH_PAGE" 
value="/philosophy/is-ever-good-use-nonfree-program.en.html" -->
+
+<!--#include virtual="/server/header.es.html" -->
+<!-- Parent-Version: 1.77 -->
+
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>¿Está bien en algunos casos utilizar un programa que no sea libre? -
+Proyecto GNU - Free Software Foundation</title>
+
+<!--#include 
virtual="/philosophy/po/is-ever-good-use-nonfree-program.translist" -->
+<!--#include virtual="/server/banner.es.html" -->
+<h2>¿Está bien en algunos casos utilizar un programa que no sea libre?</h2>
+
+<p>por <a href="http://www.stallman.org/";><strong>Richard 
Stallman</strong></a></p>
+
+<p>Si ejecuta en su ordenador un programa que no es libre, el programa coarta
+su libertad. El principal afectado es usted. El hecho de usarlo puede
+perjudicar a otros indirectamente, al alentar el desarrollo de ese programa
+privativo. Si promete no redistribuir el programa a otras personas, hace
+mal, ya que romper esa promesa es malo y mantenerla es aún peor. De todos
+modos, el principal afectado directo es usted.</p>
+
+<p>Aún peor es si recomienda o induce a otras personas a utilizar el programa
+privativo, ya que de esa manera las conduce a renunciar a su libertad. De
+modo que lo que debemos evitar con mayor firmeza es animar o empujar a otras
+personas a usar software que no es libre (cuando un programa implementa un
+protocolo secreto para la comunicación, como es el caso de Skype, el hecho
+de utilizarlo implica que estamos forzando a otras personas a que hagan lo
+mismo, así que es muy importante rechazar por completo todo uso de este tipo
+de programas).</p>
+
+<p>Pero existe una situación en particular en la que utilizar un programa
+privativo, e incluso instar a otras personas a que lo hagan, puede ser algo
+positivo. Se trata de aquellos casos en los que la utilización de un
+programa privativo tiene como objetivo terminar con el uso de ese mismo
+programa privativo.</p>
+
+<p>En 1983 decidí desarrollar el sistema operativo GNU como un sustitutivo
+libre para Unix. La única manera viable para lograrlo era escribir y probar
+los componentes uno a uno en Unix. Pero, ¿era legítimo usar Unix para esto?
+¿Era legítimo pedir a otras personas que usaran Unix con esta finalidad,
+teniendo en cuenta que Unix era software privativo? Está claro que si no
+hubiera sido privativo, no habría sido necesario sustituirlo.</p>
+
+<p>Llegué a la conclusión de que era legítimo usar Unix para terminar con el
+uso de Unix. Lo equiparaba a una pequeña participación en alguna actividad
+perversa, como una banda criminal o una campaña política deshonesta, con el
+objetivo de sacarla a la luz y acabar con ella. Si bien participar en la
+actividad misma está mal, acabar con ella justifica cierta participación
+marginal menor, equiparable a la simple utilización de Unix. Este argumento
+no justificaría convertirse en un cabecilla, pero yo sólo estaba
+considerando utilizar Unix, no ponerme a trabajar para su equipo de
+desarrollo.</p>
+
+<p>La tarea de reemplazar Unix se completó cuando el último componente 
esencial
+fue reemplazado por Linux, el núcleo que Linus Torvalds empezó a desarrollar
+en 1991. Seguimos añadiendo software al sistema GNU/Linux, pero para eso ya
+no es necesario utilizar Unix, de modo que ya no hay ninguna razón para
+volver a usarlo. Así pues, cuando se utilice un programa privativo por
+razones de este tipo, oportunamente se debe reconsiderar si sigue siendo
+necesario.</p>
+
+<p>Sin embargo, aún tenemos que reemplazar otros programas privativos y a
+menudo surge la misma cuestión. ¿Deberíamos servirnos del controlador
+privativo de un periférico para desarrollar un reemplazo libre? Sí, por
+supuesto. ¿Está bien ejecutar código <a
+href="http://www.gnu.org/philosophy/javascript-trap.html";>JavaScript que no
+sea libre</a> en una página web a fin de presentar una queja a los
+administradores para que lo liberen o hagan que el sitio funcione sin él?
+Indudablemente, pero además de eso, hay que tener instalado <a
+href="https://www.gnu.org/software/librejs/";>LibreJS</a> para que bloquee
+dicho código.</p>
+
+<p>Pero esta justificación no puede llevarse mucho más lejos. Quienes
+desarrollan software que no es libre, incluso software con características
+maliciosas, a menudo intentan excusarse alegando que financian el desarrollo
+de software libre. Sin embargo, una empresa que está básicamente mal no
+puede ser legitimada por el hecho de que destine una parte de sus beneficios
+a una causa noble. Por ejemplo, algunas de las actividades de la Fundación
+Gates (no todas) son loables, pero no justifican la trayectoria de Bill
+Gates, o de Microsoft. Si la empresa trabaja en el sentido opuesto de la
+causa noble con la que intenta legitimarse, incurre en contradicción y
+debilita la causa.</p>
+
+<p>Incluso cuando se trata de desarrollar software libre en general es mejor
+evitar el uso de software que no es libre. Por ejemplo, no deberíamos pedir
+a nadie que use Windows o MacOS para desarrollar aplicaciones libres que
+funcionen en esos sistemas. Como desarrollador de Emacs y GCC, acepté
+cambios para que pudieran ejecutarse en sistemas que no son libres como VMS,
+Windows y MacOS. No había razón alguna para rechazar ese código, pero no le
+pedí a nadie que utilizara sistemas que no fueran libres para
+desarrollarlo. Los cambios los escribieron personas que de todos modos ya
+estaban utilizando esos sistemas, y también se ocuparon de empaquetar las
+versiones de Emacs para tales sistemas.</p>
+
+<p>La excepción de «desarrollar su propio reemplazo» es válida dentro de 
unos
+límites y es crucial para el progreso del software libre, pero debemos
+resistirnos a llevarla demasiado lejos, no sea que se convierta en la excusa
+general para cualquier actividad rentable con software que no sea libre.</p>
+
+<hr />
+
+<p>A veces es necesario utilizar e incluso actualizar un sistema que no es
+libre para instalar un sistema de reemplazo libre. No se trata exactamente
+del mismo problema, pero son válidos los mismos argumentos: es legítimo
+ejecutar software privativo momentáneamente para poder librarse de él.</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.es.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<p>Envíe sus consultas acerca de la FSF y GNU a <a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>. Existen también <a
+href="/contact/">otros medios para contactar</a> con la FSF. <br /> Para
+avisar de enlaces rotos y proponer otras correcciones o sugerencias,
+diríjase a <a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>.</p>
+
+<p>
+<!-- TRANSLATORS: Ignore the original text in this paragraph,
+        replace it with the translation of these two:
+
+        We work hard and do our best to provide accurate, good quality
+        translations.  However, we are not exempt from imperfection.
+        Please send your comments and general suggestions in this regard
+        to <a href="mailto:address@hidden";>
+
+        &lt;address@hidden&gt;</a>.</p>
+
+        <p>For information on coordinating and submitting translations of
+        our web pages, see <a
+        href="/server/standards/README.translations.html">Translations
+        README</a>. -->
+El equipo de traductores al español se esfuerza por ofrecer traducciones
+fieles al original y de buena calidad, pero no estamos libres de cometer
+errores.<br /> Por favor envíe sus comentarios y sugerencias sobre las
+traducciones a <a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>.
+</p><p>Consulte la <a href="/server/standards/README.translations.html">Guía
+para las traducciones</a> para obtener información sobre la coordinación y
+el envío de traducciones de las páginas de este sitio web.</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 4.0.  Please do NOT change or remove this
+     without talking with the webmasters or licensing team first.
+     Please make sure the copyright date is consistent with the
+     document.  For web pages, it is ok to list just the latest year the
+     document was modified, or published.
+     
+     If you wish to list earlier years, that is ok too.
+     Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
+     years, as long as each year in the range is in fact a copyrightable
+     year, i.e., a year in which the document was published (including
+     being publicly visible on the web or in a revision control system).
+     
+     There is more detail about copyright years in the GNU Maintainers
+     Information document, www.gnu.org/prep/maintain. -->
+<p>Copyright &copy; 2013, 2015 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
+Commons Reconocimiento-SinObraDerivada 4.0 Internacional</a>.</p>
+
+<!--#include virtual="/server/bottom-notes.es.html" -->
+<div class="translators-credits">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.-->
+<strong>Traducción: Ondiz Zarraga, 2015.</strong></div>
+
+<p class="unprintable"><!-- timestamp start -->
+Última actualización:
+
+$Date: 2015/06/27 09:28:14 $
+
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>

Index: po/is-ever-good-use-nonfree-program.es-en.html
===================================================================
RCS file: po/is-ever-good-use-nonfree-program.es-en.html
diff -N po/is-ever-good-use-nonfree-program.es-en.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ po/is-ever-good-use-nonfree-program.es-en.html      27 Jun 2015 09:28:15 
-0000      1.1
@@ -0,0 +1,166 @@
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.77 -->
+<title>Is It Ever a Good Thing to Use a Nonfree Program? 
+- GNU Project - Free Software Foundation</title>
+ <!--#include 
virtual="/philosophy/po/is-ever-good-use-nonfree-program.translist" -->
+<!--#include virtual="/server/banner.html" -->
+
+<h2>Is It Ever a Good Thing to Use a Nonfree Program?</h2>
+
+<p>by <a href="http://www.stallman.org/";><strong>Richard
+Stallman</strong></a></p>
+
+<p>If you run a nonfree program on your computer, it denies your freedom;
+the main one harmed is you. Your usage of it can harm others
+indirectly, by encouraging development of that nonfree program. If
+you make a promise not to redistribute the program to others, you do
+wrong, because breaking such a promise is bad and keeping it is worse.
+Still, the main direct harm is to you.</p>
+
+<p>It is even worse if you recommend that others run the nonfree program,
+or lead them to do so. When you do that, you're leading them to give
+up their freedom. Thus, what we should avoid most firmly is leading
+or encouraging others to run nonfree software. (Where the program uses
+a secret protocol for communication, as in the case of Skype, your own
+use of it pressures others to use it too, so it is especially
+important to reject any use of these programs.)</p>
+
+<p>But there is one special case where using some nonfree software, and
+even urging others to use it, can be a positive thing. That's when
+the use of the nonfree software aims directly at putting an end to the
+use of that very same nonfree software.</p>
+
+<p>In 1983 I decided to develop the GNU operating system, as a free
+replacement for Unix. The feasible way to do it was to write and test
+the components one by one on Unix. But was it legitimate to use Unix
+for this? And was it legitimate to ask others to use Unix for this,
+given that Unix was proprietary software? Of course, if it had not
+been proprietary, it would not have required replacing.</p>
+
+<p>The conclusion I reached was that using Unix to put an end to the use
+of Unix was legitimate. I likened it to participating in small ways
+in some other evil activity, such as a criminal gang or a dishonest
+political campaign, in order to expose it and shut it down. While
+participating in the activity is wrong in itself, shutting it down
+excuses minor peripheral participation, comparable to merely using
+Unix. This argument would not justify being a ringleader, but I was
+only considering using Unix, not going to work for its development
+team.</p>
+
+<p>The job of replacing Unix was completed when the last essential
+component was replaced by Linux, the kernel started by Linus Torvalds
+in 1991. We still add to the GNU/Linux system, but that doesn't
+require using Unix, so it isn't a reason for using Unix&mdash;not any
+more. Thus, whenever you're using a nonfree program for this sort of
+reason, you should reconsider from time to time whether the need still
+exists.</p>
+
+<p>However, there are other nonfree programs we still need to replace,
+and the analogous question often arises. Should you run the nonfree
+driver for a peripheral to help you develop a free replacement driver?
+Yes, by all means. Is it ok to run
+the <a href="http://www.gnu.org/philosophy/javascript-trap.html";>nonfree
+JavaScript</a> on a web site in order to file complaint asking the
+webmasters to free that JavaScript code, or make the site work without
+it?  Definitely&mdash;but other than that, you should
+have <a href="https://www.gnu.org/software/librejs/";>LibreJS</a> block
+it for you.</p>
+
+<p>But this justification won't stretch any further. People that develop
+nonfree software, even software with malicious functionalities, often
+try to excuse this on the grounds that they fund some development of
+free software. However, a business that is basically wrong can't be
+legitimized by spending some of the profits on a worthy cause. For
+instance, some (not all) of the activities of the Gates Foundation are
+laudable, but they don't excuse Bill Gates's career, or Microsoft. If
+the business works directly against the worthy cause it tries to
+legitimize itself with, that is a self-contradiction and it undermines
+the cause.</p>
+
+<p>Even using a nonfree program to develop free software in general is
+better to avoid. For instance, we should not ask people to run
+Windows or MacOS in order to make free applications run on them. As
+developer of Emacs and GCC, I accepted changes to make them support
+nonfree systems such as VMS, Windows and MacOS. There was no reason
+to reject that code, but I did not ask people to run nonfree systems
+in order to develop it. These changes were written by people who were using
+those systems anyway, and they also did the packaging of Emacs
+releases for those systems.</p>
+
+<p>The &ldquo;developing its own replacement&rdquo; exception is valid within 
its
+limits, and crucial for the progress of free software, but we must
+resist stretching it any further lest it turn into an all-purpose
+excuse for any profitable activity with nonfree software.</p>
+
+<hr />
+
+<p>Occasionally it is necessary to use and even upgrade a nonfree
+system in order to install a free replacement system.  It's not
+exactly the same issue, but the same arguments apply: it is legitimate
+to run some nonfree software momentarily in order to get rid of
+it.</p>
+
+</div><!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<p>Please send general FSF &amp; GNU inquiries to
+<a href="mailto:address@hidden";>&lt;address@hidden&gt;</a>.
+There are also <a href="/contact/">other ways to contact</a>
+the FSF.  Broken links and other corrections or suggestions can be sent
+to <a href="mailto:address@hidden";>&lt;address@hidden&gt;</a>.</p>
+
+<p><!-- TRANSLATORS: Ignore the original text in this paragraph,
+        replace it with the translation of these two:
+
+        We work hard and do our best to provide accurate, good quality
+        translations.  However, we are not exempt from imperfection.
+        Please send your comments and general suggestions in this regard
+        to <a href="mailto:address@hidden";>
+        &lt;address@hidden&gt;</a>.</p>
+
+        <p>For information on coordinating and submitting translations of
+        our web pages, see <a
+        href="/server/standards/README.translations.html">Translations
+        README</a>. -->
+Please see the <a
+href="/server/standards/README.translations.html">Translations
+README</a> for information on coordinating and submitting translations
+of this article.</p>
+</div>
+
+<!-- Regarding copyright, in general, standalone pages (as opposed to
+     files generated as part of manuals) on the GNU web server should
+     be under CC BY-ND 4.0.  Please do NOT change or remove this
+     without talking with the webmasters or licensing team first.
+     Please make sure the copyright date is consistent with the
+     document.  For web pages, it is ok to list just the latest year the
+     document was modified, or published.
+     
+     If you wish to list earlier years, that is ok too.
+     Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
+     years, as long as each year in the range is in fact a copyrightable
+     year, i.e., a year in which the document was published (including
+     being publicly visible on the web or in a revision control system).
+     
+     There is more detail about copyright years in the GNU Maintainers
+     Information document, www.gnu.org/prep/maintain. -->
+
+<p>Copyright &copy; 2013, 2015 Richard Stallman</p>
+
+<p>This page is licensed under a <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/4.0/";>Creative
+Commons Attribution-NoDerivatives 4.0 International License</a>.</p>
+
+<!--#include virtual="/server/bottom-notes.html" -->
+
+<p class="unprintable">Updated:
+<!-- timestamp start -->
+$Date: 2015/06/27 09:28:15 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>