www-commits
[Top][All Lists]
Advanced

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

www/licenses po/lgpl-java.translist po/lgpl-jav...


From: GNUN
Subject: www/licenses po/lgpl-java.translist po/lgpl-jav...
Date: Sat, 7 Dec 2019 23:28:48 -0500 (EST)

CVSROOT:        /web/www
Module name:    www
Changes by:     GNUN <gnun>     19/12/07 23:28:48

Modified files:
        licenses/po    : lgpl-java.translist lgpl-java.zh-cn.po 
Added files:
        licenses       : lgpl-java.zh-cn.html 
        licenses/po    : lgpl-java.zh-cn-en.html 

Log message:
        Automatic update by GNUnited Nations.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/lgpl-java.zh-cn.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/lgpl-java.translist?cvsroot=www&r1=1.12&r2=1.13
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/lgpl-java.zh-cn.po?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/lgpl-java.zh-cn-en.html?cvsroot=www&rev=1.1

Patches:
Index: po/lgpl-java.translist
===================================================================
RCS file: /web/www/www/licenses/po/lgpl-java.translist,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -b -r1.12 -r1.13
--- po/lgpl-java.translist      13 Dec 2018 02:28:30 -0000      1.12
+++ po/lgpl-java.translist      8 Dec 2019 04:28:48 -0000       1.13
@@ -9,6 +9,7 @@
 <span dir="ltr"><a lang="pl" hreflang="pl" 
href="/licenses/lgpl-java.pl.html">polski</a>&nbsp;[pl]</span> &nbsp;
 <span dir="ltr"><a lang="pt-br" hreflang="pt-br" 
href="/licenses/lgpl-java.pt-br.html">português&nbsp;do&nbsp;Brasil</a>&nbsp;[pt-br]</span>
 &nbsp;
 <span dir="ltr"><a lang="ru" hreflang="ru" 
href="/licenses/lgpl-java.ru.html">русский</a>&nbsp;[ru]</span> &nbsp;
+<span dir="ltr"><a lang="zh-cn" hreflang="zh-cn" 
href="/licenses/lgpl-java.zh-cn.html">简体中文</a>&nbsp;[zh-cn]</span> 
&nbsp;
 </p>
 </div>' -->
 <link rel="alternate" type="text/html" href="/licenses/lgpl-java.html" 
hreflang="x-default" />
@@ -19,4 +20,5 @@
 <link rel="alternate" type="text/html" lang="pl" hreflang="pl" 
href="/licenses/lgpl-java.pl.html" title="polski" />
 <link rel="alternate" type="text/html" lang="pt-br" hreflang="pt-br" 
href="/licenses/lgpl-java.pt-br.html" title="português do Brasil" />
 <link rel="alternate" type="text/html" lang="ru" hreflang="ru" 
href="/licenses/lgpl-java.ru.html" title="русский" />
+<link rel="alternate" type="text/html" lang="zh-cn" hreflang="zh-cn" 
href="/licenses/lgpl-java.zh-cn.html" title="简体中文" />
 <!-- end translist file -->

Index: po/lgpl-java.zh-cn.po
===================================================================
RCS file: /web/www/www/licenses/po/lgpl-java.zh-cn.po,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- po/lgpl-java.zh-cn.po       8 Dec 2019 04:01:48 -0000       1.1
+++ po/lgpl-java.zh-cn.po       8 Dec 2019 04:28:48 -0000       1.2
@@ -13,7 +13,7 @@
 "Language: zh_CN\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit"
+"Content-Transfer-Encoding: 8bit\n"
 
 #. type: Content of: <title>
 msgid "The LGPL and Java - GNU Project - Free Software Foundation"

Index: lgpl-java.zh-cn.html
===================================================================
RCS file: lgpl-java.zh-cn.html
diff -N lgpl-java.zh-cn.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ lgpl-java.zh-cn.html        8 Dec 2019 04:28:47 -0000       1.1
@@ -0,0 +1,126 @@
+<!--#set var="ENGLISH_PAGE" value="/licenses/lgpl-java.en.html" -->
+
+<!--#include virtual="/server/header.zh-cn.html" -->
+<!-- Parent-Version: 1.77 -->
+
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>LGPL 和 Java - GNU 工程 - 自由软件基金会</title>
+
+<!--#include virtual="/licenses/po/lgpl-java.translist" -->
+<!--#include virtual="/server/banner.zh-cn.html" -->
+<h2>LGPL 和 Java</h2>
+
+<p><a href="mailto:address@hidden";>David Turner</a> 著</p>
+
+<div class="announcement">
+<blockquote>
+<p>本文撰写于 2004 年 11 月,当时 <a
+href="/licenses/old-licenses/lgpl-2.1.html">LGPLv2.1</a> 
是最新的许可证版本。随后,<a
+href="/licenses/lgpl-3.0.html">LGPLv3</a> 发布。本文的主要观点对 
LGPLv3
+来说也是正确的,但是其中一些细节,诸如章
节号等,有些变化。</p>
+</blockquote>
+</div>
+
+<p>
+FSF 
一直以来的立场都是如果把应用和库动态的连接到一起,就构成了一个由库代ç
 å’Œåº”用代码共同创建的单一衍生作品。GPL
+许可证要求所有衍生作品都要作为一个整体遵循 GPL 
的条款,这个效果可以用 &ldquo;遗传&rdquo;
+一词来描述。因此,如果一个应用连接到一个按照 GPL 
发布的库,那么该应用也必须按照 GPL 授权。反之,按照 GNU
+宽通用公å…
±è®¸å¯è¯ï¼ˆLGPL)授权的库可以被专有的应用连接。 </p>
+<p>
+
+在 2003 年 7 月,Slashdot 发表了一篇文章,声称我说 LGPL 对 
Java 而言不是按照预想的方式执行的。该文章基于一篇对发给
+address@hidden 的问题回复的错误理解之上,而且对 Slashdot
+文章的多次澄清努力都未能奏效。此后,我收到了å…
³äºŽæ­¤æ–‡çš„众多疑问,有发到 address@hidden 
的,也有发到我的私人邮箱的。 </p> 
+<p>
+FSF 的立场始终如一:LGPL 对所有已知编程语言都一样,包括 
Java。连接 LGPL 库的应用不一定要按照 LGPL 
授权。该应用只需遵循
+LGPL 第 6 节中的要求:允许新的库版本连接到该应用;并且å…
è®¸ä½¿ç”¨åå‘工程的方法来调试。 </p> 
+<p>
+Java 程序的典型配置是应用用到的每个库都以一个独立的 
JAR(Java Archive)文件来分发。应用使用 Java 的
+&ldquo;import&rdquo;
+机制来访问库中的类。当应用编译之后,系统æ 
¹æ®åº“的签名来创建链接。那么应用一般来说就是库的一个衍生作品。å›
 æ­¤ï¼Œåº“的版权所有者必须授权该作品的发布。LGPL
+允许这样的发布。 </p> 
+<p>
+如果你发布的 Java 应用要导入 LGPL 库,那么它很容易符合 
LGPL
+许可证的要求。你应用的许可证需要å…
è®¸ç”¨æˆ·ä¿®æ”¹è¯¥åº“,并且允许通过对你的代ç 
è¿›è¡Œåå‘工程来调试这些修改。这并不意味着你
需要提供源代码或你应用的内部详解。你不必担
心这些&mdash;&mdash;修改库的人负责让这一切能够正常工作。 
</p> 
+<p>
+当你和应用一起发布库(或者单独发布库)时,你需要包
含库的源代码。但是如果你
的应用需要用户自己去获取库,那么你
就不需要提供库的源代码。 </p> 
+<p>
+从 LGPL 的角度来看,Java 和 C 的区别只在于 Java 
是一种面向对象的语言,它支持继承。LGPL
+对继承并没有特殊的要求,因为没有必要。继承创造
衍生作品的方式和传统连接是一样的,并且 LGPL å…
è®¸æ­¤ç±»è¡ç”Ÿä½œå“çš„方式和常规函数调用也是一样的。 </p> 
+
+<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">
+<div class="unprintable">
+
+<p>请将有关自由软件基金会(FSF) &amp; 
GNU的一般性问题发送到<a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>。也可以通过<a
+href="/contact/">其他联系方法</a>联系自由软件基金会(FSF)。有å…
³å¤±æ•ˆé“¾æŽ¥æˆ–其他错误和建议,请发送邮件到<a
+href="mailto:address@hidden";>&lt;address@hidden&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:address@hidden";>
+
+        &lt;address@hidden&gt;</a>.</p>
+
+        <p>For information on coordinating and submitting translations of
+        our web pages, see <a
+        href="/server/standards/README.translations.html">Translations
+        README</a>. -->
+我们尽最大努力来提供精准和高质量的翻译,但难å…
ä¼šå­˜åœ¨é”™è¯¯å’Œä¸è¶³ã€‚如果您在这方面有评论或一般性的建议,请发送至
 <a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>。</p><p>å…
³äºŽè¿›è¡Œåè°ƒä¸Žæäº¤ç¿»è¯‘的更多信息参见
+<a href="/server/standards/README.translators.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 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. -->
+<p>Copyright &copy; 2004, 2013, 2014 Free Software Foundation, Inc.</p>
+
+<p>本页面使用 <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/";>Creative Commons
+Attribution-NoDerivs 3.0 United States 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="https://savannah.gnu.org/projects/www-zh-cn/";>&lt;CTT&gt;</a>,2019。</div>
+
+<p class="unprintable"><!-- timestamp start -->
+最后更新:
+
+$Date: 2019/12/08 04:28:47 $
+
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>

Index: po/lgpl-java.zh-cn-en.html
===================================================================
RCS file: po/lgpl-java.zh-cn-en.html
diff -N po/lgpl-java.zh-cn-en.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ po/lgpl-java.zh-cn-en.html  8 Dec 2019 04:28:48 -0000       1.1
@@ -0,0 +1,142 @@
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.77 -->
+<title>The LGPL and Java
+- GNU Project - Free Software Foundation</title>
+<!--#include virtual="/licenses/po/lgpl-java.translist" -->
+<!--#include virtual="/server/banner.html" -->
+<h2>The LGPL and Java</h2>
+
+<p>by <a href="mailto:address@hidden";>David Turner</a></p>
+
+<div class="announcement">
+<blockquote>
+<p>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.</p>
+</blockquote>
+</div>
+
+<p>
+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. </p>
+<p>
+
+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 address@hidden, 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 address@hidden and personal email. </p> 
+<p>
+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. </p> 
+<p>
+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. </p> 
+<p>
+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. </p> 
+<p>
+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. </p> 
+<p>
+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. </p> 
+
+</div><!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<p>Please send general FSF &amp; GNU inquiries to
+<a href="mailto:address@hidden";>&lt;address@hidden&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:address@hidden";>&lt;address@hidden&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:address@hidden";>
+        &lt;address@hidden&gt;</a>.</p>
+
+        <p>For information on coordinating and submitting 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 submitting 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 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. -->
+
+<p>Copyright &copy; 2004, 2013, 2014 Free Software Foundation, Inc.</p>
+
+<p>This page is licensed under a <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/";>Creative
+Commons Attribution-NoDerivs 3.0 United States License</a>.</p>
+
+<!--#include virtual="/server/bottom-notes.html" -->
+
+<p class="unprintable">Updated:
+<!-- timestamp start -->
+$Date: 2019/12/08 04:28:48 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>



reply via email to

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