Translation

(itstool) path: figure/programlisting

r151864 | bde | 2005-10-29 09:34:50 -0700 (Sat, 29 Oct 2005) | 13 lines
Changed paths:
M /head/lib/msun/src/e_rem_pio2f.c

Use double precision to simplify and optimize arg reduction for small
and medium size args too: instead of conditionally subtracting a float
17+24, 17+17+24 or 17+17+17+24 bit approximation to pi/2, always
subtract a double 33+53 bit one. The float version is now closer to
the double version than to old versions of itself -- it uses the same
33+53 bit approximation as the simplest cases in the double version,
and where the float version had to switch to the slow general case at
|x| == 2^7*pi/2, it now switches at |x| == 2^19*pi/2 the same as the
double version.

This speeds up arg reduction by a factor of 2 for |x| between 3*pi/4 and
2^7*pi/4, and by a factor of 7 for |x| between 2^7*pi/4 and 2^19*pi/4.
840/8490
Context English Spanish State
To make our work available to all under a liberal license. Poner nuestro trabajo a disposición de todos bajo una licencia liberal.
FreeBSD enjoys an open and transparent working culture. Nearly all discussion in the project happens by email, on <link xlink:href="http://lists.FreeBSD.org/mailman/listinfo">public mailing lists</link> that are also archived for posterity. The project's policies are <link xlink:href="@@URL_RELPREFIX@@/internal/policies.html">documented</link> and maintained under revision control. Participation in the project is open to all. FreeBSD disfruta de una cultura de trabajo abierta y transparente. Casi toda la discusión en el proyecto ocurre por correo electrónico, en <link xlink:href="http://lists.FreeBSD.org/mailman/listinfo">listas de correo públicas</link> que también se archivan para la posteridad. Las políticas del proyecto son <link xlink:href="@@URL_RELPREFIX@@/internal/policies.html">documentadas</link> y mantenidas bajo control de revisión. La participación en el proyecto está abierta a todos.
Understanding FreeBSD culture Comprendiendo la cultura de FreeBSD
To be able to work effectively with the FreeBSD project, you need to understand the project's culture. Para poder trabajar eficazmente con el proyecto FreeBSD necesita entender la cultura del proyecto.
Volunteer driven projects operate under different rules than for-profit corporates. A common mistake that companies make when venturing into the open-source world is that of underplaying these differences. Los proyectos impulsados por voluntarios operan bajo reglas diferentes a las de las corporaciones con fines de lucro. Un error común que cometen las empresas al aventurarse en el mundo del software libre es subestimar estas diferencias.
Motivation Motivación
Most contributions to FreeBSD are done voluntarily without monetary rewards entering the picture. The factors that motivate individuals are complex, ranging from altruism, to an interest in solving the kinds of problems that FreeBSD attempts to solve. In this environment, <quote>elegance is never optional</quote> <citation>Nor1993</citation>. La mayoría de las contribuciones a FreeBSD se hacen voluntariamente sin que las recompensas económicas entren en escena. Los factores que motivan a los individuos son complejos, desde el altruismo hasta el interés por resolver los tipos de problemas que FreeBSD intenta resolver. En este entorno, la <quote>elegancia nunca es opcional </quote> <citation>Nor1993</citation>.
The Long Term View La Visión a Largo Plazo
FreeBSD's <link xlink:href="https://svnweb.freebsd.org/">source repository</link> contains a history of the project since its inception, and there are <link xlink:href="http://www.mckusick.com/csrg/">CDROMs available</link> that contain earlier code from the CSRG. El <link xlink:href="https://svnweb.freebsd.org/">repositorio fuente</link> de FreeBSD contiene un historial del proyecto desde su inicio, y hay <link xlink:href="http://www.mckusick.com/csrg/">CDROMs disponibles</link> que contienen código anterior del CSRG.
FreeBSD traces its roots back nearly twenty years to the work of the Computer Science Research Group at the University of California Berkeley.<_:footnote-1/> A number of the original CSRG developers remain associated with the project. FreeBSD remonta sus inicios hasta hace casi veinte años en el trabajo del Grupo de Investigación en Ciencia Computacional (CSRG) de la Universidad de California en Berkeley.<_:footnote-1/> Algunos de los desarrolladores originales de CSRG siguen asociados al proyecto.
The project values long-term perspectives <citation>Nor2001</citation>. A frequent acronym encountered in the project is <acronym>DTRT</acronym>, which stands for <quote>Do The Right Thing</quote>. El proyecto valora las perspectivas a largo plazo <citation>Nor2001</citation>. Un acrónimo frecuente en el proyecto es <acronym>DTRT</acronym>, que significa <quote>Hacer lo Correcto</quote> (Do The Right Things).
Development Processes Proceso de Desarrollo
Computer programs are tools for communication: at one level programmers communicate their intentions using a precise notation to a tool (a compiler) that translates their instructions to executable code. At another level, the same notation is used for communication of intent between two programmers. Los programas de ordenador son herramientas de comunicación: en un nivel los programadores comunican sus intenciones utilizando una notación precisa a una herramienta (un compilador) que traduce sus instrucciones a código ejecutable. En otro nivel, la misma notación se utiliza para la comunicación de intenciones entre dos programadores.
Formal specifications and design documents are seldom used in the project. Clear and well-written code and well-written change logs (<xref linkend="fig-change-log"/>) are used in their place. FreeBSD development happens by <quote>rough consensus and running code</quote> <citation>Carp1996</citation>. Las especificaciones formales y los documentos de diseño rara vez se utilizan en el proyecto. En su lugar se utilizan códigos claros y bien escritos y registros de cambios bien escritos (<xref linkend="fig-change-log"/>). El desarrollo de FreeBSD se realiza mediante <quote> consenso aproximado y código en ejecución </quote> <citation>Carp1996</citation>.
A sample change log entry Un ejemplo de entrada en el registro de cambios

r151864 | bde | 2005-10-29 09:34:50 -0700 (Sat, 29 Oct 2005) | 13 lines
Changed paths:
M /head/lib/msun/src/e_rem_pio2f.c

Use double precision to simplify and optimize arg reduction for small
and medium size args too: instead of conditionally subtracting a float
17+24, 17+17+24 or 17+17+17+24 bit approximation to pi/2, always
subtract a double 33+53 bit one. The float version is now closer to
the double version than to old versions of itself -- it uses the same
33+53 bit approximation as the simplest cases in the double version,
and where the float version had to switch to the slow general case at
|x| == 2^7*pi/2, it now switches at |x| == 2^19*pi/2 the same as the
double version.

This speeds up arg reduction by a factor of 2 for |x| between 3*pi/4 and
2^7*pi/4, and by a factor of 7 for |x| between 2^7*pi/4 and 2^19*pi/4.

r151864 | bde | 2005-10-29 09:34:50 -0700 (Sat, 29 Oct 2005) | 13 lines
Changed paths:
M /head/lib/msun/src/e_rem_pio2f.c

Use double precision to simplify and optimize arg reduction for small
and medium size args too: instead of conditionally subtracting a float
17+24, 17+17+24 or 17+17+17+24 bit approximation to pi/2, always
subtract a double 33+53 bit one. The float version is now closer to
the double version than to old versions of itself -- it uses the same
33+53 bit approximation as the simplest cases in the double version,
and where the float version had to switch to the slow general case at
|x| == 2^7*pi/2, it now switches at |x| == 2^19*pi/2 the same as the
double version.

This speeds up arg reduction by a factor of 2 for |x| between 3*pi/4 and
2^7*pi/4, and by a factor of 7 for |x| between 2^7*pi/4 and 2^19*pi/4.
Communication between programmers is enhanced by the use of a common coding standard <citerefentry><refentrytitle>style</refentrytitle><manvolnum>9</manvolnum></citerefentry>. La comunicación entre programadores se mejora mediante el uso de un <citerefentry><refentrytitle>style</refentrytitle><manvolnum>9</manvolnum></citerefentry> estándar de codificación común.
Communication Channels Vías de comunicación
FreeBSD's contributors are spread across the world. Email (and to a lesser extent, IRC) is the preferred means of communication in the project. Los contribuyentes a FreeBSD están repartidos por todo el mundo. El correo electrónico (y en menor medida IRC) es el medio de comunicación preferido en el proyecto.
Best Practices for collaborating with the FreeBSD project Mejores Prácticas para colaborar con el proyecto FreeBSD
We now look at a few best practices for making the best use of FreeBSD in product development. A continuación presentamos algunas de las mejores prácticas para hacer el mejor uso de FreeBSD en el desarrollo de productos.
Plan for the long term Planificar a largo plazo
Setup processes that help in tracking the development of FreeBSD. For example: Establecer procesos que ayuden a hacer el seguimiento del desarrollo de FreeBSD. Por ejemplo:
Track FreeBSD source code Seguimiento del código fuente de FreeBSD
The project makes it easy to mirror its SVN repository using <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/articles/committers-guide/article.html#svn-advanced-use-setting-up-svnsync"><application>svnsync</application></link>. Having the complete history of the source is useful when debugging complex problems and offers valuable insight into the intentions of the original developers. Use a capable source control system that allows you to easily merge changes between the upstream FreeBSD code base and your own in-house code. El proyecto facilita la duplicación de su repositorio SVN utilizando <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/articles/committers-guide/article.html#svn-advanced-use-setting-up-svnsync"><application>svnsyncnc</application></link>. Tener el historial completo del código fuente es útil para depurar problemas complejos y ofrece una valiosa perspectiva de las intenciones de los desarrolladores iniciales. Utilice un sistema de control de código fuente capaz que le permita combinar fácilmente los cambios entre la base de código de FreeBSD y su propio código interno.
<xref linkend="fig-svn-blame"/> shows a portion of an annotated listing of the file referenced by the change log in <xref linkend="fig-change-log"/>. The ancestry of each line of the source is clearly visible. Annotated listings showing the history of every file that is part of FreeBSD are <link xlink:href="https://svnweb.freebsd.org/">available on the web</link>. <xref linkend="fig-svn-blame"/> muestra una parte de un listado anotado del archivo referenciado por el registro de cambios en <xref linkend="fig-change-log"/>. La ascendencia de cada línea de la fuente es claramente visible. Los listados anotados que muestran el historial de cada fichero que forma parte de FreeBSD están <link xlink:href="https://svnweb.freebsd.org/">disponibles en la web</link>.
An annotated source listing generated using <command>svn blame</command> Un listado de fuentes anotado generado usando <command>svn blame</command>


#REV #WHO #DATE #TEXT

176410 bde 2008-02-19 07:42:46 -0800 (Tue, 19 Feb 2008) #include &lt;sys/cdefs.h&gt;
176410 bde 2008-02-19 07:42:46 -0800 (Tue, 19 Feb 2008) __FBSDID("$FreeBSD: head/en_US.ISO8859-1/articles/building-products/article.xml 54253 2020-06-14 08:10:06Z carlavilla $");
2116 jkh 1994-08-19 02:40:01 -0700 (Fri, 19 Aug 1994)
2116 jkh 1994-08-19 02:40:01 -0700 (Fri, 19 Aug 1994) /* __ieee754_rem_pio2f(x,y)
8870 rgrimes 1995-05-29 22:51:47 -0700 (Mon, 29 May 1995) *
176552 bde 2008-02-25 05:33:20 -0800 (Mon, 25 Feb 2008) * return the remainder of x rem pi/2 in *y
176552 bde 2008-02-25 05:33:20 -0800 (Mon, 25 Feb 2008) * use double precision for everything except passing x
152535 bde 2005-11-16 18:20:04 -0800 (Wed, 16 Nov 2005) * use __kernel_rem_pio2() for large x
2116 jkh 1994-08-19 02:40:01 -0700 (Fri, 19 Aug 1994) */
2116 jkh 1994-08-19 02:40:01 -0700 (Fri, 19 Aug 1994)
176465 bde 2008-02-22 07:55:14 -0800 (Fri, 22 Feb 2008) #include &lt;float.h&gt;
176465 bde 2008-02-22 07:55:14 -0800 (Fri, 22 Feb 2008)
2116 jkh 1994-08-19 02:40:01 -0700 (Fri, 19 Aug 1994) #include "math.h"



#REV #WHO #DATE #TEXT

176410 bde 2008-02-19 07:42:46 -0800 (Tue, 19 Feb 2008) #include &lt;sys/cdefs.h&gt;
176410 bde 2008-02-19 07:42:46 -0800 (Tue, 19 Feb 2008) __FBSDID("$FreeBSD: head/en_US.ISO8859-1/articles/building-products/article.xml 54253 2020-06-14 08:10:06Z carlavilla $");
2116 jkh 1994-08-19 02:40:01 -0700 (Fri, 19 Aug 1994)
2116 jkh 1994-08-19 02:40:01 -0700 (Fri, 19 Aug 1994) /* __ieee754_rem_pio2f(x,y)
8870 rgrimes 1995-05-29 22:51:47 -0700 (Mon, 29 May 1995) *
176552 bde 2008-02-25 05:33:20 -0800 (Mon, 25 Feb 2008) * return the remainder of x rem pi/2 in *y
176552 bde 2008-02-25 05:33:20 -0800 (Mon, 25 Feb 2008) * use double precision for everything except passing x
152535 bde 2005-11-16 18:20:04 -0800 (Wed, 16 Nov 2005) * use __kernel_rem_pio2() for large x
2116 jkh 1994-08-19 02:40:01 -0700 (Fri, 19 Aug 1994) */
2116 jkh 1994-08-19 02:40:01 -0700 (Fri, 19 Aug 1994)
176465 bde 2008-02-22 07:55:14 -0800 (Fri, 22 Feb 2008) #include &lt;float.h&gt;
176465 bde 2008-02-22 07:55:14 -0800 (Fri, 22 Feb 2008)
2116 jkh 1994-08-19 02:40:01 -0700 (Fri, 19 Aug 1994) #include "math.h"

Use a gatekeeper Usar un controlador de acceso
Appoint a <firstterm>gatekeeper</firstterm> to monitor FreeBSD development, to keep an eye out for changes that could potentially impact your products. Designe un <firstterm>controlador de acceso</firstterm> para monitorizar el desarrollo de FreeBSD, para estar al tanto de los cambios que podrían afectar a sus productos.
Report bugs upstream Informar de errores a los desarrolladores

Loading…

User avatar None

New source string

FreeBSD Doc / articles_building-productsSpanish

New source string a year ago
Browse all component changes

Things to check

Mismatching line breaks

Number of new lines in translation does not match source

Reset

Mismatched full stop

Source and translation do not both end with a full stop

Reset

Trailing space

Source and translation do not both end with a space

Fix string

Reset

Glossary

English Spanish
No related strings found in the glossary.

Source information

Source string comment
(itstool) path: figure/programlisting
Flags
no-wrap
Source string location
article.translate.xml:558
String age
a year ago
Source string age
a year ago
Translation file
articles/es_ES/building-products.po, string 110