www-commits
[Top][All Lists]
Advanced

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

www/philosophy po/limit-patent-effect.translist...


From: GNUN
Subject: www/philosophy po/limit-patent-effect.translist...
Date: Wed, 31 Jan 2024 08:31:09 -0500 (EST)

CVSROOT:        /web/www
Module name:    www
Changes by:     GNUN <gnun>     24/01/31 08:31:09

Modified files:
        philosophy/po  : limit-patent-effect.translist 
                         limit-patent-effect.zh-cn.po 
Added files:
        philosophy     : limit-patent-effect.zh-cn.html 
        philosophy/po  : limit-patent-effect.zh-cn-en.html 

Log message:
        Automatic update by GNUnited Nations.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/limit-patent-effect.zh-cn.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/limit-patent-effect.translist?cvsroot=www&r1=1.11&r2=1.12
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/limit-patent-effect.zh-cn.po?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/limit-patent-effect.zh-cn-en.html?cvsroot=www&rev=1.1

Patches:
Index: po/limit-patent-effect.translist
===================================================================
RCS file: /web/www/www/philosophy/po/limit-patent-effect.translist,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- po/limit-patent-effect.translist    2 Jun 2020 09:00:54 -0000       1.11
+++ po/limit-patent-effect.translist    31 Jan 2024 13:31:09 -0000      1.12
@@ -6,6 +6,7 @@
 <span dir="ltr">[es]&nbsp;<a lang="es" hreflang="es" 
href="/philosophy/limit-patent-effect.es.html">español</a> &nbsp;</span>
 <span dir="ltr">[fr]&nbsp;<a lang="fr" hreflang="fr" 
href="/philosophy/limit-patent-effect.fr.html">français</a> &nbsp;</span>
 <span dir="ltr">[ru]&nbsp;<a lang="ru" hreflang="ru" 
href="/philosophy/limit-patent-effect.ru.html">русский</a> &nbsp;</span>
+<span dir="ltr">[zh-cn]&nbsp;<a lang="zh-cn" hreflang="zh-cn" 
href="/philosophy/limit-patent-effect.zh-cn.html">简体中文</a> &nbsp;</span>
 </p>
 </div>' -->
 <link rel="alternate" type="text/html" 
href="/philosophy/limit-patent-effect.html" hreflang="x-default" />
@@ -13,4 +14,5 @@
 <link rel="alternate" type="text/html" lang="es" hreflang="es" 
href="/philosophy/limit-patent-effect.es.html" title="español" />
 <link rel="alternate" type="text/html" lang="fr" hreflang="fr" 
href="/philosophy/limit-patent-effect.fr.html" title="français" />
 <link rel="alternate" type="text/html" lang="ru" hreflang="ru" 
href="/philosophy/limit-patent-effect.ru.html" title="русский" />
+<link rel="alternate" type="text/html" lang="zh-cn" hreflang="zh-cn" 
href="/philosophy/limit-patent-effect.zh-cn.html" title="简体中文" />
 <!-- end translist file -->

Index: po/limit-patent-effect.zh-cn.po
===================================================================
RCS file: /web/www/www/philosophy/po/limit-patent-effect.zh-cn.po,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- po/limit-patent-effect.zh-cn.po     31 Jan 2024 12:59:14 -0000      1.1
+++ po/limit-patent-effect.zh-cn.po     31 Jan 2024 13:31:09 -0000      1.2
@@ -260,11 +260,11 @@
 
 #. type: Content of: <div><div><p>
 msgid ""
-"Please send general FSF &amp; GNU inquiries to <a href=\"mailto:gnu@gnu.";
-"org\">&lt;gnu@gnu.org&gt;</a>.  There are also <a href=\"/contact/\">other "
-"ways to contact</a> the FSF.  Broken links and other corrections or "
-"suggestions can be sent to <a href=\"mailto:webmasters@gnu.org\";>&lt;"
-"webmasters@gnu.org&gt;</a>."
+"Please send general FSF &amp; GNU inquiries to <a href=\"mailto:gnu@gnu.org";
+"\">&lt;gnu@gnu.org&gt;</a>.  There are also <a href=\"/contact/\">other ways "
+"to contact</a> the FSF.  Broken links and other corrections or suggestions "
+"can be sent to <a href=\"mailto:webmasters@gnu.org\";>&lt;webmasters@gnu."
+"org&gt;</a>."
 msgstr ""
 "请将对FSF&amp;GNU的一般询问发送到<a 
href=\"mailto:gnu@gnu.org\";>&lt;gnu@gnu."
 "org&gt;</a>。还有一些其他联系FSF的<a 
href=\"/contact/\">方式</a>。关于链接错"
@@ -287,15 +287,15 @@
 #.         README</a>. 
 #. type: Content of: <div><div><p>
 msgid ""
-"Please see the <a href=\"/server/standards/README.translations."
-"html\">Translations README</a> for information on coordinating and "
-"contributing translations of this article."
+"Please see the <a href=\"/server/standards/README.translations.html"
+"\">Translations README</a> for information on coordinating and contributing "
+"translations of this article."
 msgstr ""
 "我们尽最大努力来提供精准和高质量的翻译,但难å…
ä¼šå­˜åœ¨é”™è¯¯å’Œä¸è¶³ã€‚如果您在这方"
-"面有评论或一般性的建议,请发送至 <a 
href=\"mailto:web-translators@gnu.";
-"org\">&lt;web-translators@gnu.org&gt;</a>。</p><p>å…
³äºŽè¿›è¡Œåè°ƒä¸Žæäº¤ç¿»è¯‘的更"
-"多信息参见 <a 
href=\"/server/standards/README.translations.html\">《译者指"
-"南》</a>。"
+"面有评论或一般性的建议,请发送至 <a 
href=\"mailto:web-translators@gnu.org";
+"\">&lt;web-translators@gnu.org&gt;</a>。</p><p>å…
³äºŽè¿›è¡Œåè°ƒä¸Žæäº¤ç¿»è¯‘的更多信"
+"息参见 <a href=\"/server/standards/README.translations.html\">《译者
指南》</"
+"a>。"
 
 #. type: Content of: <div><p>
 msgid "Copyright &copy; 2012, 2013, 2021 Free Software Foundation, Inc."

Index: limit-patent-effect.zh-cn.html
===================================================================
RCS file: limit-patent-effect.zh-cn.html
diff -N limit-patent-effect.zh-cn.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ limit-patent-effect.zh-cn.html      31 Jan 2024 13:31:09 -0000      1.1
@@ -0,0 +1,159 @@
+<!--#set var="ENGLISH_PAGE" value="/philosophy/limit-patent-effect.en.html" -->
+
+<!--#include virtual="/server/header.zh-cn.html" -->
+<!-- Parent-Version: 1.96 -->
+<!-- This page is derived from /server/standards/boilerplate.html -->
+<!--#set var="TAGS" value="essays laws patents" -->
+<!--#set var="DISABLE_TOP_ADDENDUM" value="yes" -->
+
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>让软件免受专利困扰 - GNU 工程 - 自由软件基金会</title>
+
+<!--#include virtual="/philosophy/po/limit-patent-effect.translist" -->
+<!--#include virtual="/server/banner.zh-cn.html" -->
+<!--#include virtual="/philosophy/ph-breadcrumb.zh-cn.html" -->
+<!--GNUN: OUT-OF-DATE NOTICE-->
+<!--#include virtual="/server/top-addendum.zh-cn.html" -->
+<div class="article reduced-width">
+<h2>让软件免受专利困扰</h2>
+
+<address class="byline"><a href="https://www.stallman.org/";>Richard 
Stallman</a> 著</address>
+
+<p>专利威胁着每一个软件开发者,我们一直担
心的专利战争已经爆发。而软件开发者
和作为社会大多数的用户都需要没有专利的软件。</p>
+
+<p>对我们构成威胁的专利通常被称为
+&ldquo;软件专利&rdquo;,但这一术语å…
·æœ‰è¯¯å¯¼æ€§ã€‚这类专利并不涉及任何å…
·ä½“程序。相反,每项专利都描述了一些实用的想法,并声称任何执行该想法的人都可能被起诉。å›
 æ­¤ï¼Œç§°å…¶ä¸º
+&ldquo;计算创意专利&rdquo; 更为明确。</p>
+
+<p>美国专利制度不会给专利贴上标签来表明一项是 
&ldquo;软件专利&ldquo;
+而另一项不是。软件开发者
区分了威胁我们的专利&mdash;&mdash;涵盖可以在软件中实现的想法的专利&mdash;&mdash;和å
…
¶ä»–专利。例如,如果专利想法是一个物理结构的形状或是一个化学反应,则没有程序可以实现该想法;该专利不会威胁软件领域。但如果获得专利的想法是一种计算方式,那么该专利的矛头就指向软件开发人员和用户。</p>
+
+<p>这并不是说计算创意专利只禁止软件。这些想法也可以在硬件中实现&mdash;&mdash;而且å
…
¶ä¸­è®¸å¤šå·²ç»å®žçŽ°äº†ã€‚æ¯ä¸ªä¸“åˆ©é€šå¸¸ä¼šæ¶µç›–è¯¥æƒ³æ³•çš„ç¡¬ä»¶<em>和</em>软件实现。</p>
+
+<h3>软件的特殊问题</h3>
+
+<p>尽管如此,软件仍然是计算创意专利引起特殊问题的地方。在软件中,很容易在一个程序中实现数千个想法。如果å
…¶ä¸­çš„10%拥有专利,那就意味着数百项专利对å…
¶æž„成威胁。</p>
+
+<p>2004年,当公共专利基金会的丹·拉维彻ç 
”究一个大型程序(Linux,<a
+href="/gnu/gnu-linux-faq.html">GNU/Linux</a>
+操作系统的内æ 
¸ï¼‰æ—¶ï¼Œä»–发现了283项美国专利,这些专利似乎涵盖了该程序源代ç
 ä¸­å®žçŽ°çš„è®¡ç®—åˆ›æ„ã€‚åŒå¹´ï¼Œä¸€æœ¬æ‚å¿—ä¼°è®¡ Linux 占整个 
GNU/Linux
+系统的0.25%。将300乘以400,我们得到的数量级估计是,整个系统
 <em>受到大约100,000项专利的威胁</em>。</p>
+
+<p>即使这些专利中有一半因
+&ldquo;劣质&rdquo;&mdash;&mdash;即专利制度的错误&mdash;&mdash;而被排除,现状也不会真正改变。æ—
 è®ºæ˜¯100,000项专利还是50,000项专利,都是同æ 
·çš„灾难。这就是为什么将我们对软件专利的批评仅限于
+&rdquo;专利流氓&ldquo; 或 &ldquo;劣质&rdquo; 
专利是错误的。当今最严重的专利侵犯者是苹果å…
¬å¸ï¼Œä½†å¹¶ä¸æ˜¯é€šå¸¸å®šä¹‰çš„
+&ldquo;专利流氓&rdquo;;我不知道苹果的专利是否 
&ldquo;质量好&rdquo;,但专利的 &ldquo;质量&rdquo;
+越好,其威胁就越大。</p>
+
+<p>我们需要解决整个问题,而不仅仅是其中一部分。</p>
+
+<p>从立法上纠正这个问题的通常建议包括改变授予专利的æ 
‡å‡†&mdash;&mdash;例如,禁止为计算方式实践以及执行这些实践的系统颁发专利。但这种方法有两个缺点。</p>
+
+<p>首å…
ˆï¼Œä¸“利律师善于重新制定专利,以适应任何可能适用的规则;他们会把任何想要限制专利实质å†
…
容的措施转化为单纯的形式要求。例如,许多美国计算创意专利描述的系统åŒ
…括一个算术逻辑单å…
ƒã€ä¸€ä¸ªå®šåºå™¨ã€ä¸€ä¸ªå­˜å‚¨å™¨ã€ä»¥åŠç”¨äºŽæ‰§è¡Œç‰¹å®šè®¡ç®—的控制器。这是一种描述计算机运行程序进行某种计算的å
…¸åž‹æ–¹å¼ï¼›å…¶ç›®çš„æ˜¯ä½¿ä¸“利申请符合标准,而此æ 
‡å‡†æ›¾æ˜¯ç¾Žå›½ä¸“利制度在过去一段时间内的要求。</p>
+
+<p>其次,美国已经有成千上万项计算创意专利,改变æ 
‡å‡†ä»¥é˜²æ­¢é¢å‘更多专利并不能消除现有专利。我们将不得不等å¾
…
近20年,通过专利到期来彻底解决这个问题。我们可以设想通过立法废除这些现有专利,但这很可能是违宪的(最高法院反常地坚持认为,国会可以以牺牲å
…¬ä¼—权利为代价来扩大私人特权,但不能反å…
¶é“而行之)。</p>
+
+<h3>另辟蹊径:不限制颁发专利,而是限制专利的效力</h3>
+
+<p>我的建议是改变专利的<em>效力</em>。我们应该立法规定在通用计算硬件上开发、分发或运行程序不构成专利侵权。这种方法有å‡
 ä¸ªä¼˜ç‚¹ï¼š</p>
+
+<ul>
+<li>它不需要将专利或专利申请按照 &ldquo;软件&rdquo; 或 
&ldquo;非软件&rdquo; 来分类。</li>
+<li>它保护开发人员和用户å…
å—现有和未来潜在的计算创意专利的威胁。</li>
+<li>专利律师不能通过以不同方式撰写申请来ç 
´åé¢„期效果。</li>
+</ul>
+
+<p>这种方法并不完全使现有的计算创意专利无效,因
为它们将继续适用于使用专有硬件的实现。这有一个好处,它消除了反对该方法法律效力的论据。美国å‡
 å¹´å‰é€šè¿‡äº†ä¸€é¡¹æ³•律,保护外科医生免受专利诉讼,因
此即使外科手术获得专利,外科医生也是安å…
¨çš„。这为我的方案提供了先例。</p>
+
+<p>软件开发者
和用户需要专利保护。这是唯一能为所有人提供å…
¨é¢ä¿æŠ¤çš„立法解决方案。然后我们可以重新开始竞争或合作&hellip;&hellip;而不用æ‹
…心某个陌生人会抹消我们的工作。</p>
+
+<div class="comment" role="complementary">
+<p><em>另见:<a
+href="/philosophy/patent-reform-is-not-enough.html">《专利改革还不够》</a></em></p>
+</div>
+
+<div class="infobox extra" role="complementary">
+<hr />
+<p>2012年11月本文最初版本发表于 <a
+href="https://www.wired.com/opinion/2012/11/richard-stallman-software-patents/";><cite>连线</cite></a></p>
+</div>
+</div>
+
+
+<div class="translators-notes">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.-->
+ </div>
+</div>
+
+<!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.zh-cn.html" -->
+<div id="footer" role="contentinfo">
+<div class="unprintable">
+
+<p>请将对FSF&amp;GNU的一般询问发送到<a
+href="mailto:gnu@gnu.org";>&lt;gnu@gnu.org&gt;</a>。还有一些å…
¶ä»–联系FSF的<a
+href="/contact/">方式</a>。关于链接错误和&rdquo;å…
¶ä»–更正或建议&ldquo;请发信到<a
+href="mailto:web-translators@gnu.org";>&lt;web-translators@gnu.org&gt;</a>。</p>
+
+<p>
+<!-- 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 <a href="mailto:web-translators@gnu.org";>
+
+        &lt;web-translators@gnu.org&gt;</a>.</p>
+
+        <p>For information on coordinating and contributing translations of
+        our web pages, see <a
+        href="/server/standards/README.translations.html">Translations
+        README</a>. -->
+我们尽最大努力来提供精准和高质量的翻译,但难å…
ä¼šå­˜åœ¨é”™è¯¯å’Œä¸è¶³ã€‚如果您在这方面有评论或一般性的建议,请发送至
 <a
+href="mailto:web-translators@gnu.org";>&lt;web-translators@gnu.org&gt;</a>。</p><p>å
…³äºŽè¿›è¡Œåè°ƒä¸Žæäº¤ç¿»è¯‘的更多信息参见
+<a href="/server/standards/README.translations.html">《译者
指南》</a>。</p>
+</div>
+
+<!-- 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 4.0.  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. -->
+<p>Copyright &copy; 2012, 2013, 2021 Free Software Foundation, Inc.</p>
+
+<p>本页面使用 <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/4.0/";>Creative Commons
+Attribution-NoDerivatives 4.0 International License</a> 授权。</p>
+
+<!--#include virtual="/server/bottom-notes.zh-cn.html" -->
+<div class="translators-credits">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.-->
+<b>翻译团队</b>:<a rel="team"
+href="//savannah.gnu.org/projects/www-zh-cn/">&lt;CTT&gt;</a>,2024。</div>
+
+<p class="unprintable"><!-- timestamp start -->
+最后更新:
+
+$Date: 2024/01/31 13:31:09 $
+
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+<!-- for class="inner", starts in the banner include -->
+</body>
+</html>

Index: po/limit-patent-effect.zh-cn-en.html
===================================================================
RCS file: po/limit-patent-effect.zh-cn-en.html
diff -N po/limit-patent-effect.zh-cn-en.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ po/limit-patent-effect.zh-cn-en.html        31 Jan 2024 13:31:09 -0000      
1.1
@@ -0,0 +1,207 @@
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.96 -->
+<!-- This page is derived from /server/standards/boilerplate.html -->
+<!--#set var="TAGS" value="essays laws patents" -->
+<!--#set var="DISABLE_TOP_ADDENDUM" value="yes" -->
+<title>Giving the Software Field Protection from Patents
+- GNU Project - Free Software Foundation</title>
+<!--#include virtual="/philosophy/po/limit-patent-effect.translist" -->
+<!--#include virtual="/server/banner.html" -->
+<!--#include virtual="/philosophy/ph-breadcrumb.html" -->
+<!--GNUN: OUT-OF-DATE NOTICE-->
+<!--#include virtual="/server/top-addendum.html" -->
+<div class="article reduced-width">
+<h2>Giving the Software Field Protection from Patents</h2>
+
+<address class="byline">by <a href="https://www.stallman.org/";>Richard
+Stallman</a></address>
+
+<p>Patents threaten every software developer, and the patent wars we have
+long feared have broken out.  Software developers and software
+users&mdash;which, in our society, is most people&mdash;need software
+to be free of patents.</p>
+
+<p>The patents that threaten us are often called &ldquo;software
+patents,&rdquo; but that term is misleading.  Such patents are not
+about any specific program.  Rather, each patent describes some
+practical idea, and says that anyone carrying out the idea can be
+sued.  So it is clearer to call them &ldquo;computational idea
+patents.&rdquo;</p>
+
+<p>The US patent system doesn't label patents to say this one's a
+&ldquo;software patent&rdquo; and that one isn't.  Software developers
+are the ones who make a distinction between the patents that threaten
+us&mdash;those that cover ideas that can be implemented in
+software&mdash;and the rest.  For example, if the patented idea is the
+shape of a physical structure or a chemical reaction, no program can
+implement that idea; that patent doesn't threaten the software field.
+But if the idea that's patented is a computation, that patent's barrel
+points at software developers and users.</p>
+
+<p>This is not to say that computational idea patents prohibit only
+software.  These ideas can also be implemented in hardware&mdash;and
+many of them have been.  Each patent typically covers both hardware
+<em>and</em> software implementations of the idea.</p>
+
+<h3>The Special Problem of Software</h3>
+
+<p>Still, software is where computational idea patents cause a special
+problem.  In software, it's easy to implement thousands of ideas
+together in one program.  If 10 percent are patented, that means hundreds of
+patents threaten it.</p>
+
+<p>When Dan Ravicher of the Public Patent Foundation studied one large program
+(Linux, which is the kernel of the
+<a href="/gnu/gnu-linux-faq.html"> GNU/Linux</a> operating system) in
+2004, he found 283 US patents that appeared to cover computing ideas
+implemented in the source code of that program.  That same year, a
+magazine estimated that Linux was .25 percent of the whole GNU/Linux system.
+Multiplying 300 by 400 we get the order-of-magnitude estimate that the
+system as a whole was <em>threatened by around 100,000 patents</em>.</p>
+
+<p>If half of those patents were eliminated as &ldquo;bad
+quality&rdquo;&mdash;mistakes of the patent system, that
+is&mdash;it would not really change things.  Whether 100,000 patents
+or 50,000, it's the same disaster.  This is why it's a mistake to
+limit our criticism of software patents to just &ldquo;patent
+trolls&rdquo; or &ldquo;bad quality&rdquo; patents.  The worst patent
+aggressor today is Apple, which isn't a &ldquo;troll&rdquo; by the
+usual definition; I don't know whether Apple's patents are &ldquo;good
+quality,&rdquo; but the better the patent's &ldquo;quality&rdquo; the
+more dangerous its threat.</p>
+
+<p>We need to fix the whole problem, not just part of it.</p>
+
+<p>The usual suggestions for correcting this problem legislatively
+involve changing the criteria for granting patents&mdash;for instance,
+to ban issuance of patents on computational practices and systems to
+perform them.  This approach has two drawbacks.</p>
+
+<p>First, patent lawyers are clever at reformulating patents to fit
+whatever rules may apply; they transform any attempt at limiting the
+substance of patents into a requirement of mere form.  For instance,
+many US computational idea patents describe a system including an
+arithmetic unit, an instruction sequencer, a memory, plus controls to
+carry out a particular computation.  This is a peculiar way of
+describing a computer running a program that does a certain
+computation; it was designed to make the patent application satisfy criteria
+that the US patent system was believed for a time to require.</p>
+
+<p>Second, the US already has many thousands of computational idea
+patents, and changing the criteria to prevent issuing more would not
+get rid of the existing ones.  We would have to wait almost 20 years
+for the problem to be entirely corrected through the expiration of
+these patents.  We could envision legislating the abolition of these
+existing patents, but that is probably unconstitutional.  (The Supreme
+Court has perversely insisted that Congress can extend private
+privileges at the expense of the public's rights but that it can't go
+in the other direction.)</p>
+
+<h3>A Different Approach: Limit Effect, Not Patentability</h3>
+
+<p>My suggestion is to change the <em>effect</em> of patents.  We
+should legislate that developing, distributing, or running a program
+on generally used computing hardware does not constitute patent
+infringement.  This approach has several advantages:</p>
+
+<ul>
+<li>It does not require classifying patents or patent applications as
+&ldquo;software&rdquo; or &ldquo;not software.&rdquo;</li>
+<li>It provides developers and users with protection from both existing
+and potential future computational idea patents.</li>
+<li>Patent lawyers cannot defeat the intended effect by writing
+applications differently.</li>
+</ul>
+
+<p>This approach doesn't entirely invalidate existing computational idea
+patents, because they would continue to apply to implementations using
+special-purpose hardware.  This is an advantage because it eliminates
+an argument against the legal validity of the plan.  The US passed a
+law some years ago shielding surgeons from patent lawsuits, so that
+even if surgical procedures are patented, surgeons are safe.  That
+provides a precedent for this solution.</p>
+
+<p>Software developers and software users need protection from patents.
+This is the only legislative solution that would provide full
+protection for all.  We could then go back to competing or
+cooperating&hellip; without the fear that some stranger will wipe away
+our work.</p>
+
+<div class="comment" role="complementary">
+<p><em>See also:
+<a href="/philosophy/patent-reform-is-not-enough.html">
+Patent Reform Is Not Enough</a></em></p>
+</div>
+
+<div class="infobox extra" role="complementary">
+<hr />
+<p>A version of this article was first published at
+<a 
href="https://www.wired.com/opinion/2012/11/richard-stallman-software-patents/";>
+<cite>Wired</cite></a> in November 2012.</p>
+</div>
+</div>
+
+
+</div><!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.html" -->
+<div id="footer" role="contentinfo">
+<div class="unprintable">
+
+<p>Please send general FSF &amp; GNU inquiries to <a
+href="mailto:gnu@gnu.org";>&lt;gnu@gnu.org&gt;</a>.  There are also <a
+href="/contact/">other ways to contact</a> the FSF.  Broken links and other
+corrections or suggestions can be sent to <a
+href="mailto:webmasters@gnu.org";>&lt;webmasters@gnu.org&gt;</a>.</p>
+
+<p><!-- 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 <a href="mailto:web-translators@gnu.org";>
+        &lt;web-translators@gnu.org&gt;</a>.</p>
+
+        <p>For information on coordinating and contributing translations of
+        our web pages, see <a
+        href="/server/standards/README.translations.html">Translations
+        README</a>. -->
+Please see the <a
+href="/server/standards/README.translations.html">Translations README</a> for
+information on coordinating and contributing translations of this article.</p>
+</div>
+
+<!-- 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 4.0.  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. -->
+
+<p>Copyright &copy; 2012, 2013, 2021 Free Software Foundation, Inc.</p>
+
+<p>This page is licensed under a <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/4.0/";>Creative
+Commons Attribution-NoDerivatives 4.0 International License</a>.</p>
+
+<!--#include virtual="/server/bottom-notes.html" -->
+
+<p class="unprintable">Updated:
+<!-- timestamp start -->
+$Date: 2024/01/31 13:31:09 $
+<!-- timestamp end -->
+</p>
+</div>
+</div><!-- for class="inner", starts in the banner include -->
+</body>
+</html>



reply via email to

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