msgid "The LGPL and Java - GNU Project - Free Software Foundation" msgstr "" #. type: Content of: <div><h2> msgid "The LGPL and Java" msgstr "" #. type: Content of: <div><address> msgid "by <a href=\"mailto:licensing@fsf.org\">David Turner</a>" msgstr "" #. type: Content of: <div><div><p> msgid "" "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." msgstr "" #. type: Content of: <div><p> msgid "" "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 “hereditary.” 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." msgstr "" #. type: Content of: <div><p> msgid "" "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." msgstr "" #. type: Content of: <div><p> msgid "" "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." msgstr "" #. type: Content of: <div><p> msgid "" "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 " "“import” 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." msgstr "" #. type: Content of: <div><p> msgid "" "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—people who modify the library are responsible for making it work." msgstr "" #. type: Content of: <div><p> msgid "" "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." msgstr "" #. type: Content of: <div><p> msgid "" "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." msgstr "" #. TRANSLATORS: Use space (SPC) as msgstr if you don't have notes. #. type: Content of: <div> msgid "*GNUN-SLOT: TRANSLATOR'S NOTES*" msgstr "" #. type: Content of: <div><div><p> msgid "" "Please send general FSF & GNU inquiries to <a " "href=\"mailto:gnu@gnu.org\"><gnu@gnu.org></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\"><webmasters@gnu.org></a>." msgstr "" #. 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"> # #. <web-translators@gnu.org></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>. #. 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." msgstr "" #. type: Content of: <div><p> msgid "Copyright © 2004, 2013, 2014, 2021 Free Software Foundation, Inc." msgstr "" #. type: Content of: <div><p> msgid "" "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>." msgstr "" #. TRANSLATORS: Use space (SPC) as msgstr if you don't want credits. #. type: Content of: <div><div> msgid "*GNUN-SLOT: TRANSLATOR'S CREDITS*" msgstr "" #. timestamp start #. type: Content of: <div><p> msgid "Updated:" msgstr ""

# LANGUAGE translation of https://www.gnu.org/licenses/lgpl-java.html # Copyright (C) YEAR Free Software Foundation, Inc. # This file is distributed under the same license as the original article. # FIRST AUTHOR , YEAR. # #, fuzzy msgid "" msgstr "" "Project-Id-Version: lgpl-java.html\n" "POT-Creation-Date: 2021-12-25 21:25+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" "Language: \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=CHARSET\n" "Content-Transfer-Encoding: 8bit\n" #. type: Content of: msgid "The LGPL and Java - GNU Project - Free Software Foundation" msgstr "" #. type: Content of: <div><h2> msgid "The LGPL and Java" msgstr "" #. type: Content of: <div><address> msgid "by <a href=\"mailto:licensing@fsf.org\">David Turner</a>" msgstr "" #. type: Content of: <div><div><p> msgid "" "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." msgstr "" #. type: Content of: <div><p> msgid "" "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 “hereditary.” 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." msgstr "" #. type: Content of: <div><p> msgid "" "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." msgstr "" #. type: Content of: <div><p> msgid "" "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." msgstr "" #. type: Content of: <div><p> msgid "" "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 " "“import” 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." msgstr "" #. type: Content of: <div><p> msgid "" "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—people who modify the library are responsible for making it work." msgstr "" #. type: Content of: <div><p> msgid "" "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." msgstr "" #. type: Content of: <div><p> msgid "" "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." msgstr "" #. TRANSLATORS: Use space (SPC) as msgstr if you don't have notes. #. type: Content of: <div> msgid "*GNUN-SLOT: TRANSLATOR'S NOTES*" msgstr "" #. type: Content of: <div><div><p> msgid "" "Please send general FSF & GNU inquiries to <a " "href=\"mailto:gnu@gnu.org\"><gnu@gnu.org></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\"><webmasters@gnu.org></a>." msgstr "" #. 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"> # #. <web-translators@gnu.org></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>. #. 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." msgstr "" #. type: Content of: <div><p> msgid "Copyright © 2004, 2013, 2014, 2021 Free Software Foundation, Inc." msgstr "" #. type: Content of: <div><p> msgid "" "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>." msgstr "" #. TRANSLATORS: Use space (SPC) as msgstr if you don't want credits. #. type: Content of: <div><div> msgid "*GNUN-SLOT: TRANSLATOR'S CREDITS*" msgstr "" #. timestamp start #. type: Content of: <div><p> msgid "Updated:" msgstr ""