www-commits
[Top][All Lists]
Advanced

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

www/philosophy when-free-depends-on-nonfree.html


From: Pavel Kharitonov
Subject: www/philosophy when-free-depends-on-nonfree.html
Date: Sat, 09 Apr 2016 05:28:20 +0000

CVSROOT:        /web/www
Module name:    www
Changes by:     Pavel Kharitonov <ineiev>       16/04/09 05:28:20

Modified files:
        philosophy     : when-free-depends-on-nonfree.html 

Log message:
        Consistently use &mdash; and &{l,r}dquo;, s/non-free/nonfree/, other 
minor fixes.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/when-free-depends-on-nonfree.html?cvsroot=www&r1=1.3&r2=1.4

Patches:
Index: when-free-depends-on-nonfree.html
===================================================================
RCS file: /web/www/www/philosophy/when-free-depends-on-nonfree.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -b -r1.3 -r1.4
--- when-free-depends-on-nonfree.html   8 Apr 2016 21:25:13 -0000       1.3
+++ when-free-depends-on-nonfree.html   9 Apr 2016 05:28:20 -0000       1.4
@@ -1,10 +1,10 @@
 <!--#include virtual="/server/header.html" -->
-<!-- Parent-Version: 1.79 $ -->
+<!-- Parent-Version: 1.79 -->
 
-<title>When Free Software Depends On Non-Free - GNU Project - Free Software 
Foundation</title>
+<title>When Free Software Depends on Nonfree - GNU Project - Free Software 
Foundation</title>
 <!--#include virtual="/server/gnun/initial-translations-list.html" -->
 <!--#include virtual="/server/banner.html" -->
-<h2>When Free Software Depends On Non-Free</h2>
+<h2>When Free Software Depends on Nonfree</h2>
 
  <p>by <strong>Richard Stallman</strong></p>
 
@@ -18,7 +18,7 @@
 upgrading the free program requires using a nonfree program.</p>
 
 <p>If the free program's use depends unavoidably on another program which
-is nonfree, we say that the free program is "trapped". Its code is
+is nonfree, we say that the free program is &ldquo;trapped.&rdquo; Its code is
 free software, and you may be able to copy pieces of its code into
 other free programs with good, ethical results. But you shouldn't
 <em>run</em> the trapped program, because that entails surrendering
@@ -47,7 +47,7 @@
 <p>This kind of dependence is conceptually simple because it stems from
 the situation at one given instant in time. At time T, free program P
 won't run without nonfree programming platform Q. To borrow a term
-from linguistics, this relationship is "synchronic".</p>
+from linguistics, this relationship is &ldquo;synchronic.&rdquo;</p>
 
 <p>More recently, we have seen another kind of dependence in database
 programs, where you can build and run any given version of the program
@@ -62,13 +62,13 @@
 
 <p>If the way you are supposed to do this is by running a proprietary
 database reformat program, or using the developer's service which is
-SaaSS, the database software is trapped &mdash; but in a more subtle
+SaaSS, the database software is trapped&mdash;but in a more subtle
 way. Any single version of the database program can be used without
 nonfree software or SaaSS. The problem arises when you try to keep
 using the program for the long-term, which entails upgrading it from
 time to time; you can't use it this way without some nonfree software
-or equivalent. This database program is trapped across time -- we
-could call it "diachronically trapped," borrowing another term from
+or equivalent. This database program is trapped across time&mdash;we
+could call it &ldquo;diachronically trapped,&rdquo; borrowing another term from
 linguistics.</p>
 
 <p>For example, the program OpenERP, though free, is diachronically
@@ -92,14 +92,14 @@
 intelligence agencies of various countries</a> or security-breaking
 crackers <a
 href="http://stallman.org/articles/on-hacking.html";>(please don't call
-them "hackers")</a>.</p>
+them &ldquo;hackers&rdquo;)</a>.</p>
 
 <p>When a program is diachronically trapped, releasing it from the trap
 requires more than a one-time job of programming. Rather, the job has
 to be done continually, each time there is a change in the data
 format. Launching a project with a long-term commitment to continue
 doing this is not easy. It may be easier to pressure the company to
-stop trying to trap users -- by rejecting the trapped program until it
+stop trying to trap users&mdash;by rejecting the trapped program until it
 does so. Given how difficult it is to free the program, you had
 better stay away from it.</p>
 
@@ -166,7 +166,7 @@
 
 <p class="unprintable">Updated:
 <!-- timestamp start -->
-$Date: 2016/04/08 21:25:13 $
+$Date: 2016/04/09 05:28:20 $
 <!-- timestamp end -->
 </p>
 </div>



reply via email to

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