[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www/licenses po/gcc-exception-3.1-faq.translist...
|
From: |
GNUN |
|
Subject: |
www/licenses po/gcc-exception-3.1-faq.translist... |
|
Date: |
Fri, 30 Nov 2018 22:27:54 -0500 (EST) |
CVSROOT: /web/www
Module name: www
Changes by: GNUN <gnun> 18/11/30 22:27:54
Modified files:
licenses/po : gcc-exception-3.1-faq.translist
gcc-exception-3.1-faq.zh-cn.po
Added files:
licenses : gcc-exception-3.1-faq.zh-cn.html
licenses/po : gcc-exception-3.1-faq.zh-cn-en.html
Log message:
Automatic update by GNUnited Nations.
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/gcc-exception-3.1-faq.zh-cn.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/gcc-exception-3.1-faq.translist?cvsroot=www&r1=1.14&r2=1.15
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/gcc-exception-3.1-faq.zh-cn.po?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/gcc-exception-3.1-faq.zh-cn-en.html?cvsroot=www&rev=1.1
Patches:
Index: po/gcc-exception-3.1-faq.translist
===================================================================
RCS file: /web/www/www/licenses/po/gcc-exception-3.1-faq.translist,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -b -r1.14 -r1.15
--- po/gcc-exception-3.1-faq.translist 24 Sep 2018 12:58:28 -0000 1.14
+++ po/gcc-exception-3.1-faq.translist 1 Dec 2018 03:27:54 -0000 1.15
@@ -8,6 +8,7 @@
<span dir="ltr"><a lang="ja" hreflang="ja"
href="/licenses/gcc-exception-3.1-faq.ja.html">æ¥æ¬èª</a> [ja]</span>
<span dir="ltr"><a lang="pt-br" hreflang="pt-br"
href="/licenses/gcc-exception-3.1-faq.pt-br.html">português do Brasil</a> [pt-br]</span>
<span dir="ltr"><a lang="ru" hreflang="ru"
href="/licenses/gcc-exception-3.1-faq.ru.html">ÑÑÑÑкий</a> [ru]</span>
+<span dir="ltr"><a lang="zh-cn" hreflang="zh-cn"
href="/licenses/gcc-exception-3.1-faq.zh-cn.html">ç®ä½ä¸æ</a> [zh-cn]</span>
</p>
</div>' -->
<link rel="alternate" type="text/html"
href="/licenses/gcc-exception-3.1-faq.html" hreflang="x-default" />
@@ -17,4 +18,5 @@
<link rel="alternate" type="text/html" lang="ja" hreflang="ja"
href="/licenses/gcc-exception-3.1-faq.ja.html" title="æ¥æ¬èª" />
<link rel="alternate" type="text/html" lang="pt-br" hreflang="pt-br"
href="/licenses/gcc-exception-3.1-faq.pt-br.html" title="português do Brasil"
/>
<link rel="alternate" type="text/html" lang="ru" hreflang="ru"
href="/licenses/gcc-exception-3.1-faq.ru.html" title="ÑÑÑÑкий" />
+<link rel="alternate" type="text/html" lang="zh-cn" hreflang="zh-cn"
href="/licenses/gcc-exception-3.1-faq.zh-cn.html" title="ç®ä½ä¸æ" />
<!-- end translist file -->
Index: po/gcc-exception-3.1-faq.zh-cn.po
===================================================================
RCS file: /web/www/www/licenses/po/gcc-exception-3.1-faq.zh-cn.po,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- po/gcc-exception-3.1-faq.zh-cn.po 1 Dec 2018 03:06:17 -0000 1.1
+++ po/gcc-exception-3.1-faq.zh-cn.po 1 Dec 2018 03:27: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: gcc-exception-3.1-faq.zh-cn.html
===================================================================
RCS file: gcc-exception-3.1-faq.zh-cn.html
diff -N gcc-exception-3.1-faq.zh-cn.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ gcc-exception-3.1-faq.zh-cn.html 1 Dec 2018 03:27:54 -0000 1.1
@@ -0,0 +1,165 @@
+<!--#set var="ENGLISH_PAGE" value="/licenses/gcc-exception-3.1-faq.en.html" -->
+
+<!--#include virtual="/server/header.zh-cn.html" -->
+<!-- Parent-Version: 1.77 -->
+
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>GCCè¿è¡åºä¾å¤ççç±å常è§é®é¢è§£ç - GNUå·¥ç¨ -
èªç±è½¯ä»¶åºéä¼</title>
+
+<!--#include virtual="/licenses/po/gcc-exception-3.1-faq.translist" -->
+<!--#include virtual="/server/banner.zh-cn.html" -->
+<h2>GCCè¿è¡åºä¾å¤ççç±å常è§é®é¢è§£ç</h2>
+
+<h3>å¼è¨</h3>
+
+<p>2007å¹´6æ29æ¥ï¼èªç±è½¯ä»¶åºéä¼åå¸äºGPLv3ãå®é©¬ä¸è¢«15个GNU项ç®é纳ï¼å¨éåçå
个æå
ææ´å¤ç项ç®åæ¢å°äºè¯¥è®¸å¯è¯ãGCCç大å¤æ°ä»£ç
å¨4.2.2çæ¬åå¸æ¶é½éç¨äºæ°ç许å¯è¯ï¼ç°å¨æ们æ£å¨å¯¹æ¤è¿è¡æ¶å°¾ã</p>
+
+<p>æäºä¼´éGCCç软件åºç许å¯è¯è¿æ²¡æåæ´ãè¿äºè½¯ä»¶åºèªå¨è¢«GCC产ççç®æ
代ç 使ç¨ãå æ¤ï¼å¦æåªç®åå
许è¿äºåºæç
§GPLåå¸ï¼é£ä¹GCC产ççææç®æ 代ç é½å°éè¦æç
§åæ
·çæ¡æ¬¾åå¸ãç¶èï¼FSFå¾ä¹
以åå°±å³å®å
许å¼åè
使ç¨GCCç软件åºç¼è¯ä»»ä½ç¨åºï¼æ
论该ç¨åºä½¿ç¨ä½ç§è®¸å¯è¯ãå¼åéèªç±è½¯ä»¶å¯¹ç¤¾ä¼ä¸å©ï¼èä¸æ们ä¹æ²¡æä¹å¡ä½¿ä¹æ´å®¹æãæ们å
许è¿æ ·åæ¯å 为ç¦æ¢å®çæ¥æ¯éå¾å
¶åï¼å¦å¤çåå æ¯å
为使ç¨äºå
¶ä»å°è½¯ä»¶åºèéå¶GCCç使ç¨çæ¥æ¯æäºè麻丢äºè¥¿çã</p>
+
+<p>æ以ï¼è¿äºè½¯ä»¶åºä¸ç´æ¯è®¸å¯è¯ä¾å¤ï¼è¯¥ä¾å¤å
许人们å°ä½¿ç¨GCC产ççç®æ 代ç
ç¨ä»»ä½è®¸å¯è¯åå¸ãæ们ç°å¨å°è¿äºè½¯ä»¶åºç许å¯è¯æ¹å°GPLv3ï¼å¹¶æ´æ°è¿äºä¾å¤ãæ们çåºæ¬æ¿ç没æååï¼æ°ç许å¯è¯è¿æ¯å
许æç
§ä»¥åçæ¹å¼ä½¿ç¨GCCãä¸è¿ï¼æ们å³å®å©ç¨è¿ä¸ªæºä¼æ´æ°ä¾å¤è¾¾æ3个ç®çï¼</p>
+
+<ul>
+<li><p>å©ç¨GPLv3çæ°æ¡æ¬¾ãGPLv3æ好å
个æå©äºææ软件çæ°æ¡æ¬¾ãè¿å
¶ä¸å
æ¬ç¬¬7èï¼å®æ建äºä¸ä¸ªæä¾è®¸å¯è¯ä¾å¤çæ¡æ¶ã为äºä½¿GCCè½å¤æ大èå´å°ä»GPLv3è·çï¼æ们éè¦ä½¿ç¨ç¬¬7èçè¯è¨èèè¿äºæ°æ¡æ¬¾å¹¶æ´æ°ä¾å¤ã</p></li>
+<li><p>å¥ å®GCCæ件æ¶æçåºç¡ãé¿æ以æ¥ï¼GCCçå¼åè
ä¸ç´å¨èè为ç¼è¯å¨æ·»å
ä¸ä¸ªæ件æ¡æ¶ãè¿ä¼è®©å¤§å®¶ä¸ºGCC项ç®åè´¡ç®åå¾æ´å®¹æï¼å¹¶ä¸ä¹ä¼å
éGCCæ°ç¼è¯ææ¯çå¼åãç¶èï¼å
¶ä¸ä¹åå¨ç对ä¸æ©æ段çå¼åè
çæ
å¿ï¼ä»ä»¬åçæ件å¯è½ä¼è°ç¨ä¸æ软件æ¹åç¼è¯åç代ç
—è¿å®é
ä¸å°±æ¯ç»GCCæ·»å äºä¸æçæ©å±å¹¶æ«è´¥GPLçç®æ
ãæ´æ°åçä¾å¤ä¼é²æ¢è¿ç§æ»¥ç¨ï¼è®©GCCå¢éè½å¤å¼å§å±ææ件å¼åã</p></li>
+<li><p>ä¿ä½¿GCC代ç
çä¾å¤æ´ä½ä¸ä¸è´ãç»å¹´ç´¯æï¼éçéè¦è®¸å¯è¯ä¾å¤çæ件添å
å°GCCä¹ä¸ï¼æ们ä¸æ审æ¥åæ´æ°æ们çç¨è¯ä»¥æ¾æ¸
è¿äºä¾å¤å¹¶æ¶µçæ°çé®é¢ãç±æ¤å¯¼è´GCCä¸ç°å¨æ许å¤ä¸åçä¾å¤æåï¼å®ä»¬æä¾çåºæ¬è®¸å¯é½æ¯ä¸æ
·çãç°å¨ï¼ææè¿äºæ件é½å¯ä»¥ä½¿ç¨æ们æå®å¥½çåä¸æ°ä¾å¤æåï¼è¿ä½¿ä»£ç
çæ³å¾å®¡æ ¸åå¾æ´å®¹æã</p></li>
+</ul>
+
+<p>æ£å¦GPLv3ï¼æ们èææ¤ææ¶åªåå¬åäºå¤æ¹ç¨æ·çæè§ï¼å¹¶å¯¹è¿äºæè§ååºäºéå½çå¤çãæ»èè¨ä¹ï¼æ们为æ¤è±è´¹äºè¶
è¿ä¸å¹´çæ¶é´ãèªç±è½¯ä»¶åºéä¼åGCCæ§è¡å§åä¼æ谢软件èªç±æ³å¾ä¸å¿çRichard
+FontanaãBradley KuhnåKaren
+Sandlerï¼æè°¢ä»ä»¬å¯¹æ¤ä¾å¤æåçææè¾å¤åªåååå©ãè¿äºæ´æ°ä¼å¼ºåGCC社åºï¼æ们æå¾
å®ä¸ºç¼è¯å¨çå¼åæå¼æ°çç¯ç« ã</p>
+
+<p>GCC对å¼åè
æ¯å¦æ¤å
³é®ï¼æ们ææ³ä»ä»¬å¯¹æ¤æ´æ¹ä¼æé®é¢ï¼æ们å¸æè¿äºé®é¢é½æåºå¯¹ãä¸é¢ï¼æ们å举äºç¨æ·å¯è½ä¼æçæ
忧ãå¦æä½ å
³äºæ¤ä¾å¤çé®é¢æ²¡æååºï¼è¯·éæ¶éè¿<a
+href="mailto:address@hidden";><address@hidden></a>èç³»æ们ã</p>
+
+<h3>ä¾å¤æ¯æä¹åäº</h3>
+
+<p>ä½ éè¦ç许寗ç¨GCCåºæ代ç 转æ¢ææç
§ä½
ç许å¯è¯åå¸çç®æ ä»£ç —ä¸»è¦å¨ç¬¬1èä¸ï¼</p>
+
+<blockquote>
+ <p>ä½ ææä¼ æç±ç¬ç«æ¨¡ååè¿è¡åºç»åèæçç®æ 代ç
ä½åï¼å³ä½¿è¯¥ä¼ æä»å
¶ä»æ¹é¢æ¥çå¯è½è¿åäºGPLv3çæ¡æ¬¾ï¼åææ¯ææçç®æ 代ç
é½æ¯ç»ç±åæ³çç¼è¯è¿ç¨äº§ççãé£ä¹ä½
å¯ä»¥ä¸ºè¯¥ç»å使ç¨ä½
éæ©ç许å¯è¯æ¡æ¬¾ï¼åªè¦å®åç¬ç«æ¨¡åç许å¯è¯ä¸è´ã</p>
+</blockquote>
+
+<p>æ¬è使ç¨äºå¾å¤æ¯è¯ï¼è¿äºæ¯è¯çç¹å®å«ä¹åä¾å¤å¦ä½æä½ä¸å¯åå²ãæ¬è详解è¿äºæ¯è¯å常è§åºæ¯çå
³ç³»ã</p>
+
+<p>å½ä½ ç¼å软件æ¶ï¼è½¯ä»¶å°±å
å«äºä¸ç³»åæºä»£ç
æ件ãå¦æä¸ä¸ªæ件ä¸å
å«GCCåºéçæºä»£ç
ï¼é£ä¹è¿ä¸ªæ件就æ¯ä¸ä¸ª“ç¬ç«æ¨¡å”ã</p>
+
+<p>å½ä½ ç¼è¯è¿äºæºä»£ç
æ件æ¶ï¼å®ä»¬é常ä¼ç»åä¸ç³»åæ¥éª¤ï¼æºä»£ç
çæãé¢å¤çãç¼è¯æä½çº§ä»£ç ãæ±ç¼åè¿æ¥ãæ
¹æ®æç¨çè¯è¨å软件ç¼åçæ¹å¼ï¼æäºé¡¹ç®å¯è½æ²¡æ以ä¸ææçæ¥éª¤ï¼ä½æ¯å®ä»¬æ»ä¼æç
§è¿ä¸ªé¡ºåºæ§è¡ï¼ä½¿ç¨GCCç人ä¼æç
§è¿ä¸ªæ¥éª¤ä»é«çº§è¯è¨ç¼è¯å°è¯¸å¦æ±ç¼æJava
+bytecode<sup><a
+href="#TransNote1">1</a></sup>ãå¨è¿ä¸ªé¶æ®µï¼GCCæä½ ç代ç
åGCCåºå并æè¿æ¥èµ·æ¥ãæ们称ä¹ä¸º“ç¼è¯è¿ç¨ãåªè¦æ¤æ¶çè¾åºä¸æ¯ç¼è¯å¨è¿è¦ç¨çè¿æ¸¡ä»£ç
ï¼ä¹ä¸æ¯ç¼è¯å¨è¦è¾åºçè¿æ¸¡ä»£ç
ï¼”æ¤æ¶çè¾åºå°±å«å“ç®æ 代ç ã”</p>
+
+<p>è¦æ³å©ç¨æ¬è®¸å¯ï¼äº§çç®æ 代ç çç¼è¯è¿ç¨å¿
é¡»“åæ³”ï¼å°±æ¯è¯´å
¶ä¸æ²¡æå¼å
¥åGCC以åGPLä¸å
¼å®¹ç软件ãéè¦çä¸ç¹æ¯ç¼è¯è¿ç¨ä»ä½
æ<em>ä»»ä½</em>é«çº§è¯è¨ä»£ç è¾å
¥ç»GCCå°±å¼å§ï¼ä¸æ¦è¾åºäºç®æ
代ç å°±ç»æãå æ¤ï¼åªè¦GCC没æè¾åºè¿æ¸¡ä»£ç ï¼å³ä½¿ä½ ç¨å
¶ä»GPLä¸å
¼å®¹çæ±ç¼å¨ãè¿æ¥å¨æè
é«çº§è¯è¨äº§çå·¥å
·åGCCä¸èµ·å·¥ä½ï¼ä½ çç¼è¯è¿ç¨è¿å¯ä»¥æ¯åæ³çï¼è¿äºGPLä¸å
¼å®¹å·¥å
·æç
§æ们çå®ä¹ä¸ç®åä¸ç¼è¯è¿ç¨ãåªæä¸ä¸ªå°æ¹ä½
ä¸è½ä½¿ç¨è¿äºGPLä¸å
¼å®¹ç软件ï¼è¿å°±æ¯å½GCCå¨è¿è¡æ
¸å¿ç¼è¯å·¥ä½çæ¶åã</p>
+
+<p>æ以ï¼å¦æä½ ç¨äºGCCï¼ä¸ç®¡æ没æGPLä¸å
¼å®¹ç软件ï¼ç¼è¯è¿ç¨é½å¯ä»¥æ¯åæ³çãå¦æä½ åªç¨äºGPLå
¼å®¹çç¼è¯å·¥å
·ï¼ç¼è¯è¿ç¨ä¹æ¯åæ³çãï¼å³ä½¿ä½¿ç¨ä¸åçç¼è¯å¨ï¼äººä»¬ä¹å¸¸å¸¸ä¼ä¸ºGNU/Linux软件è¿æ¥GCCåºãï¼ä¸è¿ï¼å¦æä½
å¨æé«çº§è¯è¨ä»£ç 转æ¢æä½çº§è¯è¨ä»£ç çè¿ç¨ä¸ç¨äºGCCå
ä¸GPLä¸å
¼å®¹çå·¥å
·ï¼é£ä¹è¿å°±<em>ä¸æ¯</em>ä¸ä¸ªåæ³çç¼è¯è¿ç¨ãæ¯å¦ï¼ä½
使ç¨GCCå ä¸ä¸ä¸ªä¸æçæ件就æ¯è¿ä¹ä¸ä¸ªéæ³ç¼è¯è¿ç¨ã</p>
+
+<p>åªè¦ç¼è¯è¿ç¨æ¯åæ³çï¼é£ä¹ä½ ææ为GCC产ççç®æ 代ç
çå帓éæ©ä½ çæ¡æ¬¾ã”</p>
+
+<p>å¦æä½ å¨ç¼è¯è¿ç¨ä¸ä½¿ç¨äºGPLä¸å
¼å®¹çå·¥å
·ï¼é£ä¹ä½
ä¸è½ä½¿ç¨è¿é¡¹æå©ãç±äºGCC产ççç®æ 代ç
é½æ¥èªGPL软件åºï¼æ以å¦æè¦åå¸è¿äºç®æ 代ç
å°±è¦éµå¾ªGPLçæ¡æ¬¾ãä½ ä¸è½ä½¿ç¨GCCå¼åä½ èªå·±çGPLä¸å
¼å®¹è½¯ä»¶ã</p>
+
+<h3>常è§é®é¢è§£ç</h3>
+
+<dl>
+<dt>æ使ç¨çæ¯GCCçæ ååå¸çï¼æ¯å¦ç±FSFæä¾çï¼æè
æ¯æä½ç³»ç»èªå¸¦çï¼ï¼æç¨å®ç¼è¯GPLä¸å
¼å®¹è½¯ä»¶ãä¾å¤çæ´æ¹å¯¹ææä»ä¹å½±åï¼</dt>
+
+<dd><p>æ¤æ¬¡æ´æ¹ä¸ä¼å½±åä½ ãé¤éä½ æGCCé
ç½®æè¾åºè¿æ¸¡ä»£ç
—è¿ç§æ
åµå¾å°è§—æ°çä¾å¤æ¯è¦ç¡®ä¿ä½ è¿æ
·åæ¶æ²¡æè¿å许å¯è¯ï¼æ£å¦èçä¾å¤ä¸æ ·ã</p></dd>
+
+<dt>è¿ä¸ªåæ´ä¼å½±ååªäºäººï¼</dt>
+
+<dd><p>ç®å使ç¨GCCç人åºè¯¥ä¸ä¼åå°å½±åãå
¶ä¸å¯ä¸çæ¿çæ§ä¿®æ¹æ¯ä¸ºäºé²æ¢å¼åè
å¨<em>å°æ¥</em>对GCCçåè½ååºæäºä¿®æ¹ãFSFä¸ç´åGCCå¼åè
ç´§å¯åä½æ¥äºè§£äººä»¬ç®å使ç¨GCCçæ¹å¼ï¼ä»¥ç¡®ä¿ä»ä»¬å¨æ°çä¾å¤æ¡æ¬¾ä¸ä»ç¶è½å¤ç»§ç»æç
§å·²æçæ¹å¼ä½¿ç¨GCCã</p></dd>
+
+<dt>æ使ç¨GCCå ä¸ä¸æçé¢å¤çå·¥å
·/æºä»£ç çæå·¥å
·æ¥åç¼è¯ãæå¯ä»¥å©ç¨è¿ä¸ªä¾å¤åï¼</dt>
+
+<dd><p>æ¯çãç¼è¯è¿ç¨å¼å§äºä»»ä½“å®å
¨ç±é«çº§è¯è¨è¡¨è¾¾ç代ç ï¼èä¸æ¯è¿æ¸¡ä»£ç è¯è¨ã”è¿å
æ¬ç±é¢å¤çå·¥å
·æå
¶ä»ä¸æ软件çæç代ç ãè¿æ
·ï¼ç¼è¯è¿ç¨ä¸å
å«ä»»ä½ä¸æ软件ï¼å®æ¯åæ³çï¼ä¾å¤å¯¹è¿æ
·çç¨åºéç¨ã</p></dd>
+
+<dt>æ使ç¨GCCå
ä¸ä¸æçæ±ç¼å¨/è¿æ¥å¨åç¼è¯ãæè¿å¯ä»¥å©ç¨è¿ä¸ªä¾å¤åï¼</dt>
+
+<dd><p>æ¯çãç¼è¯è¿ç¨å½ç¼è¯å¨äº§çç®æ 代ç æ¶ç»æï¼è¿ä¸ªå
æ¬è¾åº“éç¨äºæ±ç¼å¨ãè½½å
¥å¨ãè¿æ¥å¨/è¿è¡ç¨åºçè¾å
¥æ件ã”æ¢å¥è¯è¯´ï¼å¨è¿ç§æ
åµä¸ç¼è¯è¿ç¨å¨GCCè¾åºæ±ç¼ä»£ç ææªè¿æ¥çç®æ
æ件æ¶å·²ç»ç»æï¼æ以å
¶ä¸ä¸å
å«ä»»ä½ä¸æ软件çåä¸ãå®æ¯åæ³çï¼ä¾å¤å¯¹è¿æ
·çç¨åºéç¨ã</p></dd>
+
+<dt>æ使ç¨GCCç¼è¯ç¨åºçä¸é¨åï¼ä½¿ç¨ä¸æ软件ç¼è¯ç¨åºçå
¶ä½é¨åãç¶åè¿äºé¨åå¨æ±ç¼æè¿æ¥é¶æ®µåå¨ä¸èµ·ãæè¿è½å©ç¨è¿ä¸ªä¾å¤åï¼</dt>
+
+<dd><p>æ¯çãå¨è¿ç§æ
åµä¸ï¼æ¯ä¸ªç¬ç«æ¨¡åé½æ¯æç
§åæ³çç¼è¯è¿ç¨åæç®æ 代ç
çã尽管ä¸å模åç»åäºä¸åçè¿ç¨ï¼è¯¥ä¾å¤è¿æ¯éç¨äºè¿ä¸ªç¨åºçã</p></dd>
+
+<dt>æ使ç¨ä¸å
å«ä»»ä½GCCæåçä¸æç¼è¯å¨ç¼è¯æçç¨åºï¼ç¶åå°å®ålibstdc++è¿æ¥èµ·æ¥ãæçç¨åºæ¬èº«ä¸å
å«ä»»ä½åç¨GCCç¼è¯çç¨åºé£æ
·çè¿è¡åºï¼libgccï¼ãæè¿è½å©ç¨è¿ä¸ªä¾å¤åï¼</dt>
+
+<dd><p>æ¯çãè½ç¶è¯¥ä¾å¤æ常è§çåºæ¯å¯è½æ¯ç¨äºælibgccåGCCç¼è¯çç®æ
代ç
åå¨ä¸èµ·ï¼ä½æ¯GPLåGCCè¿è¡åºä¾å¤é½ä¸åºåéæè¿æ¥ãå¨æè¿æ¥ä»¥åå
¶ä»åææ¹å¼ã该ä¾å¤è®¸å¯ä½ å¯ä»¥ç¨ï¼åæ ·çæ¡æ¬¾ï¼æ 论ä½
éç¨äºåªä¸ä¸ªåææ¹å¼ã</p>
+
+<p>请注æï¼å¦æä½ è¦åå¸çæ¯ç¬ç«çlibstdc++åºï¼é£ä¹ä½
éè¦æç
§GPLçæ¡æ¬¾æ¥åå¸ãæ¯å¦ï¼å¦æä½ çåºæ¯æç
§ç®æ 代ç
çå½¢å¼åå¸çï¼é£ä¹ä½
éè¦ä½¿ç¨ç±GPLv3第6èéè§å®çæ¹æ³ä¹ä¸æ¥æä¾æºä»£ç
ãä½æ¯åªè¦ä½
çç¨åºéç¨GCCè¿è¡åºä¾å¤ï¼GPLæ¡æ¬¾å°±ä¸ä¼æ©å±å°ä½
çç¨åºã</p></dd>
+
+<dt>为ä»ä¹ç¼è¯å¨è¿æ¸¡ä»£ç ä¸å¨“ç®æ 代ç
”çå®ä¹ä¹å
ï¼</dt>
+
+<dd><p>å½æ们第ä¸æ¬¡èèç»GCCæ·»å æ件æ¶ææ¶ï¼æ们é常æ
å¿æ人ä¼åä¸ä¸ªæ件æ¥ç®åæGCCçè¿æ¸¡ä»£ç ãåºå±ç¼è¯æ°æ®æ
¼å¼ä¿åå°ç£çãè¿æ ·çè¯ï¼å
¶ä»è½¯ä»¶å°±å¯ä»¥ä¸ç»GCCèä¼åææ¹è¿è¿äºä»£ç
ãæ们å¯è½å¾é¾äºè¾©è¯´è¿äºç¨åºåºè¯¥éµå¾ªGPLçcopyleftæ¡æ¬¾ï¼æ以æ们æ³è¦é»æ¢è¿ç§æ´»å¨ã</p>
+
+<p>æ们çåæ³æ¯æè¿äºè¾åºæé¤å¨ç®æ 代ç ä¹å¤ãæ£å
为å¦æ¤ï¼å³ä½¿æ人åäºä¿åä¸é´ä¿¡æ¯çæ件ï¼ä»»ä½å¨GCCè¾åºç®æ
代ç
ä¹åä¿®æ¹è¿äºä¿¡æ¯çç¨åºä¹é½åä¸å°äºç¼è¯è¿ç¨ä¹ä¸ãå¦æ该ç¨åºæ¯ä¸æ软件ï¼é£ä¹ä¾å¤å°±ä¸éç¨äºå®ç¼è¯ç软件ï¼GCCæåè¾åºçç®æ
代ç å°±å¿
é¡»æç
§GPLçæ¡æ¬¾æ¥åå¸ã</p></dd>
+
+<dt>å¦ææåäºä¸äºæ±ç¼è¯è¨ç代ç ï¼ææ¯å¦è¿å¯ä»¥æå®åå
¶ä»æ£å¸¸ç¼è¯çç®æ 代ç åå¨ä¸èµ·ï¼å¹¶å©ç¨è¯¥ä¾å¤ï¼</dt>
+
+<dd><p>æ¯çï¼åªè¦è¿äºç®æ 代ç
æ¯ç»ç±åæ³ç¼è¯è¿ç¨äº§ççãå¨æ±ç¼å¨éè·æåçæ±ç¼ä»£ç
å°±æ¯ä¸ä¸ªç¼è¯è¿ç¨ï¼å 为å®æ让人ç¼å代ç
ç[a]éè¿æ¸¡æ§è¯è¨[]ç代ç 转æ¢æ...ç®æ 代ç ã”</p></dd>
+
+<dt>GCCè¿è¡åºä¾å¤å
å«åªäºåºï¼</dt>
+
+<dd><p>GCCè¿è¡åºä¾å¤æ¶µçäºææç许å¯è¯è¯´æééè¿°äºä¾å¤éç¨çæ件ãè¿å
æ¬libgccãlibstdc++ãlibfortranãlibgompãlibdecnumberãlibgcov以åå
¶ä»åGCCä¸èµ·åå¸çåºã</p></dd>
+
+<dt>Classpathä¼ä½¿ç¨è¯¥ä¾å¤åï¼</dt>
+
+<dd><p>尽管Classpathå½åçä¾å¤èµ·çç¸ä¼¼çä½ç¨ï¼æ们è¿æ¬¡ä¹è¿æ²¡ææ´æ°å®ãå
为èªç±è½¯ä»¶Java社åºçææ°åå±ï¼Classpath许å¯è¯æ¿ççä¼å
级åå
¶ä»GCCåºææä¸åï¼æ们ä¼åç¬è¯ä¼°ã</p></dd></dl>
+<div class="translators-notes">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.-->
+<h3>è¯æ³¨</h3>
+<ol>
+<li id="TransNote1">Java
+bytecodeï¼è¿æ¯Javaè¯è¨ç¼è¯åçä¸é´è¯è¨ï¼å°±åæ±ç¼æ¯C/C++ç¼è¯åçä¸é´è¯è¨ä¸æ
·ã</li>
+</ol></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ï¼&GNUçä¸è¬æ§é®é¢åéå°<a
+href="mailto:address@hidden";><address@hidden></a>ãä¹å¯ä»¥éè¿<a
+href="/contact/">å
¶ä»èç³»æ¹æ³</a>èç³»èªç±è½¯ä»¶åºéä¼(FSF)ã请å°æ æé¾æ¥ï¼å
¶ä»é误æ建议åéç»<a
+href="mailto:address@hidden";><address@hidden></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";>
+
+ <address@hidden></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="/server/standards/README.translations.html">ç¿»è¯é¡»ç¥</a>ã</p>
+</div>
+
+<p>Copyright © 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/";><CTT></a>ï¼2018ã</div>
+
+<p class="unprintable"><!-- timestamp start -->
+æåæ´æ°ï¼
+
+$Date: 2018/12/01 03:27:54 $
+
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>
Index: po/gcc-exception-3.1-faq.zh-cn-en.html
===================================================================
RCS file: po/gcc-exception-3.1-faq.zh-cn-en.html
diff -N po/gcc-exception-3.1-faq.zh-cn-en.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ po/gcc-exception-3.1-faq.zh-cn-en.html 1 Dec 2018 03:27:54 -0000
1.1
@@ -0,0 +1,321 @@
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.77 -->
+<title>GCC Runtime Library Exception Rationale and FAQ
+- GNU Project - Free Software Foundation</title>
+<!--#include virtual="/licenses/po/gcc-exception-3.1-faq.translist" -->
+<!--#include virtual="/server/banner.html" -->
+<h2>GCC Runtime Library Exception Rationale and FAQ</h2>
+
+<h3>Introduction</h3>
+
+<p>On June 29th, 2007 the Free Software Foundation released GPLv3. It
+was immediately adopted by fifteen GNU projects, and more made the
+switch in the following months. Most of the GCC codebase migrated to
+the new license in the 4.2.2 release, and now we are preparing to
+finish that process.</p>
+
+<p>The licenses for some libraries that accompany GCC have not been
+changed yet. These libraries are automatically used by the object
+code that GCC produces. Because of that, if these libraries were
+simply distributed only under the terms of the GPL, all the object
+code that GCC produces would have to be distributed under the same
+terms. However, the FSF decided long ago to allow developers to use
+GCC's libraries to compile any program, regardless of its license.
+Developing nonfree software is not good for society, and we have no
+obligation to make it easier. We decided to permit this because
+forbidding it seemed likely to backfire, and because using small
+libraries to limit the use of GCC seemed like the tail wagging the
+dog.</p>
+
+<p>Therefore, these libraries have always had license exceptions that
+allow people to distribute the object code GCC produces under any
+license. We are now moving these libraries to GPLv3 and updating
+their exceptions. Our fundamental policy has not changed; the new
+license is meant to permit all the uses of GCC that were permitted
+before. However, we have decided to use this opportunity to update
+the exception to accomplish three goals:</p>
+
+<ul>
+<li><p>Take advantage of GPLv3's new provisions. GPLv3 features a number
+of new terms which benefit all software. These include section 7,
+which establishes a framework for providing license exceptions. In
+order for GCC to get the most benefit from GPLv3, we need to update
+the exception to take these new terms into account, and work within
+the parameters of section 7.</p></li>
+<li><p>Lay the groundwork for a plugin infrastructure in GCC. For a while
+now, the GCC developers have considered adding a plugin framework to
+the compiler. This would make it easier for others to contribute to
+the project, and accelerate the development of new compilation
+techniques for GCC. However, there have also been concerns that
+unscrupulous developers could write plugins that called out to
+proprietary software to transform the compiled code—effectively
+creating proprietary extensions to GCC and defeating the purpose of
+the GPL. The updated exception prevents such abuse, enabling the
+GCC team to look forward to plugin developments.</p></li>
+<li><p>Make exceptions throughout the GCC code base consistent. Over the
+years, as new files were added to GCC that needed to carry this
+license exception, we reviewed and updated the language to help
+clarify it and address new concerns. As a result, there are now
+many different exception texts in GCC that provide the same basic
+permissions. Now all of those files will be able to use the single
+new exception text that we've prepared, making it easier to perform
+legal reviews on the code.</p></li>
+</ul>
+
+<p>As with GPLv3, we worked hard to listen to various users' concerns
+while we drafted this, and address them appropriately. All told, we
+have spent more than a year on this process. The Free Software
+Foundation and the GCC Steering Committee would like to thank Richard
+Fontana, Bradley Kuhn, and Karen Sandler at the Software Freedom Law
+Center for all their hard work and assistance with the exception. The
+changes here will strengthen the GCC community, and we look forward to
+the compiler developments it will enable.</p>
+
+<p>Because GCC is such a crucial part of developers' lives, we're
+expecting lots of questions about these changes, and we want to make
+sure that they're addressed. Below we've addressed specific concerns
+that we expect users will have. If you have questions about the new
+exception that aren't mentioned here, please feel free to contact us
+at <a href="mailto:address@hidden";><address@hidden></a>.</p>
+
+<h3>How the Exception Works</h3>
+
+<p>The permission you need—to convey the object code from these GCC
+libraries under your own project's license—is primarily contained in
+section 1:</p>
+
+<blockquote>
+ <p>You have permission to propagate a work of Target Code formed by
+ combining the Runtime Library with Independent Modules, even if such
+ propagation would otherwise violate the terms of GPLv3, provided
+ that all Target Code was generated by Eligible Compilation
+ Processes. You may then convey such a combination under terms of
+ your choice, consistent with the licensing of the Independent
+ Modules.</p>
+</blockquote>
+
+<p>This section uses many defined terms, and their specific meanings are
+integral to how the exception works. This section looks at how these
+terms relate to common scenarios.</p>
+
+<p>When you write your software, it consists of a set of source code
+files. Each file is an “Independent Module,” as long as
+it doesn't contain any source from the GCC libraries.</p>
+
+<p>When you compile those source code files, they usually go through a
+series of steps: source code generation, preprocessing, compilation to
+low-level code, assembling, and linking. Not all projects follow all
+these steps, depending on what language you're using and how it's
+written, but they'll always go in this order, and everyone using GCC
+will go through the process of compiling high-level code into some
+low-level language such as assembly code or Java bytecode. This phase
+is when GCC combines or links your own code with code from the GCC
+libraries. We call it the “Compilation Process.” The
+output you get from it is called “Target Code,” as long as
+that output is not used as compiler intermediate representation, or to
+create such an intermediate representation.</p>
+
+<p>In order to take advantage of this permission, the Compilation
+Process that you use to create Target Code has to be
+“Eligible,” which means that it does not involve both GCC
+and GPL-incompatible software. It's important to remember that the
+Compilation Process starts when you feed <em>any</em> high-level code
+to GCC, and ends as soon as it generates anything that can be
+considered Target Code. Because of that, as long as GCC isn't writing
+out intermediate representation, your Compilation Process can still be
+Eligible even if you use GCC in conjunction with GPL-incompatible
+assemblers, linkers, or high-level source generators: those programs
+aren't involved in the Compilation Process as it's defined here. The
+only place you can't use GPL-incompatible software with GCC is when
+it's performing the core compilation work.</p>
+
+<p>So, if you use GCC, with or without GPL-compatible enhancements, that
+would be an Eligible Compilation Process. If you only use
+GPL-incompatible compiler tools, that would be an Eligible Compilation
+Process as well. (It's not uncommon for people who build software for
+GNU/Linux to link against the GCC libraries even if they're using a
+different compiler.) However, if you used GCC in conjunction with
+GPL-incompatible software during the process of transforming
+high-level code to low-level code, that would <em>not</em> be an Eligible
+Compilation Process. This would happen if, for example, you used GCC
+with a proprietary plugin.</p>
+
+<p>As long as you use an Eligible Compilation Process, then you have
+permission to take the Target Code that GCC generates and propagate it
+“under terms of your choice.”</p>
+
+<p>If you did use GPL-incompatible software in conjunction with GCC
+during the Compilation Process, you would not be able to take
+advantage of this permission. Since all of the object code that GCC
+generates is derived from these GPLed libraries, that means you would
+be required to follow the terms of the GPL when propagating any of
+that object code. You could not use GCC to develop your own
+GPL-incompatible software.</p>
+
+<h3>Frequently Asked Questions</h3>
+
+<dl>
+<dt>I am using a standard release of GCC (such as one provided by the
+FSF, or with my operating system) to compile GPL-incompatible
+software. How does this change affect me?</dt>
+
+<dd><p>It should not affect you at all. Unless you've configured GCC
+to output intermediate representation—which is rare—the
+new exception is designed to ensure that you have no license
+obligations when you do this, just as the old exceptions
+were.</p></dd>
+
+<dt>Who does this change affect?</dt>
+
+<dd><p>Nobody who is currently using GCC should be affected by this change.
+The only changes in policy are meant to prevent developers from making
+certain modifications to GCC that <em>will</em> become feasible in the future.
+The FSF has been working closely with GCC developers to learn more about
+the many different ways people use GCC today, and ensure that they will all
+be able to continue those activities under the new exception.</p></dd>
+
+<dt>I use GCC in conjunction with proprietary preprocessors and/or source
+generators to compile my program. Can I still take advantage of the
+exception?</dt>
+
+<dd><p>Yes. The Compilation Process can start with any “code
+entirely represented in a high-level, non-intermediate
+language.” This includes code generated by a preprocessor or
+other proprietary software. As such, the Compilation Process in this
+case does not involve any proprietary software; it qualifies as
+Eligible, and the exception is available for this program.</p></dd>
+
+<dt>I use GCC in conjunction with proprietary assemblers and/or linkers to
+compile my program. Can I still take advantage of the exception?</dt>
+
+<dd><p>Yes. The Compilation Process ends when the compiler generates
+Target Code, which includes output that is “suitable for input
+to an assembler, loader, linker and/or execution phase.” In
+other words, the Compilation Process in this case is over when you
+have assembly code or unlinked object files from GCC, and so it does
+not involve any proprietary software. It qualifies as Eligible, and
+the exception is thus available for this program.</p></dd>
+
+<dt>I use GCC to compile parts of my program, and a proprietary
+compiler to compile other parts. The pieces are combined afterward,
+during assembler or linking phases. Can I still take advantage of the
+exception?</dt>
+
+<dd><p>Yes. In this case, each Independent Module is turned into Target Code
+through an Eligible Compilation Process. Even though different modules
+will go through different processes, the exception is still available
+for this program.</p></dd>
+
+<dt>I use a proprietary compiler toolchain without any parts of GCC to
+compile my program, and link it with libstdc++. My program itself
+does not include any runtime library code the same way that
+GCC-compiled programs include libgcc. Can I still take advantage of
+the exception?</dt>
+
+<dd><p>Yes. While combining libgcc with GCC-compiled object code is
+probably the most common way the exception is used, neither the GPL
+nor the GCC Runtime Library Exception distinguish between static
+linking, dynamic linking, and other methods for combining code in
+their conditions. The same permissions are available to you, under
+the same terms, no matter which method you use.</p>
+
+<p>Note that if you distribute libstdc++ as an independent library,
+you will need to follow the terms of the GPL when doing so. For
+example, if you distribute the library itself in object code form, you
+will need to provide source code to your recipients using one of the
+methods listed in section 6 of GPLv3. But as long as you are eligible
+to take advantage of the GCC Runtime Library Exception's permissions
+for your own program, the GPL's terms do not extend to it.</p></dd>
+
+<dt>Why is compiler intermediate representation excluded from the
+definition of “Target Code?”</dt>
+
+<dd><p>When we first considered adding a plugin infrastructure to GCC, we
+were deeply concerned about the possibility that someone would write a
+plugin that would merely save GCC's internal, low-level compilation
+data structures to disk. With that done, other software would be able
+to optimize or otherwise improve that code without being directly
+connected to GCC. It may have been difficult for us to argue that
+those programs should be subject to the GPL's copyleft, so we wanted
+to discourage these sorts of arrangements.</p>
+
+<p>We do that by excluding such output from the definition of Target
+Code. Because of this, even if someone writes a plugin that saves
+this information to disk, any programs that change the structures
+before GCC writes out Target Code will be involved in the Compilation
+Process. If that program is proprietary, the exception will not be
+available to any software compiled with it; the object code that GCC
+ultimately creates will have to be distributed under the terms of the
+GPL.</p></dd>
+
+<dt>If I write some code in assembly language, can I combine that with
+other object code compiled normally, and still take advantage of the
+exception?</dt>
+
+<dd><p>Yes, as long as all of the object code was compiled through an
+Eligible Compilation Process. The process of running hand-written
+assembly through an assembler is a Compilation Process, since it
+“transforms code entirely represented in [a] non-intermediate
+language[] designed for human-written code... into Target
+Code.”</p></dd>
+
+<dt>What libraries does the GCC Runtime Library Exception cover?</dt>
+
+<dd><p>The GCC Runtime Library Exception covers any file that has a
+notice in its license headers stating that the exception applies.
+This includes libgcc, libstdc++, libfortran, libgomp, libdecnumber,
+libgcov, and other libraries distributed with GCC.</p></dd>
+
+<dt>Will Classpath use this new exception?</dt>
+
+<dd><p>Even though Classpath's current exception serves a similar purpose,
+we are not updating it at this time. Because of recent developments
+in the free software Java community, the priorities for Classpath's
+licensing policies are different from other GCC libraries, and we are
+evaluating it separately.</p></dd></dl>
+</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 & GNU inquiries to <a
+href="mailto:address@hidden";><address@hidden></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";><address@hidden></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";>
+ <address@hidden></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>
+
+<p>Copyright © 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: 2018/12/01 03:27:54 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- www/licenses po/gcc-exception-3.1-faq.translist...,
GNUN <=