[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www philosophy/open-source-misses-the-point.es....
From: |
GNUN |
Subject: |
www philosophy/open-source-misses-the-point.es.... |
Date: |
Mon, 4 Mar 2019 06:00:10 -0500 (EST) |
CVSROOT: /web/www
Module name: www
Changes by: GNUN <gnun> 19/03/04 06:00:09
Modified files:
philosophy : open-source-misses-the-point.es.html
philosophy/po : open-source-misses-the-point.es-en.html
proprietary/po : es.po proprietary-coverups.translist
Added files:
proprietary : proprietary-coverups.es.html
proprietary/po : proprietary-coverups.es-en.html
Log message:
Automatic update by GNUnited Nations.
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/open-source-misses-the-point.es.html?cvsroot=www&r1=1.83&r2=1.84
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/open-source-misses-the-point.es-en.html?cvsroot=www&r1=1.44&r2=1.45
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/proprietary-coverups.es.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/es.po?cvsroot=www&r1=1.51&r2=1.52
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/proprietary-coverups.translist?cvsroot=www&r1=1.5&r2=1.6
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/proprietary-coverups.es-en.html?cvsroot=www&rev=1.1
Patches:
Index: philosophy/open-source-misses-the-point.es.html
===================================================================
RCS file: /web/www/www/philosophy/open-source-misses-the-point.es.html,v
retrieving revision 1.83
retrieving revision 1.84
diff -u -b -r1.83 -r1.84
--- philosophy/open-source-misses-the-point.es.html 23 Feb 2019 10:59:46
-0000 1.83
+++ philosophy/open-source-misses-the-point.es.html 4 Mar 2019 11:00:09
-0000 1.84
@@ -74,31 +74,23 @@
<p>Algunos de los defensores del «código abierto» lo consideraron una
«campaña
de marketing para el software libre», con el objetivo de atraer a los
ejecutivos de las empresas enfatizando los beneficios prácticos sin
-mencionar conceptos de lo que es correcto e incorrecto —y que quizá
-los empresarios no deseaban oÃr—. Otros defensores rechazaban
-rotundamente los valores éticos y sociales del software libre. Cualesquiera
-que hayan sido sus puntos de vista, cuando hacÃan campaña por el «código
-abierto» no mencionaban ni abogaban por esos valores. La expresión «código
-abierto» fue rápidamente asociada con ideas y argumentaciones basadas
-únicamente en valores de orden práctico, tales como desarrollar o usar
-software potente y confiable. La mayorÃa de los partidarios del «código
-abierto» llegaron al movimiento después de entonces y hacen la misma
-asociación de conceptos.</p>
-
-<p>Ambas expresiones describen casi la misma categorÃa de software, pero
-representan puntos de vista basados en valores fundamentalmente
-diferentes. El código abierto es una metodologÃa de programación, el
-software libre es un movimiento social. Para el movimiento del software
-libre, el software libre es un imperativo ético, respeto esencial por la
-libertad de los usuarios. En cambio la filosofÃa del código abierto plantea
-las cuestiones en términos de cómo «mejorar» el software, en sentido
-meramente práctico. Sostiene que el software privativo no es una solución
-óptima para los problemas prácticos que hay que resolver. En la mayorÃa de
-los casos, cuando se discute sobre «código abierto» no se toma en
-consideración el bien y el mal sino únicamente la popularidad y el éxito; he
-aquà un <a
-href="http://www.linuxinsider.com/story/Open-Source-Is-Woven-Into-the-Latest-Hottest-Trends-78937.html">ejemplo
-tÃpico</a>.</p>
+mencionar conceptos de lo que es correcto e incorrecto, que quizá los
+empresarios no deseaban oÃr. Otros defensores rechazaban rotundamente los
+valores éticos y sociales del software libre. Cualesquiera que hayan sido
+sus puntos de vista, cuando hacÃan campaña por el «código abierto» no
+mencionaban ni abogaban por esos valores. La expresión «código abierto» fue
+rápidamente asociada con ideas y argumentaciones basadas únicamente en
+valores de orden práctico, tales como desarrollar o usar software potente y
+confiable. La mayorÃa de los partidarios del «código abierto» llegaron al
+movimiento después de entonces y hacen la misma asociación de conceptos.</p>
+
+<p>Ambos describen casi la misma categorÃa de software, pero representan
puntos
+de vista basados en valores fundamentalmente diferentes. Para el movimiento
+del software libre, el software libre es un imperativo ético, respeto
+esencial por la libertad de los usuarios. En cambio, la filosofÃa del código
+abierto plantea las cuestiones en términos de cómo «mejorar» el software,
en
+sentido meramente práctico. Sostiene que el software privativo no es una
+solución óptima para los problemas prácticos que hay que resolver.</p>
<p>Para el movimiento del software libre, sin embargo, el software que no es
libre es un problema social y la solución consiste en dejar de usarlo,
@@ -518,7 +510,7 @@
<p class="unprintable"><!-- timestamp start -->
Ãltima actualización:
-$Date: 2019/02/23 10:59:46 $
+$Date: 2019/03/04 11:00:09 $
<!-- timestamp end -->
</p>
Index: philosophy/po/open-source-misses-the-point.es-en.html
===================================================================
RCS file: /web/www/www/philosophy/po/open-source-misses-the-point.es-en.html,v
retrieving revision 1.44
retrieving revision 1.45
diff -u -b -r1.44 -r1.45
--- philosophy/po/open-source-misses-the-point.es-en.html 23 Feb 2019
10:59:46 -0000 1.44
+++ philosophy/po/open-source-misses-the-point.es-en.html 4 Mar 2019
11:00:09 -0000 1.45
@@ -72,21 +72,22 @@
with ideas and arguments based only on practical values, such as
making or having powerful, reliable software. Most of the supporters
of open source have come to it since then, and they make the same
-association.</p>
+association. Most discussion of “open source” pays no
+attention to right and wrong, only to popularity and success; here's
+a <a
href="http://www.linuxinsider.com/story/Open-Source-Is-Woven-Into-the-Latest-Hottest-Trends-78937.html">
+typical example</a>. A minority of supporters of open source do
+nowadays say freedom is part of the issue, but they are not very visible
+among the many that don't.</p>
-<p>The two terms
+<p>The two now
describe almost the same category of software, but they stand for
-views based on fundamentally different values. Open source is a
-development methodology; free software is a social movement. For the
+views based on fundamentally different values. For the
free software movement, free software is an ethical imperative,
essential respect for the users' freedom. By contrast,
the philosophy of open source considers issues in terms of how to make
software “better”—in a practical sense only. It
says that nonfree software is an inferior solution to the practical
-problem at hand. Most discussion of “open source” pays no
-attention to right and wrong, only to popularity and success; here's
-a <a
href="http://www.linuxinsider.com/story/Open-Source-Is-Woven-Into-the-Latest-Hottest-Trends-78937.html">
-typical example</a>.</p>
+problem at hand.</p>
<p>For the free software movement, however, nonfree software is a
social problem, and the solution is to stop using it and move to free
@@ -474,7 +475,7 @@
<p class="unprintable">Updated:
<!-- timestamp start -->
-$Date: 2019/02/23 10:59:46 $
+$Date: 2019/03/04 11:00:09 $
<!-- timestamp end -->
</p>
</div>
Index: proprietary/po/es.po
===================================================================
RCS file: /web/www/www/proprietary/po/es.po,v
retrieving revision 1.51
retrieving revision 1.52
diff -u -b -r1.51 -r1.52
--- proprietary/po/es.po 4 Mar 2019 09:00:09 -0000 1.51
+++ proprietary/po/es.po 4 Mar 2019 11:00:09 -0000 1.52
@@ -6998,6 +6998,9 @@
"developers converted it into a malicious functionality by trying to cover up "
"the existence of the bug."
msgstr ""
+"En esta página se muestran ejemplos en los que el software privativo tenÃa "
+"un error de programación, y los desarrolladores, al intentar ocultar su "
+"existencia, lo convirtieron en una funcionalidad maliciosa."
#. type: Content of: <ul><li><p>
msgid ""
@@ -7006,6 +7009,10 @@
"and-desist-letter-instead-of-fixing-security-flaw/\"> making legal threats "
"against the security company that found it</a>."
msgstr ""
+"Price Waterhouse Coopers intentó que no se conociera un fallo de seguridad, "
+"mediante <a href=\"http://www.zdnet.com/article/pwc-sends-security-"
+"researchers-cease-and-desist-letter-instead-of-fixing-security-flaw/"
+"\">amenazas legales a la empresa de seguridad que lo descubrió</a>."
#. type: Content of: <title>
#, fuzzy
Index: proprietary/po/proprietary-coverups.translist
===================================================================
RCS file: /web/www/www/proprietary/po/proprietary-coverups.translist,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -b -r1.5 -r1.6
--- proprietary/po/proprietary-coverups.translist 1 Feb 2017 12:01:17
-0000 1.5
+++ proprietary/po/proprietary-coverups.translist 4 Mar 2019 11:00:09
-0000 1.6
@@ -4,6 +4,7 @@
<p>
<span dir="ltr" class="original"><a lang="en" hreflang="en"
href="/proprietary/proprietary-coverups.en.html">English</a> [en]</span>
<span dir="ltr"><a lang="de" hreflang="de"
href="/proprietary/proprietary-coverups.de.html">Deutsch</a> [de]</span>
+<span dir="ltr"><a lang="es" hreflang="es"
href="/proprietary/proprietary-coverups.es.html">español</a> [es]</span>
<span dir="ltr"><a lang="fr" hreflang="fr"
href="/proprietary/proprietary-coverups.fr.html">français</a> [fr]</span>
<span dir="ltr"><a lang="ja" hreflang="ja"
href="/proprietary/proprietary-coverups.ja.html">æ¥æ¬èª</a> [ja]</span>
<span dir="ltr"><a lang="ru" hreflang="ru"
href="/proprietary/proprietary-coverups.ru.html">ÑÑÑÑкий</a> [ru]</span>
@@ -12,6 +13,7 @@
<link rel="alternate" type="text/html"
href="/proprietary/proprietary-coverups.html" hreflang="x-default" />
<link rel="alternate" type="text/html" lang="en" hreflang="en"
href="/proprietary/proprietary-coverups.en.html" title="English" />
<link rel="alternate" type="text/html" lang="de" hreflang="de"
href="/proprietary/proprietary-coverups.de.html" title="Deutsch" />
+<link rel="alternate" type="text/html" lang="es" hreflang="es"
href="/proprietary/proprietary-coverups.es.html" title="español" />
<link rel="alternate" type="text/html" lang="fr" hreflang="fr"
href="/proprietary/proprietary-coverups.fr.html" title="français" />
<link rel="alternate" type="text/html" lang="ja" hreflang="ja"
href="/proprietary/proprietary-coverups.ja.html" title="æ¥æ¬èª" />
<link rel="alternate" type="text/html" lang="ru" hreflang="ru"
href="/proprietary/proprietary-coverups.ru.html" title="ÑÑÑÑкий" />
Index: proprietary/proprietary-coverups.es.html
===================================================================
RCS file: proprietary/proprietary-coverups.es.html
diff -N proprietary/proprietary-coverups.es.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ proprietary/proprietary-coverups.es.html 4 Mar 2019 11:00:09 -0000
1.1
@@ -0,0 +1,138 @@
+<!--#set var="ENGLISH_PAGE" value="/proprietary/proprietary-coverups.en.html"
-->
+
+<!--#include virtual="/server/header.es.html" -->
+<!-- Parent-Version: 1.86 -->
+<!--
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ Please do not edit <ul class="blurbs">
+!
+ Instead, edit /proprietary/workshop/mal.rec, then regenerate pages.
+ See explanations in /proprietary/workshop/README.md.
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+-->
+
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>Encubrimiento en el software privativo - GNU Project - Free Software
+Foundation</title>
+
+<!--#include virtual="/proprietary/po/proprietary-coverups.translist" -->
+<!--#include virtual="/server/banner.es.html" -->
+<h2>Encubrimiento en el software privativo</h2>
+
+<p><a href="/proprietary/proprietary.html">Otros ejemplos de
+<cite>malware</cite> privativo</a></p>
+
+<div class="comment">
+<p>El software que no es libre (privativo) a menudo es <cite>malware</cite>
+(diseñado para maltratar a los usuarios). El software que no es libre está
+controlado por quienes lo han desarrollado, lo que los coloca en una
+posición de poder sobre los usuarios; <a
+href="/philosophy/free-software-even-more-important.html">esa es la
+injusticia básica</a>. A menudo los desarrolladores ejercen ese poder en
+perjuicio de los usuarios a cuyo servicio deberÃan estar.</p>
+
+<p>En esta página se muestran ejemplos en los que el software privativo tenÃa
+un error de programación, y los desarrolladores, al intentar ocultar su
+existencia, lo convirtieron en una funcionalidad maliciosa.</p>
+
+<div class="important">
+<p>Si conoce algún ejemplo más que deba estar incluido en esta página,
escriba
+por favor a <a
+href="mailto:address@hidden"><address@hidden></a> para
+informarnos. Incluya la URL de una o dos referencias confiables para
+justificar su inclusión.</p>
+</div>
+</div>
+<div class="column-limit" id="proprietary-coverups"></div>
+
+<ul class="blurbs">
+ <li id="M201612120">
+ <p>Price Waterhouse Coopers intentó que no se conociera un fallo de
seguridad,
+mediante <a
+href="http://www.zdnet.com/article/pwc-sends-security-researchers-cease-and-desist-letter-instead-of-fixing-security-flaw/">amenazas
+legales a la empresa de seguridad que lo descubrió</a>.</p>
+ </li>
+</ul>
+
+
+<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"><address@hidden></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"><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>. -->
+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"><address@hidden></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 © 2017, 2018, 2019 Free Software Foundation, Inc.</p>
+
+<p> </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: Daniel Gutiérrez, 2019.</strong></div>
+
+<p class="unprintable"><!-- timestamp start -->
+Ãltima actualización:
+
+$Date: 2019/03/04 11:00:09 $
+
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+<!-- for class="inner", starts in the banner include -->
+</body>
+</html>
Index: proprietary/po/proprietary-coverups.es-en.html
===================================================================
RCS file: proprietary/po/proprietary-coverups.es-en.html
diff -N proprietary/po/proprietary-coverups.es-en.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ proprietary/po/proprietary-coverups.es-en.html 4 Mar 2019 11:00:09
-0000 1.1
@@ -0,0 +1,114 @@
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.86 -->
+<!--
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ Please do not edit <ul class="blurbs">!
+ Instead, edit /proprietary/workshop/mal.rec, then regenerate pages.
+ See explanations in /proprietary/workshop/README.md.
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+-->
+<title>Proprietary Coverups
+- GNU Project - Free Software Foundation</title>
+ <!--#include virtual="/proprietary/po/proprietary-coverups.translist" -->
+<!--#include virtual="/server/banner.html" -->
+<h2>Proprietary Coverups</h2>
+
+<p><a href="/proprietary/proprietary.html">Other examples of proprietary
malware</a></p>
+
+<div class="comment">
+<p>Nonfree (proprietary) software is very often malware (designed to
+mistreat the user). Nonfree software is controlled by its developers,
+which puts them in a position of power over the users; <a
+href="/philosophy/free-software-even-more-important.html">that is the
+basic injustice</a>. The developers often exercise that power to the
+detriment of the users they ought to serve.</p>
+
+<p>This page lists instances where proprietary software had a bug,
+and the developers converted it into a malicious functionality by
+trying to cover up the existence of the bug.</p>
+
+<div class="important">
+<p>If you know of an example that ought to be in this page but isn't
+here, please write
+to <a href="mailto:address@hidden"><address@hidden></a>
+to inform us. Please include the URL of a trustworthy reference or two
+to serve as specific substantiation.</p>
+</div>
+</div>
+<div class="column-limit" id="proprietary-coverups"></div>
+
+<ul class="blurbs">
+ <li id="M201612120">
+ <p>Price Waterhouse Coopers tried
+ to suppress knowledge of a security flaw by <a
+
href="http://www.zdnet.com/article/pwc-sends-security-researchers-cease-and-desist-letter-instead-of-fixing-security-flaw/">
+ making legal threats against the security company that found
+ it</a>.</p>
+ </li>
+</ul>
+
+
+</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 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 © 2017, 2018, 2019 Free Software Foundation, Inc.</p>
+
+<p>This page is licensed under a <a rel="license"
+href="http://creativecommons.org/licenses/by/4.0/">Creative
+Commons Attribution 4.0 International License</a>.</p>
+
+<!--#include virtual="/server/bottom-notes.html" -->
+
+<p class="unprintable">Updated:
+<!-- timestamp start -->
+$Date: 2019/03/04 11:00:09 $
+<!-- timestamp end -->
+</p>
+</div>
+</div><!-- for class="inner", starts in the banner include -->
+</body>
+</html>
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- www philosophy/open-source-misses-the-point.es....,
GNUN <=