www-commits
[Top][All Lists]
Advanced

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

www/licenses/po identify-licenses-clearly.zh-cn.po


From: Wensheng XIE
Subject: www/licenses/po identify-licenses-clearly.zh-cn.po
Date: Sun, 1 Sep 2019 05:23:03 -0400 (EDT)

CVSROOT:        /web/www
Module name:    www
Changes by:     Wensheng XIE <wxie>     19/09/01 05:23:03

Added files:
        licenses/po    : identify-licenses-clearly.zh-cn.po 

Log message:
        zh-cn: new translation

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/identify-licenses-clearly.zh-cn.po?cvsroot=www&rev=1.1

Patches:
Index: identify-licenses-clearly.zh-cn.po
===================================================================
RCS file: identify-licenses-clearly.zh-cn.po
diff -N identify-licenses-clearly.zh-cn.po
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ identify-licenses-clearly.zh-cn.po  1 Sep 2019 09:23:02 -0000       1.1
@@ -0,0 +1,407 @@
+# Simplified Chinese translation of 
https://www.gnu.org/licenses/identify-licenses-clearly.html
+# Copyright (C) 2019 Free Software Foundation, Inc.
+# This file is distributed under the same license as the original article.
+# Wensheng Xie <address@hidden>, 2019.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: identify-licenses-clearly.html\n"
+"POT-Creation-Date: 2018-02-18 21:56+0000\n"
+"PO-Revision-Date: 2019-09-01 17:20+0800\n"
+"Last-Translator: Wensheng Xie <address@hidden>\n"
+"Language-Team: Chinese <address@hidden>\n"
+"Language: zh_CN\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. type: Content of: <title>
+msgid ""
+"Don't Say &ldquo;Licensed under GNU GPL 2&rdquo;! - GNU Project - Free "
+"Software Foundation"
+msgstr ""
+"请不要说 &ldquo;使用 GNU GPL 2 授权&rdquo;! - GNU 工程 - 
自由软件基金会"
+
+#. type: Content of: <h2>
+msgid ""
+"For Clarity's Sake, Please Don't Say &ldquo;Licensed under GNU GPL 2&rdquo;!"
+msgstr "为了明确,请不要说 &ldquo;使用 GNU GPL 2 授权&rdquo;!"
+
+#. type: Content of: <p>
+msgid ""
+"by <a href=\"http://www.stallman.org/\";><strong>Richard Stallman</strong></a>"
+msgstr ""
+"<a href=\"http://www.stallman.org/\";><strong>Richard Stallman</strong></a> 
著"
+
+#. type: Content of: <p>
+msgid ""
+"When I wrote the GNU General Public License (GNU GPL), in 1989, I recognized "
+"that changes might be necessary: the FSF might someday have reasons to "
+"publish a new version. So I called the license &ldquo;version 1,&rdquo; and "
+"set up a framework to enable users to upgrade programs to later license "
+"versions."
+msgstr ""
+"当我在 1989 年写成 GNU 通用公共许可证(GNU 
GPL)时,我就意识到它将来会有所更"
+"改:FSF 可能需要在未来的某一天发布一个新的版本。因
此,我把那个版本的许可证叫"
+"做 &ldquo;版本 1&rdquo;,并且构建了一套å…
è®¸ç”¨æˆ·å°†ç¨‹åºè®¸å¯è¯å‡çº§åˆ°åŽæ¥ç‰ˆæœ¬çš„框"
+"架。"
+
+#. type: Content of: <p>
+msgid ""
+"There was no customary way of doing this with a free license; as far as I "
+"know, it had never been done before. Developers had released a new version "
+"of a program under a different license, and maybe they had made new releases "
+"of old versions offering use under a different license, but they had never "
+"set up a systematic way to offer users the choice of using a future license "
+"version for already-released versions of a program."
+msgstr ""
+"当时并没有一个升级自由软件许可证的惯用方法;就我所知,以前也从来没有人这么做"
+"过。开发者
使用一个不同的许可证发布软件的新版本,他们也可能使用一个不同的许可"
+"证作老版本软件的新发布,但是从来也没有为用户提供选择已发布程序要使用的新版许"
+"可证的系统方法。"
+
+#. type: Content of: <p>
+msgid ""
+"I did not know how developers would respond to this innovation, so I decided "
+"to give each developer a choice about allowing future versions. This meant "
+"developers could release a program under GNU GPL version 1 <b>only</b>, or "
+"release it under GPL version 1 <b>or any later version</b>. The way "
+"developers state their choice is in the <b>license notice</b> that goes at "
+"the start of each source file. That's where the GPL says the decision is "
+"stated."
+msgstr ""
+"我并不知道开发者
对这个新事物的反应,所以我决定让每个开发者
自己选择新版许可证"
+"的使用。这就意味着开发者可以按照 <b>仅</b> 使用 GNU GPL 
版本 1 授权,或者使"
+"用 GPL 版本 1 <b>或任何以后版本</b> 授权。开发者
可以在每个源文件开头的 <b>许"
+"可证声明</b> 处陈述他们的选择。GPL 就是这么说的。"
+
+#. type: Content of: <p>
+msgid ""
+"The Free Software Foundation urged developers to choose <b>or any later "
+"version</b>, since that meant users would be free to use that program under "
+"GNU GPL version 1, or under version 2 (once there was a version 2), or under "
+"version 3 (once there was a version 3). And they will be free to use it "
+"under version 4, if we ever have to make a version 4."
+msgstr ""
+"自由软件基金会敦促开发者选择 
<b>或任何以后版本</b>,这样的话,用户就有自由按"
+"照 GNU GPL 版本 1、或版本 2(一旦有了版本 2)、或版本 
3(一旦有了版本 3)来使"
+"用程序。而他们也有自由按照版本 4 
使用程序,如果将来我们要发布版本 4。"
+
+#. type: Content of: <p>
+msgid ""
+"Since then, the FSF has released GNU GPL version 2 in 1991 and version 3 in "
+"2007. Each version offers developers the choice to insist on that one "
+"license version only, or permit use under future license versions. (GPL 3 "
+"also permits the &ldquo;proxy&rdquo; option, where a specified Web page can "
+"subsequently give permission to use a particular future version.)"
+msgstr ""
+"从那时起,FSF 先后在 1991 年发布了 GNU GPL 版本 2,在 2007 
年发布了版本 3。每"
+"个版本都为开发者提供了只使用一个许可证版本、或å…
è®¸ä½¿ç”¨å°†æ¥çš„许可证版本这两个"
+"选项。(GPL 3 还允许 &ldquo;代理&rdquo; 
选项,它会指向一个特定的网页,该网页"
+"会指明程序所用许可证的将来版本。)"
+
+#. type: Content of: <p>
+msgid ""
+"Publishing programs with license upgrade permission is vital to avoid "
+"incompatibility between programs released under different GPL versions."
+msgstr "允许程序的许可证升级对使用不同版本 GPL 
发布的程序保持兼容性非常重要。"
+
+#. type: Content of: <p>
+msgid ""
+"Two different copyleft licenses are almost inevitably incompatible in the "
+"absence of some explicit compatibility mechanism. That is because each one "
+"necessarily requires modified versions of a program to be released under "
+"that very same license. As a consequence, code released under GPL version 2 "
+"only can't be merged with code released under GPL version 3 only."
+msgstr ""
+"如果缺失明确的兼容机制,那么两个不同的 copyleft 
许可证将很难保持兼容。其原因"
+"就是每个许可证都必然会要求修改按照完全一æ 
·çš„许可证发布。后果就是,仅按照 "
+"GPLv2 发布的代码无法和仅按照 GPLv3 发布的程序合并。"
+
+#. type: Content of: <p>
+msgid ""
+"The mechanism for compatibility between GPL versions is to release a program "
+"under &ldquo;version N or any later version.&rdquo; A program released under "
+"GPL-2.0-or-later can be merged with code under GPL-3.0-or-later, because "
+"&ldquo;3 or later&rdquo; is a subset of &ldquo;2 or later&rdquo;."
+msgstr ""
+"GPL 各版本之间的兼容机制就是让程序可以按照遵循 
&ldquo;版本 N 或任何以后版本"
+"&rdquo; 来发布。按照 GPL-2.0-或-以后版 发布的程序可以和按ç…
§ GPL-3.0-或-以后"
+"版 的代码合并,因为 &ldquo;3 或以后版&rdquo; 是 &ldquo;2 
或以后版&rdquo; 的子"
+"集。"
+
+#. type: Content of: <p>
+msgid ""
+"Some developers say, &ldquo;I will release now under GNU GPL version 3 "
+"only.  When I see GPL version 4, if I like it, I will relicense my program "
+"to allow use under version 4.&rdquo; That will work fine if you are the only "
+"author, provided you're still alive, healthy, contactable, and paying "
+"attention at that time. But copyright lasts an insanely long time nowadays; "
+"in the absence of major reforms, the copyright on your code will last 70 "
+"years after your death, in the US (and 100 years, in Mexico). Have you made "
+"arrangements for your heirs to consider the question of relicensing your "
+"code to GPL version 4 if you are no longer around to consider it?"
+msgstr ""
+"有些开发者说,&ldquo;我目前只按照 GNU GPLv3 发布软件。当 
GPLv4 发布时,如果我"
+"喜欢,我会把我的程序重新按照版本 4 发布。&rdquo;如果你
是唯一的作者,这个行得"
+"通,还得假定你健在、健康、联系得上、å…
³æ³¨è¿™ä»¶äº‹ã€‚但是现今的版权会持续非常长的"
+"时间;如果没有大的变化,在美国,代码的版权在你死后 
70 年都有效(墨西哥是 100 "
+"年)。如果你不在场,难道你已经让继承者考虑重新按照 
GPL 版本 4 来发布你的代"
+"码?"
+
+#. type: Content of: <p>
+msgid ""
+"But trouble will happen even during your lifetime. What if we release GNU "
+"GPL version 4 ten years from now, and by that time 50 others have added to "
+"your program, releasing their added code under GPL-3.0-only simply because "
+"you did? You could approve GPL 4 for the program you initially released, but "
+"it would be a big job to contact the 50 subsequent developers at that time "
+"to get their permission for GPL 4 usage of their additions."
+msgstr ""
+"但是在你的有生之年就会烦恼不断。如果我们在 10 
年后发布了 GNU GPL 版本 4,假定"
+"那时已经有 50 个人为你的程序添加了代ç 
ï¼Œéš¾é“他们就应该仅仅是因为你选择按照仅"
+"使用 GPL-3.0 发布就必须继续这样?你也许可以批准你
的原始程序使用 GPL 4,但是联"
+"系其他 50 个程序员来获取他们的许可是一个艰巨的工作。"
+
+#. type: Content of: <p>
+msgid ""
+"The way to avoid these problems is by approving future GPL versions in the "
+"license notice at the outset. Please put on each nontrivial file of the "
+"source release a license notice of the form shown at the end of the GPL "
+"version you are using."
+msgstr ""
+"避免这些麻烦的方法就是在许可证声明里批准使用将来的 
GPL 版本。请在每个源文件的"
+"许可证声明里加上你所使用的 GPL 版本末尾的许可证声明。"
+
+#. type: Content of: <p>
+msgid ""
+"Because we handle license compatibility this way, when people tell you a "
+"program is released &ldquo;under GNU GPL version 2,&rdquo; they are leaving "
+"the licensing of the program unclear. Is it released under GPL-2.0-only, or "
+"GPL-2.0-or-later? Can you merge the code with packages released under "
+"GPL-3.0-or-later?"
+msgstr ""
+"由于我们这样处理许可证兼容性的问题,当人们告诉你
一个程序是按照 &ldquo;GNU "
+"GPLv2&rdquo; 发布的,那么他们没有理清
该程序的许可证状态。它是仅按照 GPL-2.0 "
+"发布,还是按照 GPL-2.0-或者-以后版 发布?你
是否可以把它和按照 GPL-3.0-或者-以"
+"后版 发布的软件合并?"
+
+#. type: Content of: <p>
+msgid ""
+"When sites such as GitHub invite developers to choose &ldquo;GPL 3&rdquo; or "
+"&ldquo;GPL 2&rdquo; among other license options, and don't raise the issue "
+"of future versions, this leads thousands of developers to leave their code's "
+"licensing unclear. Asking those users to choose between &ldquo;only&rdquo; "
+"and &ldquo;or later&rdquo; would lead them to make their code's licensing "
+"clear. It also provides an opportunity to explain how the latter choice "
+"avoids future incompatibility."
+msgstr ""
+"当诸如 GitHub 这样的网站邀请开发者选择按照 &ldquo;GPL 
3&rdquo; 或者 &ldquo;"
+"GPL 2&rdquo; 
等许可证来发布时,并没有提出许可证将来版本的问题,这就导致数以千"
+"计的开发者没有理清他们代ç 
çš„许可证。如果请这些用户在 &ldquo;仅&rdquo; 和 "
+"&ldquo;或者将来版&rdquo; 之间选择,那么他们代ç 
çš„许可证问题就会比较清晰。这也"
+"让大家有机会了解后一个选项如何避免了许可证未来的不å…
¼å®¹æ€§ã€‚"
+
+#. type: Content of: <p>
+msgid ""
+"Abbreviated license indicators such as &ldquo;GPL-2.0&rdquo; or &ldquo;"
+"GPL-3.0&rdquo; will lead to confusion too. People and organizations that "
+"don't recognize the difference between &ldquo;2 only&rdquo; and &ldquo;2 or "
+"later&rdquo; will be prone to write &ldquo;GPL-2.0&rdquo; in both cases, not "
+"realizing there is a distinction to be made."
+msgstr ""
+"象 &ldquo;GPL-2.0&rdquo; 或者 &ldquo;GPL-3.0&rdquo; 这æ 
·çš„许可证缩写也会导致"
+"混乱。人们或其他组织无法区分 &ldquo;仅 2&rdquo; 和 &ldquo;2 
或以后版&rdquo; "
+"之间的区别,他们就可能都写成 &ldquo;GPL-2.0&rdquo;,而实际
上两者是应该明确区"
+"分的。"
+
+#. type: Content of: <p>
+msgid "Therefore, when you use SPDX license indicators, please use these:"
+msgstr ""
+"因此,如果你要使用 SPDX<sup><a href=\"#TransNote1\">1</a></sup> 
许可证缩减"
+"版,请使用以下:"
+
+#. type: Content of: <ul><li>
+msgid "GPL-2.0-only or GPL-2.0-or-later"
+msgstr "GPL-2.0-only 或者 GPL-2.0-or-later"
+
+#. type: Content of: <ul><li>
+msgid "GPL-3.0-only or GPL-3.0-or-later"
+msgstr "GPL-3.0-only 或者 GPL-3.0-or-later"
+
+#. type: Content of: <ul><li>
+msgid "LGPL-2.0-only or LGPL-2.0-or-later"
+msgstr "LGPL-2.0-only 或者 LGPL-2.0-or-later"
+
+#. type: Content of: <ul><li>
+msgid "LGPL-2.1-only or LGPL-2.1-or-later"
+msgstr "LGPL-2.1-only 或者 LGPL-2.1-or-later"
+
+#. type: Content of: <ul><li>
+msgid "LGPL-3.0-only or LGPL-3.0-or-later"
+msgstr "LGPL-3.0-only 或者 LGPL-3.0-or-later"
+
+#. type: Content of: <ul><li>
+msgid "AGPL-3.0-only or AGPL-3.0-or-later"
+msgstr "AGPL-3.0-only 或者 AGPL-3.0-or-later"
+
+#. type: Content of: <ul><li>
+msgid "GFDL-1.3-only or GFDL-1.3-or-later"
+msgstr "GFDL-1.3-only 或者 GFDL-1.3-or-later"
+
+#. type: Content of: <p>
+msgid ""
+"Please do not use the old, ambiguous license indicators, which will be "
+"deprecated:"
+msgstr 
"请不要使用过去的、模糊的许可证缩写,它们就要被废弃:"
+
+#. type: Content of: <ul><li>
+msgid "GPL-2.0"
+msgstr "GPL-2.0"
+
+#. type: Content of: <ul><li>
+msgid "GPL-3.0"
+msgstr "GPL-3.0"
+
+#. type: Content of: <ul><li>
+msgid "LGPL-2.0"
+msgstr "LGPL-2.0"
+
+#. type: Content of: <ul><li>
+msgid "LGPL-2.1"
+msgstr "LGPL-2.1"
+
+#. type: Content of: <ul><li>
+msgid "LGPL-3.0"
+msgstr "LGPL-3.0"
+
+#. type: Content of: <ul><li>
+msgid "AGPL-3.0"
+msgstr "AGPL-3.0"
+
+#. type: Content of: <ul><li>
+msgid "GFDL-1.3."
+msgstr "GFDL-1.3."
+
+#. type: Content of: <p>
+msgid ""
+"Giving developers the choice of GPL version &ldquo;1 only&rdquo; or GPL "
+"version &ldquo;1 or later&rdquo; seemed obligatory in 1989, but it has "
+"created a complexity that we would be better off without. Meanwhile, several "
+"licenses that unconditionally give users the choice to upgrade to later "
+"license versions have become widely accepted. These include the Mozilla "
+"Public License, the Eclipse Public License, and all the Creative Commons "
+"licenses. Each version says that a user is free to use the work under later "
+"versions, if any, of the same license."
+msgstr ""
+"让开发者有权利选择 GPL 版本 &ldquo;仅 1&rdquo; 或者 GPL 版本 
&ldquo;1 或以后"
+"版&rdquo; 在 1989 年看起来是必
须的,但是它带来的复杂性比没有这个选项更多。同"
+"时,好多无
条件给予用户选择升级到以后版的许可证被广泛的接受。它们åŒ
…括 Mozilla "
+"公共许可证,Eclipse 公共许可证以及全部的 Creative Commons 
许可证。每个版本都"
+"说明用户有自由选择以后版的该许可证,如果有的话。"
+
+#. type: Content of: <p>
+msgid ""
+"Perhaps we should switch to that approach for future versions of the GNU "
+"GPL. But that is something to think about in the future."
+msgstr ""
+"我们也许在将来的 GNU GPL 版本上也采取这æ 
·çš„策略。但这是将来要考虑的事情。"
+
+#. type: Content of: <p>
+msgid ""
+"We thank SPDX for deciding to change the the short identifiers for the GNU "
+"family of licenses to make the &ldquo;or later&rdquo; versus &ldquo;"
+"only&rdquo; choice explicit. The upcoming version of the SPDX License List "
+"for license identifiers will use the identifiers recommended above. The "
+"confusing identifiers, such as &ldquo;GPL-2.0,&rdquo; will be deprecated. We "
+"ask people to replace them with the new unambiguous identifiers as soon as "
+"possible."
+msgstr ""
+"我们感谢 SPDX 决定为 GNU 许可证家族修改缩写,这样就使 
&ldquo;或者以后版"
+"&rdquo; 和 &ldquo;仅&rdquo; 变得明确。SPDX 
许可证列表下一版的缩写就会包含我们"
+"上面建议的缩写。而那些产生混淆的缩写,比如 
&ldquo;GPL-2.0&rdquo; 会被废弃。我"
+"们恳求大家尽可能地把旧的缩写换成新的明确的许可证缩写。"
+
+#. type: Content of: <p>
+msgid ""
+"By using identifiers that are explicit as to <b>only</b> or <b>any later "
+"version</b>, we can make the community aware of the difference and encourage "
+"developers to state their decisions clearly."
+msgstr ""
+"通过明确使用 <b>仅</b> 或者 
<b>任何以后版本</b>,我们能够让社区明白这些不同,"
+"并且鼓励开发者清新地表述他们的决定。"
+
+#. TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.
+#. type: Content of: <div>
+msgid "*GNUN-SLOT: TRANSLATOR'S NOTES*"
+msgstr ""
+"<h3>译注</h3>\n"
+"<ol>\n"
+"<li id=\"TransNote1\">SPDX,Software Package Data Exchange. 
这是一个沟通软件"
+"组成(组件、许可证、版权和安全参考)的开放æ 
‡å‡†ã€‚</li>\n"
+"</ol>"
+
+#. type: Content of: <div><div><p>
+msgid ""
+"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;webmasters@gnu."
+"org&gt;</a>."
+msgstr ""
+"请将有关自由软件基金会(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>。"
+
+#
+#
+#
+#.  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>. 
+#. 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 submitting "
+"translations of this article."
+msgstr ""
+"我们尽最大努力来提供精准和高质量的翻译,但难å…
ä¼šå­˜åœ¨é”™è¯¯å’Œä¸è¶³ã€‚如果您在这方"
+"面有评论或一般性的建议,请发送至 <a 
href=\"mailto:address@hidden";
+"\">&lt;address@hidden&gt;</a>。</p><p>å…
³äºŽè¿›è¡Œåè°ƒä¸Žæäº¤ç¿»è¯‘的更多信"
+"息参见 <a href=\"/server/standards/README.translators.html\">《译者
指南》</"
+"a>。"
+
+#. type: Content of: <div><p>
+msgid "Copyright &copy; 2017, 2018 Free Software Foundation, Inc."
+msgstr "Copyright &copy; 2017, 2018 Free Software Foundation, Inc."
+
+#. 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 ""
+"本页面使用 <a rel=\"license\" 
href=\"http://creativecommons.org/licenses/by-";
+"nd/4.0/\">Creative Commons Attribution-NoDerivatives 4.0 International "
+"License</a> 授权。"
+
+#. TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.
+#. type: Content of: <div><div>
+msgid "*GNUN-SLOT: TRANSLATOR'S CREDITS*"
+msgstr ""
+"<b>翻译团队</b>:<a rel=\"team\" 
href=\"https://savannah.gnu.org/projects/";
+"www-zh-cn/\">&lt;CTT&gt;</a>,2019。"
+
+#.  timestamp start 
+#. type: Content of: <div><p>
+msgid "Updated:"
+msgstr "最后更新:"



reply via email to

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