Date: Sat, 31 May 2008 13:10:32 GMT From: Gabor Kovesdan <gabor@FreeBSD.org> To: Perforce Change Reviews <perforce@freebsd.org> Subject: PERFORCE change 142624 for review Message-ID: <200805311310.m4VDAW8q006899@repoman.freebsd.org>
next in thread | raw e-mail | index | archive | help
http://perforce.freebsd.org/chv.cgi?CH=142624 Change 142624 by gabor@gabor_server on 2008/05/31 13:09:41 - Translate some paragraphs Affected files ... .. //depot/projects/docproj_es/src/release/doc/es_ES.ISO8859-1/readme/article.sgml#5 edit Differences ... ==== //depot/projects/docproj_es/src/release/doc/es_ES.ISO8859-1/readme/article.sgml#5 (text+ko) ==== @@ -94,27 +94,28 @@ </sect2> <sect2> - <title>Target Audience</title> + <title>Audiencia destinada</title> <![ %release.type.current; [ - <para>This &release.type; is aimed primarily at early adopters - and various other users who want to get involved with the - ongoing development of &os;. While the &os; development team - tries its best to ensure that each &release.type; works as - advertised, &release.branch; is very much a - work-in-progress.</para> + <para>La &release.type; es primeramente para los que quieran + beneficiarse de las funciones nuevas cuanto antes o los que + quieran echar un mano al proceso del desarrollo de &os;. Aunque + el equipo del desarrollo de &os; invierte todos sus esfuerzos + para hacer cada &release.type; funcionar como se supone, + &release.branch; es primeramente una versión en curso.</para> - <para>The basic requirements for using this &release.type; are - technical proficiency with &os; and an understanding of the - ongoing development process of &os; &release.branch; (as - discussed on the &a.current;).</para> + <para>Los requisitos de usar esta &release.type; son un buen nivel + de conocimientos técnicos con &os; y una comprensión + del proceso de del desarrollo de &os; &release.branch; + (como se ha aclarado en la lista &a.current;).</para> - <para>For those more interested in doing business with &os; than - in experimenting with new &os; technology, formal releases - (such as &release.prev.stable;) are frequently more appropriate. - Releases undergo a period of testing and quality assurance - checking to ensure high reliability and dependability.</para> + <para>Para los que estén más interesados en hacer + comercio con &os; que experimentar con las nuevas tecnologías + en &os;, las releases oficiales (como p.ej. &release.prev.stable;) + son más adecuadas. Cada release pasa un proceso de + prueba y aseguración de calidad para asegurar el alta + fiabilidad.</para> ]]>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200805311310.m4VDAW8q006899>