www/licenses po/gpl-howto.translist gpl-howto.z...

[GNUN]

CVSROOT:        /web/www
Module name:    www
Changes by:     GNUN <gnun>     19/06/16 09:00:27

Modified files:
        licenses/po    : gpl-howto.translist 
Added files:
        licenses       : gpl-howto.zh-cn.html 
        licenses/po    : gpl-howto.zh-cn-en.html 

Log message:
        Automatic update by GNUnited Nations.

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

Patches:
Index: po/gpl-howto.translist
===================================================================
RCS file: /web/www/www/licenses/po/gpl-howto.translist,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -b -r1.12 -r1.13
--- po/gpl-howto.translist      22 May 2015 06:07:07 -0000      1.12
+++ po/gpl-howto.translist      16 Jun 2019 13:00:26 -0000      1.13
@@ -13,6 +13,7 @@
 <span dir="ltr"><a lang="pt-br" hreflang="pt-br" 
href="/licenses/gpl-howto.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/gpl-howto.ru.html">русский</a>&nbsp;[ru]</span> &nbsp;
 <span dir="ltr"><a lang="ta" hreflang="ta" 
href="/licenses/gpl-howto.ta.html">தமிழ்</a>&nbsp;[ta]</span> &nbsp;
+<span dir="ltr"><a lang="zh-cn" hreflang="zh-cn" 
href="/licenses/gpl-howto.zh-cn.html">简体中文</a>&nbsp;[zh-cn]</span> 
&nbsp;
 </p>
 </div>' -->
 <link rel="alternate" type="text/html" href="/licenses/gpl-howto.html" 
hreflang="x-default" />
@@ -27,4 +28,5 @@
 <link rel="alternate" type="text/html" lang="pt-br" hreflang="pt-br" 
href="/licenses/gpl-howto.pt-br.html" title="português do Brasil" />
 <link rel="alternate" type="text/html" lang="ru" hreflang="ru" 
href="/licenses/gpl-howto.ru.html" title="русский" />
 <link rel="alternate" type="text/html" lang="ta" hreflang="ta" 
href="/licenses/gpl-howto.ta.html" title="தமிழ்" />
+<link rel="alternate" type="text/html" lang="zh-cn" hreflang="zh-cn" 
href="/licenses/gpl-howto.zh-cn.html" title="简体中文" />
 <!-- end translist file -->

Index: gpl-howto.zh-cn.html
===================================================================
RCS file: gpl-howto.zh-cn.html
diff -N gpl-howto.zh-cn.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ gpl-howto.zh-cn.html        16 Jun 2019 13:00:26 -0000      1.1
@@ -0,0 +1,252 @@
+<!--#set var="ENGLISH_PAGE" value="/licenses/gpl-howto.en.html" -->
+
+<!--#include virtual="/server/header.zh-cn.html" -->
+<!-- Parent-Version: 1.86 -->
+
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>å¦‚ä½•åœ¨ä½ çš„è½¯ä»¶ä¸­ä½¿ç”¨ GNU 许可证 - GNU 工程 - 
自由软件基金会</title>
+
+<!--#include virtual="/licenses/po/gpl-howto.translist" -->
+<!--#include virtual="/server/banner.zh-cn.html" -->
+<h2>å¦‚ä½•åœ¨ä½ çš„è½¯ä»¶ä¸­ä½¿ç”¨ GNU 许可证</h2>
+
+<p>æœ¬æ–‡ç®€ä»‹å¦‚ä½•è®©ä½ çš„ç¨‹åºä½¿ç”¨ <a href="/licenses/gpl.html">GNU 
通用公共许可证</a>、<a
+href="/licenses/lgpl.html">GNU 宽通用公共许可证</a>或者 <a
+href="/licenses/agpl.html">GNU Affero 通用公共许可证</a>。对 <a
+href="/licenses/fdl.html">GNU 自由文档许可证</a>，请参看我们的 <a
+href="/licenses/fdl-howto.html">独立页面</a>。</p>
+
+<p>更多信息，请参看我们的 <a 
href="/licenses/gpl-faq.html">许可证常见问题解答</a>。</p>
+
+<p>å¦‚æžœä½ è€ƒè™‘ä½¿ç”¨ GNU 宽通用公共许可证，请先阅读 &ldquo;<a
+href="/licenses/why-not-lgpl.html">ä¸ºä»€ä¹ˆä½ çš„ä¸‹ä¸€ä¸ªåº“ä¸åº”è¯¥ä½¿ç”¨
+LGPL</a>&rdquo;ã€‚è¯¥æ–‡ç« è§£é‡Šäº†ä¸ºä»€ä¹ˆä½¿ç”¨æ™®é€šçš„ GPL 
更好，以及我们会如何决定。</p>
+
+<p>ä»¥ä¸‹æ€»ç»“äº†åœ¨é€‰æ‹©æŒ‰ç…§æˆ‘ä»¬çš„è®¸å¯è¯å‘å¸ƒç¨‹åºæ—¶ï¼Œä½ 
需要做的事项：</p>
+
+<ul>
+<li>ä»Žä½ çš„é›‡ä¸»æˆ–å­¦æ ¡èŽ·å–ä¸€ä»½ç‰ˆæƒå…é™¤å£°æ˜Žã€‚</li>
+<li>为每个文件提供适当的版权声明。确保 <a
+href="/licenses/identify-licenses-clearly.html">用户可用的许可证版本被æ¸
…æ™°åœ°æ ‡è¯†å‡ºæ¥</a>。</li>
+<li>æ·»åŠ ä¸€ä¸ªå¸¦æœ‰ GNU GPL 或 GNU AGPL 副本的 COPYING 文件。</li>
+<li>如果使用了 GNU LGPLï¼Œé‚£ä¹ˆå†æ·»åŠ ä¸€ä¸ªå¸¦æœ‰ GNU LGPL 副本的 
COPYING.LESSER 文件。</li>
+<li>每个文件都要有许可证声明。</li>
+<li>（可选项）程序开始时显示一个声明。</li>
+<li>（如果使用 AGPLï¼‰è®©ç¨‹åºå¸¦æœ‰æä¾›æºä»£ç çš„é€‰é¡¹ã€‚</li>
+</ul>
+
+<p>è¿™æ„å‘³ç€æ¯ä¸ªç¨‹åºéƒ½è¦æ·»åŠ ä¸¤ä¸ªå•å…ƒï¼šç‰ˆæƒå£°æ˜Žï¼ˆæ¯”å¦‚ 
&ldquo;Copyright 1999 Terry
+Jones&rdquo;）和拷贝授权声明，说明本程序按照 GNU 通用公å…
±è®¸å¯è¯ï¼ˆæˆ– LGPL、Affero GPL）的条款发布。</p>
+
+<h3>版权免除声明</h3>
+
+<p>å¦‚æžœä½ æ˜¯ä¸ªäººï¼Œå¹¶ä¸”ä½ æœ‰é›‡ä¸»æˆ–ä½ åœ¨æ ¡å­¦ä¹ ï¼Œè¯·ä½ 
çš„é›‡ä¸»æˆ–å­¦æ ¡å°±ä½ çš„ç¨‹åºç­¾ç½²ä¸€ä»½ç‰ˆæƒå…
é™¤å£°æ˜Žæ˜¯æ˜ŽçŸ¥ä¹‹ä¸¾ï¼Œè¿™æ ·ä»–ä»¬ä»¥åŽå°±ä¸èƒ½å†å¯¹æ­¤ä¸»å¼ 
ç‰ˆæƒè€Œå½»åº•å‰¥å¤ºä½ å‘å¸ƒç¨‹åºçš„æƒåˆ©ã€‚è¿™ä¸ªçœŸçš„å’Œ
+GNU GPL æ— å…³&mdash;&mdash;æ— è®ºä½ 
çš„ç¨‹åºä½¿ç”¨ä½•ç§è‡ªç”±è½¯ä»¶è®¸å¯è¯ï¼Œä½ éƒ½è¦è€ƒè™‘è¿™ä¸ªç‰ˆæƒå…
é™¤å£°æ˜Žã€‚</p>
+
+<p>ä»¥ä¸‹æ˜¯ä¸€ä¸ªç‰ˆæƒå…é™¤å£°æ˜Žçš„å¼æ ·ï¼›ä½ 
只需适当修改名字、题目和程序说明就好了：</p>
+
+<blockquote>
+<p>Yoyodyne 公司，现在声明放弃所有与由 James Hacker 
编写的程序
+&ldquo;Woodpecker&rdquo;ï¼ˆè¯¥ç¨‹åºåˆ†è§£æ ‘å½¢ç»“æž„ï¼‰æœ‰å…
³çš„版权利益。</p>
+
+<p><em>Moe Ghoul 签署</em> 1989 年 4 月 1 日<br />
+  Moe Ghoul，副总裁</p>
+</blockquote>
+
+<p>å¦‚æžœä½ æ˜¯å¤§å­¦ç”Ÿï¼Œæˆ‘ä»¬å»ºè®®ä½  <a 
href="/philosophy/university.html">在编写程序的早期</a>
+å°±è¦æ±‚ç‰ˆæƒå…é™¤å£°æ˜Žä»¥å‡å°‘é˜»åŠ›ã€‚å¦‚æžœä½ ä¸æ˜¯ç 
”ç©¶åŠ©ç†æˆ–åŠ©æ•™ï¼Œé‚£ä¹ˆæœ‰å¯èƒ½å­¦æ ¡å¯¹ä½ çš„å·¥ä½œå¹¶ä¸èƒ½ä¸»å¼ 
版权，不过最好还是咨询一下律师来确认此事。</p>
+
+<p>å¦‚æžœä½ å—é›‡ï¼Œæœ€å¥½ 
<em>在商讨雇佣合约时</em>，就讨论发布自由软件的许可。</p>
+
+<h3>版权声明</h3>
+
+<p>ç‰ˆæƒå£°æ˜Žåº”è¯¥åŒ…å«ä½ å®Œæˆè®¸å¯è¯çš„å¹´ä»½ï¼ˆå¦‚æžœä½ æ˜¯ 1998 
年准备好许可证的，但是在 1999 年才使用，那么请使用 1998
+å¹´ï¼‰ã€‚ä½ è¿˜åº”è¯¥æä¾›æ¯ä¸ªå‘å¸ƒç‰ˆæœ¬çš„å¹´ä»½ï¼›æ¯”å¦‚ï¼Œå¦‚æžœåœ¨ä½  
1998 年发布了一些版本，在 1999 å¹´ä¹Ÿå‘å¸ƒäº†ä¸€äº›ç‰ˆæœ¬ï¼Œé‚£ä¹ˆä½ 
应该写上
+&ldquo;Copyright 1998, 1999 Terry Jones&rdquo;ã€‚å¦‚æžœä»£ç åŒ…
含多个人的贡献，那么请写上所有人的名字。</p>
+
+<p>å¦‚æžœåœ¨è¿žç»­å¤šå¹´éƒ½æœ‰è½¯ä»¶å‘å¸ƒï¼Œé‚£ä¹ˆä½ 
可以使用一个年限范围（&ldquo;2008-2010&rdquo;ï¼‰è€Œæ— 
需列出单个年份（&ldquo;2008,
+2009, 2010&rdquo;），除非其中有单个 &ldquo;版权&rdquo;
+年份需要单独列出；<em>而且</em>ä½ 
要在文档中明确说明这一点。</p>
+
+<p>按照国际惯例，请使用英文的 &ldquo;Copyright&rdquo; 
一词；即使文档使用的是å…
¶ä»–è¯­è¨€ã€‚å¦‚æžœæ„¿æ„ï¼ˆå¹¶ä¸”å­—ç¬¦é›†æ”¯æŒï¼‰ï¼ŒåŠ ä¸Šç‰ˆæƒçš„å›¾æ ‡
+&ldquo;&copy;&rdquo; 也没问题，但并不是必须的。使用 
&ldquo;(C)&rdquo; å¹¶æ²¡æœ‰ç‰¹åˆ«çš„æ³•å¾‹æ•ˆæžœï¼Œä½†æ˜¯ä¹Ÿæ— ä¼¤å¤§é›…ã€‚</p>
+
+<p>å¦‚æžœä½ æ‹·è´çš„å…¶ä»–ç¨‹åºçš„ä»£ç ä¹Ÿä½¿ç”¨åŒæ 
·çš„许可证，那么把它们的版权声明也拷贝过来。请把一个文件的所有版权声明放在一起，并放在文件的一开始。</p>
+
+<h3>许可证文件</h3>
+
+<p>ä½ åº”è¯¥åœ¨ç¨‹åºä¸­åŒ…å«ä¸€ä»½è®¸å¯è¯çš„æ‹·è´ã€‚æ‰€æœ‰ç¨‹åºï¼Œæ— 
论是 GPL，还是 LGPL，都应该包含 <a href="/licenses/gpl.txt">GPL
+的纯文本版</a>。对 GNU 
程序来说，我们的惯例是把许可证放在一个叫做 COPYING 
的文件里。</p>
+
+<p>å¦‚æžœä½ çš„ç¨‹åºæŒ‰ç…§ GNU AGPL 发布，那么请使用 <a 
href="/licenses/agpl.txt">GNU AGPL
+的纯文本版</a>，而不是 GNU GPL 的纯文本版。</p>
+
+<p>å¦‚æžœä½ çš„ç¨‹åºæŒ‰ç…§ Lesser GPL å‘å¸ƒï¼Œé‚£ä¹ˆä½ è¿˜è¦åŒ…å«ä¸€ä»½ <a 
href="/licenses/lgpl.txt">LGPL
+的纯文本版</a>，通常放在叫做 COPYING.LESSER 
的文件里。请注意，LGPL 是在 GPL 
åŸºç¡€ä¸Šçš„ä¸€äº›é¢å¤–æŽˆæƒï¼Œæ‰€ä»¥ä½ çš„ç¨‹åºåŒ…å«
+LGPL 和 GPL ä¸¤ä¸ªè®¸å¯è¯æ‹·è´éžå¸¸å…³é”®ï¼Œè¿™æ ·ç”¨æˆ·æ‰èƒ½å¤Ÿå…
¨é¢äº†è§£ä»–们的权利。</p>
+
+<h3>许可证声明</h3>
+
+<p>每个文件的复制许可声明（又称为许可证声明）应当紧跟在版权声明之后。对由单个文件构成的程序，该声明（对
 GPL）应该类似以下内容，使用 GPL 版本 3
+或以后版本：</p>
+
+<pre>
+    This program is free software: you can redistribute it and/or modify
+    it under the terms of the GNU General Public License as published by
+    the Free Software Foundation, either version 3 of the License, or
+    (at your option) any later version.
+
+    This program is distributed in the hope that it will be useful,
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+    GNU General Public License for more details.
+
+    You should have received a copy of the GNU General Public License
+    along with this program.  If not, see 
&lt;https://www.gnu.org/licenses/&gt;.
+</pre>
+
+<p>对由多个文件构成的程序，最好将其中的 &ldquo;this 
program&rdquo; 替换为程序的名字，并以 &ldquo;This file
+is part of NAME&rdquo; 为开头。例如，</p>
+
+<pre>
+    This file is part of Foobar.
+
+    Foobar is free software: you can redistribute it and/or modify
+    it under the terms of the GNU General Public License as published by
+    the Free Software Foundation, either version 3 of the License, or
+    (at your option) any later version.
+
+    Foobar is distributed in the hope that it will be useful,
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+    GNU General Public License for more details.
+
+    You should have received a copy of the GNU General Public License
+    along with Foobar.  If not, see &lt;https://www.gnu.org/licenses/&gt;.
+</pre>
+
+<p>如果要使用一个不同版本的 GPLï¼Œä½ 
需要改写一些第一段的末尾部分。例如，如果使用的是版本 
2 æˆ–è€…å…¶ä»¥åŽç‰ˆæœ¬ï¼Œä½ éœ€è¦æŠŠ &ldquo;3&rdquo;
+替换为 &ldquo;2&rdquo;。</p>
+
+<p>该声明应当放在每个源文件的开头，就在版权声明下面。当使用
 LGPL 时，请在 <em>三处</em> 出现 &ldquo;General&rdquo;
+一词的前面插入 &ldquo;Lesser&rdquo;。当使用 GNU AGPL 时，请在 
<em>三处</em> 出现
+&ldquo;General&rdquo; 一词的前面插入 &ldquo;Affero&rdquo;。</p>
+
+<h3>为什么要有许可证声明？</h3>
+
+<p>自由软件许可证的意义在于给所有软件用户应有的权利。如果ä½
 ç»™äºˆçš„æƒåˆ©æ²¡æœ‰æ¸…æ™°çš„æè¿°ï¼Œé‚£ä¹ˆå°±æ˜¯æ— 
的放矢。我们的做法就是避免任何不确定性。</p>
+
+<p>å¦‚æžœä¸€ä¸ªç¨‹åºåœ¨å…¶æºä»£ç é‡Œå¤åˆ¶äº†ä¸€ä»½ FOO 
许可证，但是并没有明确声明 &ldquo;This program is released under
+license FOO，&rdquo;那么这里就有 FOO 
许可证是否会应用到该程序的不确定性漏洞。</p>
+
+<p>如果一个发布版在诸如 README 文件里声明了 &ldquo;This 
program is released under license
+FOO，&rdquo;那么对 <em>该发布版</em>
+就是清
楚的。然而，程序员经常会把源文件从一个程序复制到另一个程序。如果一个源文件不åŒ
…
含许可证声明，那么文件拷贝就会让源文件失去许可证信息。这就会é€
 成混淆和错误。</p>
+
+<h3>起始声明</h3>
+
+<p>对于有交互的程序，让程序在开始时显示简要的版权声明和拷贝许可通常是一个不错的主意。请参看
 <a
+href="/licenses/gpl-3.0.html#howto">GNU GPL 末节</a> 
来了解更多信息。</p>
+
+<h3>Affero 声明</h3>
+
+<p>å¦‚æžœä½ è¦ä½¿ç”¨ GNU AGPL
+发布程序，并且程序通过网络和用户交互，那么该程序应当为å
…¶ç”¨æˆ·æä¾›æºä»£ç 
ã€‚例如，如果程序是网络应用，那么用户界面应当显示用户可以访问的
+&ldquo;æºä»£ç &rdquo; 链接。GNU AGPL 接受非常宽泛的源代ç 
è®¿é—®æ‰‹æ®µï¼Œè¯· &mdash;参看其第 13 节。</p>
+
+<h3>其他</h3>
+
+<p>ä»Žå®žç”¨çš„åŽŸå› æ¥çœ‹ï¼Œåœ¨æ¯”å¦‚ README æ–‡ä»¶é‡Œï¼ŒåŒ…å«ä½ 
的联系方式是非常重要的，但是对实施许可证的法律问题来说，这个并不相å
…³ã€‚</p>
+
+<p>æ²¡æœ‰æ³•å¾‹è¦æ±‚ä½ 
需要登记版权；编写程序就意味着有了版权。不过，在美国，通过
 US Registry of Copyrights
+æ³¨å†Œç‰ˆæƒæ˜¯ä¸€ä¸ªå¥½ä¸»æ„ï¼Œå› ä¸ºè¿™æ 
·çš„è¯ï¼Œå¦‚æžœæœ‰äººåœ¨ç¾Žå›½è¿åäº†è®¸å¯è¯ï¼Œä½ 
就处在非常有利的地位。大多数国家并没有此类版权注册的机构。</p>
+
+<p>我们想要在自由软件目录下列出所有的自由软件，包
括所有使用 GPL ï¼ˆæ— è®ºç‰ˆæœ¬ï¼‰çš„è‡ªç”±è½¯ä»¶ã€‚å› æ­¤ï¼Œå½“ä½ 
的程序达到一定的可用度时，请提交一个说明条目。请参看
+<a href="http://directory.fsf.org/";>自由软件目录的网页</a> 
æ¥äº†è§£æ›´å¤šä¿¡æ¯ä»¥åŠåœ¨çº¿æäº¤çš„æ ¼å¼ã€‚</p>
+
+<p>ä½ çš„ç¨‹åºä¹Ÿå¯ä»¥å˜æˆ GNU 软件包，作为 GNU 
å·¥ç¨‹çš„ä¸€éƒ¨åˆ†ã€‚å¦‚æžœä½ æœ‰å…´è¶£åŠ å…¥ GNU 工程，请参看 <a
+href="/help/evaluation.html">GNU 软件评价页面</a> 
æ¥äº†è§£æ›´å¤šä¿¡æ¯å¹¶å®Œæˆä¸€ä¸ªé—®å·ã€‚æˆ‘ä»¬ä¼šè”ç³»ä½ å¹¶å’Œä½ 
讨论此事。</p>
+
+<p>å³ä½¿ä½ çš„ç¨‹åºä¸æ˜¯ GNU
+è½¯ä»¶åŒ…ï¼Œä½ ä¹Ÿå¯ä»¥ä½¿ç”¨æˆ‘ä»¬çš„è®¸å¯è¯ï¼›å®žé™…ä¸Šï¼Œæˆ‘ä»¬å¾ˆæœŸå¾…
ä½ ä½¿ç”¨æˆ‘ä»¬çš„è®¸å¯è¯ï¼Œæ— 
è®ºå“ªä¸ªç‰ˆæœ¬éƒ½è¡Œã€‚å®ƒä»¬æ˜¯ä¸ºæ‰€æœ‰äººå‡†å¤‡çš„ã€‚å¦‚æžœä½ æƒ³å¯¹ä½ 
使用的许可证做推广，请放心使用
+<a href="/graphics/license-logos.html" title="GNU License
+Logos">æˆ‘ä»¬çš„è®¸å¯è¯æ ‡è¯†</a>。</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 4.0.  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; 2001, 2007, 2008, 2009, 2013, 2014, 2017, 2018 Free
+Software Foundation, Inc.</p>
+
+<p>本页面使用 <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/4.0/";>Creative Commons
+Attribution-NoDerivatives 4.0 International 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/06/16 13:00:26 $
+
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+<!-- for class="inner", starts in the banner include -->
+</body>
+</html>

Index: po/gpl-howto.zh-cn-en.html
===================================================================
RCS file: po/gpl-howto.zh-cn-en.html
diff -N po/gpl-howto.zh-cn-en.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ po/gpl-howto.zh-cn-en.html  16 Jun 2019 13:00:26 -0000      1.1
@@ -0,0 +1,316 @@
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.86 -->
+<title>How to use GNU licenses for your own software
+- GNU Project - Free Software Foundation</title>
+<!--#include virtual="/licenses/po/gpl-howto.translist" -->
+<!--#include virtual="/server/banner.html" -->
+<h2>How to use GNU licenses for your own software</h2>
+
+<p>This is a brief explanation of how to place a program under the <a
+href="/licenses/gpl.html">GNU General Public License</a>, <a
+href="/licenses/lgpl.html">GNU Lesser General Public License</a>, or <a
+href="/licenses/agpl.html">GNU Affero General Public License</a>.  For the
+<a href="/licenses/fdl.html">GNU Free Documentation License</a>, we have
+a <a href="/licenses/fdl-howto.html">separate page</a>.</p>
+
+<p>For further information, see our list
+of <a href="/licenses/gpl-faq.html">frequently asked questions about
+our licenses</a>.</p>
+
+<p>If you are considering using the GNU Lesser General Public License,
+please read the article &ldquo;<a href="/licenses/why-not-lgpl.html">Why
+you shouldn't use the LGPL for your next library</a>&rdquo; first.  The
+article explains why it may be better to use the ordinary GPL instead,
+and how we would make the decision.</p>
+
+<p>Here's a brief summary of what you need to do to release a program
+under one of our licenses:</p>
+
+<ul>
+<li>Get a copyright disclaimer from your employer or school.</li>
+<li>Give each file the proper copyright notices. Make
+sure <a href="/licenses/identify-licenses-clearly.html">to clearly
+identify which versions of the license users can use</a>.</li>
+<li>Add a COPYING file with a copy of the GNU GPL or GNU AGPL.</li>
+<li>Also add a COPYING.LESSER file with a copy of the GNU LGPL, if you
+use that.</li>
+<li>Put a license notice in each file.</li>
+<li>(Optionally) make the program display a startup notice.</li>
+<li>(If using the AGPL) make the program offer copies of its source code.</li>
+</ul>
+
+<p>This involves adding two elements to each source file of your
+program: a copyright notice (such as &ldquo;Copyright 1999 Terry
+Jones&rdquo;), and a statement of copying permission, saying that the
+program is distributed under the terms of the GNU General Public
+License (or the Lesser GPL, or the Affero GPL).</p>
+
+<h3>The copyright disclaimer</h3>
+
+<p>If you are an individual, and you have an employer or study in
+a school, it's wise to ask your
+employer or school to sign a copyright disclaimer for your
+program, so it cannot later claim that the copyright belongs to it
+and that you had no right to release the program at all.  This really
+has nothing to do with the GNU GPL&mdash;it applies no matter which
+free software license you use to release the program.</p>
+
+<p>Here is a sample copyright disclaimer; just alter the names, title,
+and program description as appropriate:</p>
+
+<blockquote>
+<p>Yoyodyne, Inc., hereby disclaims all copyright interest
+in the program &ldquo;Woodpecker&rdquo; (which deconstructs trees)
+written by James Hacker.</p>
+
+<p><em>signature of Moe Ghoul</em> 1 April 1989<br />
+  Moe Ghoul, President of Vice</p>
+</blockquote>
+
+<p>If you are a university student, we recommend you request the
+disclaimer <a href="/philosophy/university.html"> at an early stage in
+writing the program</a> to reduce resistance.  If you are not a
+research assistant or teaching assistant, it could be that the university
+has no claim to copyright on your work, but ask a lawyer to make
+sure of that.</p>
+
+<p>If you work, the best time to negotiate permission to release free
+software is <em>when negotiating your employment agreement</em>.</p>
+
+<h3>The copyright notice</h3>
+
+<p>The copyright notice should include the year in which you finished
+preparing the release (so if you finished it in 1998 but didn't post
+it until 1999, use 1998).  You should add the proper year for each
+past release; for example, &ldquo;Copyright 1998, 1999 Terry
+Jones&rdquo; if some releases were finished in 1998 and some were
+finished in 1999.  If several people helped write the code, use all
+their names.</p>
+
+<p>For software with several releases over multiple years, it's okay
+to use a range (&ldquo;2008-2010&rdquo;) instead of listing individual
+years (&ldquo;2008, 2009, 2010&rdquo;) if and only if every year in
+the range, inclusive, really is a &ldquo;copyrightable&rdquo; year
+that would be listed individually; <em>and</em> you make an explicit
+statement in your documentation about this usage.</p>
+
+<p>Always use the English word &ldquo;Copyright&rdquo;; by international
+convention, this is used worldwide, even for material in other
+languages. The copyright symbol &ldquo;&copy;&rdquo; can be included if
+you wish (and your character set supports it), but it's not necessary.
+There is no legal significance to using the three-character sequence
+&ldquo;(C)&rdquo;, but it does no harm.</p>
+
+<p>If you have copied code from other programs covered by the same
+license, copy their copyright notices too.  Put all the copyright
+notices for a file together, right near the top of the file.</p>
+
+<h3>The license files</h3>
+
+<p>You should also include a copy of the license itself somewhere in the
+distribution of your program.  All programs, whether they are released
+under the GPL or LGPL, should include <a href="/licenses/gpl.txt">the
+text version of the GPL</a>.  In GNU programs we conventionally put the
+license in a file called COPYING.</p>
+
+<p>If you are releasing your program under the GNU AGPL,
+use <a href="/licenses/agpl.txt">the text version of the GNU AGPL</a>
+instead of the GNU GPL.</p>
+
+<p>If you are releasing your program under the Lesser GPL, you should also
+include <a href="/licenses/lgpl.txt">the text version of the LGPL</a>,
+usually in a file called COPYING.LESSER.  Please note that, since the
+LGPL is a set of additional permissions on top of the GPL, it's crucial
+to include both licenses so users have all the materials they need to
+understand their rights.</p>
+
+<h3>The license notices</h3>
+
+<p>Each file's copying permission statement (also called the license notice)
+should come right after its copyright notices.  For a one-file
+program, the statement (for the GPL) should look like this, to use
+GPL version 3 or later:</p>
+
+<pre>
+    This program is free software: you can redistribute it and/or modify
+    it under the terms of the GNU General Public License as published by
+    the Free Software Foundation, either version 3 of the License, or
+    (at your option) any later version.
+
+    This program is distributed in the hope that it will be useful,
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+    GNU General Public License for more details.
+
+    You should have received a copy of the GNU General Public License
+    along with this program.  If not, see 
&lt;https://www.gnu.org/licenses/&gt;.
+</pre>
+
+<p>For programs that are more than one file, it is better to replace
+&ldquo;this program&rdquo; with the name of the program, and begin the
+statement with a line saying &ldquo;This file is part of NAME&rdquo;.
+For instance,</p>
+
+<pre>
+    This file is part of Foobar.
+
+    Foobar is free software: you can redistribute it and/or modify
+    it under the terms of the GNU General Public License as published by
+    the Free Software Foundation, either version 3 of the License, or
+    (at your option) any later version.
+
+    Foobar is distributed in the hope that it will be useful,
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+    GNU General Public License for more details.
+
+    You should have received a copy of the GNU General Public License
+    along with Foobar.  If not, see &lt;https://www.gnu.org/licenses/&gt;.
+</pre>
+
+<p>To use a different set of GPL versions, you would modify the end of
+the first long paragraph.  For instance, to license under version 2 or
+later, you would replace &ldquo;3&rdquo; with &ldquo;2&rdquo;.</p>
+
+<p>This statement should go near the beginning of every source file,
+close to the copyright notices.  When using the Lesser GPL, insert the
+word &ldquo;Lesser&rdquo; before &ldquo;General&rdquo; in <em>all
+three</em> places.  When using the GNU AGPL, insert the
+word &ldquo;Affero&rdquo; before &ldquo;General&rdquo; in <em>all
+three</em> places.</p>
+
+<h3>Why license notices?</h3>
+
+<p>The purpose of a free software license is to give certain rights to
+all users of a program.  If it is not clear what rights you have given
+them, that defeats the purpose.  Our practices are designed to
+avoid any uncertainty.</p>
+
+<p>If a program has a copy of a license FOO alongside the source files,
+but doesn't have an explicit statement that &ldquo;This program is
+released under license FOO,&rdquo; that leaves room for uncertainty
+about whether the license FOO applies to the code of that program.</p>
+
+<p>If a release has one statement that &ldquo;This program is released
+under license FOO,&rdquo; in a central place such as the README file,
+that makes the situation clear <em>for that release</em>.  However,
+programmers often copy source files from one free program into
+another.  If a source file contains no statement about what its
+license is, then moving it into another context eliminates all trace
+of that point.  This invites confusion and error.</p>
+
+<h3>The startup notice</h3>
+
+<p>For interactive programs, it is usually a good idea to make the
+program display a brief notice about copyright and copying permission
+when it starts up.  See <a href="/licenses/gpl-3.0.html#howto">the end
+of the GNU GPL</a> for more information about this.</p>
+
+<h3>The Affero notice</h3>
+
+<p>If you are releasing your program under the GNU AGPL, and it can
+interact with users over a network, the program should offer its source to
+those users in some way.  For example, if your program is a web
+application, its interface could display a &ldquo;Source&rdquo; link that
+leads users to an archive of the code.  The GNU AGPL is flexible enough
+that you can choose a method that's suitable for your specific
+program&mdash;see section 13 for details.</p>
+
+<h3>Miscellaneous</h3>
+
+<p>It is very important for practical reasons to include contact
+information for how to reach you, perhaps in the README file, but this
+has nothing to do with the legal issues of applying the license.</p>
+
+<p>There is no legal requirement to register your copyright with anyone;
+simply writing the program makes it copyrighted.  However, for the US,
+it is a good idea to register the copyright with the US Registry of
+Copyrights, because that puts you in a stronger position against anyone
+who violates the license in the US.  Most other countries have no system
+of copyright registration.</p>
+
+<p>We would like to list all free software programs in the Free
+Software Directory, including all programs licensed under the GPL (any
+version).  So please submit an entry for your program, when it has
+reached the point of being useful.  Please see
+the <a href="http://directory.fsf.org/";>Directory web page</a> for
+information and an online submission form.</p>
+
+<p>It is also possible to make your program a GNU package, a part of the
+GNU Project.  If you might be interested in joining up with the
+GNU Project in this way, please see our <a
+href="/help/evaluation.html">GNU software evaluation page</a> for more
+information and a short questionnaire.  We will respond and discuss the
+matter with you.</p>
+
+<p>You are welcome to use any of our licenses even if your program
+is not a GNU package; indeed, we hope you will.  They're available to
+everyone.  If you'd like to advertise your use of a particular license,
+feel free to use <a href="/graphics/license-logos.html"
+title="GNU License Logos">one of our logos</a>.</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 4.0.  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; 2001, 2007, 2008, 2009, 2013, 2014, 2017, 2018
+Free Software Foundation, Inc.</p>
+
+<p>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>.</p>
+
+<!--#include virtual="/server/bottom-notes.html" -->
+
+<p class="unprintable">Updated:
+<!-- timestamp start -->
+$Date: 2019/06/16 13:00:26 $
+<!-- timestamp end -->
+</p>
+</div>
+</div><!-- for class="inner", starts in the banner include -->
+</body>
+</html>