why-not-lgpl.html - en to zh_CN translation catalogue (17 entries)

note: type: Content of: <title>
en: Why you shouldn't use the Lesser GPL for your next library - GNU Project - Free Software Foundation
zh_CN: 为什么你的下一个库不应该使用 LGPL - GNU工程 - 自由软件基金会

note: type: Content of: <div><h2>
en: Why you shouldn't use the Lesser GPL for your next library
zh_CN: 为什么你的下一个库不应该使用 LGPL

note: type: Content of: <div><p>
en: The GNU Project has two principal licenses to use for libraries.  One is the GNU Lesser GPL; the other is the ordinary GNU GPL.  The choice of license makes a big difference: using the Lesser GPL permits use of the library in proprietary programs; using the ordinary GPL for a library makes it available only for free programs.
zh_CN: 在GNU工程中对函数库的使用有两种主要的许可证。一种是GNU LGPL；另一种是普通的GNU GPL。选择许可证会造成重大的区别：LGPL许可证允许专有软件使用该函数库；而普通的GNU GPL只允许在自由软件中使用该函数库。

note: type: Content of: <div><div><p>
en: See <a href="/licenses/license-recommendations.html">&ldquo;How to choose a license for your own work&rdquo;</a> for general recommendations about choosing a license for your work.
zh_CN: 请参看<a href="/licenses/license-recommendations.html">&ldquo;如何为你的工作选择许可证&rdquo;</a>一文来了解选择许可证的常规建议。

note: type: Content of: <div><p>
en: Which license is best for a given library is a matter of strategy, and it depends on the details of the situation.  At present, most GNU libraries are covered by the Lesser GPL, and that means we are using only one of these two strategies, neglecting the other.  So we are now seeking more libraries to release <strong>under the ordinary GPL</strong>.
zh_CN: 对函数库使用哪种许可证最佳的考虑是策略问题，而且它取决于具体的情况。目前，大多数GNU函数库使用LGPL，这意味着我们只使用了两种策略之一，而忽略了另一个。所以我们现在要追求更多使用<strong>普通GPL许可证</strong>的函数库。

note: type: Content of: <div><p>
en: Proprietary software developers have the advantage of money; free software developers need to make advantages for each other.  Using the ordinary GPL for a library gives free software developers an advantage over proprietary developers: a library that they can use, while proprietary developers cannot use it.
zh_CN: 专有软件的开发者有金钱上的优势，而自由软件开发者需要为彼此创造优势。使用普通GPL的函数库给予自由软件开发者一个超越专有软件开发者的优势：能够使用按照普通GPL发布的函数库，而专有软件的开发者不能使用这些库。

note: type: Content of: <div><p>
en: Using the ordinary GPL is not advantageous for every library.  There are reasons that can make it better to use the Lesser GPL in certain cases.  The most common case is when a free library's features are readily available for proprietary software through other libraries.  In that case, the library cannot give free software any particular advantage, so it is better to use the Lesser GPL for that library.
zh_CN: 使用普通GPL并非对每个函数库都有好处。在某些情况下，使用LGPL更好些。最常见的情况是，专有软件可以通过其他函数库来实现使用自由软件函数库的功能。在这种情况下，该函数库不能给自由软件带来任何特别的好处，所以最好对它使用LGPL许可证。

note: type: Content of: <div><p>
en: This is why we used the Lesser GPL for the GNU C library.  After all, there are plenty of other C libraries; using the GPL for ours would have driven proprietary software developers to use another&mdash;no problem for them, only for us.
zh_CN: 这就是为什么我们对GNU C库使用LGPL的原因。毕竟，世界上有那么多的C函数库；让我们的C库使用GPL许可证会迫使专有软件的开发者去使用其他的C库&mdash;对他们不是问题，对我们则是。

note: type: Content of: <div><p>
en: However, when a library provides a significant unique capability, like GNU Readline, that's a horse of a different color.  The Readline library implements input editing and history for interactive programs, and that's a facility not generally available elsewhere.  Releasing it under the GPL and limiting its use to free programs gives our community a real boost.  At least one application program is free software today specifically because that was necessary for using Readline.
zh_CN: 然而，当一个函数库提供了一个重要并独一无二的功能的时候，像GNU Readline，这又是另一回事了。Readline函数库实现了输入编辑和为交互程序提供历史记录的功能，而这些功能在其他库中一般是没有的。在GPL下发布它并把它的使用限制在自由软件中，这是对我们社区的一种实际帮助。今天，至少有一个应用软件就是因为需要使用Readline库而成为自由软件的。

note: type: Content of: <div><p>
en: If we amass a collection of powerful GPL-covered libraries that have no parallel available to proprietary software, they will provide a range of useful modules to serve as building blocks in new free programs.  This will be a significant advantage for further free software development, and some projects will decide to make software free in order to use these libraries.  University projects can easily be influenced; nowadays, as companies begin to consider making software free, even some commercial projects can be influenced in this way.
zh_CN: 如果我们聚集了大量的、功能强大的GPL函数库，而且它们没有专有软件的替代品，它们就会为开发新的自由软件提供广阔的可用模块。这对进一步开发自由软件是一个显著的优势，而且有些项目为了使用这些库，会决定把软件变成自由软件。大学的项目容易被影响；目前，当有公司开始考虑把软件变成自由软件的时候，这甚至也可能会影响到一些商业项目。

note: type: Content of: <div><p>
en: Proprietary software developers, seeking to deny the free competition an important advantage, will try to convince authors not to contribute libraries to the GPL-covered collection.  For example, they may appeal to the ego, promising &ldquo;more users for this library&rdquo; if we let them use the code in proprietary software products.  Popularity is tempting, and it is easy for a library developer to rationalize the idea that boosting the popularity of that one library is what the community needs above all.
zh_CN: 专有软件的开发者企图否定自由竞争这么一个重要的优势，他们将试图说服作者不要把函数库放到GPL库中。例如，他们可能会推崇自我意识，保证如果我们让他们在专有软件产品中使用这些代码，那么&ldquo;就会有更多的用户使用该库&rdquo;。普及是一种诱惑，而且函数库的开发者容易认为帮助软件库普及是社区最需要的。

note: type: Content of: <div><p>
en: But we should not listen to these temptations, because we can achieve much more if we stand together.  We free software developers should support one another.  By releasing libraries that are limited to free software only, we can help each other's free software packages outdo the proprietary counterparts.  The whole free software movement will have more popularity, because free software as a whole will stack up better against the competition.
zh_CN: 但是我们不应该听信这些诱惑，因为如果团结在一起，我们会取得多得多的成就。我们这些自由软件开发者必须相互支持。通过把函数库局限在自由软件中，我们可以使得相互的自由软件超越同类的专有软件。整个的自由软件运动也会因为自由软件在竞争中整体上获得优势而变得更加普及。

note: type: Content of: <div><div><p>
en: 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>.
zh_CN: 请将有关自由软件基金会（FSF）&amp;GNU的一般性问题发送到<a href="mailto:gnu@gnu.org">&lt;gnu@gnu.org&gt;</a>。也可以通过<a href="/contact/">其他联系方法</a>联系自由软件基金会（FSF）。请将无效链接、其他错误或建议发送给<a href="mailto:webmasters@gnu.org">&lt;webmasters@gnu.org&gt;</a>。

note: 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 hr
en: Please see the <a href="/server/standards/README.translations.html">Translations README</a> for information on coordinating and contributing translations of this article.
zh_CN: 我们尽最大努力来提供精准和高质量的翻译，但难免会存在错误和不足。如果您在这方面有评论或一般性的建议，请发送至 <a href="mailto:web-translators@gnu.org">&lt;web-translators@gnu.org&gt;</a>。</p><p>关于进行协调与提交翻译的更多信息参见 <a href="/server/standards/README.translations.html">《译者指南》</a>。

note: type: Content of: <div><p>
en: 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>.
zh_CN: 本页面使用<a rel="license" href="http://creativecommons.org/licenses/by-nd/4.0/">Creative Commons Attribution-NoDerivatives 4.0 International License</a>授权。

note: TRANSLATORS: Use space (SPC) as msgstr if you don't want credits. type: Content of: <div><div>
en: *GNUN-SLOT: TRANSLATOR'S CREDITS*
zh_CN: <b>翻译</b>: 陈亮<br></br>
    <b>审校</b>: 刘昭宏 <a href="mailto:chliu@gnu.org">&lt;chliu@gnu.org&gt;</a><br></br>
    <b>翻译团队</b>：<a rel="team" href="https://savannah.gnu.org/projects/www-zh-cn/">&lt;CTT&gt;</a>，2018-2019，2022。

note: timestamp start type: Content of: <div><p>
en: Updated:
zh_CN: 最后更新：
