www-commits
[Top][All Lists]
Advanced

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

www/licenses po/javascript-labels-rationale.tra...


From: GNUN
Subject: www/licenses po/javascript-labels-rationale.tra...
Date: Fri, 4 Oct 2019 08:58:54 -0400 (EDT)

CVSROOT:        /web/www
Module name:    www
Changes by:     GNUN <gnun>     19/10/04 08:58:54

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

Log message:
        Automatic update by GNUnited Nations.

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

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

Index: po/javascript-labels-rationale.zh-cn.po
===================================================================
RCS file: /web/www/www/licenses/po/javascript-labels-rationale.zh-cn.po,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- po/javascript-labels-rationale.zh-cn.po     4 Oct 2019 12:54:27 -0000       
1.1
+++ po/javascript-labels-rationale.zh-cn.po     4 Oct 2019 12:58:54 -0000       
1.2
@@ -13,7 +13,7 @@
 "Language: zh_CN\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit"
+"Content-Transfer-Encoding: 8bit\n"
 
 #. type: Content of: <title>
 msgid ""

Index: javascript-labels-rationale.zh-cn.html
===================================================================
RCS file: javascript-labels-rationale.zh-cn.html
diff -N javascript-labels-rationale.zh-cn.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ javascript-labels-rationale.zh-cn.html      4 Oct 2019 12:58:53 -0000       
1.1
@@ -0,0 +1,136 @@
+<!--#set var="ENGLISH_PAGE" 
value="/licenses/javascript-labels-rationale.en.html" -->
+
+<!--#include virtual="/server/header.zh-cn.html" -->
+<!-- Parent-Version: 1.77 -->
+
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>JavaScript 许可证网络标签:背景和理由 - GNU 工程 - 
自由软件基金会</title>
+
+<!--#include virtual="/licenses/po/javascript-labels-rationale.translist" -->
+<!--#include virtual="/server/banner.zh-cn.html" -->
+<h2>JavaScript 许可证网络标签:背景和理由</h2>
+
+<h3>简介</h3>
+
+<p>现如今,人们在网络浏览时通常都会在电脑里运行大量的专有软件,而大多数时间他们并不知æƒ
…。自由软件在电脑桌面上的胜利有一部分要归结于 copyleft
+的保护:使用户一定要被告知她有使用、学习
、分享和修改自由软件的自由。在网络上,浏览器下载和运行
 JavaScript
+并不会告知用户所用程序的许可证、拥有的自由&mdash;&mdash;或è€
…被剥夺的自由。</p>
+
+<p>针对这一问题,我们开发了 <a href="/software/librejs">LibreJS 
程序</a>,它会甄别非寻常的 JavaScript
+代码并查看其许可证。它的功能实现有赖于代ç 
çš„许可证按照程序可以认识的方式标记。另外,所有 GNU
+软件许可证都要求其发行者在软件中陈述其许可证,因此å…
¶æŽ¥æ”¶è€…知晓他们的权利,并且知道去哪里找到源代码。</p>
+
+<p> 标记许可证的简单方法就是 <a 
href="/philosophy/javascript-trap.html">在 JavaScript
+代码中用特定æ 
¼å¼æ³¨è§£è®¸å¯è¯</a>。不过,对于缩减版库文件,这个可能不是太方便,所以我们为之设计了另一种陈述许可证的方法:<a
+href="/licenses/javascript-labels.html">JavaScript 网络标签</a>。</p>
+
+<h3>理由</h3>
+
+<p>当软件通过网络或其他互联网渠
道发布时,自由软件许可证要求许可证拷贝和软件源代ç 
æ€»æ˜¯åº”该简便易得。然而,发布嵌入在网站里的 JavaScript
+由于特定的因素变得复杂:网站访问者
通常不是表达了请求而获得软件,而且网管只能提供一份 
JavaScript
+代码文件(因此,他们无法按ç…
§è®¸å¯è¯çš„要求,比如,发送包含其他源代ç 
æ–‡ä»¶çš„档案)。</p>
+
+<p>这些因素组合在一起就造成网管只有少数几
个明显的方法来提供自由软件许可证要求的材料。最简单的方案是只按ç
…§æºä»£ç çš„形式使用
+JavaScript,而源代码的注释中有一份许可证的å…
¨æ–‡æ‹·è´ã€‚对小型网站,这个方案还可以接收,但是当 
JavaScript
+开始为大量重复的访问量使用的时候,可以理解网管就不再愿意提供如此大量的数据。我们的方案给网管们指明一个放置额外许可证资源的明确位置&mdash;&mdash;也给访问è€
…
一个明确的位置来找到这些资源&mdash;&mdash;这就解决了两方面的问题。第一,它通过提供一个
+&ldquo;JavaScript 许可证信息&rdquo;
+的链接让软件发布信息明确化。网管可以使用链接指向的位置发布许可证要求的资料,而这些对访问è€
…重要的资料也不会使他们产生迷惑。</p>
+
+<h3>机器可读性</h3>
+
+<p>为了让人们能够更容易地拒绝浏览器里的非自由 
JavaScript,我们的方案足够具体,插件或å…
¶ä»–软件可以检测网站的 JavaScript
+许可证信息表,并确认所有的 JavaScript 
都符合已知的自由软件许可证,还可以下载源代ç 
å¹¶ç¡®è®¤ç½‘站使用的是相应的 JavaScript
+优化代码。如此,访问者就能够快速而方便地检查这些 
JavaScript 是否自由,并决定是否要运行它们。<a
+href="/software/librejs/">LibreJS</a> 是一个基于 Mozilla 
浏览器的插件,它可以帮助用户避免运行非自由的
+JavaScript,并将实施这些检查来增强它的能力。</p>
+
+<p>我们曾经考虑使用另一种格式,比如
+RDF,作为我们系统的基础,这æ 
·å¯ä»¥é€šè¿‡ç»™ç¨‹åºå‘˜æ›´è¯¦ç»†å’Œæ›´å®¹æ˜“实现机器解析的信息让他们的工作更简单。但是,我们的目æ
 ‡é¦–先是让人获得这些信息,其次才是机器。使用结构良好的
+HTML 是最符合上述优先级的选择。</p>
+
+<h3>下一步</h3>
+
+<p>我们并没有说使用 JavaScript
+自由软件的网管必
须采纳这个指定的方法才能遵循许可证。每个自由软件许可证都明确列出了它们的条件,而每个愿意使用不同方法来遵循这些条件的网管都是受欢迎的。不过,我们的方法å
…·æœ‰è®©è®¿é—®è€…访问许可证信息å…
¨æ–‡çš„好处&mdash;&mdash;这是迄今大家一直努力解决的问题&mdash;&mdash;同时也不å¿
…牺牲网管提供
+JavaScript 的自选最优方式。</p>
+
+<p>我们非常愿意听到可以完成同样目æ 
‡ï¼Œè€ŒåŒæ—¶åˆä½¿ç³»ç»Ÿå¯¹ç½‘管、网站访问者
或许可证检查软件的开发者
更有用的反馈和建议。如果我们得到了能够显著改进这个方法的å
……
分建议,我们会发布新的方法。(这也是此方法使用详细的许可证信息表æ
 ¼ä½œä¸ºæ ‡è¯†çš„原因:å…
è®¸è½¯ä»¶åŒºåˆ†æ­¤æ–¹æ³•å’Œå°†æ¥çš„新方法。)如果你对此感å…
´è¶£ï¼Œè¯·
+<a href="https://lists.gnu.org/mailman/listinfo/bug-librejs";>订阅 LibreJS
+邮件列表</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 3.0 US.  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; 2014 Free Software Foundation, Inc.</p>
+
+<p>本页面使用 <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/";>Creative Commons
+Attribution-NoDerivs 3.0 United States 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/04 12:58:53 $
+
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>

Index: po/javascript-labels-rationale.zh-cn-en.html
===================================================================
RCS file: po/javascript-labels-rationale.zh-cn-en.html
diff -N po/javascript-labels-rationale.zh-cn-en.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ po/javascript-labels-rationale.zh-cn-en.html        4 Oct 2019 12:58:54 
-0000       1.1
@@ -0,0 +1,172 @@
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.77 -->
+<title>JavaScript License Web Labels: Background and rationale - GNU Project - 
Free Software Foundation</title>
+<!--#include virtual="/licenses/po/javascript-labels-rationale.translist" -->
+<!--#include virtual="/server/banner.html" -->
+
+<h2>JavaScript License Web Labels: Background and rationale</h2>
+
+<h3>Introduction</h3>
+
+<p>Users browsing the Web nowadays typically run huge amounts of
+proprietary software on their computers, often unknowingly.  Free
+software is succeeding on the desktop partly because of the copyleft
+protection guaranteeing users be told up front when a particular
+program is free for them to use, study, share, and modify.  On the
+Web, browsers download and run JavaScript without ever informing users
+of the program's license or their freedoms &mdash; or how other
+programs deny users' freedoms.</p>
+
+<p>To address this problem, we developed
+the <a href="/software/librejs"> LibreJS program </a> which recognizes
+nontrivial JavaScript code and checks its license.  Its functioning
+depends on specifying licenses in a way that a program which lacks
+human intelligence can reliably recognize.  In addition, all GNU
+software licenses require distributors to state the license with the
+software, so recipients know their rights, and to say where to find
+the source code.</p>
+
+<p> The simple way to specify the license is with
+a <a href="/philosophy/javascript-trap.html"> stylized comment in the
+JavaScript code</a>.  However, that can be inconvenient for minified
+library files, so we have developed another way to state their
+licenses: <a href="/licenses/javascript-labels.html"> JavaScript web
+labels</a>.</p>
+
+<h3>Rationale</h3>
+
+<p>Conditions in free software licenses to include a copy of the
+license terms and access to source code are almost always easy to
+follow when software is distributed through the Web or other Internet
+channels.  However, distributing JavaScript embedded in Web sites is
+complicated by a couple of unique factors: visitors usually receive
+the software without expressly requesting it, and webmasters can only
+serve a single file of JavaScript code (so they can't, for example,
+send an archive file that includes other resources required by the
+license).</p>
+
+<p>These issues combined leave webmasters with few obvious ways to
+provide additional material required by free software licenses.  The
+simplest solution would be to serve only JavaScript in source code
+form, with a full copy of the license in its comments.  That can be
+acceptable on smaller sites, but when JavaScript begins to represent a
+lot of repeat traffic, webmasters are understandably reluctant to
+serve so much data.  Our method gives them a clear place to serve
+additional license resources&mdash;and visitors a clear place to look
+for it&mdash;by addressing both of these points.  First, it makes the
+software distribution visible by offering &ldquo;JavaScript license
+information&rdquo; through a link.  The linked page gives webmasters a
+space where they can publish those resources that's appropriately
+prominent but not confusing to visitors.</p>
+
+<h3>Machine readability</h3>
+
+<p>In order to make it easier for people to reject nonfree JavaScript
+in their browsers, our method is specific enough for a plug-in or
+other software to find the site's table of JavaScript license
+information, confirm that all of the JavaScript is under a known free
+license, download the source code, and confirm that it corresponds to
+the optimized JavaScript that's being served from the site.  This way,
+visitors can quickly and conveniently check whether or not the
+JavaScript is free, and decide accordingly whether or not they want to
+run it.  <a href="/software/librejs/">LibreJS</a> is a plug-in
+for Mozilla-based browsers that helps users avoid running nonfree
+JavaScript, and it will implement these checks to enhance its
+capabilities.</p>
+
+<p>We considered using another format like RDF as the basis for our
+system, in order to simplify this job for programmers by giving them
+more detailed information in an easily parsed format.  However, our
+goal was to make this information accessible to human readers first,
+and machines second.  Using well-structured HTML provided the best
+match with those priorities.</p>
+
+<h3>Next steps</h3>
+
+<p>We are not saying that webmasters that host free software
+JavaScript must follow this specific method to comply with the
+licenses.  Every free software license clearly lays out its own
+conditions, and any webmaster who wants to use a different method that
+meets those conditions is welcome to do so.  However, this method has
+the benefit of making full license information readily accessible to
+visitors&mdash;an issue that's been a struggle to address to
+date&mdash;without compromising webmasters' ability to serve
+JavaScript the way they feel is best.</p>
+
+<p>We are very interested to hear feedback and suggestions about other
+ways we might accomplish the same goals, while making the system more
+useful for webmasters, site visitors, or developers working on
+license-checking software.  If we get enough suggestions to publish a
+new method that's noticeably improved over this one, we'll do so.
+(That's why this method uses such a verbose identifier for the license
+information table: to allow software to distinguish this method from
+others we might craft in the future.)  If this is an issue that you're
+interested in,
+please <a href="https://lists.gnu.org/mailman/listinfo/bug-librejs";>subscribe
+to the LibreJS mailing list</a>, and write there with your comments
+and suggestions.  We look forward to hearing from you.</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 3.0 US.  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; 2014 Free Software Foundation, Inc.</p>
+
+<p>This page is licensed under a <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/";>Creative
+Commons Attribution-NoDerivs 3.0 United States License</a>.</p>
+
+<!--#include virtual="/server/bottom-notes.html" -->
+
+<p class="unprintable">Updated:
+<!-- timestamp start -->
+$Date: 2019/10/04 12:58:54 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>



reply via email to

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