El Sunday 07 January 2007 12:42, Javier Fdez. Retenaga escribió: > Del archivo me encargaba yo, pero he estado fuera y no he visto los > mensajes hasta hoy. > > De acuerdo con las correcciones, gracias. He visto que faltaba por > corregir uno de los errores que señalabas (“... de obtenga...” ->“... > de que obtenga ...”), ya que la pregunta aparece dos veces y sólo > estaba corregida la segunda. > > Lo adjunto de nuevo con esa corrección.
Respecto a la traducción, se añadieron en el original tres cosas más: *) link to novalis' essay about the font exception. =========================== -please write to +please see this this <a +href="http://www.fsf.org/blogs/licensing/20050425novalis";>explanatory +essay</a> and write to <a href="mailto:[EMAIL PROTECTED]">[EMAIL PROTECTED]</a>. + <p> To use this exception, add this text to the license notice of each file in the package (to the extent possible), at the end of the text *) Add question NonFreeTools. ================ <li><a href="#FontException" name="TOCFontException">How does the GPL apply to fonts?</a></li> - <li><a href="#WMS" name="TOCWMS">What license should I use for website maintenance system templates?</a></li> + <li><a href="#WMS" name="TOCWMS">What license should I use for + website maintenance system templates?</a></li> + + <li><a href="#NonFreeTools" name="TOCNonFreeTools">Can I release + a program under the GPL which I developed using non-free tools?</a></li> </ul> <h4>Distribution of programs released under the GPL</h4> @@ -2127,6 +2131,22 @@ </dd> +<dt><b><a href="#TOCNonFreeTools" name="NonFreeTools">Can I release + a program under the GPL which I developed using non-free tools?</a></b></dt> + +<dd> +Which programs you used to edit the source code, or to compile it, or +study it, or record it, usually makes no difference for issues +concerning the licensing of that source code. + +<p> +However, if you link non-free libraries with the source code, that +would be an issue you need to deal with. It does not preclude +releasing the source code under the GPL, but if the libraries don't +fit under the "system library" exception, you should affix an explicit +notice giving permission to link your program with them. The FSF can +give you advice on doing this.</p> +</dd> <dt><b><a href="#TOCGPLTranslations" name="GPLTranslations">Are there @@ -2449,7 +2469,7 @@ *) (GPLWrapper): New question. ================= name="TOCGPLInProprietarySystem">I'd like to incorporate GPL-covered software in my proprietary system. Can I do this?</a></li> + <li><a href="#GPLWrapper" name="TOCGPLWrapper">I'd like to + incorporate GPL-covered software in my proprietary system. + Can I do this by putting a "wrapper" module, under a GPL-compatible + lax permissive license (such as the X11 license) in between the + GPL-covered part and the proprietary part?</a></li> + <li><a href="#FSWithNFLibs" name="TOCFSWithNFLibs"> Can I write free software that uses non-free libraries?</a></li> @@ -1647,6 +1653,23 @@ program, side by side, their rights will be clear. </p></dd> +<dt><b><a href="#TOCGCCWrapper" name="GCCWrapper"> I'd like to +incorporate GPL-covered software in my proprietary system. +Can I do this by putting a "wrapper" module, under a GPL-compatible +lax permissive license (such as the X11 license) in between the +GPL-covered part and the proprietary part?</a></b></dt> + +<dd><p>No. The X11 license is compatible with the GPL, so you can add +a module to the GPL-covered program and put it under the X11 license. +But if you were to incorporate them both in a larger program, that +whole would include the GPL-covered part, so it would have to be +licensed <em> as a whole </em> under the GPL GPL.</p> + +<p>The fact that proprietary module A communicates with GPL-covered +module C only through X11-licensed module B is legally irrelevant; +what matters is the fact that module C is included in the whole. +</p></dd> + <dt><b><a href="#TOCLibGCCException" name="LibGCCException"> Does the libstdc++ exception permit dynamic linking?</a></b></dt>
pgpPfEwINAi4i.pgp
Description: PGP signature
_______________________________________________ Lista de correo Web-translators-es [email protected] http://lists.gnu.org/mailman/listinfo/web-translators-es
