www-commits
[Top][All Lists]
Advanced

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

www/philosophy microsoft-antitrust.ko.html micr...


From: GNUN
Subject: www/philosophy microsoft-antitrust.ko.html micr...
Date: Fri, 21 Mar 2014 09:28:47 +0000

CVSROOT:        /web/www
Module name:    www
Changes by:     GNUN <gnun>     14/03/21 09:28:47

Modified files:
        philosophy     : microsoft-antitrust.ko.html 
                         microsoft-antitrust.nl.html 
                         privacyaction.nl.html 
                         push-copyright-aside.nl.html 
Added files:
        philosophy/po  : microsoft-antitrust.ko-diff.html 
                         microsoft-antitrust.nl-diff.html 
                         privacyaction.nl-diff.html 
                         push-copyright-aside.nl-diff.html 

Log message:
        Automatic update by GNUnited Nations.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/microsoft-antitrust.ko.html?cvsroot=www&r1=1.24&r2=1.25
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/microsoft-antitrust.nl.html?cvsroot=www&r1=1.12&r2=1.13
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/privacyaction.nl.html?cvsroot=www&r1=1.10&r2=1.11
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/push-copyright-aside.nl.html?cvsroot=www&r1=1.11&r2=1.12
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/microsoft-antitrust.ko-diff.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/microsoft-antitrust.nl-diff.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/privacyaction.nl-diff.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/push-copyright-aside.nl-diff.html?cvsroot=www&rev=1.1

Patches:
Index: microsoft-antitrust.ko.html
===================================================================
RCS file: /web/www/www/philosophy/microsoft-antitrust.ko.html,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -b -r1.24 -r1.25
--- microsoft-antitrust.ko.html 31 Aug 2013 20:12:13 -0000      1.24
+++ microsoft-antitrust.ko.html 21 Mar 2014 09:28:45 -0000      1.25
@@ -9,6 +9,13 @@
 
 <!--#include virtual="/philosophy/po/microsoft-antitrust.translist" -->
 <!--#include virtual="/server/banner.ko.html" -->
+<!--#set var="PO_FILE"
+ value='<a href="http://www.gnu.org/philosophy/po/microsoft-antitrust.ko.po";>
+ http://www.gnu.org/philosophy/po/microsoft-antitrust.ko.po</a>' -->
+ <!--#set var="ORIGINAL_FILE" value="/philosophy/microsoft-antitrust.html" -->
+ <!--#set var="DIFF_FILE" 
value="/philosophy/po/microsoft-antitrust.ko-diff.html" -->
+ <!--#set var="OUTDATED_SINCE" value="2014-01-20" -->
+ <!--#include virtual="/server/outdated.ko.html" -->
 <h2>마이크로소프트 반독점 재판과 자유소프트웨어</h2>
 
 <p>
@@ -129,7 +136,7 @@
  <p><!-- timestamp start -->
 최종 수정일:
 
-$Date: 2013/08/31 20:12:13 $
+$Date: 2014/03/21 09:28:45 $
 
 <!-- timestamp end -->
 </p>

Index: microsoft-antitrust.nl.html
===================================================================
RCS file: /web/www/www/philosophy/microsoft-antitrust.nl.html,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -b -r1.12 -r1.13
--- microsoft-antitrust.nl.html 31 Aug 2013 20:12:13 -0000      1.12
+++ microsoft-antitrust.nl.html 21 Mar 2014 09:28:46 -0000      1.13
@@ -10,6 +10,13 @@
 
 <!--#include virtual="/philosophy/po/microsoft-antitrust.translist" -->
 <!--#include virtual="/server/banner.nl.html" -->
+<!--#set var="PO_FILE"
+ value='<a href="http://www.gnu.org/philosophy/po/microsoft-antitrust.nl.po";>
+ http://www.gnu.org/philosophy/po/microsoft-antitrust.nl.po</a>' -->
+ <!--#set var="ORIGINAL_FILE" value="/philosophy/microsoft-antitrust.html" -->
+ <!--#set var="DIFF_FILE" 
value="/philosophy/po/microsoft-antitrust.nl-diff.html" -->
+ <!--#set var="OUTDATED_SINCE" value="2014-01-20" -->
+ <!--#include virtual="/server/outdated.nl.html" -->
 <h2>Het Microsoft Mededingingsproces en Vrije Software</h2>
 
 <p>
@@ -159,7 +166,7 @@
  <p><!-- timestamp start -->
 Bijgewerkt:
 
-$Date: 2013/08/31 20:12:13 $
+$Date: 2014/03/21 09:28:46 $
 
 <!-- timestamp end -->
 </p>

Index: privacyaction.nl.html
===================================================================
RCS file: /web/www/www/philosophy/privacyaction.nl.html,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -b -r1.10 -r1.11
--- privacyaction.nl.html       31 Aug 2013 20:12:31 -0000      1.10
+++ privacyaction.nl.html       21 Mar 2014 09:28:46 -0000      1.11
@@ -8,6 +8,13 @@
 
 <!--#include virtual="/philosophy/po/privacyaction.translist" -->
 <!--#include virtual="/server/banner.nl.html" -->
+<!--#set var="PO_FILE"
+ value='<a href="http://www.gnu.org/philosophy/po/privacyaction.nl.po";>
+ http://www.gnu.org/philosophy/po/privacyaction.nl.po</a>' -->
+ <!--#set var="ORIGINAL_FILE" value="/philosophy/privacyaction.html" -->
+ <!--#set var="DIFF_FILE" value="/philosophy/po/privacyaction.nl-diff.html" -->
+ <!--#set var="OUTDATED_SINCE" value="2014-01-20" -->
+ <!--#include virtual="/server/outdated.nl.html" -->
 <h2>Bescherm Priv&eacute;post</h2>
 
 <p>
@@ -124,7 +131,7 @@
  <p><!-- timestamp start -->
 Bijgewerkt:
 
-$Date: 2013/08/31 20:12:31 $
+$Date: 2014/03/21 09:28:46 $
 
 <!-- timestamp end -->
 </p>

Index: push-copyright-aside.nl.html
===================================================================
RCS file: /web/www/www/philosophy/push-copyright-aside.nl.html,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- push-copyright-aside.nl.html        31 Aug 2013 20:12:33 -0000      1.11
+++ push-copyright-aside.nl.html        21 Mar 2014 09:28:46 -0000      1.12
@@ -9,6 +9,13 @@
 
 <!--#include virtual="/philosophy/po/push-copyright-aside.translist" -->
 <!--#include virtual="/server/banner.nl.html" -->
+<!--#set var="PO_FILE"
+ value='<a href="http://www.gnu.org/philosophy/po/push-copyright-aside.nl.po";>
+ http://www.gnu.org/philosophy/po/push-copyright-aside.nl.po</a>' -->
+ <!--#set var="ORIGINAL_FILE" value="/philosophy/push-copyright-aside.html" -->
+ <!--#set var="DIFF_FILE" 
value="/philosophy/po/push-copyright-aside.nl-diff.html" -->
+ <!--#set var="OUTDATED_SINCE" value="2014-01-20" -->
+ <!--#include virtual="/server/outdated.nl.html" -->
 <h2>De Wetenschap Moet Het Auteursrecht Terzijde Schuiven</h2>
 
 <p>door <strong>Richard M. Stallman</strong></p>
@@ -180,7 +187,7 @@
  <p><!-- timestamp start -->
 Bijgewerkt:
 
-$Date: 2013/08/31 20:12:33 $
+$Date: 2014/03/21 09:28:46 $
 
 <!-- timestamp end -->
 </p>

Index: po/microsoft-antitrust.ko-diff.html
===================================================================
RCS file: po/microsoft-antitrust.ko-diff.html
diff -N po/microsoft-antitrust.ko-diff.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ po/microsoft-antitrust.ko-diff.html 21 Mar 2014 09:28:46 -0000      1.1
@@ -0,0 +1,213 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
+<!-- Generated by GNUN -->
+<html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en" lang="en">
+<head>
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<title>/philosophy/microsoft-antitrust.html-diff</title>
+<style type="text/css">
+span.removed { background-color: #f22; color: #000; }
+span.inserted { background-color: #2f2; color: #000; }
+</style></head>
+<body><pre>
+&lt;!--#include virtual="/server/header.html" --&gt;
+<span class="inserted"><ins><em>&lt;!-- Parent-Version: 1.76 
--&gt;</em></ins></span>
+&lt;title&gt;The Microsoft Antitrust Trial and Free Software
+- GNU Project - Free Software <span class="removed"><del><strong>Foundation 
(FSF)&lt;/title&gt;</strong></del></span> <span 
class="inserted"><ins><em>Foundation&lt;/title&gt;</em></ins></span>
+&lt;!--#include virtual="/philosophy/po/microsoft-antitrust.translist" --&gt;
+&lt;!--#include virtual="/server/banner.html" --&gt;
+&lt;h2&gt;The Microsoft Antitrust Trial and Free Software&lt;/h2&gt;
+
+&lt;p&gt;
+With the Microsoft antitrust trial moving toward a conclusion, the
+question of what to demand of Microsoft if it loses is coming to the
+fore.  Ralph Nader is even [when this was written, in March 1999]
+organizing a conference about the question (see
+&lt;a 
href="http://www.appraising-microsoft.org/"&gt;http://www.appraising-microsoft.org/&lt;/a&gt;).&lt;/p&gt;
+&lt;p&gt;
+The obvious answers&mdash;to restrict contracts between Microsoft and
+computer manufacturers, or to break up the company&mdash;will not make
+a crucial difference.  The former might encourage the availability of
+computers with the GNU/Linux system preinstalled, but that is
+happening anyway.  The latter would mainly help other proprietary
+application developers compete, which would only offer users
+alternative ways to let go of their freedom.&lt;/p&gt;
+&lt;p&gt;
+So I propose three remedies that would help enable
+&lt;a href="/philosophy/free-sw.html"&gt;free software&lt;/a&gt; operating 
systems
+such as GNU/Linux compete technically while respecting users' freedom.
+These three remedies directly address the three biggest obstacles to
+development of free operating systems, and to giving them the
+capability of running programs written for Windows.  They also
+directly address the methods Microsoft has said (in the
+&ldquo;Halloween documents&rdquo;) it will use to obstruct free
+software.  It would be most effective to use all three of these
+remedies together.&lt;/p&gt;
+
+&lt;ol&gt;
+  &lt;li&gt;Require Microsoft to publish complete documentation of all
+   interfaces between software components, all communications
+   protocols, and all file formats.  This would block one of
+   Microsoft's favorite tactics: secret and incompatible interfaces.
+&lt;p&gt;
+   To make this requirement really stick, Microsoft should not be
+   allowed to use a nondisclosure agreement with some other
+   organization to excuse implementing a secret interface.  The rule
+   must be: if they cannot publish the interface, they cannot release
+   an implementation of it.&lt;/p&gt;
+&lt;p&gt;
+   It would, however, be acceptable to permit Microsoft to begin
+   implementation of an interface before the publication of the
+   interface specifications, provided that they release the
+   specifications simultaneously with the implementation.&lt;/p&gt;
+&lt;p&gt;
+   Enforcement of this requirement would not be difficult.  If other
+   software developers complain that the published documentation fails
+   to describe some aspect of the interface, or how to do a certain
+   job, the court would direct Microsoft to answer questions about it.
+   Any questions about interfaces (as distinguished from
+   implementation techniques) would have to be answered.&lt;/p&gt;
+&lt;p&gt;
+   Similar terms were included in an agreement between IBM and the
+   European Community in 1984, settling another antitrust dispute.
+   See &lt;a href="http://www.cptech.org/at/ibm/ibm1984ec.html"&gt;
+       http://www.cptech.org/at/ibm/ibm1984ec.html&lt;/a&gt;.&lt;/p&gt;
+&lt;/li&gt;
+&lt;li&gt;Require Microsoft to use its patents for defense only, in the field
+   of software.  (If they happen to own patents that apply to other
+   fields, those other fields could be included in this requirement,
+   or they could be exempt.)  This would block the other tactic
+   Microsoft mentioned in the Halloween documents: using patents to
+   block development of free software.
+&lt;p&gt;
+   We should give Microsoft the option of using either self-defense or
+   mutual defense.  Self defense means offering to cross-license all
+   patents at no charge with anyone who wishes to do so.  Mutual
+   defense means licensing all patents to a pool which anyone can
+   join&mdash;even people who have no patents of their own.  The pool
+   would license all members' patents to all members.&lt;/p&gt;
+&lt;p&gt;
+   It is crucial to address the issue of patents, because it does no
+   good to have Microsoft publish an interface, if they have managed
+   to work some patented wrinkle into it (or into the functionality it
+   gives access to), such that the rest of us are not allowed to
+   implement it.&lt;/p&gt;
+&lt;/li&gt;
+&lt;li&gt;Require Microsoft not to certify any hardware as working with
+   Microsoft software, unless the hardware's complete specifications
+   have been published, so that any programmer can implement software
+   to support the same hardware.
+&lt;p&gt;
+   Secret hardware specifications are not in general Microsoft's
+   doing, but they are a significant obstacle for the development of
+   the free operating systems that can provide competition for
+   Windows.  To remove this obstacle would be a great help.  If a
+   settlement is negotiated with Microsoft, including this sort of
+   provision in it is not impossible&mdash;it would be a matter of
+   negotiation.&lt;/p&gt;
+&lt;/li&gt;
+&lt;/ol&gt;
+&lt;p&gt;
+This April, Microsoft's Ballmer announced a possible plan to release
+source code for some part of Windows.  It is not clear whether that
+would imply making it free software, or which part of Windows it might
+be.  But if Microsoft does make some important part of Windows free
+software, it could solve these problems as regards that part.  (It
+could also be a contribution to the free software community, if the
+software in question could be useful for purposes other than running
+other proprietary Microsoft software.)&lt;/p&gt;
+&lt;p&gt;
+However, having the use as free software of a part of Windows is less
+crucial than being &lt;em&gt;permitted&lt;/em&gt; to implement all parts.  The 
remedies
+proposed above are what we really need.  They will clear the way for
+us to develop a truly superior alternative to Microsoft Windows,
+in whatever area Microsoft does not make Windows free software.&lt;/p&gt;
+
+<span class="removed"><del><strong>&lt;/div&gt;</strong></del></span>
+
+<span class="inserted"><ins><em>&lt;/div&gt;&lt;!-- for id="content", starts 
in the include above --&gt;</em></ins></span>
+&lt;!--#include virtual="/server/footer.html" --&gt;
+&lt;div id="footer"&gt;
+<span class="removed"><del><strong>&lt;p&gt;
+Please</strong></del></span>
+<span class="inserted"><ins><em>&lt;div class="unprintable"&gt;
+
+&lt;p&gt;Please</em></ins></span> send <span 
class="inserted"><ins><em>general</em></ins></span> FSF &amp; GNU inquiries to
+&lt;a <span 
class="removed"><del><strong>href="mailto:address@hidden"&gt;&lt;em&gt;address@hidden&lt;/em&gt;&lt;/a&gt;.</strong></del></span>
 <span 
class="inserted"><ins><em>href="mailto:address@hidden"&gt;&lt;address@hidden&gt;&lt;/a&gt;.</em></ins></span>
+There are also &lt;a href="/contact/"&gt;other ways to contact&lt;/a&gt;
+the FSF.
+<span class="removed"><del><strong>&lt;br /&gt;
+Please send broken</strong></del></span>  <span 
class="inserted"><ins><em>Broken</em></ins></span> links and other corrections 
or suggestions <span class="inserted"><ins><em>can be sent</em></ins></span>
+to &lt;a <span 
class="removed"><del><strong>href="mailto:address@hidden"&gt;&lt;em&gt;address@hidden&lt;/em&gt;&lt;/a&gt;.
+&lt;/p&gt;
+
+&lt;p&gt;</strong></del></span> <span 
class="inserted"><ins><em>href="mailto:address@hidden"&gt;&lt;address@hidden&gt;&lt;/a&gt;.&lt;/p&gt;
+
+&lt;p&gt;&lt;!-- TRANSLATORS: Ignore the original text in this paragraph,
+        replace it with the translation of these two:
+
+        We work hard and do our best to provide accurate, good quality
+        translations.  However, we are not exempt from imperfection.
+        Please send your comments and general suggestions in this regard
+        to &lt;a href="mailto:address@hidden"&gt;
+        &lt;address@hidden&gt;&lt;/a&gt;.&lt;/p&gt;
+
+        &lt;p&gt;For information on coordinating and submitting translations of
+        our web pages, see &lt;a
+        href="/server/standards/README.translations.html"&gt;Translations
+        README&lt;/a&gt;. --&gt;</em></ins></span>
+Please see the &lt;a
+href="/server/standards/README.translations.html"&gt;Translations
+README&lt;/a&gt; for information on coordinating and submitting translations
+of this <span class="removed"><del><strong>article.
+&lt;/p&gt;
+
+&lt;p&gt;
+Copyright</strong></del></span> <span 
class="inserted"><ins><em>article.&lt;/p&gt;
+&lt;/div&gt;
+
+&lt;!-- Regarding copyright, in general, standalone pages (as opposed to
+     files generated as part of manuals) on the GNU web server should
+     be under CC BY-ND 3.0 US.  Please do NOT change or remove this
+     without talking with the webmasters or licensing team first.
+     Please make sure the copyright date is consistent with the
+     document.  For web pages, it is ok to list just the latest year the
+     document was modified, or published.
+     
+     If you wish to list earlier years, that is ok too.
+     Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
+     years, as long as each year in the range is in fact a copyrightable
+     year, i.e., a year in which the document was published (including
+     being publicly visible on the web or in a revision control system).
+     
+     There is more detail about copyright years in the GNU Maintainers
+     Information document, www.gnu.org/prep/maintain. --&gt;
+
+&lt;p&gt;Copyright</em></ins></span> &copy; 1999, 2007, 2008 Free Software 
Foundation, <span class="removed"><del><strong>Inc.,
+&lt;/p&gt;
+&lt;address&gt;51 Franklin St, Fifth Floor, Boston, MA 02110, 
USA&lt;/address&gt;</strong></del></span> <span 
class="inserted"><ins><em>Inc.&lt;/p&gt;</em></ins></span>
+
+&lt;p&gt;This page is licensed under a &lt;a rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/"&gt;Creative
+Commons Attribution-NoDerivs 3.0 United States <span 
class="removed"><del><strong>License&lt;/a&gt;.
+&lt;/p&gt;</strong></del></span> <span 
class="inserted"><ins><em>License&lt;/a&gt;.&lt;/p&gt;</em></ins></span>
+
+&lt;!--#include virtual="/server/bottom-notes.html" --&gt;
+
+<span class="removed"><del><strong>&lt;p&gt;Updated:</strong></del></span>
+
+<span class="inserted"><ins><em>&lt;p&gt;&lt;/p&gt;&lt;p 
class="unprintable"&gt;Updated:</em></ins></span>
+&lt;!-- timestamp start --&gt;
+$Date: 2014/03/21 09:28:46 $
+&lt;!-- timestamp end --&gt;
+&lt;/p&gt;
+&lt;/div&gt;
+<span class="removed"><del><strong>&lt;!-- All pages on the GNU web server 
should have the section about    --&gt;
+&lt;!-- verbatim copying.  Please do NOT remove this without talking     --&gt;
+&lt;!-- with the webmasters first. --&gt; 
+&lt;!-- Please make sure the copyright date is consistent with the document 
--&gt;
+&lt;!-- and that it is like this "2001, 2002" not this "2001-2002." 
--&gt;</strong></del></span>
+&lt;/div&gt;
+&lt;/body&gt;
+&lt;/html&gt;
+</pre></body></html>

Index: po/microsoft-antitrust.nl-diff.html
===================================================================
RCS file: po/microsoft-antitrust.nl-diff.html
diff -N po/microsoft-antitrust.nl-diff.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ po/microsoft-antitrust.nl-diff.html 21 Mar 2014 09:28:46 -0000      1.1
@@ -0,0 +1,213 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
+<!-- Generated by GNUN -->
+<html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en" lang="en">
+<head>
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<title>/philosophy/microsoft-antitrust.html-diff</title>
+<style type="text/css">
+span.removed { background-color: #f22; color: #000; }
+span.inserted { background-color: #2f2; color: #000; }
+</style></head>
+<body><pre>
+&lt;!--#include virtual="/server/header.html" --&gt;
+<span class="inserted"><ins><em>&lt;!-- Parent-Version: 1.76 
--&gt;</em></ins></span>
+&lt;title&gt;The Microsoft Antitrust Trial and Free Software
+- GNU Project - Free Software <span class="removed"><del><strong>Foundation 
(FSF)&lt;/title&gt;</strong></del></span> <span 
class="inserted"><ins><em>Foundation&lt;/title&gt;</em></ins></span>
+&lt;!--#include virtual="/philosophy/po/microsoft-antitrust.translist" --&gt;
+&lt;!--#include virtual="/server/banner.html" --&gt;
+&lt;h2&gt;The Microsoft Antitrust Trial and Free Software&lt;/h2&gt;
+
+&lt;p&gt;
+With the Microsoft antitrust trial moving toward a conclusion, the
+question of what to demand of Microsoft if it loses is coming to the
+fore.  Ralph Nader is even [when this was written, in March 1999]
+organizing a conference about the question (see
+&lt;a 
href="http://www.appraising-microsoft.org/"&gt;http://www.appraising-microsoft.org/&lt;/a&gt;).&lt;/p&gt;
+&lt;p&gt;
+The obvious answers&mdash;to restrict contracts between Microsoft and
+computer manufacturers, or to break up the company&mdash;will not make
+a crucial difference.  The former might encourage the availability of
+computers with the GNU/Linux system preinstalled, but that is
+happening anyway.  The latter would mainly help other proprietary
+application developers compete, which would only offer users
+alternative ways to let go of their freedom.&lt;/p&gt;
+&lt;p&gt;
+So I propose three remedies that would help enable
+&lt;a href="/philosophy/free-sw.html"&gt;free software&lt;/a&gt; operating 
systems
+such as GNU/Linux compete technically while respecting users' freedom.
+These three remedies directly address the three biggest obstacles to
+development of free operating systems, and to giving them the
+capability of running programs written for Windows.  They also
+directly address the methods Microsoft has said (in the
+&ldquo;Halloween documents&rdquo;) it will use to obstruct free
+software.  It would be most effective to use all three of these
+remedies together.&lt;/p&gt;
+
+&lt;ol&gt;
+  &lt;li&gt;Require Microsoft to publish complete documentation of all
+   interfaces between software components, all communications
+   protocols, and all file formats.  This would block one of
+   Microsoft's favorite tactics: secret and incompatible interfaces.
+&lt;p&gt;
+   To make this requirement really stick, Microsoft should not be
+   allowed to use a nondisclosure agreement with some other
+   organization to excuse implementing a secret interface.  The rule
+   must be: if they cannot publish the interface, they cannot release
+   an implementation of it.&lt;/p&gt;
+&lt;p&gt;
+   It would, however, be acceptable to permit Microsoft to begin
+   implementation of an interface before the publication of the
+   interface specifications, provided that they release the
+   specifications simultaneously with the implementation.&lt;/p&gt;
+&lt;p&gt;
+   Enforcement of this requirement would not be difficult.  If other
+   software developers complain that the published documentation fails
+   to describe some aspect of the interface, or how to do a certain
+   job, the court would direct Microsoft to answer questions about it.
+   Any questions about interfaces (as distinguished from
+   implementation techniques) would have to be answered.&lt;/p&gt;
+&lt;p&gt;
+   Similar terms were included in an agreement between IBM and the
+   European Community in 1984, settling another antitrust dispute.
+   See &lt;a href="http://www.cptech.org/at/ibm/ibm1984ec.html"&gt;
+       http://www.cptech.org/at/ibm/ibm1984ec.html&lt;/a&gt;.&lt;/p&gt;
+&lt;/li&gt;
+&lt;li&gt;Require Microsoft to use its patents for defense only, in the field
+   of software.  (If they happen to own patents that apply to other
+   fields, those other fields could be included in this requirement,
+   or they could be exempt.)  This would block the other tactic
+   Microsoft mentioned in the Halloween documents: using patents to
+   block development of free software.
+&lt;p&gt;
+   We should give Microsoft the option of using either self-defense or
+   mutual defense.  Self defense means offering to cross-license all
+   patents at no charge with anyone who wishes to do so.  Mutual
+   defense means licensing all patents to a pool which anyone can
+   join&mdash;even people who have no patents of their own.  The pool
+   would license all members' patents to all members.&lt;/p&gt;
+&lt;p&gt;
+   It is crucial to address the issue of patents, because it does no
+   good to have Microsoft publish an interface, if they have managed
+   to work some patented wrinkle into it (or into the functionality it
+   gives access to), such that the rest of us are not allowed to
+   implement it.&lt;/p&gt;
+&lt;/li&gt;
+&lt;li&gt;Require Microsoft not to certify any hardware as working with
+   Microsoft software, unless the hardware's complete specifications
+   have been published, so that any programmer can implement software
+   to support the same hardware.
+&lt;p&gt;
+   Secret hardware specifications are not in general Microsoft's
+   doing, but they are a significant obstacle for the development of
+   the free operating systems that can provide competition for
+   Windows.  To remove this obstacle would be a great help.  If a
+   settlement is negotiated with Microsoft, including this sort of
+   provision in it is not impossible&mdash;it would be a matter of
+   negotiation.&lt;/p&gt;
+&lt;/li&gt;
+&lt;/ol&gt;
+&lt;p&gt;
+This April, Microsoft's Ballmer announced a possible plan to release
+source code for some part of Windows.  It is not clear whether that
+would imply making it free software, or which part of Windows it might
+be.  But if Microsoft does make some important part of Windows free
+software, it could solve these problems as regards that part.  (It
+could also be a contribution to the free software community, if the
+software in question could be useful for purposes other than running
+other proprietary Microsoft software.)&lt;/p&gt;
+&lt;p&gt;
+However, having the use as free software of a part of Windows is less
+crucial than being &lt;em&gt;permitted&lt;/em&gt; to implement all parts.  The 
remedies
+proposed above are what we really need.  They will clear the way for
+us to develop a truly superior alternative to Microsoft Windows,
+in whatever area Microsoft does not make Windows free software.&lt;/p&gt;
+
+<span class="removed"><del><strong>&lt;/div&gt;</strong></del></span>
+
+<span class="inserted"><ins><em>&lt;/div&gt;&lt;!-- for id="content", starts 
in the include above --&gt;</em></ins></span>
+&lt;!--#include virtual="/server/footer.html" --&gt;
+&lt;div id="footer"&gt;
+<span class="removed"><del><strong>&lt;p&gt;
+Please</strong></del></span>
+<span class="inserted"><ins><em>&lt;div class="unprintable"&gt;
+
+&lt;p&gt;Please</em></ins></span> send <span 
class="inserted"><ins><em>general</em></ins></span> FSF &amp; GNU inquiries to
+&lt;a <span 
class="removed"><del><strong>href="mailto:address@hidden"&gt;&lt;em&gt;address@hidden&lt;/em&gt;&lt;/a&gt;.</strong></del></span>
 <span 
class="inserted"><ins><em>href="mailto:address@hidden"&gt;&lt;address@hidden&gt;&lt;/a&gt;.</em></ins></span>
+There are also &lt;a href="/contact/"&gt;other ways to contact&lt;/a&gt;
+the FSF.
+<span class="removed"><del><strong>&lt;br /&gt;
+Please send broken</strong></del></span>  <span 
class="inserted"><ins><em>Broken</em></ins></span> links and other corrections 
or suggestions <span class="inserted"><ins><em>can be sent</em></ins></span>
+to &lt;a <span 
class="removed"><del><strong>href="mailto:address@hidden"&gt;&lt;em&gt;address@hidden&lt;/em&gt;&lt;/a&gt;.
+&lt;/p&gt;
+
+&lt;p&gt;</strong></del></span> <span 
class="inserted"><ins><em>href="mailto:address@hidden"&gt;&lt;address@hidden&gt;&lt;/a&gt;.&lt;/p&gt;
+
+&lt;p&gt;&lt;!-- TRANSLATORS: Ignore the original text in this paragraph,
+        replace it with the translation of these two:
+
+        We work hard and do our best to provide accurate, good quality
+        translations.  However, we are not exempt from imperfection.
+        Please send your comments and general suggestions in this regard
+        to &lt;a href="mailto:address@hidden"&gt;
+        &lt;address@hidden&gt;&lt;/a&gt;.&lt;/p&gt;
+
+        &lt;p&gt;For information on coordinating and submitting translations of
+        our web pages, see &lt;a
+        href="/server/standards/README.translations.html"&gt;Translations
+        README&lt;/a&gt;. --&gt;</em></ins></span>
+Please see the &lt;a
+href="/server/standards/README.translations.html"&gt;Translations
+README&lt;/a&gt; for information on coordinating and submitting translations
+of this <span class="removed"><del><strong>article.
+&lt;/p&gt;
+
+&lt;p&gt;
+Copyright</strong></del></span> <span 
class="inserted"><ins><em>article.&lt;/p&gt;
+&lt;/div&gt;
+
+&lt;!-- Regarding copyright, in general, standalone pages (as opposed to
+     files generated as part of manuals) on the GNU web server should
+     be under CC BY-ND 3.0 US.  Please do NOT change or remove this
+     without talking with the webmasters or licensing team first.
+     Please make sure the copyright date is consistent with the
+     document.  For web pages, it is ok to list just the latest year the
+     document was modified, or published.
+     
+     If you wish to list earlier years, that is ok too.
+     Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
+     years, as long as each year in the range is in fact a copyrightable
+     year, i.e., a year in which the document was published (including
+     being publicly visible on the web or in a revision control system).
+     
+     There is more detail about copyright years in the GNU Maintainers
+     Information document, www.gnu.org/prep/maintain. --&gt;
+
+&lt;p&gt;Copyright</em></ins></span> &copy; 1999, 2007, 2008 Free Software 
Foundation, <span class="removed"><del><strong>Inc.,
+&lt;/p&gt;
+&lt;address&gt;51 Franklin St, Fifth Floor, Boston, MA 02110, 
USA&lt;/address&gt;</strong></del></span> <span 
class="inserted"><ins><em>Inc.&lt;/p&gt;</em></ins></span>
+
+&lt;p&gt;This page is licensed under a &lt;a rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/"&gt;Creative
+Commons Attribution-NoDerivs 3.0 United States <span 
class="removed"><del><strong>License&lt;/a&gt;.
+&lt;/p&gt;</strong></del></span> <span 
class="inserted"><ins><em>License&lt;/a&gt;.&lt;/p&gt;</em></ins></span>
+
+&lt;!--#include virtual="/server/bottom-notes.html" --&gt;
+
+<span class="removed"><del><strong>&lt;p&gt;Updated:</strong></del></span>
+
+<span class="inserted"><ins><em>&lt;p&gt;&lt;/p&gt;&lt;p 
class="unprintable"&gt;Updated:</em></ins></span>
+&lt;!-- timestamp start --&gt;
+$Date: 2014/03/21 09:28:46 $
+&lt;!-- timestamp end --&gt;
+&lt;/p&gt;
+&lt;/div&gt;
+<span class="removed"><del><strong>&lt;!-- All pages on the GNU web server 
should have the section about    --&gt;
+&lt;!-- verbatim copying.  Please do NOT remove this without talking     --&gt;
+&lt;!-- with the webmasters first. --&gt; 
+&lt;!-- Please make sure the copyright date is consistent with the document 
--&gt;
+&lt;!-- and that it is like this "2001, 2002" not this "2001-2002." 
--&gt;</strong></del></span>
+&lt;/div&gt;
+&lt;/body&gt;
+&lt;/html&gt;
+</pre></body></html>

Index: po/privacyaction.nl-diff.html
===================================================================
RCS file: po/privacyaction.nl-diff.html
diff -N po/privacyaction.nl-diff.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ po/privacyaction.nl-diff.html       21 Mar 2014 09:28:46 -0000      1.1
@@ -0,0 +1,171 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
+<!-- Generated by GNUN -->
+<html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en" lang="en">
+<head>
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<title>/philosophy/privacyaction.html-diff</title>
+<style type="text/css">
+span.removed { background-color: #f22; color: #000; }
+span.inserted { background-color: #2f2; color: #000; }
+</style></head>
+<body><pre>
+&lt;!--#include virtual="/server/header.html" --&gt;
+<span class="inserted"><ins><em>&lt;!-- Parent-Version: 1.76 
--&gt;</em></ins></span>
+&lt;title&gt;Protect Postal Privacy
+- GNU Project - Free Software <span class="removed"><del><strong>Foundation 
(FSF)&lt;/title&gt;</strong></del></span> <span 
class="inserted"><ins><em>Foundation&lt;/title&gt;</em></ins></span>
+&lt;!--#include virtual="/philosophy/po/privacyaction.translist" --&gt;
+&lt;!--#include virtual="/server/banner.html" --&gt;
+&lt;h2&gt;Protect Postal Privacy&lt;/h2&gt;
+
+&lt;p&gt;
+The following information was written by Kathleen Ellis. The Free
+Software Foundation does not lead this campaign, but we support it by
+spreading the word and hope that you do too.&lt;/p&gt;
+
+&lt;h3&gt;Background&lt;/h3&gt;
+&lt;p&gt;
+The United States Postal Service has submitted a rule to Congress
+proposing that all Commercial Mail Recieving Agencies (CMRAs) must,
+as of June 24, 1999, collect significant personal information from
+all clients using their services. This would certainly affect
+anonymous mail transactions, and could put millions of CMRA
+customers in danger.  Any CMRA or CMRA customer who refuses to
+comply with this regulation would effectively lose their right to
+recieve mail.&lt;/p&gt;
+&lt;p&gt;
+The proposed regulation (published in the Federal Register on March
+25, 1999) requires that CMRAs collect names, home addresses,
+telephone numbers, and photo ID information about each customer.  If
+the CMRA customer classifies themselves as a business, they must
+surrender the information on that box holder to anyone who asks for
+it.  CMRAs are widely used by survivors of domestic violence,
+undercover law enforcement officials, and stalking victims in order
+to conceal their locations and identities from people who could
+cause them harm.&lt;/p&gt;
+&lt;p&gt;
+The USPS proposal was intended to help cut down on mail fraud, a
+practice that costs consumers millions of dollars every year.
+However, experts state that the Postal Service's proposal will not
+serve as a deterrent to criminals.  &ldquo;It will be a simple process
+for those with financial means to rent homes, apartments, office
+space, or the executive suites available in most major metropolitan
+areas&rdquo;, says Postal Watch's website.&lt;/p&gt;
+&lt;p&gt;
+Congressman Ron Paul has introduced House Joint Resolution 55, which
+would effectively revoke the Postal Service's new regulations
+regarding CMRAs, but the resolution needs your support in order to
+ensure that this insidious assault on consumer privacy is defeated.&lt;/p&gt;
+
+&lt;h3&gt;What you can do&lt;/h3&gt;
+
+&lt;ol&gt;
+  &lt;li&gt;Contact your Representative and urge them to co-sponsor HJR 
55.&lt;/li&gt;
+  &lt;li&gt;Write or call members of the House Appropriations Committee and
+       inform them about this issue, and urge them to pass the
+       resolution.&lt;/li&gt;
+  &lt;li&gt;Send written comments about this issue to the US Postal Service
+       before July 9, 1999 to:
+       &lt;address&gt;
+       Manager, Administration and FOIA United States Postal Service
+       &lt;br /&gt;
+       475 L'Enfant Plaza SW, Room 8141 Washington, DC  20260-5202
+       &lt;/address&gt;&lt;/li&gt;
+&lt;/ol&gt;
+
+&lt;h3&gt;More information&lt;/h3&gt;
+For further information, see the following web pages:
+
+&lt;ul&gt;
+<span class="removed"><del><strong>&lt;!--  &lt;li&gt;&lt;a 
href="http://www.postalwatch.org/"&gt;Postal Watch&lt;/a&gt; --&gt;
+&lt;!--  dead link, yavor, 9 Jun 07 --&gt;</strong></del></span>
+  &lt;li&gt;&lt;a 
href="http://www.privacy.org/"&gt;Privacy.org&lt;/a&gt;&lt;/li&gt;
+<span class="removed"><del><strong>&lt;!-- &lt;li&gt;&lt;a 
href="http://thomas.loc.gov/cgi-bin/query/C?c106:./temp/~c106MQgA5I"&gt;HJR 
55&lt;/a&gt;&lt;/li&gt; --&gt;
+&lt;!-- doesn't work, yavor, 9 Jun 07 --&gt;</strong></del></span>
+  &lt;li&gt;&lt;a href="http://www.house.gov/appropriations/"&gt;
+       House Appropriations Committee&lt;/a&gt;&lt;/li&gt;
+&lt;/ul&gt;
+<span class="removed"><del><strong>&lt;/div&gt;</strong></del></span>
+
+<span class="inserted"><ins><em>&lt;/div&gt;&lt;!-- for id="content", starts 
in the include above --&gt;</em></ins></span>
+&lt;!--#include virtual="/server/footer.html" --&gt;
+&lt;div id="footer"&gt;
+
+<span class="removed"><del><strong>&lt;p&gt;
+Please</strong></del></span>
+<span class="inserted"><ins><em>&lt;div class="unprintable"&gt;
+
+&lt;p&gt;Please</em></ins></span> send <span 
class="inserted"><ins><em>general</em></ins></span> FSF &amp; GNU inquiries to
+&lt;a <span 
class="removed"><del><strong>href="mailto:address@hidden"&gt;&lt;em&gt;address@hidden&lt;/em&gt;&lt;/a&gt;.</strong></del></span>
 <span 
class="inserted"><ins><em>href="mailto:address@hidden"&gt;&lt;address@hidden&gt;&lt;/a&gt;.</em></ins></span>
+There are also &lt;a href="/contact/"&gt;other ways to contact&lt;/a&gt;
+the FSF.
+<span class="removed"><del><strong>&lt;br /&gt;
+Please send broken</strong></del></span>  <span 
class="inserted"><ins><em>Broken</em></ins></span> links and other corrections 
or suggestions <span class="inserted"><ins><em>can be sent</em></ins></span>
+to &lt;a <span 
class="removed"><del><strong>href="mailto:address@hidden"&gt;&lt;em&gt;address@hidden&lt;/em&gt;&lt;/a&gt;.
+&lt;/p&gt;
+
+&lt;p&gt;</strong></del></span> <span 
class="inserted"><ins><em>href="mailto:address@hidden"&gt;&lt;address@hidden&gt;&lt;/a&gt;.&lt;/p&gt;
+
+&lt;p&gt;&lt;!-- TRANSLATORS: Ignore the original text in this paragraph,
+        replace it with the translation of these two:
+
+        We work hard and do our best to provide accurate, good quality
+        translations.  However, we are not exempt from imperfection.
+        Please send your comments and general suggestions in this regard
+        to &lt;a href="mailto:address@hidden"&gt;
+        &lt;address@hidden&gt;&lt;/a&gt;.&lt;/p&gt;
+
+        &lt;p&gt;For information on coordinating and submitting translations of
+        our web pages, see &lt;a
+        href="/server/standards/README.translations.html"&gt;Translations
+        README&lt;/a&gt;. --&gt;</em></ins></span>
+Please see the &lt;a
+href="/server/standards/README.translations.html"&gt;Translations
+README&lt;/a&gt; for information on coordinating and submitting translations
+of this <span class="removed"><del><strong>article.
+&lt;/p&gt;
+
+&lt;p&gt;
+Copyright</strong></del></span> <span 
class="inserted"><ins><em>article.&lt;/p&gt;
+&lt;/div&gt;
+
+&lt;!-- Regarding copyright, in general, standalone pages (as opposed to
+     files generated as part of manuals) on the GNU web server should
+     be under CC BY-ND 3.0 US.  Please do NOT change or remove this
+     without talking with the webmasters or licensing team first.
+     Please make sure the copyright date is consistent with the
+     document.  For web pages, it is ok to list just the latest year the
+     document was modified, or published.
+     
+     If you wish to list earlier years, that is ok too.
+     Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
+     years, as long as each year in the range is in fact a copyrightable
+     year, i.e., a year in which the document was published (including
+     being publicly visible on the web or in a revision control system).
+     
+     There is more detail about copyright years in the GNU Maintainers
+     Information document, www.gnu.org/prep/maintain. --&gt;
+
+&lt;p&gt;Copyright</em></ins></span> &copy; 1996, 1997, 1998, 2007, 2008 Free 
Software
+Foundation, <span class="removed"><del><strong>Inc.,&lt;/p&gt;
+&lt;address&gt;51 Franklin St, Fifth Floor, Boston, MA 02110, 
USA&lt;/address&gt;</strong></del></span> <span 
class="inserted"><ins><em>Inc.&lt;/p&gt;</em></ins></span>
+
+&lt;p&gt;This page is licensed under a &lt;a rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/"&gt;Creative
+Commons Attribution-NoDerivs 3.0 United States <span 
class="removed"><del><strong>License&lt;/a&gt;.
+&lt;/p&gt;</strong></del></span> <span 
class="inserted"><ins><em>License&lt;/a&gt;.&lt;/p&gt;</em></ins></span>
+
+&lt;!--#include virtual="/server/bottom-notes.html" --&gt;
+
+<span class="removed"><del><strong>&lt;p&gt;Updated:</strong></del></span>
+
+<span class="inserted"><ins><em>&lt;p&gt;&lt;/p&gt;&lt;p 
class="unprintable"&gt;Updated:</em></ins></span>
+&lt;!-- timestamp start --&gt;
+$Date: 2014/03/21 09:28:46 $
+&lt;!-- timestamp end --&gt;
+&lt;/p&gt;
+&lt;/div&gt;
+&lt;/div&gt;
+&lt;/body&gt;
+&lt;/html&gt;
+</pre></body></html>

Index: po/push-copyright-aside.nl-diff.html
===================================================================
RCS file: po/push-copyright-aside.nl-diff.html
diff -N po/push-copyright-aside.nl-diff.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ po/push-copyright-aside.nl-diff.html        21 Mar 2014 09:28:47 -0000      
1.1
@@ -0,0 +1,244 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
+<!-- Generated by GNUN -->
+<html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en" lang="en">
+<head>
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<title>/philosophy/push-copyright-aside.html-diff</title>
+<style type="text/css">
+span.removed { background-color: #f22; color: #000; }
+span.inserted { background-color: #2f2; color: #000; }
+</style></head>
+<body><pre>
+&lt;!--#include virtual="/server/header.html" --&gt;
+<span class="inserted"><ins><em>&lt;!-- Parent-Version: 1.76 
--&gt;</em></ins></span>
+&lt;title&gt;Science must &ldquo;push copyright aside&rdquo;
+- GNU Project - Free Software <span class="removed"><del><strong>Foundation 
(FSF)&lt;/title&gt;</strong></del></span> <span 
class="inserted"><ins><em>Foundation&lt;/title&gt;</em></ins></span>
+&lt;!--#include virtual="/philosophy/po/push-copyright-aside.translist" --&gt;
+&lt;!--#include virtual="/server/banner.html" --&gt;
+&lt;h2&gt;Science must push copyright aside&lt;/h2&gt;
+
+&lt;p&gt;by &lt;strong&gt;Richard M. Stallman&lt;/strong&gt;&lt;/p&gt;
+
+&lt;p&gt;&lt;em&gt;Many points that lead to a conclusion that software freedom 
must be
+universal often apply to other forms of expressive works, albeit in
+different ways. This essay concerns the application of principles
+related to software freedom to the area of literature.
+Generally, such issues are orthogonal to software freedom, but we
+include essays like this here since many people interested in Free
+Software want to know more about how the principles can be applied to
+areas other than software.&lt;/em&gt;&lt;/p&gt;
+
+&lt;p&gt;(This article appeared in &lt;em&gt;Nature&lt;/em&gt; magazine's
+&lt;b&gt;web&lt;/b&gt;debates forum in 2001.)&lt;/p&gt;
+
+&lt;p&gt;It should be a truism that the scientific literature exists to
+disseminate scientific knowledge, and that scientific journals exist
+to facilitate the process.  It therefore follows that rules for use of
+the scientific literature should be designed to help achieve that
+goal.&lt;/p&gt;
+
+&lt;p&gt;The rules we have now, known as copyright, were established in the
+age of the printing press, an inherently centralized method of
+mass-production copying.  In a print environment, copyright on journal
+articles restricted only journal publishers&mdash;requiring them to
+obtain permission to publish an article&mdash;and would-be
+plagiarists. It helped journals to operate and disseminate knowledge,
+without interfering with the useful work of scientists or students,
+either as writers or readers of articles. These rules fit that system
+well.&lt;/p&gt;
+
+&lt;p&gt;The modern technology for scientific publishing, however, is the
+World Wide Web.  What rules would best ensure the maximum
+dissemination of scientific articles, and knowledge, on the web?
+Articles should be distributed in nonproprietary formats, with open
+access for all. And everyone should have the right to
+&ldquo;mirror&rdquo; articles&mdash;that is, to republish them verbatim
+with proper attribution.&lt;/p&gt;
+
+&lt;p&gt;These rules should apply to past as well as future articles, when
+they are distributed in electronic form. But there is no crucial need
+to change the present copyright system as it applies to paper
+publication of journals because the problem is not in that domain.&lt;/p&gt;
+
+&lt;p&gt;Unfortunately, it seems that not everyone agrees with the truisms
+that began this article. Many journal publishers appear to believe
+that the purpose of scientific literature is to enable them to publish
+journals so as to collect subscriptions from scientists and
+students. Such thinking is known as &ldquo;confusion of the means with
+the ends&rdquo;.&lt;/p&gt;
+
+&lt;p&gt;Their approach has been to restrict access even to read the
+scientific literature to those who can and will pay for it. They use
+copyright law, which is still in force despite its inappropriateness
+for computer networks, as an excuse to stop scientists from choosing
+new rules.&lt;/p&gt;
+
+&lt;p&gt;For the sake of scientific cooperation and humanity's future, we
+must reject that approach at its root&mdash;not merely the
+obstructive systems that have been instituted, but the mistaken
+priorities that inspired them.&lt;/p&gt;
+
+&lt;p&gt;Journal publishers sometimes claim that online access requires
+expensive high-powered server machines, and that they must charge
+access fees to pay for these servers. This &ldquo;problem&rdquo; is a
+consequence of its own &ldquo;solution.&rdquo; Give everyone the
+freedom to mirror, and libraries around the world will set up mirror
+sites to meet the demand. This decentralized solution will reduce
+network bandwidth needs and provide faster access, all the while
+protecting the scholarly record against accidental loss.&lt;/p&gt;
+
+&lt;p&gt;Publishers also argue that paying the editors requires charging for
+access.  Let us accept the assumption that editors must be paid; this
+tail need not wag the dog. The cost of editing for a typical paper is
+between 1 percent and 3 percent of the cost of funding the research to produce
+it. Such a small percentage of the cost can hardly justify obstructing
+the use of the results.&lt;/p&gt;
+
+&lt;p&gt;Instead, the cost of editing could be recovered, for example,
+through page charges to the authors, who can pass these on to the
+research sponsors.  The sponsors should not mind, given that they
+currently pay for publication in a more cumbersome way, through
+overhead fees for the university library's subscription to the
+journal. By changing the economic model to charge editing costs to the
+research sponsors, we can eliminate the apparent need to restrict
+access. The occasional author who is not affiliated with an
+institution or company, and who has no research sponsor, could be
+exempted from page charges, with costs levied on institution-based
+authors.&lt;/p&gt;
+
+&lt;p&gt;Another justification for access fees to online publications is to
+fund conversion of the print archives of a journal into online
+form. That work needs to be done, but we should seek alternative ways
+of funding it that do not involve obstructing access to the
+result. The work itself will not be any more difficult, or cost any
+more. It is self-defeating to digitize the archives and waste the
+results by restricting access.&lt;/p&gt;
+
+&lt;p&gt;The US Constitution says that copyright exists &ldquo;to promote
+the Progress of Science&rdquo;. When copyright impedes the progress of
+science, science must push copyright out of the way.&lt;/p&gt;
+
+&lt;hr /&gt;
+
+Later developments:
+
+&lt;p&gt;Some universities have adopted policies to thwart the journal
+publishers' power. For instance, here is MIT's.&lt;br/&gt;
+&lt;a 
href="http://info-libraries.mit.edu/scholarly/mit-open-access/open-access-at-mit/mit-open-access-policy/"&gt;http://info-libraries.mit.edu/scholarly/mit-open-access/open-access-at-mit/mit-open-access-policy/&lt;/a&gt;.
+Stronger policies are needed, however, as this one permits individual
+authors to "opt out" (i.e., cave in).&lt;/p&gt;
+
+&lt;p&gt;The US government has imposed a requirement known as "public
+access" on some funded research.  This requires publication within a
+certain period in a site that allows anyone to view the article.  This
+requirement is a positive step, but inadequate because it does not
+include freedom to redistribute the article.&lt;/p&gt;
+
+&lt;p&gt;Curiously, the concept of "open access" in the 2002 Budapest Open
+Access Initiative did include freedom to redistribute.  I signed that
+declaration, despite my distaste for the word "open", because the
+substance of the position was right.&lt;/p&gt;
+
+&lt;p&gt;However, the word "open" had the last laugh: influential
+campaigners for "open access" subsequently dropped freedom to
+redistribute from their goals.  I stand by the position of
+the &lt;a href="http://www.soros.org/openaccess"&gt;BOAI&lt;/a&gt;, but now 
that
+"open access" means something else, I refer to it as "redistributable
+publication" or "free-to-mirror publication".&lt;/p&gt;
+
+<span class="removed"><del><strong>&lt;/div&gt;</strong></del></span>
+
+<span class="inserted"><ins><em>&lt;/div&gt;&lt;!-- for id="content", starts 
in the include above --&gt;</em></ins></span>
+&lt;!--#include virtual="/server/footer.html" --&gt;
+&lt;div id="footer"&gt;
+<span class="removed"><del><strong>&lt;p&gt;
+Please</strong></del></span>
+<span class="inserted"><ins><em>&lt;div class="unprintable"&gt;
+
+&lt;p&gt;Please</em></ins></span> send <span 
class="inserted"><ins><em>general</em></ins></span> FSF &amp; GNU inquiries to
+&lt;a <span 
class="removed"><del><strong>href="mailto:address@hidden"&gt;&lt;em&gt;address@hidden&lt;/em&gt;&lt;/a&gt;.</strong></del></span>
 <span 
class="inserted"><ins><em>href="mailto:address@hidden"&gt;&lt;address@hidden&gt;&lt;/a&gt;.</em></ins></span>
+There are also &lt;a href="/contact/"&gt;other ways to contact&lt;/a&gt;
+the FSF.
+<span class="removed"><del><strong>&lt;br /&gt;
+Please send broken</strong></del></span>  <span 
class="inserted"><ins><em>Broken</em></ins></span> links and other corrections 
or suggestions <span class="inserted"><ins><em>can be sent</em></ins></span>
+to &lt;a <span 
class="removed"><del><strong>href="mailto:address@hidden"&gt;&lt;em&gt;address@hidden&lt;/em&gt;&lt;/a&gt;.
+&lt;/p&gt;
+
+&lt;p&gt;</strong></del></span> <span 
class="inserted"><ins><em>href="mailto:address@hidden"&gt;&lt;address@hidden&gt;&lt;/a&gt;.&lt;/p&gt;
+
+&lt;p&gt;&lt;!-- TRANSLATORS: Ignore the original text in this paragraph,
+        replace it with the translation of these two:
+
+        We work hard and do our best to provide accurate, good quality
+        translations.  However, we are not exempt from imperfection.
+        Please send your comments and general suggestions in this regard
+        to &lt;a href="mailto:address@hidden"&gt;
+        &lt;address@hidden&gt;&lt;/a&gt;.&lt;/p&gt;
+
+        &lt;p&gt;For information on coordinating and submitting translations of
+        our web pages, see &lt;a
+        href="/server/standards/README.translations.html"&gt;Translations
+        README&lt;/a&gt;. --&gt;</em></ins></span>
+Please see the &lt;a
+href="/server/standards/README.translations.html"&gt;Translations
+README&lt;/a&gt; for information on coordinating and submitting translations
+of this <span class="removed"><del><strong>article.
+&lt;/p&gt;
+
+&lt;p&gt;
+Copyright &copy; 2001, 2012 Richard M. Stallman
+&lt;br /&gt;
+This page is licensed under a &lt;a rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/"&gt;Creative
+Commons Attribution-NoDerivs 3.0 United States License&lt;/a&gt;.
+&lt;/p&gt;
+
+&lt;!--#include virtual="/server/bottom-notes.html" --&gt;
+
+&lt;p&gt;Updated:
+&lt;!-- timestamp start --&gt;
+$Date: 2014/03/21 09:28:47 $
+&lt;!-- timestamp end --&gt;
+&lt;/p&gt;</strong></del></span> <span 
class="inserted"><ins><em>article.&lt;/p&gt;</em></ins></span>
+&lt;/div&gt;
+
+&lt;!-- <span class="removed"><del><strong>All</strong></del></span> <span 
class="inserted"><ins><em>Regarding copyright, in general, 
standalone</em></ins></span> pages <span class="inserted"><ins><em>(as opposed 
to
+     files generated as part of manuals)</em></ins></span> on the GNU web 
server should <span class="removed"><del><strong>have the section about    
--&gt;
+&lt;!-- verbatim copying.</strong></del></span>
+     <span class="inserted"><ins><em>be under CC BY-ND 3.0 
US.</em></ins></span>  Please do NOT <span class="inserted"><ins><em>change 
or</em></ins></span> remove this
+     without talking     <span class="removed"><del><strong>--&gt;
+&lt;!--</strong></del></span> with the webmasters <span 
class="inserted"><ins><em>or licensing team</em></ins></span> first. <span 
class="removed"><del><strong>--&gt; 
+&lt;!--</strong></del></span>
+     Please make sure the copyright date is consistent with the
+     <span class="inserted"><ins><em>document.  For web pages, it is ok to 
list just the latest year the</em></ins></span>
+     document <span class="removed"><del><strong>--&gt;
+&lt;!-- and</strong></del></span> <span class="inserted"><ins><em>was 
modified, or published.
+     
+     If you wish to list earlier years,</em></ins></span> that <span 
class="removed"><del><strong>it</strong></del></span> is <span 
class="removed"><del><strong>like this</strong></del></span> <span 
class="inserted"><ins><em>ok too.
+     Either</em></ins></span> "2001, <span class="removed"><del><strong>2002" 
not this "2001-2002."</strong></del></span> <span 
class="inserted"><ins><em>2002, 2003" or "2001-2003" are ok for specifying
+     years, as long as each year in the range is in fact a copyrightable
+     year, i.e., a year in which the document was published (including
+     being publicly visible on the web or in a revision control system).
+     
+     There is more detail about copyright years in the GNU Maintainers
+     Information document, www.gnu.org/prep/maintain. --&gt;
+
+&lt;p&gt;Copyright &copy; 2001, 2012 Richard M. Stallman&lt;/p&gt;
+
+&lt;p&gt;This page is licensed under a &lt;a rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/"&gt;Creative
+Commons Attribution-NoDerivs 3.0 United States License&lt;/a&gt;.&lt;/p&gt;
+
+&lt;!--#include virtual="/server/bottom-notes.html"</em></ins></span> --&gt;
+
+<span class="inserted"><ins><em>&lt;p&gt;&lt;/p&gt;&lt;p 
class="unprintable"&gt;Updated:
+&lt;!-- timestamp start --&gt;
+$Date: 2014/03/21 09:28:47 $
+&lt;!-- timestamp end --&gt;
+&lt;/p&gt;
+&lt;/div&gt;</em></ins></span>
+&lt;/div&gt;
+&lt;/body&gt;
+&lt;/html&gt;
+</pre></body></html>



reply via email to

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