GNU loose Public License (lgpl)

Statement!

This is an informal Chinese Translation of GNU's loose Public License. It is not released by the Free Software Foundation and cannot be applied to software using GNU lgpl-only the version of GNU lgpl in the original English version. However, we hope this translation will help Chinese users better understand GNU lgpl.

GNU loose Public License

1999.2, Version 2.1

Copyright (c) 1991,199 9 Free Software Foundation, Inc.
59 temple place, Suite 330, Boston, MA 02111-1307 USA

Each person is allowed to copy and publish a full copy of this authorization file,
However, it cannot be modified.

[This is the first published version of lesser GPL. It can also be regarded as the successor of GNU Library Public License 2nd, so it is called version 2.1]

This version is translated by Leo-hong (leohca (AT) Yahoo.com) and corrected by Chao-hong Liu.

Introduction

Most software licenses are determined to deprive you of the freedom to share and modify the software. On the contrary, the GNU General Public License strives to ensure that you are free to share and modify free software-to ensure that free software is free for all users.

This license, a loose Public License, applies to software writers who are determined by the Free Software Foundation and others to use this license, software suites specially designed-like function libraries. You can also use it, but we recommend that you carefully consider based on the following instructions whether this license or the original General Public License is a better solution in any special circumstances.

When talking about free software, we mean freedom, not price. Our GNU General Public License is designed to ensure that you have the freedom to release free software backups (if you wish, you can charge a certain fee for this service ); make sure that you receive the original code of the program or get it when you need it; Make sure that you can modify the software or use part of it for new free software; make sure that you know that you can do the above.

To protect your rights, we need to restrict the denial of your rights, or request that you give up these rights. If you publish a copy of the software or modify it, these regulations are translated into your responsibility.

For example, if you publish a copy of this function library, whether it is free or charged, you must give all your rights to the recipient; you must ensure that they can also receive or get the original code; if you link this function library with other program codes, you must provide the complete object file and Program (Object File) to the recipient. After they modify this function library and re-compile it, you can link to the target file again. You should also inform them of these terms so that they have such rights.

We take two measures to protect your rights: (1) use copyright to protect the function library. In addition, (2) we provide you with this license, giving you legal permission to copy, publish, and/or modify these function libraries.
To protect every publisher, we need to make it clear to everyone that the free function library has no warranty responsibility. If someone modifies the function library and continues to spread it, we need its recipients to understand that what they get is not the original version. Therefore, any problems introduced by others will not affect the reputation of the original author.

Finally, as software patents constantly threaten the existence of free software, we hope that commercial companies will not be able to effectively restrict the users of free software by obtaining a restricted license from their patent holders. Therefore, we insist that any patent that a function library can obtain must be consistent with the "completely free to use" stated in this license.

Most GNU software, including some function libraries, is protected by the original GNU General Public License. This license, GNU is a loose General Public License, applies to function libraries specially designed, and is very different from the original General Public License. We use it in a specific function library to allow non-free programs to connect to these function libraries. When a program is linked to a function library, whether it is a static link or a shared function library, the combination of the two can be reasonably a combination of works, a derivative of the original function library. Therefore, the original General Public License can be linked only when the entire product meets its free criteria. Loose General Public Licenses allow other code codes to be linked to this function library with looser standards.

We call this license a "loose" General Public License because it provides less protection for user freedom than the original General Public License. In the competition with non-free software, it also provides a small number of authors of other free software. These disadvantages are exactly why we used the original General Public License for many function libraries. However, loose licenses can benefit in some special cases. For example, in a few cases, there may be special needs to encourage everyone to use the specific function library as widely as possible, so that it becomes the actual standard. To achieve this goal, non-free programs must be allowed to use this function library. A common case is that a free function library works the same as a widely used non-free function library. In this case, limits that only free software can use this function library do not have much benefit, so we use a loose General Public License.

In other cases, allow non-free programs to use specific function libraries, allowing more people to use most of the free software. For example, to allow non-free programs to use the gnu c function library, more people can use the entire GNU operating system and its deformation, the GNU/Linux operating system.

Although loose generic common Public Licenses provide less protection for user freedom, they can ensure that the user of the program linked to this function library has freedom, it also has the necessary methods to run the program using the modified function library version.

The following are precise terms and conditions for reproduction, publication, and modification. Note the differences between "works based on function libraries" and "works using function libraries": the former contains the original code modified by the function library, and the latter must be combined with the function library before execution.

Terms and Conditions for reproduction, publication and Modification

0. this license applies to any software function library, or other programs that contain precautions for copyright owners, or other credible groups claim that their programs can be published under the terms of a more loose General Public License (also known as "this license. Each license recipient is called "you.

A "function library" refers to a collection of software functions, as well as prepared materials, to facilitate linking with applications (which use some of these functions and materials) to form executable programs.

The term "function library" refers to any software function library or works released under these terms, A "work based on this function library" means a function library or any derivative work under the Copyright Law: that is, a work that contains this function library or a part of it can be intact, or modified, and/or directly translated into other languages. (The translation is not limited to include in the "modification" clause below .)

The "original code" of the work indicates the most preferred form of modification to the work. For the function library, the complete original code refers to all the original programs of all modules, the definition of the interface, and the script for installing and compiling the function library.

The terms of this License do not apply to activities other than reproduction, publication, and modification. These activities are beyond the scope of these terms. Using this function library to execute this program is not restricted by the terms and conditions, the program output clause is applicable only when the work composed of the program content is based on the function library (it is irrelevant to the tool used to output the function library. Whether the above is true depends on what the function library is used.

1. as long as you clearly and appropriately declare copyright statements and do not undertake a warranty statement on each copy of the program, and maintain that the license statement and the non-Warranty statement are complete and intact, together with the program, you can copy a license to each other receiver, and then use any media to copy and publish the complete original code of the function library you have received.

You may be charged for the transfer of copies. You can also choose to provide a guarantee in exchange for a certain amount of fee.

2. as long as you meet all the following conditions, you can modify one or several copies of the function library or any part of the library as required in the first section to form works based on this function library, and copy and publish this modified program or file:

The modified file must be a software function library.

You must include a clear description in the modified file: You modified this file and any modification date.

You must allow a third party to use the entire work under the terms of this License for free.

If a device of the modified function library uses the function or data table provided by "applications using this function library", but does not use parameter columns when the device is called, then, you must make sure that the device still works and its execution is meaningful if the application does not provide such functions or tables.
(For example, a function in a function library is used to calculate the square root. Its purpose is to have a complete definition and is irrelevant to the application. Therefore, section 2D requires that any function will be used by this function, and the functions or tables provided by the application must be optional: If the application does not provide, then, the function that calculates the square root must still calculate the square root)

These requirements apply to the entire modified work. If it is determined that part of the work is not a derivative product of this function library and can be reasonably considered separately and separated from the original work, when you publish it as an independent work, it is not subject to this license and its terms. However, when you publish this part together with works based on this function library, the entire suite will be subject to the terms of this License and its use of other license holders will be extended to the entire product, that is, each part of the suite, no matter who it is written.

Therefore, the intention of these terms is not to request a right or deprive you of the right to complete the work, but to fulfill the right to control the publishing of collective works or derivative works based on this function library. In addition, files irrelevant to this function library and the function library (or files based on this function library) are stored on the same volume as the storage media or publishing media, other works are not restricted by this license.

3. for a copy of a function library, you may choose to replace the terms of this License by using the terms of the original GNU General Public License. If you want to do so, you must modify all precautions for reference to this license so that they point to the original GNU General Public License, Version 2, to replace this license (if there is a version newer than the old GNU General Public License of version 2, you can specify to use the new version if you want ). Do not make other changes to these considerations.

Once such a change is made on a copy, the copy cannot be recalled, therefore, the original GNU General Public License will apply to all subsequent copies and Works derived from this copy.

This option is optional when you want to copy part of the original code of the function library to a program that is not a function library.

4. you can copy or publish this function library (or works in accordance with section 2nd, based on this function library) as long as you comply with section 1st and section 2 above, at the same time, it provides complete machine-readable original codes, which must be released on the media that is typically used for software exchange under the first 1st and 2nd conditions.

If the published target code is a copy request from a specified location, the equivalent original code copy request provided by the same location can be counted as the original code release, even if the third party does not force the source code to be copied together with the target code.

5. If a program contains a function library that is not modified in any part, it is designed to work with the function library through compilation or linking. It is called "works using the function library ". Such a work, strictly speaking, is not a derivative work of this function library and thus is not within the scope of this License.

However, linking "works using function libraries" with this function library to generate executable programs is a derivative of this function library (because it includes part of this function library ), instead of "work using the function library", its executable program is included within the scope of this License. Section 6th describes the terms for publishing the executable program.

When "files using the function library" Use the header content of the function library, the object code of this file is still the object code even if its original code does not belong to the derivatives of the function library. Whether this is true is especially obvious when this work can be linked without the need for this function library, or whether the work itself is also a function library.

If such a target file only uses the numeric parameters, data structure level and accessories, as well as the mega and inner □formula (less than or equal to 10 rows ), the use of this target file is unrestricted, whether or not it is a legal derivative file. (However, if the executable program includes this target file and some function libraries, it will still be included in section 6th)

Otherwise, if the work is a derivative of the function library, you must publish the target code of the work under section 6th. Any executable program that contains this file is within the range of section 6th, whether or not they are directly linked to this function library.

6. as an exception to the above terms, you can also combine or link "works using the function library" with this function library to produce works that contain some of this function library, you can modify the file when you allow the user to use it, and publish the file according to your choice when performing anti-group translation and debugging on the modification.

You must note the following in a copy of each file: This function library is used in the file, and this function library and its use are subject to this license. You must provide a copy of this License. If the copyright statement is displayed during execution of the work, you must include the copyright statement of this function library and guide the user to obtain a copy of this License. At the same time, you must do one of the following:

The complete machine-readable original code of the function library must be included in the work, including any changes to the use of the work (these changes must be released as required by the aforementioned paragraphs 1st and 2nd ); in addition, if the work is a "complete" "linked to the function library, the target code and/or the original code are required, in this way, the user can modify the function library and relink it to generate a package to generate the modified executable program of the modified function library. (If the user modifies the file definition of the function library, the file cannot be re-compiled to use the modified definition .)

Use the appropriate sharing function library connection mechanism when linking to the function library. An appropriate mechanism is as follows: (1) Use a copy of the function library that already exists in the user's computer during execution, rather than copying the function of the function library to the executable program, and (2) if you have installed a modified function library, as long as the modified version is compatible with the version used in the compilation link of the file on the interface, the program runs well with the modified function library.

A written quotation shall be provided in the work for a period of not less than three years, so as to provide the content in section 6a of the same user, and the fee shall not exceed the actual cost of the program release. If the published file is a copy request from a specified location, the same location provides an equivalent copy request for the above content.

Confirm that the user has received a copy of the work, or you have sent a copy to the user.
For an executable program, the "work using the function library" format must include any information and tools required to generate the executable program. However, with a special exception, the published content does not need to include any major part (such as the compiler and core) of the "operating system that can run the program) the parts that are released together (whether the original code or executable code), unless these components and executable works are combined.

One possibility is that these requirements conflict with the copyright restrictions of other private function libraries that are usually not associated with the operating system, this conflict means that you cannot use them together with this function library in your published executable program.

7. you can put the function library devices that use this function library and other function libraries that are not in the scope of this License into a separate function library, in addition, you may agree to release a function library in other states based on the work of this function library and other function libraries. If you do the following, you can release this function library:

Works based on this function library are released together with other function library devices. This work must be published in accordance with the above terms.

In this function library, it is clearly pointed out that some of the works are based on this function library, and that works that are not in the same form can be found.
8. Unless you explicitly follow the requirements of the license, you cannot copy, modify, or forward the license, link to the function library, or publish this function library. Any attempt to copy, modify, or forward a license, link to this function library, or publish this function library in other ways is invalid and will automatically terminate the license to you. However, for those who have obtained copies and rights from you by license terms, the rights granted to them by the license remain valid as long as they continue to fully enforce the terms.

9. You have not signed the license, so you do not have to accept it. However, nothing else grants you the right to modify and publish this function library and its derivative works. If you do not accept a license, these actions are prohibited by law. Therefore, if you modify or publish a function library (or any function library-based work ), you agree to this license and all its terms and conditions for copying, publishing, and modifying this function library or its work.

10. whenever you re-release a function library (or any function library-based work, the recipient is automatically licensed from the issuer of the original license to copy, publish, link or modify the function library subject to these terms and conditions. You cannot force the recipient to fulfill the limitations other than the rights granted to them. You have no obligation to force a third party to fulfill the license terms.

11. the conditions imposed on you (whether it is a court decision, agreement, or other) as a result of the Court's decision or alleged violation of a patent or any other reason (not limited to patent issues) when there is a conflict with the license conditions, they cannot make you deviate from the license terms. If you cannot release a function library by simultaneously meeting the obligations and other related obligations stipulated in this license, you can only release the function library. For example, if a patent license does not allow anyone who accepts copies directly or indirectly from you to re-release the function library without paying the Patent Fee, the only way to meet both requirements is to stop publishing the function library.

If any part of these terms is invalid or cannot be implemented in a specific environment, the remainder of the terms will be used and the terms will be used as a whole in other environments. The purpose of these terms is not to induce you to infringe upon a patent or other property right request, or to dispute the validity of such request. The main purpose of these terms is to protect the integrity of the Free Software Release System. It is implemented through the application of Public Licenses. Many people have relied on applications from the same system, and have made generous contributions by releasing a large number of free software. The author/donor has the right to decide whether or not he/she publishes software through any other system, and the license holder cannot impose such an option.

This section aims to clarify the possible results of the remaining part of the license.

12. if the publishing and use of function libraries are restricted due to patents or copyrighted interface issues, the original copyright owner under license restrictions may add restrictions on the publishing area, exclude these countries explicitly and release function libraries outside these countries. In this case, the restrictions contained in the license suite are as valid as the license body. 13. The Free Software Foundation may publish a revised or new version of the loose General Public License at any time. The new version is consistent with the current version in principle, but may differ in details when it comes to new issues or related matters.

Each version has a different version number. If the function library specifies the applicable license version number and "any updated version", you have the right to choose a new version that will be published after the specified version or the Free Software Foundation. If no license version is specified for the function library, you can select any version that has been published by the Free Software Foundation. 14. If you are willing to integrate a part of the function library into other free programs and their publishing conditions are different, please write to the author and ask for permission. If it is software copyrighted by the Free Software Foundation and written to the Free Software Foundation, we sometimes handle exceptions. Our decisions are guided by two main goals: the continued freedom of derivative works of our free software and the overall promotion of software sharing and reuse.

No warranty
15. The function library is free of charge and is not guaranteed to the extent permitted by applicable law. Unless otherwise stated in writing, the copyright owner and/or other persons providing function libraries "do not provide any type of warranty, whether explicit or implied, includes, but is not limited to, implied warranties that are salable and applicable for specific purposes. You are responsible for all risks, such as the quality and performance problems of the function library. If the function library has any defects, you shall bear the costs of all necessary services, repairs and corrections.

16. unless required by applicable law or written agreement, no copyright owner or any person Who modifies or releases function libraries under license terms shall be liable for your losses under any circumstances. Including any general, special, accidental, or major losses (including but not limited to data losses, or data becoming inaccurate) caused by the use or inability to use the function library, or you or a third party's sustained losses, or the function library cannot coordinate with other software ). Even if the copyright owner and others mention the possibility of such a loss.

-End of provision-

How to use these terms to your new function library

If you have developed a new function library and you need it to be used by the public to the maximum extent, the best way to do this is to turn it into a free software, this allows everyone to modify and re-publish the terms in compliance with these terms (or the terms of the original General Public License.

To do this, attach the following statement to the function library. The safest way is to place it at the beginning of each original code file so that the information about the denial of guarantee can be most effectively transmitted. Each file should have at least "All rights reserved" lines and where the full text of the statement can be viewed.

Describe the name of the function library and its usage in a row of space.
Copyright (c) Name of 19xx author
This function library is a free software. You can modify and re-release this program in accordance with the GNU loose General Public License Terms published by the Free Software Foundation, or use the second version of the license, or use any updated version (based on your choice.

The purpose of publishing this function library is to make it useful, but there is no guarantee. There is even no implicit guarantee suitable for a specific purpose. For more details, see GNU's loose General Public License.

You should have received a copy of the GNU loose General Public License with the function library. If not, write:

Free Software Foundation, inc., 59 temple place-Suite 330, Boston, MA 02111-1307, USA.

In addition, information on how to maintain contact with you by email or general mail should be added.
If necessary, you shall obtain your supervisor (if you are a programmer) or your school's statement of abolishing the copyright of the function library. The following is an example. You should change the corresponding name:

Yoyodyne abandoned all copyright interests of the 'frob' function library (used to reverse the knobs function library) written by James random hacker in this way.
Ty coon signature, 1990.4.1
Vice president of Ty coon

That's all!