[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www/philosophy shouldbefree.es.html software-pa...
|
From: |
GNUN |
|
Subject: |
www/philosophy shouldbefree.es.html software-pa... |
|
Date: |
Tue, 21 Sep 2021 07:32:58 -0400 (EDT) |
CVSROOT: /web/www
Module name: www
Changes by: GNUN <gnun> 21/09/21 07:32:58
Modified files:
philosophy : shouldbefree.es.html software-patents.es.html
philosophy/po : shouldbefree.es-en.html shouldbefree.es.po
software-patents.es-en.html
software-patents.es.po
Log message:
Automatic update by GNUnited Nations.
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/shouldbefree.es.html?cvsroot=www&r1=1.46&r2=1.47
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/software-patents.es.html?cvsroot=www&r1=1.12&r2=1.13
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/shouldbefree.es-en.html?cvsroot=www&r1=1.30&r2=1.31
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/shouldbefree.es.po?cvsroot=www&r1=1.38&r2=1.39
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/software-patents.es-en.html?cvsroot=www&r1=1.5&r2=1.6
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/software-patents.es.po?cvsroot=www&r1=1.23&r2=1.24
Patches:
Index: shouldbefree.es.html
===================================================================
RCS file: /web/www/www/philosophy/shouldbefree.es.html,v
retrieving revision 1.46
retrieving revision 1.47
diff -u -b -r1.46 -r1.47
--- shouldbefree.es.html 13 Sep 2021 11:04:35 -0000 1.46
+++ shouldbefree.es.html 21 Sep 2021 11:32:55 -0000 1.47
@@ -334,10 +334,11 @@
Los programadores trabajan normalmente con el «código fuente» del
programa,
que está escrito en un lenguaje de programación como por ejemplo Fortran o
C. Mediante nombres se designan los datos que se están usando y las partes
-del programa, y se representan las operaciones con sÃmbolos tales como «+»
-para la suma y «-» para la resta. El lenguaje está diseñado para ayudar a
-los programadores a leer y modificar los programas. He aquà un ejemplo. un
-programa que calcula la distancia entre dos puntos en un plano:</p>
+del programa, y se representan las operaciones con sÃmbolos tales como
+<code>+</code> para la suma y <code>-</code> para la resta. El lenguaje está
+diseñado para ayudar a los programadores a leer y modificar los
+programas. He aquà un ejemplo. un programa que calcula la distancia entre
+dos puntos en un plano:</p>
<pre>
float
@@ -964,7 +965,7 @@
<p class="unprintable"><!-- timestamp start -->
Ãltima actualización:
-$Date: 2021/09/13 11:04:35 $
+$Date: 2021/09/21 11:32:55 $
<!-- timestamp end -->
</p>
Index: software-patents.es.html
===================================================================
RCS file: /web/www/www/philosophy/software-patents.es.html,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -b -r1.12 -r1.13
--- software-patents.es.html 2 Sep 2021 17:36:33 -0000 1.12
+++ software-patents.es.html 21 Sep 2021 11:32:55 -0000 1.13
@@ -841,27 +841,27 @@
</p>
<p>
-Si quiero poner una declaración <cite>if</cite> dentro de una declaración
-<cite>while</cite>, no tengo que preocuparme de que la declaración
-<cite>if</cite> pueda oscilar a una determinada frecuencia, friccionar con
-la declaración <cite>while</cite> y llegar a romperse. No tengo que
+Si quiero poner una declaración <code>if</code> dentro de una declaración
+<code>while</code>, no tengo que preocuparme de que la declaración
+<code>if</code> pueda oscilar a una determinada frecuencia, friccionar con
+la declaración <code>while</code> y llegar a romperse. No tengo que
preocuparme de que oscile a una frecuencia demasiado alta y genere una señal
que modifique el valor de alguna otra variable. No tengo que preocuparme de
-cuánta corriente puede requerir la declaración <cite>if</cite> y si podrá
-disipar el calor dentro de la declaración <cite>while</cite>. O de si habrá
-una caÃda de tensión en la declaración <cite>while</cite> que impida que la
-declaración <cite>if</cite> funcione.
+cuánta corriente puede requerir la declaración <code>if</code> y si podrá
+disipar el calor dentro de la declaración <code>while</code>. O de si habrá
+una caÃda de tensión en la declaración <code>while</code> que impida que la
+declaración <code>if</code> funcione.
No tengo que preocuparme de que si ejecuto el programa en un entorno de agua
-salada, el agua pueda introducirse entre las declaraciones <cite>if</cite> y
-<cite>while</cite> y provocar corrosión. Cuando hago referencia al valor de
+salada, el agua pueda introducirse entre las declaraciones <code>if</code> y
+<code>while</code> y provocar corrosión. Cuando hago referencia al valor de
una variable, no tengo que preocuparme de que se exceda ningún lÃmite si eso
sucede veinte veces. Cuando hago referencia a la variable tampoco tengo que
preocuparme de su capacitancia, ni de si habrá tiempo suficiente para que se
cargue su valor. Cuando escribo el programa no tengo que preocuparme de cómo
ensamblaré fÃsicamente cada copia ni de si podré arreglármelas para
insertar
-la declaración <cite>if</cite> dentro de la declaración
-<cite>while</cite>. No tengo que preocuparme de cómo acceder a la
-declaración <cite>if</cite>, en caso de que se rompa, para retirarla y
+la declaración <code>if</code> dentro de la declaración
+<code>while</code>. No tengo que preocuparme de cómo acceder a la
+declaración <code>if</code>, en caso de que se rompa, para retirarla y
sustituirla por una nueva.
</p>
@@ -894,9 +894,9 @@
Hay otra gran ventaja. Si usted ha diseñado un producto fÃsico, el siguiente
paso será diseñar la fábrica para construirlo. Edificar esa fábrica puede
costar millones o decenas de millones, mientras que para hacer copias del
-programa no hay más que escribir «copiar». La misma orden de copiar copiará
-cualquier programa. ¿Queremos copias en CD? De acuerdo, entonces grabamos un
-CD maestro y lo enviamos a una planta de CD. Utilizarán el mismo
+programa no hay más que escribir <kbd>copy</kbd>. La misma orden de copiar
+copiará cualquier programa. ¿Queremos copias en CD? De acuerdo, entonces
+grabamos un CD maestro y lo enviamos a una planta de CD. Utilizarán el mismo
equipamiento para copiar cualquier contenido en un CD, no tenemos que
levantar una fábrica para hacer este producto. Hay una tremenda
simplificación y una tremenda reducción de costes en el diseño.
@@ -1290,7 +1290,7 @@
<p class="unprintable"><!-- timestamp start -->
Ãltima actualización:
-$Date: 2021/09/02 17:36:33 $
+$Date: 2021/09/21 11:32:55 $
<!-- timestamp end -->
</p>
Index: po/shouldbefree.es-en.html
===================================================================
RCS file: /web/www/www/philosophy/po/shouldbefree.es-en.html,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -b -r1.30 -r1.31
--- po/shouldbefree.es-en.html 13 Sep 2021 11:04:35 -0000 1.30
+++ po/shouldbefree.es-en.html 21 Sep 2021 11:32:57 -0000 1.31
@@ -323,7 +323,7 @@
program, which is written in a programming language such as Fortran or
C. It uses names to designate the data being used and the parts of
the program, and it represents operations with symbols such as
-‘+’ for addition and ‘-’ for subtraction. It
+<code>+</code> for addition and <code>-</code> for subtraction. It
is designed to help programmers read and change programs. Here is an
example; a program to calculate the distance between two points in a
plane:</p>
@@ -906,7 +906,7 @@
<p class="unprintable">Updated:
<!-- timestamp start -->
-$Date: 2021/09/13 11:04:35 $
+$Date: 2021/09/21 11:32:57 $
<!-- timestamp end -->
</p>
</div>
Index: po/shouldbefree.es.po
===================================================================
RCS file: /web/www/www/philosophy/po/shouldbefree.es.po,v
retrieving revision 1.38
retrieving revision 1.39
diff -u -b -r1.38 -r1.39
--- po/shouldbefree.es.po 21 Sep 2021 10:56:37 -0000 1.38
+++ po/shouldbefree.es.po 21 Sep 2021 11:32:57 -0000 1.39
@@ -705,14 +705,6 @@
"permanece oscuro. Nadie, ni siquiera un buen programador, puede cambiar "
"fácilmente esos números para lograr que el programa haga algo diferente."
-# | Programmers normally work with the “source code” for a
-# | program, which is written in a programming language such as Fortran or C.
-# | It uses names to designate the data being used and the parts of the
-# | program, and it represents operations with symbols such as
-# | [-‘+’-] {+<code>+</code>+} for addition and
-# | [-‘-’-] {+<code>-</code>+} for subtraction. It is designed to
-# | help programmers read and change programs. Here is an example; a program
-# | to calculate the distance between two points in a plane:
#. type: Content of: <div><p>
msgid ""
"Programmers normally work with the “source code” for a program, "
Index: po/software-patents.es-en.html
===================================================================
RCS file: /web/www/www/philosophy/po/software-patents.es-en.html,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -b -r1.5 -r1.6
--- po/software-patents.es-en.html 2 Sep 2021 17:36:40 -0000 1.5
+++ po/software-patents.es-en.html 21 Sep 2021 11:32:57 -0000 1.6
@@ -846,30 +846,30 @@
</p>
<p>
-If I wanted to put an ‘If’ statement in a
-‘While’ statement, I don't have to worry about whether the
-‘If’ statement will oscillate at a certain frequency and
-rub against the ‘While’ statement and eventually they will
+If I wanted to put an <code>if</code> statement in a
+<code>while</code> statement, I don't have to worry about whether the
+<code>if</code> statement will oscillate at a certain frequency and
+rub against the <code>while</code> statement and eventually they will
fracture. I don't have to worry whether it will oscillate at a
certain higher frequency and induce a signal in the value of some
other variable. I don't have to worry about how much current that
-‘If’ statement will draw and whether it can dissipate the
-heat there inside that while statement. Whether there will be a
-voltage drop across the while statement that will make the
-‘If’ statement not function.
+<code>if</code> statement will draw and whether it can dissipate the
+heat there inside that <code>while</code> statement. Whether there will be a
+voltage drop across the <code>while</code> statement that will make the
+<code>if</code> statement not function.
<span class="gnun-split"></span>I don't have to worry that
if i run this program in a salt water environment that the salt water
-may get in between the ‘If’ statement and the
-‘While’ statement and cause corrosion. I don't have to
+may get in between the <code>if</code> statement and the
+<code>while</code> statement and cause corrosion. I don't have to
worry when I refer to the value of a variable whether I am exceeding
the fan-out limit by referring to it 20 times. I don't have to worry,
when I refer to the variable, how much capacitance it has and whether
there has been sufficient time to charge up the value. I don't have
to worry when I write the program, about how I am going to physically
assemble each copy and whether I can manage to get access to put that
-‘If’ statement inside the ‘While’ statement.
+<code>if</code> statement inside the <code>while</code> statement.
I don't have to worry about how I am going to gain access in case that
-‘If’ statement breaks, to remove it and replace it with a
+<code>if</code> statement breaks, to remove it and replace it with a
new one.
</p>
@@ -904,7 +904,7 @@
There is another big saving. If you have designed a physical product,
the next thing you have to do is design the factory to make it. To
build this factory may cost millions or tens of millions whereas to
-make copies of the program, you just have to type ‘copy’.
+make copies of the program, you just have to type <kbd>copy</kbd>.
The same copy command will copy any program. You want copies on CD
then fine. You burn a master CD and send it off to a CD plant. They
will use the same equipment which will copy any contents on a CD. You
@@ -1286,7 +1286,7 @@
<p class="unprintable">Updated:
<!-- timestamp start -->
-$Date: 2021/09/02 17:36:40 $
+$Date: 2021/09/21 11:32:57 $
<!-- timestamp end -->
</p>
</div>
Index: po/software-patents.es.po
===================================================================
RCS file: /web/www/www/philosophy/po/software-patents.es.po,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -b -r1.23 -r1.24
--- po/software-patents.es.po 21 Sep 2021 10:56:37 -0000 1.23
+++ po/software-patents.es.po 21 Sep 2021 11:32:57 -0000 1.24
@@ -1572,19 +1572,6 @@
"entonces tenemos un problema, porque el reto es construir objetos fÃsicos "
"que funcionen en la realidad."
-# | If I wanted to put an [-‘If’-] {+<code>if</code>+} statement
-# | in a [-‘While’-] {+<code>while</code>+} statement, I don't
-# | have to worry about whether the [-‘If’-] {+<code>if</code>+}
-# | statement will oscillate at a certain frequency and rub against the
-# | [-‘While’-] {+<code>while</code>+} statement and eventually
-# | they will fracture. I don't have to worry whether it will oscillate at a
-# | certain higher frequency and induce a signal in the value of some other
-# | variable. I don't have to worry about how much current that
-# | [-‘If’-] {+<code>if</code>+} statement will draw and whether
-# | it can dissipate the heat there inside that [-while-]
-# | {+<code>while</code>+} statement. Whether there will be a voltage drop
-# | across the [-while-] {+<code>while</code>+} statement that will make the
-# | [-‘If’-] {+<code>if</code>+} statement not function.
#. type: Content of: <div><p>
msgid ""
"If I wanted to put an <code>if</code> statement in a <code>while</code> "
@@ -1609,21 +1596,6 @@
"una caÃda de tensión en la declaración <code>while</code> que impida que
la "
"declaración <code>if</code> funcione."
-# | I don't have to worry that if i run this program in a salt water
-# | environment that the salt water may get in between the
-# | [-‘If’-] {+<code>if</code>+} statement and the
-# | [-‘While’-] {+<code>while</code>+} statement and cause
-# | corrosion. I don't have to worry when I refer to the value of a variable
-# | whether I am exceeding the fan-out limit by referring to it 20 times. I
-# | don't have to worry, when I refer to the variable, how much capacitance it
-# | has and whether there has been sufficient time to charge up the value. I
-# | don't have to worry when I write the program, about how I am going to
-# | physically assemble each copy and whether I can manage to get access to
-# | put that [-‘If’-] {+<code>if</code>+} statement inside the
-# | [-‘While’-] {+<code>while</code>+} statement. I don't have to
-# | worry about how I am going to gain access in case that
-# | [-‘If’-] {+<code>if</code>+} statement breaks, to remove it
-# | and replace it with a new one.
#. type: Content of: <div><p>
msgid ""
"I don't have to worry that if i run this program in a salt water environment "
@@ -1702,16 +1674,6 @@
"millón de lÃneas de código. Es un proyecto realizado prácticamente sin "
"financiación, realizado en su mayor parte por gente en su tiempo libre."
-# | There is another big saving. If you have designed a physical product, the
-# | next thing you have to do is design the factory to make it. To build this
-# | factory may cost millions or tens of millions whereas to make copies of
-# | the program, you just have to type [-‘copy’.-]
-# | {+<kbd>copy</kbd>.+} The same copy command will copy any program. You
-# | want copies on CD then fine. You burn a master CD and send it off to a CD
-# | plant. They will use the same equipment which will copy any contents on a
-# | CD. You don't have to build a factory to make this product. There is
-# | tremendous simplification and tremendous reduction in costs of designing
-# | things.
#. type: Content of: <div><p>
msgid ""
"There is another big saving. If you have designed a physical product, the "
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- www/philosophy shouldbefree.es.html software-pa...,
GNUN <=