Overview

Project website docs.freebsd.org/en
Translation license BSD 2-Clause "Simplified" License
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Only chosen users can contribute.
  • The translation uses bilingual files.
File mask documentation/content/*/articles/bsdl-gpl/_index.po
Translation file Download documentation/content/zh_CN/articles/bsdl-gpl/_index.po
Last change May 31, 2025, 5:31 a.m.
Last author Yulong Han

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 82 3,642 23,048
Translated 100% 82 100% 3,642 100% 23,048
Needs editing 0% 0 0% 0 0% 0
Read-only 0% 0 0% 0 0% 0
Failing checks 0% 0 0% 0 0% 0
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 0% 0 0% 0 0% 0
Last 12 months Previous

Activity in last 12 months

42 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 35 changes 0 changes 24 changes 0 changes 2 changes 0 changes 0 changes 0 changes 0 changes 0 changes 17 changes
Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun

Quick numbers

3,642
Hosted words
82
Hosted strings
100%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
+14%
Translated
+85%
—
Contributors
—
User avatar None

Committed changes

Documentation / articles/bsdl-gpl — Chinese (Simplified) (zh_CN)

Committed changes a month ago
User avatar wheatfox

Translation changed

Documentation / articles/bsdl-gpl — Chinese (Simplified) (zh_CN)

The GPL was designed to be the antithesis of the standard proprietary license. To this end, any modifications that were made to a GPL program were required to be given back to the GPL community (by requiring that the source of the program be available to the user) and any program that used or linked to GPL code was required to be under the GPL. The GPL was intended to keep software from becoming proprietary. As the last paragraph of the GPL states:
GPL 旨在与标准专有许可证相对立。 为此，对 GPL 程序所做的任何修改都必须反馈给 GPL 社区（通过要求用户可以使用程序的源代码），并且任何使用或链接到 GPL 代码的程序都必须遵守 GPL该许可证。 GPL 的目的是防止软件成为专有软件。 正如 GPL 最后一段所述：
a month ago
User avatar wheatfox

Translation changed

Documentation / articles/bsdl-gpl — Chinese (Simplified) (zh_CN)

Richard Stallman, the developer of Emacs, was a member of the staff at MIT when his lab switched from home-grown to proprietary systems. Stallman became upset when he found that he could not legally add minor improvements to the system. (Many of Stallman's co-workers had left to form two companies based on software developed at MIT and licensed by MIT; there appears to have been disagreement over access to the source code for this software). Stallman devised an alternative to the commercial software license and called it the GPL, or "GNU Public License". He also started a non-profit foundation, the http://www.fsf.org[Free Software Foundation] (FSF), which intended to develop an entire operating system, including all associated software, that would not be subject to proprietary licensing. This system was called GNU, for "GNU is Not Unix".
Emacs 的开发者理查德·斯托曼 (Richard Stallman) 是麻省理工学院的一名员工，当时他的实验室从自制系统转向专有系统。 当斯托曼发现他无法合法地对系统进行微小改进时，他感到很沮丧。 （斯托曼的许多同事已经离开，成立了两家基于麻省理工学院开发并获得麻省理工学院许可的软件的公司；在获取该软件的源代码方面似乎存在分歧）。 斯托曼设计了商业软件许可证的替代方案，并将其称为 GPL，或“GNU 公共许可证”。 他还创办了一个非盈利基金会 http://www.fsf.org[自由软件基金会] (FSF)，该基金会旨在开发一个完整的操作系统，包括所有相关软件，并且不受专有许可的约束。 这个系统被称为 GNU，意思是“GNU 不是 Unix”。
a month ago
User avatar wheatfox

Suggestion removed

Documentation / articles/bsdl-gpl — Chinese (Simplified) (zh_CN)

Richard Stallman, the developer of Emacs, was a member of the staff at MIT when his lab switched from home-grown to proprietary systems. Stallman became upset when he found that he could not legally add minor improvements to the system. (Many of Stallman's co-workers had left to form two companies based on software developed at MIT and licensed by MIT; there appears to have been disagreement over access to the source code for this software). Stallman devised an alternative to the commercial software license and called it the GPL, or "GNU Public License". He also started a non-profit foundation, the http://www.fsf.org[Free Software Foundation] (FSF), which intended to develop an entire operating system, including all associated software, that would not be subject to proprietary licensing. This system was called GNU, for "GNU is Not Unix".
Emacs 的开发者理查德·斯托曼 (Richard Stallman) 是麻省理工学院的一名员工，当时他的实验室从自制系统转向专有系统。 当斯托曼发现他无法合法地对系统进行微小改进时，他感到很沮丧。 （斯托曼的许多同事已经离开，成立了两家基于麻省理工学院开发并获得麻省理工学院许可的软件的公司；在获取该软件的源代码方面似乎存在分歧）。 斯托曼设计了商业软件许可证的替代方案，并将其称为 GPL，或“GNU 公共许可证”。 他还创办了一个非盈利基金会 http://www.fsf.org[自由软件基金会] (FSF)，该基金会旨在开发一个完整的操作系统，包括所有相关软件，并且不受专有许可的约束。 这个系统被称为 GNU，意思是“GNU 不是 Unix”。
a month ago
User avatar wheatfox

Suggestion added

Documentation / articles/bsdl-gpl — Chinese (Simplified) (zh_CN)

Richard Stallman, the developer of Emacs, was a member of the staff at MIT when his lab switched from home-grown to proprietary systems. Stallman became upset when he found that he could not legally add minor improvements to the system. (Many of Stallman's co-workers had left to form two companies based on software developed at MIT and licensed by MIT; there appears to have been disagreement over access to the source code for this software). Stallman devised an alternative to the commercial software license and called it the GPL, or "GNU Public License". He also started a non-profit foundation, the http://www.fsf.org[Free Software Foundation] (FSF), which intended to develop an entire operating system, including all associated software, that would not be subject to proprietary licensing. This system was called GNU, for "GNU is Not Unix".
Emacs 的开发者理查德·斯托曼 (Richard Stallman) 是麻省理工学院的一名员工，当时他的实验室从自制系统转向专有系统。 当斯托曼发现他无法合法地对系统进行微小改进时，他感到很沮丧。 （斯托曼的许多同事已经离开，成立了两家基于麻省理工学院开发并获得麻省理工学院许可的软件的公司；在获取该软件的源代码方面似乎存在分歧）。 斯托曼设计了商业软件许可证的替代方案，并将其称为 GPL，或“GNU 公共许可证”。 他还创办了一个非盈利基金会 http://www.fsf.org[自由软件基金会] (FSF)，该基金会旨在开发一个完整的操作系统，包括所有相关软件，并且不受专有许可的约束。 这个系统被称为 GNU，意思是“GNU 不是 Unix”。
a month ago
User avatar wheatfox

New translation

Documentation / articles/bsdl-gpl — Chinese (Simplified) (zh_CN)

In addition, since the BSD license does not come with the legal complexity of the GPL or LGPL licenses, it allows developers and companies to spend their time creating and promoting good code rather than worrying if that code violates licensing.
此外，由于 BSD 许可证不像 GPL 或 LGPL 那样具有法律上的复杂性，它使得开发者和公司可以将时间花在编写和推广优质代码上，而不是担心这些代码是否违反了许可证规定。
a month ago
User avatar wheatfox

New translation

Documentation / articles/bsdl-gpl — Chinese (Simplified) (zh_CN)

In contrast to the GPL, which is designed to prevent the proprietary commercialization of Open Source code, the BSD license places minimal restrictions on future behavior. This allows BSD code to remain Open Source or become integrated into commercial solutions, as a project's or company's needs change. In other words, the BSD license does not become a legal time-bomb at any point in the development process.
与旨在防止开源代码被专有商业化的 GPL 不同，BSD 许可证对未来的使用行为几乎没有限制。这使得 BSD 代码既可以保持开源，也可以根据项目或公司的需求被整合进商业解决方案中。换句话说，BSD 许可证在整个开发过程中不会变成一个法律上的“定时炸弹”。
a month ago
User avatar wheatfox

New translation

Documentation / articles/bsdl-gpl — Chinese (Simplified) (zh_CN)

Non-profits should participate in Open Source projects when possible. To minimize software engineering problems, such as mixing code under different licenses, BSD-style licenses should be encouraged. Being leery of the GPL should particularly be the case with non-profits that interact with the developing world. In some locales where application of law becomes a costly exercise, the simplicity of the new BSD license, as compared to the GPL, may be of considerable advantage.
非营利组织在可能的情况下应积极参与开源项目。为了尽量减少软件工程中的问题（例如不同许可证代码的混合使用），应优先鼓励采用 BSD 风格的许可证。对于与发展中国家有合作的非营利组织，更应对 GPL 保持谨慎。在某些法律执行成本高昂的地区，相较于 GPL，新的 BSD 许可证因其简单明了，可能具有显著优势。
a month ago
User avatar wheatfox

New translation

Documentation / articles/bsdl-gpl — Chinese (Simplified) (zh_CN)

Small companies with software projects vulnerable to orphaning should attempt to use the BSD license when possible. Companies of all sizes should consider forming such Open Source projects when it is to their mutual advantage to maintain the minimal legal and organization overheads associated with a true BSD-style Open Source project.
对于那些容易被弃置的软件项目，小型公司应在可能的情况下尽量采用 BSD 许可证。对于所有规模的公司来说，当有共同利益需要维护一个开源项目时，也应考虑以真正 BSD 风格的开源方式来合作，因为这种模式能保持最小的法律和组织开销。
a month ago
User avatar wheatfox

New translation

Documentation / articles/bsdl-gpl — Chinese (Simplified) (zh_CN)

Large companies, in which Open Source code is developed, should be aware that programmers appreciate Open Source because it leaves the software available to the employee when they change employers. Some companies encourage this behavior as an employment perk, especially when the software involved is not directly strategic. It is, in effect, a front-loaded retirement benefit with potential lost opportunity costs but no direct costs. Encouraging employees to work for peer acclaim outside the company is a cheap portable benefit a company can sometimes provide with near zero downside.
大型公司在开发开源代码时应意识到，程序员之所以喜爱开源，一个重要原因是这使得他们在更换工作后仍能继续使用和访问这些软件。一些公司会鼓励这种行为，将其视为一种员工福利，尤其是在相关软件对公司并不具有直接战略意义的情况下。实际上，这相当于一种“前置式的退休福利”——它可能带来机会成本的损失，但不会产生直接费用。鼓励员工在公司外通过开源项目赢得同行认可，是一种几乎没有负面影响的廉价、可转移的福利，有时对公司来说也非常划算。
a month ago
Browse all translation changes