www-commits
[Top][All Lists]
Advanced
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

www gnu/thegnuproject.zh-cn.html gnu/po/thegnup...

From: GNUN
Subject: www gnu/thegnuproject.zh-cn.html gnu/po/thegnup...
Date: Tue, 1 Oct 2019 22:59:48 -0400 (EDT) 
CVSROOT:        /web/www
Module name:    www
Changes by:     GNUN <gnun>     19/10/01 22:59:48

Modified files:
        gnu            : thegnuproject.zh-cn.html 
        gnu/po         : thegnuproject.zh-cn.po 
        licenses/po    : javascript-labels.translist 
Added files:
        licenses       : javascript-labels.zh-cn.html 
        licenses/po    : javascript-labels.zh-cn-en.html 

Log message:
        Automatic update by GNUnited Nations.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/thegnuproject.zh-cn.html?cvsroot=www&r1=1.11&r2=1.12
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/thegnuproject.zh-cn.po?cvsroot=www&r1=1.10&r2=1.11
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/javascript-labels.zh-cn.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/javascript-labels.translist?cvsroot=www&r1=1.11&r2=1.12
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/javascript-labels.zh-cn-en.html?cvsroot=www&rev=1.1

Patches:
Index: gnu/thegnuproject.zh-cn.html
===================================================================
RCS file: /web/www/www/gnu/thegnuproject.zh-cn.html,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- gnu/thegnuproject.zh-cn.html        16 Feb 2019 12:59:25 -0000      1.11
+++ gnu/thegnuproject.zh-cn.html        2 Oct 2019 02:59:48 -0000       1.12
@@ -300,7 +300,7 @@
 
有些GNU程序的开发是为了对付威胁我们自由的某些特殊敌人。为此，我们开发了gzip来代替Compress程序，该程序由于<acronym
 
title="Lempel-Ziv-Welch">LZW</acronym>专利而离开自由社区。我们找人开发LessTif，最近又开始开发<acronym
 title="GNU Network Object Model
-Environment">GNOME</acronym>和Harmony，用来解决由于某些专利库（见下）带来的问题。我们还在开发GNU
 Privacy
+Environment">GNOME</acronym>和Harmony，用来解决由于某些专有库（见下）带来的问题。我们还在开发GNU
 Privacy
 Guard来代替非自由的加密软件，因
为用户不应该在自由和隐私之间做选择。</p>
 <p>
 当然，编程的人对这些工作很感兴趣，并且许多人因
为自己需要和兴趣添加
了许多功能。但那不是这些程序存在的理由。</p>
@@ -518,7 +518,7 @@
 <p class="unprintable"><!-- timestamp start -->
 最后更新：
 
-$Date: 2019/02/16 12:59:25 $
+$Date: 2019/10/02 02:59:48 $
 
 <!-- timestamp end -->
 </p>

Index: gnu/po/thegnuproject.zh-cn.po
===================================================================
RCS file: /web/www/www/gnu/po/thegnuproject.zh-cn.po,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -b -r1.10 -r1.11
--- gnu/po/thegnuproject.zh-cn.po       2 Oct 2019 02:53:38 -0000       1.10
+++ gnu/po/thegnuproject.zh-cn.po       2 Oct 2019 02:59:48 -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: 2018-03-31 00:56+0000\n"
 
 #. type: Content of: <title>
 msgid "About the GNU Project - GNU Project - Free Software Foundation"

Index: licenses/po/javascript-labels.translist
===================================================================
RCS file: /web/www/www/licenses/po/javascript-labels.translist,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- licenses/po/javascript-labels.translist     13 Dec 2018 02:28:30 -0000      
1.11
+++ licenses/po/javascript-labels.translist     2 Oct 2019 02:59:48 -0000       
1.12
@@ -7,6 +7,7 @@
 <span dir="ltr"><a lang="ja" hreflang="ja" 
href="/licenses/javascript-labels.ja.html">日本語</a>&nbsp;[ja]</span> &nbsp;
 <span dir="ltr"><a lang="pt-br" hreflang="pt-br" 
href="/licenses/javascript-labels.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/javascript-labels.ru.html">русский</a>&nbsp;[ru]</span> 
&nbsp;
+<span dir="ltr"><a lang="zh-cn" hreflang="zh-cn" 
href="/licenses/javascript-labels.zh-cn.html">简体中文</a>&nbsp;[zh-cn]</span>
 &nbsp;
 </p>
 </div>' -->
 <link rel="alternate" type="text/html" href="/licenses/javascript-labels.html" 
hreflang="x-default" />
@@ -15,4 +16,5 @@
 <link rel="alternate" type="text/html" lang="ja" hreflang="ja" 
href="/licenses/javascript-labels.ja.html" title="日本語" />
 <link rel="alternate" type="text/html" lang="pt-br" hreflang="pt-br" 
href="/licenses/javascript-labels.pt-br.html" title="português do Brasil" />
 <link rel="alternate" type="text/html" lang="ru" hreflang="ru" 
href="/licenses/javascript-labels.ru.html" title="русский" />
+<link rel="alternate" type="text/html" lang="zh-cn" hreflang="zh-cn" 
href="/licenses/javascript-labels.zh-cn.html" title="简体中文" />
 <!-- end translist file -->

Index: licenses/javascript-labels.zh-cn.html
===================================================================
RCS file: licenses/javascript-labels.zh-cn.html
diff -N licenses/javascript-labels.zh-cn.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ licenses/javascript-labels.zh-cn.html       2 Oct 2019 02:59:48 -0000       
1.1
@@ -0,0 +1,175 @@
+<!--#set var="ENGLISH_PAGE" value="/licenses/javascript-labels.en.html" -->
+
+<!--#include virtual="/server/header.zh-cn.html" -->
+<!-- Parent-Version: 1.86 -->
+
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>JavaScript 许可证的网络标签 - GNU 工程 - 
自由软件基金会</title>
+
+<!--#include virtual="/licenses/po/javascript-labels.translist" -->
+<!--#include virtual="/server/banner.zh-cn.html" -->
+<h2>JavaScript 许可证的网络标签</h2>
+
+<p>如果你是一个为网站布署缩减版 JavaScript 
的网站管理员，那么这里有一个无
需修改缩减版文件本身来陈述其许可证和源代ç 
è·¯å¾„的方法。这个方法在
+JavaScript 程序使用 GNU 许可证时尤其有用，但是它不包括 Loic 
Duros 所著 <em><a
+href="/software/librejs/free-your-javascript.html">Setting Your JavaScript
+Free</a></em> 一文第 3.2 节建议的额外许可。</p>
+
+<p>JavaScript 许可证的网络标签是为缩减版 JavaScript 代ç 
è®¾è®¡çš„。该方法符合 GNU 软件许可证的相å…
³æ¡ä»¶ï¼Œè€Œä¸”它启用 LibreJS
+以保证网站信息的正确性。</p>
+
+<p>使用网络标签就是假定相关的 JavaScript
+源代码文件所包含的许可证声明是可以将源代码按ç…
§è‡ªç”±è®¸å¯è¯å‘布的。只有源代码是自由的，编译后的代ç 
æ‰æ˜¯è‡ªç”±çš„，而这就意味着其许可证是其源代ç 
è‡ªç”±å‘布的基础。如果这个不满足，那么你首å…
ˆè¦åšè¿™ä»¶äº‹ã€‚</p>
+
+<p>你也可以为非缩减版的 JavaScript
+文件使用网络æ 
‡ç­¾ï¼Œè¿™ä½¿å¾—程序能够有方法知道文件的许可证；但是文件是源代ç
 
ï¼Œæ‰€ä»¥è¯·æ˜Žæ–‡ä¹¦å†™è®¸å¯è¯å£°æ˜Žã€‚略去许可证声明会对这些文件的法律状态é€
 æˆä¸ç¡®å®šæ€§ã€‚</p>
+
+<p>网络标签不适用于直接包含在 HTML 页面中的内置 
JavaScript&mdash;&mdash;它们的许可证信息应该在 <a
+href="/software/librejs/free-your-javascript.html">所属的页面中直接表述</a>。</p>
+
+<p>更多关于我们设计此格式的解释，请参看 <a
+href="/licenses/javascript-labels-rationale.html">理由</a>。</p>
+
+<h3>编写标签页面</h3>
+
+<p>在你的网站添加一个 JavaScript 许可证网络标签的页面。你
可以使用一个方便的路径和文件名；å…
¶ä»–人将通过链接找到。该页面必须有一个属性为
+<code>id=&quot;jslicense-labels1&quot;</code>
+的表格。自动工具很容易根据该名字找到这个表æ 
¼ï¼Œè¿™ä¸ªåå­—也告诉自动工具表格的格式。表格的行包
括三个格子，它们提供的信息是网站使用的独立
+JavaScript 文件、其许可证和访问者如何获取其源代码。</p>
+
+<p>第一个格子里是网站使用的 JavaScript 的文件名。该格子必
须包含可以链接到该文件的导航标识，就像网站通篇使用的
+<code>script</code> 标识一样。</p>
+
+<p>第二个格子里是该 JavaScript
+文件的许可证。该格子必须包含链接到许可证全文的导航æ 
‡è¯†ï¼Œå…¶æ–‡æœ¬åŒ…含许可证å…
¨åã€ç‰ˆæœ¬å·ï¼ˆå¦‚果许可证有多个版本）和该文件是否会按ç…
§è®¸å¯è¯å°†æ¥çš„版本授权。一个好的许可证标识及其相å…
³é“¾æŽ¥å¦‚下：</p>
+
+<ul>
+<li><a href="/licenses/gpl-2.0.html">GNU-GPL-2.0-or-later</a></li>
+<li><a href="/licenses/gpl-3.0.html">GNU-GPL-3.0-or-later</a></li>
+<li><a href="/licenses/lgpl-2.1.html">GNU-LGPL-2.1-or-later</a></li>
+<li><a href="/licenses/lgpl-3.0.html">GNU-LGPL-3.0-or-later</a></li>
+<li><a href="/licenses/agpl-3.0.html">GNU-AGPL-3.0-or-later</a></li>
+<li><a 
href="http://www.apache.org/licenses/LICENSE-2.0";>Apache-2.0-only</a></li>
+<li><a 
href="http://directory.fsf.org/wiki/License:BSD_3Clause";>Modified-BSD</a></li>
+<li><a
+href="http://creativecommons.org/publicdomain/zero/1.0/legalcode";>CC0-1.0-only</a></li>
+<li><a href="http://www.jclark.com/xml/copying.txt";>Expat</a></li>
+<li><a href="http://www.mozilla.org/MPL/2.0";>MPL-2.0-or-later</a></li>
+</ul>
+
+<p>第三个格子提供指向 JavaScript 源代码的链接。该源代ç 
æ–‡ä»¶å¯ä»¥æ˜¯å•ä¸ªéžç¼©å‡ç‰ˆçš„ JavaScript
+文件、<code>.tar.gz</code> 档案、或是 <code>.zip</code> 
档案。如果源代码档案包含多个 JavaScript
+文件，那么该档案必须包含一个名为 <code>00-INDEX</code>
+的文件，该文件按顺序列出制造
该网站所需的单一文件应该由哪些独立文件合成。如果网站所用的
 JavaScript
+文件在第一个格子已经链接到源代码，那么第三个æ 
¼å­é‡Œå¯ä»¥å†å†™ä¸ŠåŒæ ·çš„ URL。</p>
+
+<p>下面是表格的示例。假定网站只使用一个 JavaScript 
文件：一个缩减版的 jQuery 1.7，按照 Expat
+许可证授权。表格列出文件及其许可证，还有指向源代ç 
çš„链接：</p>
+
+<pre><code>&lt;table id=&quot;jslicense-labels1&quot;&gt;
+
+&lt;tr&gt;
+&lt;td&gt;&lt;a 
href=&quot;/js/jquery-1.7.min.js&quot;&gt;jquery-1.7.min.js&lt;/a&gt;&lt;/td&gt;
+
+&lt;td&gt;&lt;a 
href=&quot;http://www.jclark.com/xml/copying.txt&quot;&gt;Expat&lt;/a&gt;&lt;/td&gt;
+
+&lt;td&gt;&lt;a 
href=&quot;/js/jquery-1.7.tar.gz&quot;&gt;jquery-1.7.tar.gz&lt;/a&gt;&lt;/td&gt;
+&lt;/tr&gt;
+
+&lt;/table&gt;
+</code></pre>
+
+<p>网页还有其他的文本和元素，包括网站的格式和导航工å…
·ï¼Œä½†æ˜¯è¯¥è¡¨æ ¼å¿…须显著的展现在页面上。</p>
+
+<h3>指向标签页面的链接</h3>
+
+<p>每个使用 JavaScript 的页面，都包括一个指向前文所述的æ 
‡ç­¾é¡µé¢çš„链接。将该链接的属性标记为
+<code>rel=&quot;jslicense&quot;</code>，这样自动工å…
·å°±å¯ä»¥æ‰¾åˆ°ã€‚例如，链接可以是这样的：</p>
+
+<pre><code>&lt;a href=&quot;/about/javascript&quot; 
rel=&quot;jslicense&quot;&gt;JavaScript license information&lt;/a&gt;
+</code></pre>
+
+<p>该链接可以不大，但是要明显让访问者看到。</p>
+
+<h3>注解</h3>
+
+<p>如果这些都做到了，那么你遵循了 GNU 软件许可证的相å…
³æ¡æ¬¾ï¼Œæ¯”如 GNU
+通用公共许可证。这样也应该充分符合了许多å…
¶ä»–自由软件许可证的要求，但是我们不能确信这就符合了所有自由软件许可证的要求。一如既往，请确信ä½
 ç†è§£å¹¶æŒ‰ç…§ä½ æ‰€ç”¨çš„自由软件许可证条款发布软件。</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; 2015, 2017, 2018, 2019 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/10/02 02:59:48 $
+
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+<!-- for class="inner", starts in the banner include -->
+</body>
+</html>

Index: licenses/po/javascript-labels.zh-cn-en.html
===================================================================
RCS file: licenses/po/javascript-labels.zh-cn-en.html
diff -N licenses/po/javascript-labels.zh-cn-en.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ licenses/po/javascript-labels.zh-cn-en.html 2 Oct 2019 02:59:48 -0000       
1.1
@@ -0,0 +1,198 @@
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.86 -->
+<title>JavaScript License Web Labels - GNU Project - Free Software 
Foundation</title>
+<!--#include virtual="/licenses/po/javascript-labels.translist" -->
+<!--#include virtual="/server/banner.html" -->
+
+<h2>JavaScript License Web Labels</h2>
+
+<p>If you are a webmaster deploying minified JavaScript on a site,
+here's a method for stating their licenses and source code locations
+without altering the minified files themselves.  It's especially helpful in 
cases where
+the JavaScript is under one of the GNU licenses, but does not include
+the additional permission proposed in Section 3.2 of <em><a
+href="/software/librejs/free-your-javascript.html">Setting Your
+JavaScript Free</a></em>, by Loic Duros.</p>
+
+<p>The JavaScript license web labels method is meant for files of
+minified JavaScript code.  This method complies with the relevant
+conditions in the GNU software licenses, and it enables LibreJS to
+confirm the correctness of the information on a site.</p>
+
+<p>Using web labels presumes that the corresponding JavaScript source
+files carry license notices that properly release them under a free
+license.  The compiled code isn't free unless its source code is, and
+indicating the license is essential for proper release of free source
+code.  If you haven't done that, you should do that first.</p>
+
+<p>You can use web labels on non-minified JavaScript files too, to
+indicate their licenses in a way a program can recognize; but these
+are source files, so please don't fail to give them human-readable
+license notices.  Omitting those notices creates uncertainty about
+these files legal status.</p>
+
+<p>The web labels method is not applicable to inline JavaScript
+included directly in HTML pages &mdash; their license information
+should be <a href="/software/librejs/free-your-javascript.html">stated
+directly in those pages</a>.</p>
+
+<p>For more
+explanation of why we designed this format, see the
+<a href="/licenses/javascript-labels-rationale.html">rationale</a>.</p>
+
+<h3>Writing the labels page</h3>
+
+<p>Add a page for JavaScript license web labels to your site.  You can
+use whatever path or filename is most convenient for you; others will
+find it through links.  The page must include one table marked with
+the attribute <code>id=&quot;jslicense-labels1&quot;</code>.  This name lets
+automated tools find the table easily, and tells them what format to
+expect.  Each row of this table will contain three cells, providing
+information about a standalone JavaScript file used on the site, its
+license, and how visitors can obtain its source code.</p>
+
+<p>The first cell of each row names a JavaScript file used by the
+site.  The cell must contain an anchor tag that links to that file,
+just as
+<code>script</code> tags throughout the site do.</p>
+
+<p>The second cell provides information about the license of this
+JavaScript file.  The cell must contain an anchor tag whose link
+refers to the full license text, and whose text provides the license's
+full name, and if the license has multiple versions, the version
+number and whether or not the file is licensed under later versions of
+the license.  Good license identifiers and their associated links
+are:</p>
+
+<ul>
+<li><a href="/licenses/gpl-2.0.html">GNU-GPL-2.0-or-later</a></li>
+<li><a href="/licenses/gpl-3.0.html">GNU-GPL-3.0-or-later</a></li>
+<li><a href="/licenses/lgpl-2.1.html">GNU-LGPL-2.1-or-later</a></li>
+<li><a href="/licenses/lgpl-3.0.html">GNU-LGPL-3.0-or-later</a></li>
+<li><a href="/licenses/agpl-3.0.html">GNU-AGPL-3.0-or-later</a></li>
+<li><a 
href="http://www.apache.org/licenses/LICENSE-2.0";>Apache-2.0-only</a></li>
+<li><a 
href="http://directory.fsf.org/wiki/License:BSD_3Clause";>Modified-BSD</a></li>
+<li><a 
href="http://creativecommons.org/publicdomain/zero/1.0/legalcode";>CC0-1.0-only</a></li>
+<li><a href="http://www.jclark.com/xml/copying.txt";>Expat</a></li>
+<li><a href="http://www.mozilla.org/MPL/2.0";>MPL-2.0-or-later</a></li>
+</ul>
+
+<p>The third cell provides a link to the JavaScript's source code.
+The source code file can be a single, unminified JavaScript file, a
+<code>.tar.gz</code> archive, or a <code>.zip</code> archive.  If a source 
archive includes
+multiple JavaScript files, the archive must include a file named
+<code>00-INDEX</code> that lists the order in which individual source files
+should be concatenated to produce a single file that's
+equivalent to what's hosted on the site.  If the JavaScript as it's
+served from the site, and linked from the first cell, is already in
+source code form, link to the same URL again in this cell.</p>
+
+<p>Below is an example table for illustration.  This site just uses
+one JavaScript file: a minified version of jQuery 1.7, distributed
+under the Expat license.  The table lists the file with corresponding
+license information and a link to full source code:</p>
+
+<pre><code>&lt;table id=&quot;jslicense-labels1&quot;&gt;
+
+&lt;tr&gt;
+&lt;td&gt;&lt;a 
href=&quot;/js/jquery-1.7.min.js&quot;&gt;jquery-1.7.min.js&lt;/a&gt;&lt;/td&gt;
+
+&lt;td&gt;&lt;a 
href=&quot;http://www.jclark.com/xml/copying.txt&quot;&gt;Expat&lt;/a&gt;&lt;/td&gt;
+
+&lt;td&gt;&lt;a 
href=&quot;/js/jquery-1.7.tar.gz&quot;&gt;jquery-1.7.tar.gz&lt;/a&gt;&lt;/td&gt;
+&lt;/tr&gt;
+
+&lt;/table&gt;
+</code></pre>
+
+<p>This page may include other text and markup, including your site's
+normal layout and navigation tools, but the table must be displayed
+prominently on it.</p>
+
+<h3>Links to the labels page</h3>
+
+<p>On each page that uses JavaScript, include a link that points to
+the labels page described above.  Mark this link with the
+attribute <code>rel=&quot;jslicense&quot;</code>, so that automated tools can
+find it.  For example, your final link might look like this:</p>
+
+<pre><code>&lt;a href=&quot;/about/javascript&quot; 
rel=&quot;jslicense&quot;&gt;JavaScript license information&lt;/a&gt;
+</code></pre>
+
+<p>This link can be small, but it should be clearly visible to people
+who visit your site.</p>
+
+<h3>Notes</h3>
+
+<p>If you do these things, you will comply with the relevant
+conditions in the GNU software licenses, such as the GNU General
+Public License.  They should also suffice to comply with many other
+free software licenses, but we can't say with certainty that they will
+comply with all of them.  As always, please make sure you understand
+and follow the license conditions of any free software you
+distribute.</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; 2015, 2017, 2018, 2019 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/10/02 02:59:48 $
+<!-- timestamp end -->
+</p>
+</div>
+</div><!-- for class="inner", starts in the banner include -->
+</body>
+</html>
reply via email to
[Prev in Thread] Current Thread [Next in Thread]