web-translators-pl
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[gnu-pl] wwwgnudiff - raport nr 167


From: Wojciech Kotwica
Subject: [gnu-pl] wwwgnudiff - raport nr 167
Date: Sat, 04 Oct 2003 05:12:42 +0200

--- prev/root/home.html Thu Oct  2 05:11:55 2003
+++ curr/root/home.html Sat Oct  4 05:12:01 2003
@@ -122,17 +122,13 @@
 
 <p>
-<a href="http://ftp.gnu.org/MISSING-FILES.README";>A statement is available 
regarding the crack of the GNU FTP site</a>.
+For other news, as well as for items that used to be in this GNUs Flashes 
section, see <a href="/server/whatsnew.html">What's New</a> in and about the 
GNU Project.
 </p>
 
-<p>
-<a href="/philosophy/sco/sco.html">FSF has released statements regarding SCO's 
attacks on Free Software</a>.
-</p>
+<h2><a id="Action">Take Action</a></h2>
 
 <p>
-For other news, as well as for items that used to be in this GNUs Flashes 
section, see <a href="/server/whatsnew.html">What's New</a> in and about the 
GNU Project.
+The European Parliament's vote against software patents is not the final 
decision.  We need to keep the pressure up to win a final victory in Europe.  
<a href="http://swpat.ffii.org/group/todo/";>Please join and help</a>.
 </p>
 
-<h2><a id="Action">Take Action</a></h2>
-
 <p>
 <strong>Urgent:</strong> Please visit <a 
href="http://www.digitalspeech.org/";>http://www.digitalspeech.org</a> and help 
resist the media companies' campaign to impose restrictions on what your 
computer can do.
@@ -151,8 +147,4 @@
 
 <p>
-The philosophy and history of the GNU project is featured in <a 
href="http://www.stallman.org/";>Richard M. Stallman</a>'s article <a 
href="/gnu/thegnuproject.html">The GNU Project</a> and in several other texts 
in our <a href="/philosophy/philosophy.html">philosophy</a> section.
-</p>
-
-<p>
 The FSF supports the <a href="/philosophy/basic-freedoms.html">freedoms of 
speech, press, and association</a> on the Internet, <a 
href="http://www.eff.org/privnow/";>the right to use encryption software for 
private communication</a>, and the <a href="/philosophy/protecting.html">right 
to write software</a> unimpeded by private monopolies.
 </p>
@@ -297,5 +289,5 @@
 Updated:
 <!-- timestamp start -->
-$Date: 2003/10/02 00:43:07 $ $Author: rms46 $
+$Date: 2003/10/02 22:39:22 $ $Author: sinuhe $
 <!-- timestamp end -->
 </p>
--- prev/licenses/gpl-faq.html  Wed Oct  1 05:12:10 2003
+++ curr/licenses/gpl-faq.html  Sat Oct  4 05:12:18 2003
@@ -409,7 +409,10 @@
     software in my proprietary system.  Can I do this?</A>
   
-    <LI><A HREF="#WritingFSWithNFLibs" NAME="TOCWritingFSWithNFLibs">I am
-    writing free software that uses non-free libraries.  What legal issues
-    come up if I use the GPL?</A>
+    <LI><A HREF="#FSWithNFLibs" NAME="TOCFSWithNFLibs" Can I write
+    free software that uses non-free libraries?</A>
+
+    <LI><A HREF="#GPLIncompatibleLibs" NAME="TOCGPLIncompatibleLibs"
+    What legal issues come up if I use GPL-incompatible libraries with
+    GPL software?</A>
   
     <LI><A HREF="#WindowsRuntimeAndGPL" NAME="TOCWindowsRuntimeAndGPL">I'm
@@ -418,10 +421,10 @@
     the Visual C++ run-time library permitted under the GPL?</A>
   
-    <LI><A HREF="#MoneyGuzzlerInc" NAME="TOCMoneyGuzzlerInc">I'd like to
-    modify GPL-covered programs and link them with the portability
-    libraries from Money Guzzler Inc.  I cannot distribute the source code
-    for these libraries, so any user who wanted to change these versions
-    would have to obtain those libraries separately.  Why doesn't the GPL 
permit
-    this?</A>
+    <LI><A HREF="#MoneyGuzzlerInc" NAME="TOCMoneyGuzzlerInc">I'd like
+    to modify GPL-covered programs and link them with the portability
+    libraries from Money Guzzler Inc.  I cannot distribute the source
+    code for these libraries, so any user who wanted to change these
+    versions would have to obtain those libraries separately.  Why
+    doesn't the GPL permit this?</A>
   
     <li><a href="#GPLIncompatibleAlone" name="TOCGPLIncompatibleAlone">If
@@ -843,12 +846,44 @@
 <p>
 
-<dt><h4><A HREF="#TOCWritingFSWithNFLibs" NAME="WritingFSWithNFLibs">I am 
writing free software that uses non-free libraries.
-  What legal issues come up if I use the GPL?</A></h4>
+
+<dt><h4><A HREF="#TOCFSWithNFLibs" name="FSWithNFLibs">Can I write
+free software that uses non-free libraries?</A></h4>
 
 <dd>
-If the libraries that you link with fall within the following
-exception in the GPL:
 <p>
-<pre>
+If you do this, your program won't be fully usable in a free
+environment. If your program depends on a non-free library to do a
+certain job, it cannot do that job in the Free World. If it depends on a
+non-free library to run at all, it cannot be part of a free operating
+system such as GNU; it is entirely off limits to the Free World.
+</p><p>
+So please consider: can you find a way to get the job done without using
+this library? Can you write a free replacement for that library?
+</p><p>
+If the program is already written using the non-free library, perhaps it
+is too late to change the decision. You may as well release the program
+as it stands, rather than not release it. But please mention in the
+README that the need for the non-free library is a drawback, and suggest
+the task of changing the program so that it does the same job without
+the non-free library.  Please suggest that anyone who thinks of doing
+substantial further work on the program first free it from dependence
+on the non-free library.
+</p><p>
+Note that there may also be legal issues with combining certain non-free
+libraries with GPL-covered Free Software.  Please see <a
+href="#GPLIncompatibleLibs">the question on GPL software with
+GPL-incompatible libraries</a> for more information.
+</p>
+</dt>
+
+
+<dt><h4><A HREF="#TOCGPLIncompatibleLibs" name="GPLIncompatibleLibs">What
+legal issues come up if I use GPL-incompatible libraries with GPL
+software?</A></h4>
+
+<p>
+If the libraries that you link with fall within the following exception
+in the GPL:
+<blockquote>       
      However, as a special exception, the source code distributed need not
      include anything that is normally distributed (in either source or
@@ -856,35 +891,36 @@
      the operating system on which the executable runs, unless that
      component itself accompanies the executable.
-</pre>
-<p>
-then you don't have to do anything special to use them; the
-requirement to distribute source code for the whole program does not
-include those libraries, even if you distribute a linked executable
-containing them.  Thus, if the libraries you need come with major
-parts of a proprietary operating system, the GPL says people can link
-your program with them without any conditions.
-<p>
+</blockquote>
+</p><p>
+then you don't have to do anything special to use them; the requirement
+to distribute source code for the whole program does not include those
+libraries, even if you distribute a linked executable containing them.
+Thus, if the libraries you need come with major parts of a proprietary
+operating system, the GPL says people can link your program with them
+without any conditions.
+</p><p>       
 If you want your program to link against a library not covered by that
 exception, you need to add your own exception, wholly outside of the
-GPL.  This copyright notice and license notice give permission to link
+GPL. This copyright notice and license notice give permission to link
 with the program FOO:
-<p>
-<pre>
-   Copyright (C) yyyy  &lt;name of copyright holder&gt;
 
+<blockquote>
+<p>       
+   Copyright (C) yyyy  &lt;name of copyright holder&gt;
+</p><p>
     This program is free software; you can redistribute it and/or modify
     it under the terms of the GNU General Public License as published by
     the Free Software Foundation; either version 2 of the License, or
     (at your option) any later version.
-
+</p><p>
     This program is distributed in the hope that it will be useful,
     but WITHOUT ANY WARRANTY; without even the implied warranty of
     MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
     GNU General Public License for more details.
-
+</p><p>
     You should have received a copy of the GNU General Public License
     along with this program; if not, write to the Free Software
     Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
-
+</p><p>
     In addition, as a special exception, &lt;name of copyright
     holder&gt; gives permission to link the code of this program with
@@ -896,44 +932,21 @@
     file, but you are not obligated to do so.  If you do not wish to
     do so, delete this exception statement from your version.
-</pre>
-
-<p>
+</blockquote>
+</p><p>
 Only the copyright holders for the program can legally authorize this
-exception.  If you wrote the whole program yourself, then assuming
-your employer or school does not claim the copyright, you are the
-copyright holder--so you can authorize the exception.  But if you want
-to use parts of other GPL-covered programs by other authors in your
-code, you cannot authorize the exception for them.  You have to get
-the approval of the copyright holders of those programs.
-<p>
-When other people modify the program, they do not have to make the
-same exception for their code--it is their choice whether to do so.
-<p>
-Adding this exception eliminates the legal issue, but does nothing
-about the more serious problem of using a non-free library: your
-program won't be fully usable in a free environment.  If your program
-depends on a non-free library to do a certain job, it cannot do that
-job in the Free World.  If it depends on a non-free library to run at
-all, it cannot be part of a free operating system such as GNU; it is
-entirely off limits to the Free World.
-<p>
-So please consider: can you find a way to get the job done without
-using this library?  Can you write a free replacement for that
-library?
-<p>
-If the program is already written using the non-free library, perhaps
-it is too late to change the decision.  You may as well release the
-program as it stands, rather than not release it.  But please mention
-in the README that the need for the non-free library is a drawback,
-and suggest the task of changing the program so that it does the same
-job without the non-free library.
-<p>
-
-Also please tell us (<A
-HREF="mailto:address@hidden";>&lt;address@hidden&gt;</A>) about the
-non-free library and what job it does.  We could encourage people to
-develop a free library to do the same job.
-
-<p>
+exception. If you wrote the whole program yourself, then assuming your
+employer or school does not claim the copyright, you are the copyright
+holder--so you can authorize the exception. But if you want to use parts
+of other GPL-covered programs by other authors in your code, you cannot
+authorize the exception for them. You have to get the approval of the
+copyright holders of those programs.
+</p><p>
+When other people modify the program, they do not have to make the same
+exception for their code--it is their choice whether to do so.
+</p><p>
+If the libraries you intend to link with are non-free, please also see
+<a href="#FSWithNFLibs">the section on writing Free Software which
+uses non-free libraries</a>.
+</td>
 
 <dt><h4><A HREF="#TOCHowIGetCopyright" NAME="HowIGetCopyright">How do I
@@ -942,5 +955,5 @@
 
 <dd>
-Under the Bern Convention, everything written is automatically
+Under the Berne Convention, everything written is automatically
 copyrighted from whenever it is put in fixed form.  So you don't have
 to do anything to "get" the copyright on what you write--as long as
@@ -2189,5 +2202,5 @@
 Updated:
 <!-- timestamp start -->
-$Date: 2003/09/30 05:13:45 $ $Author: sinuhe $
+$Date: 2003/10/03 23:16:26 $ $Author: novalis $
 <!-- timestamp end -->
 <HR>
--- prev/licenses/license-list.html     Tue Sep 23 05:12:10 2003
+++ curr/licenses/license-list.html     Sat Oct  4 05:12:18 2003
@@ -1112,5 +1112,5 @@
 <DT>The <A HREF="http://squeak.org/license.html";>Squeek license</A>.
 
-<DD>As applied to software, this is not a free softare license because
+<DD>As applied to software, this is not a free software license because
 it requires all users in whatever country to obey US export control
 laws.  As applied to fonts, it also does not permit modification.
@@ -1358,5 +1358,5 @@
 Updated:
 <!-- timestamp start -->
-$Date: 2003/09/22 11:41:03 $ $Author: sinuhe $
+$Date: 2003/10/02 22:16:58 $ $Author: sinuhe $
 <!-- timestamp end -->
 <HR>
--- prev/philosophy/fs-translations.html        Thu Oct  2 05:12:28 2003
+++ curr/philosophy/fs-translations.html        Sat Oct  4 05:12:26 2003
@@ -34,8 +34,7 @@
 -->
 <UL>
-<LI><STRONG>Bu³garski:</STRONG> ñâîáîäåí
-ñîôòóåð (svoboden softuer)
+  <LI><STRONG>Bulgariani:</STRONG> свободен софтуер (svoboden 
softuer)
   <LI><STRONG>Chinese(Simplified):</STRONG> 自由软件 (zi-you ruan-jian)
-         <LI><STRONG>Chinese(Traditional):</STRONG> 自由軟體 (zih-yo
+  <LI><STRONG>Chinese(Traditional):</STRONG> 自由軟體 (zih-yo
   <LI><STRONG>Czech:</STRONG> svobodny software
   <LI><STRONG>Danish:</STRONG> fri software OR frit programmel
--- prev/philosophy/philosophy.html     Thu Oct  2 05:12:30 2003
+++ curr/philosophy/philosophy.html     Sat Oct  4 05:12:26 2003
@@ -186,7 +186,6 @@
 href="/philosophy/boldrin-levine.html">a review of Boldrin and Levine's
 "The case against intellectual property."</a>
-<li><a href="/philosophy/sco/sco-gnu-linux.html">SCO, GNU, and Linux</a>, by
-Richard Stallman, discusses how SCO's lawsuit against IBM pertains to the
-work of the GNU project.
+<li><a href="/philosophy/sco/sco-gnu-linux.html">SCO, GNU, and Linux</a>, by 
Richard Stallman, discusses how SCO's lawsuit against IBM pertains to the work 
of the GNU project.  Please see the <a href="/philosophy/sco/sco.html">FSF SCO 
Response Page</a>
+for more details on this subject.
 <li><a href="/philosophy/guardian-article.html">That's fighting talk</a> a 
slightly modified version of the article, originally published in<a 
href="http://www.guardian.co.uk";>The Guardian</a> of London by <a 
href="http://www.stallman.org";>Richard Stallman</a> and Nick Hill. 
 <li><a href="/philosophy/ebooks.html">Ebooks: Freedom Or Copyright</a> a 
slightly modified version of the article, originally published in Technology 
Review in 2000, by <a href="http://www.stallman.org";>Richard Stallman</a>
@@ -808,5 +807,5 @@
 Updated:
 <!-- timestamp start -->
-$Date: 2003/10/01 17:30:16 $ $Author: sinuhe $
+$Date: 2003/10/02 22:39:22 $ $Author: sinuhe $
 <!-- timestamp end -->
 <HR>




reply via email to

[Prev in Thread] Current Thread [Next in Thread]