lgpl-java.html - en to zh_CN translation catalogue (16 entries)

note: type: Content of: <title>
en: The LGPL and Java - GNU Project - Free Software Foundation
zh_CN: LGPL 和 Java - GNU 工程 - 自由软件基金会

note: type: Content of: <div><h2>
en: The LGPL and Java
zh_CN: LGPL 和 Java

note: type: Content of: <div><address>
en: by <a href="mailto:licensing@fsf.org">David Turner</a>
zh_CN: <a href="mailto:licensing@fsf.org">David Turner</a> 著

note: type: Content of: <div><div><p>
en: This article was written in November 2004, when <a href="/licenses/old-licenses/lgpl-2.1.html">LGPLv2.1</a> was the most current version of the license.  Since then, <a href="/licenses/lgpl-3.0.html">LGPLv3</a> has been published.  The main points of this article remain true about LGPLv3, but some of the details, such as section numbers, have changed.
zh_CN: 本文撰写于 2004 年 11 月，当时 <a href="/licenses/old-licenses/lgpl-2.1.html">LGPLv2.1</a> 是最新的许可证版本。随后，<a href="/licenses/lgpl-3.0.html">LGPLv3</a> 发布。本文的主要观点对 LGPLv3 来说也是正确的，但是其中一些细节，诸如章节号等，有些变化。

note: type: Content of: <div><p>
en: It has always been the FSF's position that dynamically linking applications to libraries creates a single work derived from both the library code and the application code.  The GPL requires that all derivative works be licensed as a whole under the terms of the GPL, an effect which can be described as &ldquo;hereditary.&rdquo; So, if an application links to a library licensed under the GPL, the application too must be licensed under the GPL.  By contrast, libraries licensed under the GNU Lesser General Public License (LGPL) may be linked to proprietary applications.
zh_CN: FSF 一直以来的立场都是如果把应用和库动态的连接到一起，就构成了一个由库代码和应用代码共同创建的单一衍生作品。GPL 许可证要求所有衍生作品都要作为一个整体遵循 GPL 的条款，这个效果可以用 &ldquo;遗传&rdquo; 一词来描述。因此，如果一个应用连接到一个按照 GPL 发布的库，那么该应用也必须按照 GPL 授权。反之，按照 GNU 宽通用公共许可证（LGPL）授权的库可以被专有的应用连接。

note: type: Content of: <div><p>
en: In July of 2003, Slashdot published a story claiming that I had claimed that the LGPL did not function as intended in the case of Java.  This story was based on a misunderstanding of a response to a question sent to licensing@gnu.org, and many attempts to clarify the issue in the Slashdot story did not get across.  I have received numerous questions about the story since, via both licensing@gnu.org and personal email.
zh_CN: 在 2003 年 7 月，Slashdot 发表了一篇文章，声称我说 LGPL 对 Java 而言不是按照预想的方式执行的。该文章基于一篇对发给 licensing@gnu.org 的问题回复的错误理解之上，而且对 Slashdot 文章的多次澄清努力都未能奏效。此后，我收到了关于此文的众多疑问，有发到 licensing@gnu.org 的，也有发到我的私人邮箱的。

note: type: Content of: <div><p>
en: FSF's position has remained constant throughout: the LGPL works as intended with all known programming languages, including Java.  Applications which link to LGPL libraries need not be released under the LGPL.  Applications need only follow the requirements in section 6 of the LGPL: allow new versions of the library to be linked with the application; and allow reverse engineering to debug this.
zh_CN: FSF 的立场始终如一：LGPL 对所有已知编程语言都一样，包括 Java。连接 LGPL 库的应用不一定要按照 LGPL 授权。该应用只需遵循 LGPL 第 6 节中的要求：允许新的库版本连接到该应用；并且允许使用反向工程的方法来调试。

note: type: Content of: <div><p>
en: The typical arrangement for Java is that each library an application uses is distributed as a separate JAR (Java Archive) file.  Applications use Java's &ldquo;import&rdquo; functionality to access classes from these libraries.  When the application is compiled, function signatures are checked against the library, creating a link.  The application is then generally a derivative work of the library.  So, the copyright holder for the library must authorize distribution of the work.  The LGPL permits this distribution.
zh_CN: Java 程序的典型配置是应用用到的每个库都以一个独立的 JAR（Java Archive）文件来分发。应用使用 Java 的 &ldquo;import&rdquo; 机制来访问库中的类。当应用编译之后，系统根据库的签名来创建链接。那么应用一般来说就是库的一个衍生作品。因此，库的版权所有者必须授权该作品的发布。LGPL 允许这样的发布。

note: type: Content of: <div><p>
en: If you distribute a Java application that imports LGPL libraries, it's easy to comply with the LGPL.  Your application's license needs to allow users to modify the library, and reverse engineer your code to debug these modifications.  This doesn't mean you need to provide source code or any details about the internals of your application. Of course, some changes the users may make to the library may break the interface, rendering the library unable to work with your application.  You don't need to worry about that&mdash;people who modify the library are responsible for making it work.
zh_CN: 如果你发布的 Java 应用要导入 LGPL 库，那么它很容易符合 LGPL 许可证的要求。你应用的许可证需要允许用户修改该库，并且允许通过对你的代码进行反向工程来调试这些修改。这并不意味着你需要提供源代码或你应用的内部详解。你不必担心这些&mdash;&mdash;修改库的人负责让这一切能够正常工作。

note: type: Content of: <div><p>
en: When you distribute the library with your application (or on its own), you need to include source code for the library.  But if your application instead requires users to obtain the library on their own, you don't need to provide source code for the library.
zh_CN: 当你和应用一起发布库（或者单独发布库）时，你需要包含库的源代码。但是如果你的应用需要用户自己去获取库，那么你就不需要提供库的源代码。

note: type: Content of: <div><p>
en: The only difference between Java and C from the LGPL's perspective is that Java is an object-oriented language, supporting inheritance.  The LGPL contains no special provisions for inheritance, because none are needed.  Inheritance creates derivative works in the same way as traditional linking, and the LGPL permits this type of derivative work in the same way as it permits ordinary function calls.
zh_CN: 从 LGPL 的角度来看，Java 和 C 的区别只在于 Java 是一种面向对象的语言，它支持继承。LGPL 对继承并没有特殊的要求，因为没有必要。继承创造衍生作品的方式和传统连接是一样的，并且 LGPL 允许此类衍生作品的方式和常规函数调用也是一样的。

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="/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>：<a rel="team" href="https://savannah.gnu.org/projects/www-zh-cn/">&lt;CTT&gt;</a>，2019，2021。

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