www-commits
[Top][All Lists]
Advanced

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

www/licenses license-compatibility.zh-cn.html p...


From: GNUN
Subject: www/licenses license-compatibility.zh-cn.html p...
Date: Wed, 29 Dec 2021 21:29:58 -0500 (EST)

CVSROOT:        /web/www
Module name:    www
Changes by:     GNUN <gnun>     21/12/29 21:29:58

Modified files:
        licenses       : license-compatibility.zh-cn.html 
        licenses/po    : license-compatibility.zh-cn-en.html 
                         license-compatibility.zh-cn.po 

Log message:
        Automatic update by GNUnited Nations.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/license-compatibility.zh-cn.html?cvsroot=www&r1=1.3&r2=1.4
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/license-compatibility.zh-cn-en.html?cvsroot=www&r1=1.2&r2=1.3
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/license-compatibility.zh-cn.po?cvsroot=www&r1=1.10&r2=1.11

Patches:
Index: license-compatibility.zh-cn.html
===================================================================
RCS file: /web/www/www/licenses/license-compatibility.zh-cn.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -b -r1.3 -r1.4
--- license-compatibility.zh-cn.html    24 Nov 2020 04:29:49 -0000      1.3
+++ license-compatibility.zh-cn.html    30 Dec 2021 02:29:57 -0000      1.4
@@ -1,21 +1,23 @@
 <!--#set var="ENGLISH_PAGE" value="/licenses/license-compatibility.en.html" -->
 
 <!--#include virtual="/server/header.zh-cn.html" -->
-<!-- Parent-Version: 1.86 -->
+<!-- Parent-Version: 1.96 -->
+<!-- This page is derived from /server/standards/boilerplate.html -->
 
 <!-- This file is automatically generated by GNUnited Nations! -->
 <title>许可证兼容性和再次授权 - GNU 工程 - 
自由软件基金会</title>
 
 <!--#include virtual="/licenses/po/license-compatibility.translist" -->
 <!--#include virtual="/server/banner.zh-cn.html" -->
+<div class="article reduced-width">
 <h2>许可证兼容性和再次授权</h2>
 
-<p>Richard Stallman 著</p>
+<address class="byline">Richard Stallman 著</address>
 
 <p>如果你要把两个自由程序合而为一,或者把å…
¶ä¸­ä¹‹ä¸€çš„代码并å…
¥å¦ä¸€ä¸ªï¼Œé‚£ä¹ˆå°±ä¼šæœ‰ä¸€ä¸ªå®ƒä»¬çš„许可证是否允许/禁止这æ 
·åšçš„问题。<a
-href="#f1">(*)</a></p>
+href="#f1">[1]</a></p>
 
-<p>如果两个软件使用同æ 
·çš„许可证,应该没有问题,假定该许可证象几
乎所有的自由软件许可证一样顺理成章。<a href="#f2">(**)</a></p>
+<p>如果两个软件使用同æ 
·çš„许可证,应该没有问题,假定该许可证象几
乎所有的自由软件许可证一样顺理成章。<a href="#f2">[2]</a></p>
 
 <p>那么如果许可证不一æ 
·ä¼šå¦‚何呢?一般来说,如果有方法可以合并代ç 
è€Œåˆèƒ½åŒæ—¶éµå¾ªå„个代ç 
çš„许可证,那么我们就说这些许可证是
 <em>兼容的</em>。å…
¶ç»“果经常是一个由各个部分使用不同许可证的组合程序&mdash;&mdash;但也不尽然。å
…·æœ‰è¿™ä¸ªå…¼å®¹æ€§ï¼Œæˆ–者没有此å…
¼å®¹æ€§ï¼Œæ˜¯è®¸å¯è¯ç»„合在一起的特点,这个特点并不依赖于你
使用它们的顺序。该许可证组合还决定着该合并程序需要哪个许可证。</p>
@@ -29,7 +31,7 @@
 
&ldquo;顺从型许可证&rdquo;,理由是它们在用户的自由被否定时没有说
 &ldquo;不&rdquo;。</p>
 
 <p>在把使用松散型许可证的代ç 
åˆåœ¨ä¸€èµ·æ—¶ï¼Œç»„合程序的每个部分都带有自己的许可证。当这些代ç
 äº¤ç»‡åœ¨ä¸€èµ·æ— æ³•åˆ†è¾¨æ—¶ï¼Œç»„合程序应该带上所有代ç 
çš„许可证。由于这些许可证都是松散型的,所以å…
¨éƒ½å¸¦ä¸Šé™¤äº†å¤ªé•¿ä¹‹å¤–也没有别的问题。<a
-href="#f3">(***)</a></p>
+href="#f3">[3]</a></p>
 
 <p>同理可知,松散型许可证通常也和 copyleft 许可证å…
¼å®¹ã€‚在组合程序中,使用松散型许可证的代ç 
ä»ç„¶å¸¦ç€æ¾æ•£åž‹è®¸å¯è¯ï¼Œè€Œç»„合程序整体使用
 copyleft 许可证。有一个松散型许可证,Apache 2.0,带有和 GPL 
v2 不å…
¼å®¹çš„专利条款;由于我认为这些专利条款还不错,所以我让
@@ -70,7 +72,7 @@
 GPL 1&rdquo; 或者 &ldquo;用 GPL 1 或以后版&rdquo; 来发布。</p>
 
 <p>从那时起,我就在思量当时的决定是否明智。像 Linux 这æ 
·çš„程序,只允许一个版本的 GNU GPL 
并拒绝升级许可证,这就导致实际上的不兼容。<a
-href="#f4">(****)</a>或许我们应该在 GPL v4 的时侯包
含一个自动升级条款,如果我们需要版本 4 的话。</p>
+href="#f4">[4]</a>或许我们应该在 GPL v4 的时侯包
含一个自动升级条款,如果我们需要版本 4 的话。</p>
 
 <p>有些 copyleft 许可证有一个明确的再次授权条款,该条款å…
è®¸å°†ä»£ç æŒ‰ç…§ä¸åŒçš„ copyleft 许可证授权,这样就允许了 
copyleft
 许可证之间的交叉授权。例如,CeCILL 许可证明确许可将代ç 
æŒ‰ç…§ GNU GPL v2 或以后版再次授权。如果程序 P 使用 CeCILL
@@ -111,9 +113,9 @@
 许可证。Mozilla 公共许可证允许将代码再次授权到 GNU 
GPL,除非该代码明确拒绝这样做。</p>
 
 <p>最后,双重许可证怎么办呢?<a
-href="#f5">(*****)</a>双重许可证是一种或的å…
³ç³»ï¼šå®ƒçš„意思是同一个程序可以选择两个或多个许可证中的一个或å‡
 ä¸ªã€‚例如,老版本的
-Perl 就带有双重许可证:或者是 Artistic 许可证,或者是 GNU 
通用公共许可证。这意味着每个用户都可以选择并按照å…
¶ä¸­ä¸€ä¸ªè®¸å¯è¯æˆ–者就按照
-Perl 原来的方式再次授权 
Perl。如果双重许可证中的一个许可证和一组许可证å…
¼å®¹ï¼Œé‚£ä¹ˆè¯¥åŒé‡è®¸å¯è¯å°±å’Œè¯¥ç»„许可证兼容。</p>
+href="#f5">[5]</a>双重许可证是一种或的å…
³ç³»ï¼šå®ƒçš„意思是同一个程序可以选择两个或多个许可证中的一个或å‡
 ä¸ªã€‚例如,老版本的 Perl
+就带有双重许可证:或者是 Artistic 许可证,或者是 GNU 
通用公共许可证。这意味着每个用户都可以选择并按照å…
¶ä¸­ä¸€ä¸ªè®¸å¯è¯æˆ–者就按照 Perl
+原来的方式再次授权 
Perl。如果双重许可证中的一个许可证和一组许可证å…
¼å®¹ï¼Œé‚£ä¹ˆè¯¥åŒé‡è®¸å¯è¯å°±å’Œè¯¥ç»„许可证兼容。</p>
 
 <p>当你选择许可证时,请选择 GNU GPL v3 或者以后版本,或者
是与之兼容的许可证。这是使你的代码能够和几
乎所有自由软件集合的代码组合的正确方法。选择
 GPL 或 AGPL,v3 或者
以后版本,也会最大程度地保护所有使用你各个版本代ç 
çš„用户的自由。</p>
@@ -142,29 +144,30 @@
 <p>此处并非要提供一个完整列表,但是如果我们发现还有å…
¶ä»–值得说明的例子,我们还会添加。</p>
 
 <p>当某些许可证被包含时,你仍然需要在发布组合程序时包
含该许可证的拷贝。</p>
+<div class="column-limit"></div>
 
-<h3 id="footnotes">脚注</h3>
+<h3 id="footnotes" class="footnote">脚注</h3>
+<ol>
+<li id="f1"><p>可以想象还可能有关于合并程序的å…
¶ä»–法律问题,这些问题可能和合并程序的许可证无å…
³ã€‚我们只讨论和许可证本身有关的问题。</p></li>
 
-<p id="f1"><b>*</b> 可以想象还可能有关于合并程序的å…
¶ä»–法律问题,这些问题可能和合并程序的许可证无å…
³ã€‚我们只讨论和许可证本身有关的问题。</p>
-
-<p id="f2"><b>**</b> 实际当中用到的不那么顺理成章
的许可证主要是 TeX 的许可证:如果两个程序都按照 TeX
-的方式授权,那么你
就没有办法发布两个程序的组合程序。</p>
+<li id="f2"><p>实际当中用到的不那么顺理成章的许可证主要是 
TeX 的许可证:如果两个程序都按照 TeX 的方式授权,那么你
就没有办法发布两个程序的组合程序。</p>
 
 <p>TeX 许可证允许发布的修改版只能是原来的版本加
上一个差异文件。如果甲和乙两个程序分别按照 Tex
 许可证发布,然后再合并,那么按照甲程序加
上一个差异文件来发布合并程序就违反了乙程序的许可证。反过来,发布乙程序åŠ
 ä¸Šå·®å¼‚文件的话又违反了甲的许可证。按照å…
¶ä»–方式发布的话就违反了甲乙两个程序的许可证。</p>
 
 <p>这个并不意外,TeX 早在 1982 
年就发布了:社区从此逐渐学会了撰写顺理成章
的许可证。</p>
+</li>
 
-<p id="f3"><b>***</b>
-当发布源代码时,在源代码里加å…
¥è®¸å¯è¯å£°æ˜Žé€šå¸¸å°±è¶³å¤Ÿäº†ï¼›åªæœ‰è±¡ä½¿ç”¨æ¾æ•£åž‹è®¸å¯è¯çš„ä»…
发布二进制而不带源代ç 
çš„程序才需要额外的许可证声明。</p>
+<li id="f3"><p>当发布源代码时,在源代码里加å…
¥è®¸å¯è¯å£°æ˜Žé€šå¸¸å°±è¶³å¤Ÿäº†ï¼›åªæœ‰è±¡ä½¿ç”¨æ¾æ•£åž‹è®¸å¯è¯çš„ä»…
发布二进制而不带源代ç 
çš„程序才需要额外的许可证声明。</p></li>
 
-<p id="f4"><b>****</b> 另外,GPL v2
-仍然å…
è®¸éžè‡ªç”±çš„二进制&mdash;&mdash;硬件只运行特别签名的二进制而拒绝å
…¶ä»–二进制文件,而且仍然不允许使用 torrent 发布二进制。<a
-href="/licenses/rms-why-gplv3.html">我们在版本 3 
中修复了这些问题,还修复了å…
¶ä»–问题</a>,但是我们不能改变版本
-2。</p>
+<li id="f4"><p>另外,GPL v2 仍然å…
è®¸éžè‡ªç”±çš„二进制&mdash;&mdash;硬件只运行特别签名的二进制而拒绝å
…¶ä»–二进制文件,而且仍然不允许使用 torrent
+发布二进制。<a href="/licenses/rms-why-gplv3.html">我们在版本 3
+中修复了这些问题,还修复了å…
¶ä»–问题</a>,但是我们不能改变版本 2。</p></li>
 
-<p id="f5"><b>*****</b> 有人使用 &ldquo;双重许可证&rdquo; 来å…
œå”®è®¸å¯è¯ä¾‹å¤–,但是词不达意。请参看 <a
-href="/philosophy/selling-exceptions.html">å…
œå”®ä¾‹å¤–</a>。请注意,如果某个许可证兜售的程序包
含了任何非自由的代码,那么它就不是在å…
œå”®ä¾‹å¤–,它就是非自由软件。</p>
+<li id="f5"><p>有人使用 &ldquo;双重许可证&rdquo; 来å…
œå”®è®¸å¯è¯ä¾‹å¤–,但是词不达意。请参看 <a
+href="/philosophy/selling-exceptions.html">å…
œå”®ä¾‹å¤–</a>。请注意,如果某个许可证兜售的程序包
含了任何非自由的代码,那么它就不是在å…
œå”®ä¾‹å¤–,它就是非自由软件。</p></li>
+</ol>
+</div>
 
 <div class="translators-notes">
 
@@ -174,7 +177,7 @@
 
 <!-- for id="content", starts in the include above -->
 <!--#include virtual="/server/footer.zh-cn.html" -->
-<div id="footer">
+<div id="footer" role="contentinfo">
 <div class="unprintable">
 
 <p>请将有关自由软件基金会(FSF) &amp; 
GNU的一般性问题发送到<a
@@ -193,13 +196,13 @@
 
         &lt;web-translators@gnu.org&gt;</a>.</p>
 
-        <p>For information on coordinating and submitting translations of
+        <p>For information on coordinating and contributing translations of
         our web pages, see <a
         href="/server/standards/README.translations.html">Translations
         README</a>. -->
 我们尽最大努力来提供精准和高质量的翻译,但难å…
ä¼šå­˜åœ¨é”™è¯¯å’Œä¸è¶³ã€‚如果您在这方面有评论或一般性的建议,请发送至
 <a
 
href="mailto:web-translators@gnu.org";>&lt;web-translators@gnu.org&gt;</a>。</p><p>å
…³äºŽè¿›è¡Œåè°ƒä¸Žæäº¤ç¿»è¯‘的更多信息参见
-<a href="/server/standards/README.translators.html">《译者
指南》</a>。</p>
+<a href="/server/standards/README.translations.html">《译者
指南》</a>。</p>
 </div>
 
 <!-- Regarding copyright, in general, standalone pages (as opposed to
@@ -218,7 +221,7 @@
      
      There is more detail about copyright years in the GNU Maintainers
      Information document, www.gnu.org/prep/maintain. -->
-<p>Copyright &copy; 2016, 2018, 2020 Free Software Foundation, Inc.</p>
+<p>Copyright &copy; 2016, 2018, 2020, 2021 Free Software Foundation, Inc.</p>
 
 <p>本页面使用 <a rel="license"
 href="http://creativecommons.org/licenses/by-nd/4.0/";>Creative Commons
@@ -229,12 +232,12 @@
 
 <!--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>,2020。</div>
+href="https://savannah.gnu.org/projects/www-zh-cn/";>&lt;CTT&gt;</a>,2020,2021。</div>
 
 <p class="unprintable"><!-- timestamp start -->
 最后更新:
 
-$Date: 2020/11/24 04:29:49 $
+$Date: 2021/12/30 02:29:57 $
 
 <!-- timestamp end -->
 </p>

Index: po/license-compatibility.zh-cn-en.html
===================================================================
RCS file: /web/www/www/licenses/po/license-compatibility.zh-cn-en.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- po/license-compatibility.zh-cn-en.html      24 Nov 2020 04:29:49 -0000      
1.2
+++ po/license-compatibility.zh-cn-en.html      30 Dec 2021 02:29:58 -0000      
1.3
@@ -1,20 +1,22 @@
 <!--#include virtual="/server/header.html" -->
-<!-- Parent-Version: 1.86 -->
+<!-- Parent-Version: 1.96 -->
+<!-- This page is derived from /server/standards/boilerplate.html -->
 <title>License Compatibility and Relicensing
 - GNU Project - Free Software Foundation</title>
  <!--#include virtual="/licenses/po/license-compatibility.translist" -->
 <!--#include virtual="/server/banner.html" -->
+<div class="article reduced-width">
 <h2>License Compatibility and Relicensing</h2>
 
-<p>by Richard Stallman</p>
+<address class="byline">by Richard Stallman</address>
 
 <p>If you want to combine two free programs into one, or merge code from
 one into the other, this raises the question of whether their licenses
-allow combining them, or prohibit combining them.<a href="#f1">(*)</a></p>
+allow combining them, or prohibit combining them.<a href="#f1">[1]</a></p>
 
 <p>There is no problem merging programs that have the same license, if it
 is a reasonably behaved license, as nearly all free licenses
-are.<a href="#f2">(**)</a></p>
+are.<a href="#f2">[2]</a></p>
 
 <p>What then when the licenses are different?  In general we say that
 several licenses are <em>compatible</em> if there is a way to merge
@@ -46,7 +48,7 @@
 parts can't be distinguished any more, that merged code should carry
 all the licenses of the merged parts.  Since all the licenses are lax
 anyway, this causes no practical problem except that the list of
-licenses gets long.<a href="#f3">(***)</a></p>
+licenses gets long.<a href="#f3">[3]</a></p>
 
 <p>By the same token, lax licenses are usually compatible with any
 copyleft license.  In the combined program, the parts that came in
@@ -97,9 +99,9 @@
 &ldquo;GNU GPL version N or any later version.&rdquo;  This licensing is
 compatible with version N, and also with N+1 (because it offers
 version N+1 as an option).  When you combine code under &ldquo;GPL 3 or
-later&rdquo; with code under &ldquo;GPL 2 or later&rdquo;, the license
+later&rdquo; with code under &ldquo;GPL 2 or later,&rdquo; the license
 of the combination is their intersection, which is &ldquo;GPL 3 or
-later&rdquo;.</p>
+later.&rdquo;</p>
 
 <p>We hope we will never need to make a GNU GPL version 4, but nothing is
 perfect and we can't assume we have anticipated all the issues.  By
@@ -123,7 +125,7 @@
 <p>Since then, I have come to question the wisdom of that decision.
 Programs such as Linux, which allow only one GNU GPL version and
 reject license upgrades, cause practical
-incompatibility.<a href="#f4">(****)</a>  If we ever make a GPL version
+incompatibility.<a href="#f4">[4]</a>  If we ever make a GPL version
 4, perhaps we should include an upgrade clause that automatically
 permits relicensing to higher-numbered versions, 5 and up.</p>
 
@@ -146,24 +148,24 @@
 to release that combined program is under the appropriate GPL
 version(s).</p>
 
-<p>Likewise, CC-BY-SA 4.0 explicitly permits relicensing modified
+<p>Likewise, CC BY-SA 4.0 explicitly permits relicensing modified
 versions to GNU GPL version 3, but GPL version 3 does not permit
-relicensing to CC-BY-SA.  This issue should never arise for software
+relicensing to CC BY-SA.  This issue should never arise for software
 code; Creative Commons says its licenses are not meant for code, and
 says that the license to use for code is the GNU GPL.  But there are
 other kinds of works, such as hardware designs or game art, where you
 might have occasion to merge material released under CC-BY-SA with
 material released under the GNU GPL.  This can be done through
-CC-BY-SA's explicit relicensing permission.</p>
+CC BY-SA's explicit relicensing permission.</p>
 
-<p>Unfortunately, CC-BY-SA 4.0 does not permit relicensing to future GPL
+<p>Unfortunately, CC BY-SA 4.0 does not permit relicensing to future GPL
 versions.  What you should do, when you relicense material under
-CC-BY-SA 4.0 to the GPL, is <a
+CC BY-SA 4.0 to the GPL, is <a
 href="/licenses/rms-why-gplv3.html#future-proofing">specify
 yourself as a license version proxy</a> to indicate whether future GPL
 versions have been authorized for that material.  If someday there is
 a GPL version 4 and Creative Commons decides to allow relicensing from
-CC-BY-SA to GPL version 4, you as proxy will be able to retroactively
+CC BY-SA to GPL version 4, you as proxy will be able to retroactively
 authorize use of that relicensed material under GPL version 4.
 (Alternatively, you can ask the authors of that material to give
 permission right away.)</p>
@@ -204,7 +206,7 @@
 the GNU GPL except when the code explicitly denies this
 permission.</p>
 
-<p>Finally, what about dual licensing?<a href="#f5">(*****)</a> A dual
+<p>Finally, what about dual licensing?<a href="#f5">[5]</a> A dual
 license is a disjunction: it means that the same program carries a
 choice of two or more different licenses.  For instance, older
 versions of Perl carried a dual license: the disjunction of the
@@ -253,22 +255,23 @@
 
 <p>The Apache 2.0 license subsumes the BSD, Expat, X11, ISC and CC-0
 licenses.  BSD 3 clause subsumes BSD 2 clause.  The BSD licenses
-subsume the Expat, X11 and ISC licenses and CC-0.</p>
+subsume the Expat, X11 and ISC licenses and CC0.</p>
 
 <p>This is not meant to be a complete list, but if we are informed of
 other cases worth mentioning, we will add them.</p>
 
 <p>When some license is subsumed, you still need to include a copy
 of it with all distribution of the combined program.</p>
+<div class="column-limit"></div>
 
-<h3 id="footnotes">Footnotes</h3>
-
-<p id="f1"><b>*</b> It is not inconceivable that other legal issues
+<h3 id="footnotes" class="footnote">Footnotes</h3>
+<ol>
+<li id="f1"><p>It is not inconceivable that other legal issues
 might arise about a specific combination of programs, issues not
 related to the copyright licenses of the programs to be combined.  We
-discuss only the implications of the licenses themselves.</p>
+discuss only the implications of the licenses themselves.</p></li>
 
-<p id="f2"><b>**</b> The main license in actual use that isn't
+<li id="f2"><p>The main license in actual use that isn't
 reasonably behaved is the license of TeX: if two programs are licensed
 just the way TeX is, there is no authorized way to distribute a merged
 version of them.</p>
@@ -282,29 +285,32 @@
 
 <p>It is no coincidence that TeX was released in 1982: our community has
 learned, since then, to write reasonably behaved licenses.</p>
+</li>
 
-<p id="f3"><b>***</b> When distributing in source code
+<li id="f3"><p>When distributing in source code
 form, it is usually sufficient to leave the license notices in the
 source code as they stand; extra license notice requirements typically
 only come up for lax licenses when distributing binaries without the
-source code.</p>
+source code.</p></li>
 
-<p id="f4"><b>****</b> In addition, GPL version 2 still allows
+<li id="f4"><p>In addition, GPL version 2 still allows
 binaries to be made nonfree by hardware that rejects all but special
 signed binaries, and still does not allow distribution of binaries by
 torrent.  <a href="/licenses/rms-why-gplv3.html">We fixed those
-problems, and others, in version 3</a>, but we can't change version 2.</p>
+problems, and others, in version 3</a>, but we can't change version 2.</p></li>
 
-<p id="f5"><b>*****</b> Some use the term &ldquo;dual licensing&rdquo;
+<li id="f5"><p>Some use the term &ldquo;dual licensing&rdquo;
 to refer to selling exceptions, but that is a misnomer.
 See <a href="/philosophy/selling-exceptions.html"> Selling
 Exceptions</a>.  Note that if the program on which the license is sold
 includes any code that is not in the free (libre) release, that's not
-selling exceptions, that's nonfree software.</p>
+selling exceptions, that's nonfree software.</p></li>
+</ol>
+</div>
 
 </div><!-- for id="content", starts in the include above -->
 <!--#include virtual="/server/footer.html" -->
-<div id="footer">
+<div id="footer" role="contentinfo">
 <div class="unprintable">
 
 <p>Please send general FSF &amp; GNU inquiries to
@@ -322,13 +328,13 @@
         to <a href="mailto:web-translators@gnu.org";>
         &lt;web-translators@gnu.org&gt;</a>.</p>
 
-        <p>For information on coordinating and submitting translations of
+        <p>For information on coordinating and contributing 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
+README</a> for information on coordinating and contributing translations
 of this article.</p>
 </div>
 
@@ -349,7 +355,7 @@
      There is more detail about copyright years in the GNU Maintainers
      Information document, www.gnu.org/prep/maintain. -->
 
-<p>Copyright &copy; 2016, 2018, 2020 Free Software Foundation, Inc.</p>
+<p>Copyright &copy; 2016, 2018, 2020, 2021 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
@@ -359,7 +365,7 @@
 
 <p class="unprintable">Updated:
 <!-- timestamp start -->
-$Date: 2020/11/24 04:29:49 $
+$Date: 2021/12/30 02:29:58 $
 <!-- timestamp end -->
 </p>
 </div>

Index: po/license-compatibility.zh-cn.po
===================================================================
RCS file: /web/www/www/licenses/po/license-compatibility.zh-cn.po,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -b -r1.10 -r1.11
--- po/license-compatibility.zh-cn.po   30 Dec 2021 02:11:28 -0000      1.10
+++ po/license-compatibility.zh-cn.po   30 Dec 2021 02:29:58 -0000      1.11
@@ -14,7 +14,6 @@
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"X-Outdated-Since: 2021-12-29 15:55+0000\n"
 
 #. type: Content of: <title>
 msgid ""
@@ -42,8 +41,8 @@
 #. type: Content of: <div><p>
 msgid ""
 "There is no problem merging programs that have the same license, if it is a "
-"reasonably behaved license, as nearly all free licenses are.<a href="
-"\"#f2\">[2]</a>"
+"reasonably behaved license, as nearly all free licenses are.<a href=\"#f2\">"
+"[2]</a>"
 msgstr ""
 "如果两个软件使用同æ 
·çš„许可证,应该没有问题,假定该许可证象几
乎所有的自由软件"
 "许可证一样顺理成章。<a href=\"#f2\">[2]</a>"
@@ -105,8 +104,8 @@
 msgstr ""
 "在把使用松散型许可证的代ç 
åˆåœ¨ä¸€èµ·æ—¶ï¼Œç»„合程序的每个部分都带有自己的许可证。"
 "当这些代码交织在一起无
法分辨时,组合程序应该带上所有代ç 
çš„许可证。由于这些许"
-"可证都是松散型的,所以å…
¨éƒ½å¸¦ä¸Šé™¤äº†å¤ªé•¿ä¹‹å¤–也没有别的问题。<a href="
-"\"#f3\">[3]</a>"
+"可证都是松散型的,所以å…
¨éƒ½å¸¦ä¸Šé™¤äº†å¤ªé•¿ä¹‹å¤–也没有别的问题。<a href=\"#f3\">[3]"
+"</a>"
 
 #. type: Content of: <div><p>
 msgid ""



reply via email to

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