You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openoffice.apache.org by bu...@apache.org on 2012/05/09 12:08:43 UTC

svn commit: r816869 [17/20] - in /websites/staging/ooo-site/trunk: cgi-bin/ content/ content/zh/ content/zh/css/ content/zh/doc/ content/zh/faq/ content/zh/images/ content/zh/new/ content/zh/products/ content/zh/zh.openoffice.org-20120508/ content/zh/z...

Added: websites/staging/ooo-site/trunk/content/zh/zh.openoffice.org-20120508/new/zh_tw/faq/apifaq.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/zh/zh.openoffice.org-20120508/new/zh_tw/faq/apifaq.html (added)
+++ websites/staging/ooo-site/trunk/content/zh/zh.openoffice.org-20120508/new/zh_tw/faq/apifaq.html Wed May  9 10:08:34 2012
@@ -0,0 +1,209 @@
+<!--#include virtual="/doctype.html" -->
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+
+<title>OpenOffice.org 中文網站</title>
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+<link rel="stylesheet" type="text/css" href="../../css/menuStyle.css" />
+<link rel="stylesheet" type="text/css" href="../../css/gen.css" />
+
+</head>
+<body>
+<!--#include virtual="/brand.html" -->
+  <div id="topbara">
+    <!--#include virtual="/topnav.html" -->
+    <div id="breadcrumbsa"><a href="/">home</a>&nbsp;&raquo;&nbsp;<a href="/zh/">zh</a>&nbsp;&raquo;&nbsp;<a href="/zh/zh.openoffice.org-20120508/">zh.openoffice.org-20120508</a>&nbsp;&raquo;&nbsp;<a href="/zh/zh.openoffice.org-20120508/new/">new</a>&nbsp;&raquo;&nbsp;<a href="/zh/zh.openoffice.org-20120508/new/zh_tw/">zh_tw</a>&nbsp;&raquo;&nbsp;<a href="/zh/zh.openoffice.org-20120508/new/zh_tw/faq/">faq</a></div>
+  </div>
+  <div id="clear"></div>
+  
+  
+  <div id="content">
+    
+    
+    
+<table id="zh_top" class="zhCore">
+  <tr>
+    <td class="zhContent"><h1 id="faq_gen">關於 OpenOffice.org API 的常見問題</h1>
+      <p>原文:<a href="http://api.openoffice.org/faq.html">http://api.openoffice.org/faq.html</a></p>
+      <p>翻譯:<a href="mailto:ZhangXiaofei@redoffice.com">Zhang Xiaofei </a>&nbsp; 校對:  Cheng Lin &nbsp;&nbsp;&nbsp; Sept, 2007</p>
+      <table class="zh_num">
+        <tr>
+          <td class="num">一、</td>
+          <td><a href="#gen_1">我可以在哪些語言中使用 OpenOffice.org-API ?</a></td>
+        </tr>
+        <tr>
+          <td class="num">二、</td>
+          <td><a href="#gen_2">UNO IDL 與 CORBA 間有哪些區別?</a></td>
+        </tr>
+        <tr>
+          <td class="num">三、</td>
+          <td><a href="#gen_3">API 設計部分有多大?</a></td>
+        </tr>
+        <tr>
+          <td class="num">四、</td>
+          <td><a href="#gen_4">API 的文檔是怎麼寫的?</a></td>
+        </tr>
+        <tr>
+          <td class="num">五、</td>
+          <td><a href="#gen_5">API 實現部分有多大?</a></td>
+        </tr>
+        <tr>
+          <td class="num">六、</td>
+          <td><a href="#gen_6">有沒有文檔或者示例可供 Java 程序員參考?</a></td>
+        </tr>
+        <tr>
+          <td class="num">七、</td>
+          <td><a href="#gen_7">為什麼 OpenOffice.org-API 中有些接口在任何 OpenOffice.org 組件中都沒有實現?</a></td>
+        </tr>
+        <tr>
+          <td class="num">八、</td>
+          <td><a href="#gen_8">我如何知道我是否可以使用 OpenOffice.org-API 中的某個特定接口?</a></td>
+        </tr>
+        <tr>
+          <td class="num">九、</td>
+          <td><a href="#gen_9">有沒有像微軟的 OLE 那樣可以構建復合文檔的接口?</a></td>
+        </tr>
+        <tr>
+          <td class="num">十、</td>
+          <td><a href="#gen_10">如何解決設計上的衝突?</a></td>
+        </tr>
+      </table>
+      <hr />
+      <h2>解答</h2>
+      <table class="zh_num">
+        <tr id="gen_1">
+          <td class="num">一、</td>
+          <td><dl>
+              <dt>我可以在哪些語言中使用 OpenOffice.org-API?</dt>
+              <dd> OpenOffice.org用UNO(Universal Network Object,通用網絡對像)實現API。目前對於Java和C++實現了綁定。你可以實現你自己的語言綁定,而且實際上我們正在積極尋找實現C語言綁定的志願者。<br />
+                <br />
+                而且,UNO中允許對腳本語言和腳本環境(比如調試器)進行控制。目前StarBasic(與VBA語法兼容)可以調用API,一個用做Python實現的原型也開發了出來。 </dd>
+            </dl>
+            <p class="zh_toTop"><a href="#faq_gen">回目錄</a></p></td>
+        </tr>
+        <tr id="gen_2">
+          <td class="num">二、</td>
+          <td><dl>
+              <dt>UNO IDL 與 CORBA 間有哪些區別?</dt>
+              <dd> UNO IDL 基於 CORBA IDL,不過它還額外支持:<br />
+                &nbsp; * 結構與異常的繼承關係,<br />
+                &nbsp; * 為枚舉變量賦值,<br />
+                &nbsp; * 新的服務(service)數據類型(是接口與屬性的組合)。<br />
+                <br />
+                而且目前它不支持:<br />
+                &nbsp; * 有確定類型的數組<br />
+                &nbsp; * 共用體 </dd>
+            </dl>
+            <p class="zh_toTop"><a href="#faq_gen">回目錄</a></p></td>
+        </tr>
+        <tr id="gen_3">
+          <td class="num">三、</td>
+          <td><dl>
+              <dt>API 設計部分有多大?</dt>
+              <dd> API包含大概2000個文件,每個文件設計一種類型。一個類型可以是一個服務、接口、結構、異常、一個常量組(constant group)或一個枚舉變量。這些文件總共有大概6MB數據。 </dd>
+            </dl>
+            <p class="zh_toTop"><a href="#faq_gen">回目錄</a></p></td>
+        </tr>
+        <tr id="gen_4">
+          <td class="num">四、</td>
+          <td><dl>
+              <dt>API 的文檔是怎麼寫的?</dt>
+              <dd> IDL文件內部包含一個可供參考的文檔。該文檔的文法在JavaDoc的基礎上為標識符的標記做了一些拓展。目前,我們正為這個文法開發一個新的生成器,將可以從IDL直接生成HTML文檔。<br />
+                <br />
+                我們的<a href="http://api.openoffice.org/DevelopersGuide/DevelopersGuide.html">開發者指南</a>中對於OpenOffice.org中全部具有API的組件的概念都進行了描述,是開始學習API最好的資料。
+                
+                
+                對於StarBasic程序員我們還特別有一份<a href="http://api.openoffice.org/basic/man/tutorial/tutorial.pdf">教程</a>。它解釋了基本概念,列出了組件結構的一些UML圖表,並包括大量帶註釋的關於API使用的示例。 </dd>
+            </dl>
+            <p class="zh_toTop"><a href="#faq_gen">回目錄</a></p></td>
+        </tr>
+        <tr id="gen_5">
+          <td class="num">五、</td>
+          <td><dl>
+              <dt>API 實現部分有多大?</dt>
+              <dd> 這個很難講清。目前的API實現只對大多數部分都會用到的核心API做了封裝。只有新的組件直接實現了API。因此,要搞清實現API總共有多少代碼並沒有太大意義——甚至在未來可能性都不大。基於這個角度,我們大概可以說,整個OpenOffice.org就是API的實現,尤其是因為有越來越多的特性正在使用其它組件的API整合進去。 </dd>
+            </dl>
+            <p class="zh_toTop"><a href="#faq_gen">回目錄</a></p></td>
+        </tr>
+        <tr id="gen_6">
+          <td class="num">六、</td>
+          <td><dl>
+              <dt>有沒有文檔或者示例可供 Java 程序員參考?</dt>
+              <dd> 您可以在<a href="http://udk.openoffice.org/">UDK項目</a>中找到Java的語言綁定。在<a href="http://soldc.sun.com/staroffice">OpenOffice/StarOffice SDK</a>裡有一些Java示例,也許對您有幫助。 </dd>
+            </dl>
+            <p class="zh_toTop"><a href="#faq_gen">回目錄</a></p></td>
+        </tr>
+        <tr id="gen_7">
+          <td class="num">七、</td>
+          <td><dl>
+              <dt>為什麼 OpenOffice.org-API 中有些接口在任何 OpenOffice.org 組件中都沒有實現?</dt>
+              <dd> OpenOffice.org-API其實更像一個需求文檔,而不是一個已經實現完畢的API。因此,有些接口沒有任何實現,存在以下幾種原因:<br />
+                <br />
+                &nbsp; a. 有可能在所有用到該接口的服務中它都是一個可選的(optional)接口,但目前所有的實現部分都還沒有實現它。<br />
+                &nbsp; b. 它可能是一個為了保持概念正交性(concept orthogonal)提出的接口,但它所代表的維度目前沒有用到。<br />
+                &nbsp; c. 它可能是近期設計的一部分,實現還沒有完成。<br />
+                &nbsp; d. 在任意實現中缺少它有可能會引發bug。 </dd>
+            </dl>
+            <p class="zh_toTop"><a href="#faq_gen">回目錄</a></p></td>
+        </tr>
+        <tr id="gen_8">
+          <td class="num">八、</td>
+          <td><dl>
+              <dt>我如何知道我是否可以使用 OpenOffice.org-API 中的某個特定接口?</dt>
+              <dd> 找一個輸出這個接口的服務,然後找一個確定會支持這個服務的組件。別忘了有些接口是可選的(在這個服務的輸出文檔中會提到)。如果你使用的組件還沒有實現這個接口,那就是一個bug。遇到這種情況,請把這個bug提交給組件的所有者。如果是設計文檔的bug,他們會把bug轉交給設計文檔的所有者。 </dd>
+            </dl>
+            <p class="zh_toTop"><a href="#faq_gen">回目錄</a></p></td>
+        </tr>
+        <tr id="gen_9">
+          <td class="num">九、</td>
+          <td><dl>
+              <dt>有沒有像微軟的 OLE 那樣可以構建復合文檔的接口?</dt>
+              <dd> 目前在OpenOffice/StarOffice API中沒有構建復合文檔的接口(譯者註:可能在您閱讀本FAQ時已經實現)。我們的構想是使用Bonobo模型達到這個目標。 </dd>
+            </dl>
+            <p class="zh_toTop"><a href="#faq_gen">回目錄</a></p></td>
+        </tr>
+        <tr id="gen_10">
+          <td class="num">十、</td>
+          <td><dl>
+              <dt>如何解決設計上的衝突?</dt>
+              <dd> 首先,API被定位成一個注重正交結構與可復用性的設計文檔。另外我們盡可能使之與Java相似。使實現部分與使用部分這兩方面都具有易用性也是一個重點。這使我們常常不得不做出妥協——有時甚至只是因為已經存在了一個實現。<br />
+                <br />
+                如果出現衝突,我們會尋求達成一致的方法,聽取所有的爭論,在匆忙做決定之前再花些時間找出新的分歧。這樣努力找出讓所有人都滿意的解決方案。 </dd>
+            </dl>
+            <p class="zh_toTop"><a href="#faq_gen">回目錄</a></p></td>
+        </tr>
+        <tr id="gen_11">
+          <td class="num">十一、</td>
+          <td><dl>
+              <dt>支持系統在何處?</dt>
+              <dd> 最新版本的 OpenOffice.org 上附有支持系統。如果無法使用支持系統,請到<a href="../downloads.html">下載區</a>下載並升級至最新版本。 </dd>
+            </dl>
+            <p class="zh_toTop"><a href="#faq_gen">回目錄</a></p></td>
+        </tr>
+      </table>
+      <p>&nbsp;</p>
+      </td>
+    
+    <td class="zhMenu"><!-- zh Menu Start -->
+      <a href="http://zh.OpenOffice.org"><img src="../../zh_ooo_logo_nav.png" alt="zh.OpenOffice.org" border="0" /></a>
+      <table class="zh_menu">
+        <tr>
+          <th>幫助</th>
+        </tr>
+        <tr>
+          <td><a href="../help-faq.html">常見問題</a> <br />
+            ∟各種常見問題</td>
+        </tr>
+      </table>
+    <!-- zh Menu End -->    </td>
+  </tr>
+</table>
+
+  </div>
+
+<!--#include virtual="/footer.html" -->
+
+</body>
+</html>

Added: websites/staging/ooo-site/trunk/content/zh/zh.openoffice.org-20120508/new/zh_tw/faq/buildfaq.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/zh/zh.openoffice.org-20120508/new/zh_tw/faq/buildfaq.html (added)
+++ websites/staging/ooo-site/trunk/content/zh/zh.openoffice.org-20120508/new/zh_tw/faq/buildfaq.html Wed May  9 10:08:34 2012
@@ -0,0 +1,302 @@
+<!--#include virtual="/doctype.html" -->
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+
+<title>OpenOffice.org 中文網站</title>
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+<link rel="stylesheet" type="text/css" href="../../css/menuStyle.css" />
+<link rel="stylesheet" type="text/css" href="../../css/gen.css" />
+
+</head>
+<body>
+<!--#include virtual="/brand.html" -->
+  <div id="topbara">
+    <!--#include virtual="/topnav.html" -->
+    <div id="breadcrumbsa"><a href="/">home</a>&nbsp;&raquo;&nbsp;<a href="/zh/">zh</a>&nbsp;&raquo;&nbsp;<a href="/zh/zh.openoffice.org-20120508/">zh.openoffice.org-20120508</a>&nbsp;&raquo;&nbsp;<a href="/zh/zh.openoffice.org-20120508/new/">new</a>&nbsp;&raquo;&nbsp;<a href="/zh/zh.openoffice.org-20120508/new/zh_tw/">zh_tw</a>&nbsp;&raquo;&nbsp;<a href="/zh/zh.openoffice.org-20120508/new/zh_tw/faq/">faq</a></div>
+  </div>
+  <div id="clear"></div>
+  
+  
+  <div id="content">
+    
+    
+    
+<table id="zh_top" class="zhCore">
+  <tr>
+    <td class="zhContent"><h1 id="faq_gen">OpenOffice.org 開發構建常見問題</h1>
+      <p>原文:<a href="http://www.openoffice.org/FAQs/build_faq.html">http://www.openoffice.org/FAQs/build_faq.html</a></p>
+      <p class="STYLE1">翻譯:<a href="mailto:jacky.l.woo@gmail.com">Jacky Woo</a> 校對:Chen Lishuang, Sun Jing, Cheng Lin  &nbsp; &nbsp; Aug, 2007</p>
+      <table class="zh_num">
+        <tr>
+          <td class="num">一、</td>
+          <td><a href="#gen_1">什麼樣的源代碼可以在www.openoffice.org獲得?</a></td>
+        </tr>
+        <tr>
+          <td class="num">二、</td>
+          <td><a href="#gen_2">OpenOffice是基於什麼操作平台而設計的? </a></td>
+        </tr>
+        <tr>
+          <td class="num">三、</td>
+          <td><a href="#gen_3">OpenOffice.org是如何構建的?</a></td>
+        </tr>
+        <tr>
+          <td class="num">四、</td>
+          <td><a href="#gen_4">完全構建openoffice (包括源代碼)需要多少硬盤空間?</a></td>
+        </tr>
+        <tr>
+          <td class="num">五、</td>
+          <td><a href="#gen_5">構建OpenOffice.org需要多長時間?</a></td>
+        </tr>
+        <tr>
+          <td class="num">六、</td>
+          <td><a href="#gen_6">在 StarOffice 下,軟件開發員是怎樣工作的?</a></td>
+        </tr>
+        <tr>
+          <td class="num">七、</td>
+          <td><a href="#gen_7">你們有多少工作項目? </a></td>
+        </tr>
+        <tr>
+          <td class="num">八、</td>
+          <td><a href="#gen_8">大約有多少源代碼?</a></td>
+        </tr>
+        <tr>
+          <td class="num">九、</td>
+          <td><a href="#gen_9">發佈中所未包含的(以及為何)?</a></td>
+        </tr>
+        <tr>
+          <td class="num">十、</td>
+          <td><a href="#gen_10">有人能解釋分支工作空間Child Workspaces是什麼嗎?</a></td>
+        </tr>
+        <tr>
+          <td class="num">十一、</td>
+          <td><a href="#gen_11">我可以從哪裡獲得幫助?</a></td>
+        </tr>
+        <tr>
+          <td class="num">十二、</td>
+          <td><a href="#gen_12">還有什麼其它的我們需要瞭解?</a></td>
+        </tr>
+        <tr>
+          <td class="num">十三、</td>
+          <td><a href="#gen_13">有沒有什麼已知的軟件錯誤?</a></td>
+        </tr>
+      </table>
+      <hr />
+      <h2>解答</h2>
+      <table class="zh_num">
+        <tr id="gen_1">
+          <td class="num">一、</td>
+          <td><dl>
+              <dt>什麼樣的源代碼可以在 www.openoffice.org 獲得?</dt>
+              <dd> OpenOffice.org 的源代碼和用於開發StarOffice的源代碼幾乎完全一樣。那些在 OpenOffice.org 中未能公開的源代碼或者程序插件,全部是 Sun Mircosystems 從第三方取得,並且無權進行公開發佈的。Openoffice.org 中的任何無權發佈的代碼,已經被確認並刪除。另外,為了保證 OpenOffice.org 的順利構建,外部引進代碼的構建方法將可獲得,否則其代碼將被清除。OpenOffice.org 可從這個領域工作中受益。<br />
+                <br />
+                StarOffice/OpenOffice 的開發人員將繼續提交代碼修改到CVS上,該CVS與www.OpenOffice.org  所能訪問的相同。 </dd>
+            </dl>
+            <p class="zh_toTop"><a href="#faq_gen">回目錄</a></p></td>
+        </tr>
+        <tr id="gen_2">
+          <td class="num">二、</td>
+          <td><dl>
+              <dt>OpenOffice 是基於什麼操作平台而設計的?</dt>
+              <dd> OpenOffice.org 已經可以在 Linux(RedHat 8), Solaris(Sparec 2.6-2.9) 和 Windows NT 上成功構建。<br />
+                <br />
+                為Mac OS X系統的移植工作正在進行,當前進行的工作可以在CVS目錄下獲得。<br />
+                <br />
+                對於以前支持的OS/2, HP/UX 和其他的操作平台,源代碼可以獲得,但是還未被構建(譯者註:該FAQ寫於03年,現在這些工作應都已完成) </dd>
+            </dl>
+            <p><a href="#faq_gen">回目錄</a></p></td>
+        </tr>
+        <tr id="gen_3">
+          <td class="num">三、</td>
+          <td><dl>
+              <dt>OpenOffice.org是如何構建的?</dt>
+              <dd> Sun Microsystems已經對構建環境進行了調整,目的是在其他開發團隊所自行定制和優化的環境中得以構建OpenOffice.org。Openoffice.org盡可能使用開源構建工具,仍有可能使用更多。源代碼對所有構建工具均可獲得。<br />
+                <br />
+                雖然已經做了很多工作使OpenOffice.org的構建經驗盡可能地接近開源標準,但是鑒於應用程序的複雜性和規模,這些構建經驗還是與開源標準有所不同。更多詳細資料請參閱:<br />
+                <br />
+                http://tools.openoffice.org#Build<br />
+                <br />
+              </dd>
+            </dl>
+            <p class="zh_toTop"><a href="#faq_gen">回目錄</a></p></td>
+        </tr>
+        <tr id="gen_4">
+          <td class="num">四、</td>
+          <td><dl>
+              <dt>完全構建openoffice (包括源代碼)需要多少硬盤空間?</dt>
+              <dd> 目前的推薦大小是3GB。<br />
+                源代碼的大小是400MB左右<br />
+                構建需要大約3GB(包括源代碼)<br />
+                安裝需要300MB左右<br />
+                為構建增加debug符號信息還需要佔用大約5G。<br />
+                <br />
+                軟件開發人員通常因為這個原因,僅在特定的目錄中使用「build debug=true」來進行完全debug構建。<br />
+                <br />
+              </dd>
+            </dl>
+            <p class="zh_toTop"><a href="#faq_gen">回目錄</a></p></td>
+        </tr>
+        <tr id="gen_5">
+          <td class="num">五、</td>
+          <td><dl>
+              <dt>構建OpenOffice.org需要多長時間?</dt>
+              <dd> 依據我們目前的經驗,如果完全構建OpenOffice.org大約需要20個小時(一個奔騰III CPU,內存256MB,操作系統Linux)<br />
+                <br />
+                使用CC="ccache gcc" CXX="ccache g++" 在一台奔騰1.8Ghz的電腦上完成一次構建大約需要4個小時。<br />
+                <br />
+              </dd>
+            </dl>
+            <p class="zh_toTop"><a href="#faq_gen">回目錄</a></p></td>
+        </tr>
+        <tr id="gen_6">
+          <td class="num">六、</td>
+          <td><dl>
+              <dt>在 StarOffice 下,軟件開發員是怎樣工作的?</dt>
+              <dd> 每週Sun的發佈工程師都會在一個優化的環境下,進行一次Staroffice的完全構建。在成功進行完全構建後,最新的solver目錄(譯者註:solver是編譯構建OpenOffice源代碼中產生的一個目錄名,不需翻譯,開發者都明白)會對所有開發人員公開。開發人員會在當前的solver構建自己的CVS模塊。在代碼修改後,開發人員構建CVS模塊並且「提交」("deliver")一份共享頭文件、共享庫與二進制文件的拷貝到當
 前solver目錄中,以供測試。<br />
+                <br />
+                在不同版本的完全創建中,不可兼容的代碼改變是允許的。為了不兼容的工作不混在一起,每個共享庫/DLL的名字包括構建號,該構建號每週增加一。<br />
+                <br />
+                為了支持OpenOffice.org的社區,Sun計劃提供一個相似的環境。原因是代碼庫過於龐大,而現在的開發人員就在使用它。Sun打算在www.openoffice.org上,為每一個操作平台提供一個solver的tarball。這些被人們稱為「里程碑」(milestone)。<br />
+                <br />
+                因此,建議的開發過程為: <br />
+                1. 開發人員下載對應操作平台的里程碑 solver tarball <br />
+                2. 通過CVS檢出針對同樣里程碑(milestone)的相關項目。 <br />
+                3. 修改代碼 <br />
+                4. 構建(這將基於 solver 內容構建,如果成功,則提交結果到solver) <br />
+                5. 測試新版本 <br />
+                6. 提交補丁 patch <br />
+                <br />
+                OpenOffice.org 擁有一個巨大的代碼庫。開發團隊之間將 CVS 作為一個同步系統機制使用。在底層 CVS 模塊中的 API 修改會被檢入,以便更高層的模塊反應這些變化。在不兼容的里程碑(milestone)中構建,通常會出現這樣的情況:API 已經在底層修改,可是並不是所有的使用這些 API 的模塊都已經被相應修改。因此,使用 head revision 的構建不一定總是成功的。<br />
+                <br />
+                一個新的方法正在被引進中。在短期內,head可以成為一個可構建的主幹工作空間(master workspace)。<br />
+                <br />
+              </dd>
+            </dl>
+            <p class="zh_toTop"><a href="#faq_gen">回目錄</a></p></td>
+        </tr>
+        <tr id="gen_7">
+          <td class="num">七、</td>
+          <td><dl>
+              <dt>你們有多少工作項目?</dt>
+              <dd> 將會為OpenOffice.org創建大約20個項目。這些項目是促進社區溝通與交流的一種嘗試,比如說包括XML Office,Porting,Localization,Applications 和 Build Tools在內的項目。 </dd>
+            </dl>
+            <p class="zh_toTop"><a href="#faq_gen">回目錄</a></p></td>
+        </tr>
+        <tr id="gen_8">
+          <td class="num">八、</td>
+          <td><dl>
+              <dt>大約有多少源代碼?</dt>
+              <dd> OpenOffice.org大約有30,000個代碼文件。<br />
+                <br />
+                OpenOffice.org有大約9,000,000行代碼。絕大多數代碼是C++。 </dd>
+            </dl>
+            <p class="zh_toTop"><a href="#faq_gen">回目錄</a></p></td>
+        </tr>
+        <tr id="gen_9">
+          <td class="num">九、</td>
+          <td><dl>
+              <dt>發佈中所未包含的(以及為何)?</dt>
+              <dd> 一些StarOffice從第三方獲得授權的外部組件的源代碼不能從OpenOffice.org 源代碼中獲取 。這些組件包括:<br />
+                <br />
+                * L&H International CorrectSpell, Intl. Electronic Thesaurus – 拼寫檢查,國際字典&辭典<br />
+                * Inso Word for Word - 除MS Office 外的用於文件格式的文檔過濾<br />
+                * Adabas D – 數據庫引擎<br />
+                <br />
+                下載無法在 www.OpenOffice.org 上發佈的外部源代碼時會有一些指示。<br />
+                <br />
+                GPC代碼是一個特例,必須單獨地由 OOo 開發人員獲得。請參閱構建指南。 </dd>
+            </dl>
+            <p class="zh_toTop"><a href="#faq_gen">回目錄</a></p></td>
+        </tr>
+        <tr id="gen_10">
+          <td class="num">十、</td>
+          <td><dl>
+              <dt>有人能解釋分支工作空間Child Workspaces是什麼嗎?</dt>
+              <dd>Child workspaces,即分支工作空間,它的主要內容是:<br />
+                <br />
+                * 只有完全經過測試的代碼才會進入主要CVS的分支<br />
+                * 所有的里程碑的快照(snapshot)都接近最終產品質量<br />
+                * 更快的為開發主幹作出貢獻(因為校對和測試可以在cvs目錄上直接進行)<br />
+                <br />
+                更多信息在http://tools.openoffice.org上可以查詢到。 </dd>
+            </dl>
+            <p class="zh_toTop"><a href="#faq_gen">回目錄</a></p></td>
+        </tr>
+        <tr id="gen_11">
+          <td class="num">十一、</td>
+          <td><dl>
+              <dt>我可以從哪裡獲得幫助?</dt>
+              <dd> 首先,您可以瀏覽dev@openoffice.org的郵件列表文檔來查詢、解決類似的問題。<br />
+                <br />
+                其次,您還可以在dev@openoffice.org上發佈一封郵件來說明您的問題。如果您有一個更加專業的問題,那麼你將會被引導到另外一個針對你的問題的郵件列表(mail list),比如dev@sw.openoffice.org可以用來查詢您的文字處理問題。<br />
+                <br />
+                對於一個簡單的問題或者閒聊,您可以通過IRC和別的開發人員聊天。IRC不僅僅是提供給開發人員,然而很多專業問題都能在IRC的討論中給予好的建議。<br />
+                <br />
+                服務器:irc.freenode.net<br />
+                頻道: #openoffice.org<br />
+                <br />
+                簡單介紹如何使用IRC:<br />
+                <br />
+                首先,為您自己找一個IRC 客戶端軟件:<br />
+                windows用戶,您可以使用mIRC - http://www.mirc.com<br />
+                Unix、linux用戶,有很多軟件可以使用,然而我們推薦kvirc - http://www.kvirc.net<br />
+                <br />
+                如果您的客戶端已經設定完成了,您可以在命令欄中輸入:/SERVER irc.openprojects.net<br />
+                <br />
+                在您登錄之後可以輸入: /JOIN #OpenOffice.org </dd>
+            </dl>
+            <p class="zh_toTop"><a href="#faq_gen">回目錄</a></p></td>
+        </tr>
+        <tr id="gen_12">
+          <td class="num">十二、</td>
+          <td><dl>
+              <dt>還有什麼其它的我們需要瞭解?</dt>
+              <dd> 大多數評論都是德文的,一部分是英文的。未來,所有的新的評論都是英文的。<br />
+                <br />
+                要下載和構建 OpenOffice.org 還需要大量的先決條件,請查閱http://tools.openoffice.org#Build來查看完整清單。<br />
+                <br />
+              </dd>
+            </dl>
+            <p class="zh_toTop"><a href="#faq_gen">回目錄</a></p></td>
+        </tr>
+        <tr id="gen_13">
+          <td class="num">十三、</td>
+          <td><dl>
+              <dt>有沒有什麼已知的軟件錯誤?</dt>
+              <dd> 我們有一些構建問題:<br />
+                <br />
+                * Bison 1.875 - 該版本在發佈時有問題,請嘗試升級版本為bison 1.875a 。<br />
+                * Xwindows 4.3 – 我知道有人遇到過這個問題,但不清楚是怎麼解決的。讓我們瞭解一下!<br />
+                * 未定義的符號:_Z16XineramaIsActiveP9_XDisplay<br />
+                <br />
+                這是一個頭文件問題,在'#include
+                <X11/extensions/Xinerama.h>
+                '旁邊添加'extern "C" { }' , 然後通過libvcl644li.so構建。 </dd>
+            </dl>
+            <p class="zh_toTop"><a href="#faq_gen">回目錄</a></p></td>
+        </tr>
+      </table></td>
+    
+    <td class="zhMenu"><!-- zh Menu Start -->
+      <a href="http://zh.OpenOffice.org"><img src="../../zh_ooo_logo_nav.png" alt="zh.OpenOffice.org" border="0" /></a>
+      <table class="zh_menu">
+        <tr>
+          <th>幫助</th>
+        </tr>
+        <tr>
+          <td><a href="../help-faq.html">常見問題</a> <br />
+            ∟各種常見問題</td>
+        </tr>
+      </table>
+      <!-- zh Menu End -->
+    </td>
+  </tr>
+</table>
+
+  </div>
+
+<!--#include virtual="/footer.html" -->
+
+</body>
+</html>

Added: websites/staging/ooo-site/trunk/content/zh/zh.openoffice.org-20120508/new/zh_tw/faq/licensingFAQ.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/zh/zh.openoffice.org-20120508/new/zh_tw/faq/licensingFAQ.html (added)
+++ websites/staging/ooo-site/trunk/content/zh/zh.openoffice.org-20120508/new/zh_tw/faq/licensingFAQ.html Wed May  9 10:08:34 2012
@@ -0,0 +1,573 @@
+<!--#include virtual="/doctype.html" -->
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+
+<title>OpenOffice.org 中文網站</title>
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+<link rel="stylesheet" type="text/css" href="../../css/menuStyle.css" />
+<link rel="stylesheet" type="text/css" href="../../css/gen.css" />
+
+</head>
+<body>
+<!--#include virtual="/brand.html" -->
+  <div id="topbara">
+    <!--#include virtual="/topnav.html" -->
+    <div id="breadcrumbsa"><a href="/">home</a>&nbsp;&raquo;&nbsp;<a href="/zh/">zh</a>&nbsp;&raquo;&nbsp;<a href="/zh/zh.openoffice.org-20120508/">zh.openoffice.org-20120508</a>&nbsp;&raquo;&nbsp;<a href="/zh/zh.openoffice.org-20120508/new/">new</a>&nbsp;&raquo;&nbsp;<a href="/zh/zh.openoffice.org-20120508/new/zh_tw/">zh_tw</a>&nbsp;&raquo;&nbsp;<a href="/zh/zh.openoffice.org-20120508/new/zh_tw/faq/">faq</a></div>
+  </div>
+  <div id="clear"></div>
+  
+  
+  <div id="content">
+    
+    
+    
+<table id="zh_top" class="zhCore">
+  <tr>
+    <td class="zhContent"><h1>軟件授權常見問題</h1>
+      <h2 id="faq_gen">一般問題</h2>
+      <table class="zh_num">
+        <tr>
+          <td class="num">一、</td>
+          <td><a href="#gen_1">OpenOffice.org 計劃用哪些授權聲明?</a></td>
+        </tr>
+        <tr>
+          <td class="num">二、</td>
+          <td><a href="#gen_2">我該採用哪種授權聲明呢?</a></td>
+        </tr>
+        <tr>
+          <td class="num">三、</td>
+          <td><a href="#gen_3">我可以在哪裡找到更多關於授權聲明的資料呢?</a></td>
+        </tr>
+        <tr>
+          <td class="num">四、</td>
+          <td><a href="#gen_4">OpenOffice.org 的原始程序碼為何用雙重授權法?</a></td>
+        </tr>
+        <tr>
+          <td class="num">五、</td>
+          <td><a href="#gen_5">若我貢獻原始程序碼給 OpenOffice.org 的話,我在授權聲明方面需要做什麼呢?</a></td>
+        </tr>
+        <tr>
+          <td class="num">六、</td>
+          <td><a href="#gen_6">為何 OpenOffice.org 用 GNU 次通用公共授權 (LGPL)?</a></td>
+        </tr>
+        <tr>
+          <td class="num">七、</td>
+          <td><a href="#gen_7">升陽的 Sun Industry Standards Source License (SISSL) 是什麼?</a></td>
+        </tr>
+        <tr>
+          <td class="num">八、</td>
+          <td><a href="#gen_8">我可否用 OpenOffice.org 的部分原始程序碼來改進其他程序?</a></td>
+        </tr>
+        <tr>
+          <td class="num">九、</td>
+          <td><a href="#gen_9">這授權結構是如何定下的?</a></td>
+        </tr>
+        <tr>
+          <td class="num">十、</td>
+          <td><a href="#gen_10">以 OpenOffice.org 的程序作商業用途是否合法?</a></td>
+        </tr>
+        <tr>
+          <td class="num">十一、</td>
+          <td><a href="#gen_11">OpenOffice.org 會否授權讓我修改及分發 StarOffice?</a></td>
+        </tr>
+        <tr>
+          <td class="num">十二、</td>
+          <td><a href="#gen_12">升陽能否將 OpenOffice.org 奪去?</a></td>
+        </tr>
+        <tr>
+          <td class="num">十三、</td>
+          <td><a href="#gen_13">GPL 和 LGPL 的主要分別是什麼?</a></td>
+        </tr>
+      </table>
+      <h2 id="faq_jca">Joint Copyright Assignment (JCA)</h2>
+      <table class="zh_num">
+        <tr>
+          <td class="num">一、</td>
+          <td>Joint Copyright Assignment (JCA) 與舊的 Copyright Assignment 有何分別?</td>
+        </tr>
+        <tr>
+          <td class="num">二、</td>
+          <td>我是否必須填寫 JCA?</td>
+        </tr>
+        <tr>
+          <td class="num">三、</td>
+          <td>若我已簽了舊合約,但卻較喜歡新合約,我該怎麼做?</td>
+        </tr>
+        <tr>
+          <td class="num">四、</td>
+          <td>我如何以填寫了的 JCA 完成申請程序?</td>
+        </tr>
+        <tr>
+          <td class="num">五、</td>
+          <td>我已用 JCA 申請成功了,但我現在不再想簽署這些表格。我可否取消這些簽署了的表格?</td>
+        </tr>
+        <tr>
+          <td class="num">六、</td>
+          <td>我已簽署了 JCA,且已貢獻了一些原始程序碼,但我的原始程序碼沒被接納。那現在誰是我的原始程序碼的擁有者?</td>
+        </tr>
+        <tr>
+          <td class="num">七、</td>
+          <td>我已簽署了版權合約,且已貢獻了一些原始程序碼。你們可否在版權佈告中把我的姓名列出來?</td>
+        </tr>
+        <tr>
+          <td class="num">八、</td>
+          <td>我並非升陽員工,但我貢獻了一些 OpenOffice.org 網站內容。為何網頁底部的版權佈告只列出升陽?</td>
+        </tr>
+        <tr>
+          <td class="num">九、</td>
+          <td>JCA 中給予我道義上的權力,然而我的國家並不容許國民擁有這種權力。那該怎麼辦?</td>
+        </tr>
+        <tr>
+          <td class="num">十、</td>
+          <td>我有 GPL 軟件,或其他我想貢獻給 OpenOffice.org 的程序。然而,因為我不擁有這些軟件的版權,所以我不能讓這些程序在 JCA 或 PDL 授權聲明下貢獻出來。我該怎樣做?</td>
+        </tr>
+      </table>
+      <h2 id="faq_pdl">Public Documentation License (PDL)</h2>
+      <table class="zh_num">
+        <tr>
+          <td class="num">一、</td>
+          <td>PDL 是什麼?</td>
+        </tr>
+        <tr>
+          <td class="num">二、</td>
+          <td>我該怎樣用 PDL?</td>
+        </tr>
+        <tr>
+          <td class="num">三、</td>
+          <td>若我想以 PDL 來授權某一份文件,我是否需要將一份 PDL 放在文件中?</td>
+        </tr>
+        <tr>
+          <td class="num">四、</td>
+          <td>我什麼時侯才該用 PDL 而不用 JCA?</td>
+        </tr>
+      </table>
+      <h2 id="faq_tou">使用規定</h2>
+      <table class="zh_num">
+        <tr>
+          <td class="num">一、</td>
+          <td>為何 OpenOffice.org 網站會有使用規定聲明?</td>
+        </tr>
+        <tr>
+          <td class="num">二、</td>
+          <td>使用規定聲明的效力是否包括了所有我貢獻了給 OpenOffice.org 的文件和原始程序碼?</td>
+        </tr>
+      </table>
+      <br />
+      <br />
+      <hr />
+      <h2>一般問題:解答</h2>
+      <table class="zh_num">
+        <tr id="gen_1">
+          <td class="num">一、</td>
+          <td><dl>
+              <dt>OpenOffice.org 計劃用哪些授權聲明?</dt>
+              <dd> OpenOffice.org 原始程序碼用的是雙重授權聲明策略。這兩個授權聲明就是 GNU 次通用公共授權 (LGPL) 及 Sun Industry Standards Source License (SISSL)。另外,OpenOffice.org 以 Public Documentation License (PDL) 作為為用戶而設,且並非 OpenOffice.org 軟件一部分的文件的授權聲明。詳情請看下面相關的部分。 </dd>
+            </dl>
+            <p class="zh_toTop"><a href="#faq_gen">回一般問題</a></p></td>
+        </tr>
+        <tr id="gen_2">
+          <td class="num">二、</td>
+          <td><dl>
+              <dt>我該採用哪種授權聲明呢?</dt>
+              <dd> 這要看您想做什麼。若您想將您的原始程序碼包括在 OpenOffice.org 軟件內,那您就必須用其中一個原始程序碼授權聲明。否則,如放在網站上的常見問題集等不包括在 OpenOffice.org 軟件內的原始程序碼,都可以用 PDL 為授權聲明。若您想用原始程序碼授權聲明,您必須簽署 Joint Copyright Assignment (JCA)。若您想用 PDL 的話,就只需將 PDL 放在您的文件內。詳情請看下面 JCA 與 PDL 的部分。 </dd>
+            </dl>
+            <p class="zh_toTop"><a href="#faq_gen">回一般問題</a></p></td>
+        </tr>
+        <tr id="gen_3">
+          <td class="num">三、</td>
+          <td><dl>
+              <dt>我可以在哪裡找到更多關於授權聲明的資料呢?</dt>
+              <dd>您可以到這網站中的<a href="../about-licenses.html">授權聲明</a>一頁中找到更多關於 GNU 次通用公共授權 (LGPL),Sun Industry Standards Source License (SISSL),與 Public Documentation License (PDL) 的資料。這網頁中也有相關的資料可供參考。</dd>
+            </dl>
+            <p class="zh_toTop"><a href="#faq_gen">回一般問題</a></p></td>
+        </tr>
+        <tr id="gen_4">
+          <td class="num">四、</td>
+          <td><dl>
+              <dt>OpenOffice.org 的原始程序碼為何用雙重授權法?</dt>
+              <dd>雙重授權法給予開發者很大的自由度,讓自由軟件社區與其他不願或不能使用 GNU 通用公共許可證 (GPL) 的開發者與公司都可以自由取用 OpenOffice.org 的原始程序碼。雙重授權法於自由軟件社區中頗為普遍,其中較出名的有 Mozilla 及 Perl 等計劃。</dd>
+            </dl>
+            <p class="zh_toTop"><a href="#faq_gen">回一般問題</a></p></td>
+        </tr>
+        <tr id="gen_5">
+          <td class="num">五、</td>
+          <td><dl>
+              <dt>若我貢獻原始程序碼給 OpenOffice.org 的話,我需要在原始程序碼授權方面做什麼呢?</dt>
+              <dd>您若將原始程序碼貢獻給 OpenOffice.org,LGPL 與 SISSL 會自動對您的原始程序碼產生效力。為了統一版權,所有開發者都需要填寫 Joint Copyright Assignment (JCA)。若您只是想貢獻一些並不會包括在 OpenOffice.org 軟件內的文件,則可以使用 Public Documentation Licence (PDL)。</dd>
+            </dl>
+            <p class="zh_toTop"><a href="#faq_gen">回一般問題</a></p></td>
+        </tr>
+        <tr id="gen_6">
+          <td class="num">六、</td>
+          <td><dl>
+              <dt>為何 OpenOffice.org 用 LGPL 授權聲明?</dt>
+              <dd>OpenOffice.org 原始程序碼的授權聲明是 GNU 通用公共授權 (GPL) 系列中的 GNU 次通用公共授權 (LGPL)。LGPL 基本上與 GPL 完全一樣。它們唯一的不同之處就是 LGPL 准許您自由使用 OpenOffice.org 的原始程序碼,且不需以 GNU 通用公共授權 (GPL) 來公開自己的原始程序碼。詳情請看<a href="http://www.openoffice.org/white_papers/index.html">升陽的白皮書</a></dd>
+            </dl>
+            <p class="zh_toTop"><a href="#faq_gen">回一般問題</a></p></td>
+        </tr>
+        <tr id="gen_7">
+          <td class="num">七、</td>
+          <td><dl>
+              <dt>Sun Industry Standards Source License (SISSL) 是什麼?</dt>
+              <dd>Sun Industry Standards Source License (SISSL) 是 OpenOffice.org 原始程序碼的授權聲明,與 GNU 次通用公共授權 (LGPL) 一同生效。這授權聲明讓用戶可以自由運用、修改、及延伸 OpenOffice.org 的原始程序碼。不過開發者一定要保持 OpenOffice.org 語言中立的 API 及以 XML 為基礎的文件格式。</dd>
+            </dl>
+            <p class="zh_toTop"><a href="#faq_gen">回一般問題</a></p></td>
+        </tr>
+      </table>
+      The second license under which the sources will be made available is the SISSL. This license allows the user to do what they like with the source base, modify it, extend it, etc., but s/he must maintain compatibility. Attachment A of the SISSL defines the standards that must be met to comply with the license. For OpenOffice.org, the standards identified will be the LGPL versions of the OpenOffice.org technology language-independent APIs and XML-based file formats. If these standards are broken, the licensee must provide a reference implementation of sources which constitute the modification, thereby opening the details of any incompatibility/modification which has been introduced.
+      
+      
+      
+      Back to main question page
+      
+      Back to top
+      
+      
+      
+      8. May I take portions of the OpenOffice.org code and use it to extend and improve another application?
+      
+      
+      
+      Yes. You may freely modify, extend, and improve the OpenOffice.org source code. The only question is whether or not you must publish the source code and contribute modifications to the community. The GPL and the Sun Industry Standards Source License (SISSL) allow different ranges of flexibility in this regard but, in the end, regardless of the license used, any and all incompatible changes must be provided openly.
+      
+      
+      
+      Back to main question page
+      
+      Back to top
+      
+      
+      
+      9. How did this licensing architecture come about?
+      
+      
+      
+      Since the nature of OpenOffice.org technology is to provide re-usable and embedable office productivity components as well as the common applications services, the source code of the OpenOffice.org is dual licensed under a member of the GPL family of licenses, the Lesser GNU Public License (LGPL) and the Sun Industry Standards Source License (SISSL). Both of these are officially recognized free and open licenses. This licensing structure provides the necessary flexibility for combination of OpenOffice.org technologies with projects using other licenses (e.g. MPL, Apache, Artistic, etc.). It also provides the means through which commercial entities can participate with the OpenOffice.org community.
+      
+      
+      
+      Back to main question page
+      
+      Back to top
+      
+      
+      
+      10. Are OpenOffice.org binaries legal for commercial use?
+      
+      
+      
+      Yes, you may use OpenOffice.org binaries (the usable application) for commercial use. Please go to our download page to find the latest releases.
+      
+      
+      
+      Back to main question page
+      
+      Back to top
+      
+      
+      
+      11. Does the OpenOffice.org open source license give me the right to modify and distribute any version of StarOffice, for example, the currently shipping StarOffice? For example, can I undertake and ship a current version StarOffice for Catalan?
+      
+      
+      
+      No. The OpenOffice.org source license does not allow anyone to modify, repackage, or redistribute any version of StarOffice, or any other commercial version of the OpenOffice.org source code without an assignment from the vendor. For StarOffice the vendor is Sun Microsystems. Additionally, the source code in the OpenOffice.org project is the development project for future releases of StarOffice, starting with StarOffice 6.0. StarOffice 5.2 code is not part of the OpenOffice.org project.
+      
+      
+      
+      Back to main question page
+      
+      Back to top
+      
+      
+      
+      12. Can Sun ever take away the code?
+      
+      
+      
+      The simple answer to this is NO. Once code is released under the LGPL, it can never be taken away. Once LGPL, always LGPL. Sun has no plans to return to a closed development model. Sun is subject to the same rules as the rest of the community, including giving back modifications under the LGPL (or a specification and reference implementation under the terms of the SISSL). Thus, Sun can never take away the code and the community's contributions to it. This code belongs to the community as guaranteed by the LGPL and the SISSL.
+      
+      
+      
+      Back to main question page
+      
+      Back to top
+      
+      
+      
+      13. What is the essential difference between the GPL and the LGPL?
+      
+      
+      
+      When code licensed under the GPL is combined or linked with any other code, that code must also then be licensed under the GPL. In effect, this license demands that any code combined with GPL'd code falls under the GPL itself.
+      
+      
+      
+      Code licensed under the LGPL can be dynamically or statically linked to any other code, regardless of its license, as long as users are allowed to run debuggers on the combined program. In effect, this license recognizes kind of a boundary between the LGPL'd code and the code that is linked to it.
+      
+      
+      
+      Back to main question page
+      
+      Back to top
+      
+      Contributing Works
+      
+      The Joint Copyright Assignment: Answers
+      
+      
+      
+      1. How is the Joint Copyright Assignment (JCA) different from the old Copyright Assignment form?
+      
+      
+      
+      Under the Joint Copyright Assignment, both Sun and the contributor retain full rights to use, modify, and redistribute the copyrighted work. Under the Copyright Agreement form, the contributor』s rights were transferred to Sun and not shared with the contributor.
+      
+      
+      
+      Back to main question page
+      
+      Back to top
+      
+      
+      
+      2. Do I have to fill out a JCA?
+      
+      
+      
+      Yes, if you intend to contribute source code or other materials which are intended to be compiled or otherwise integrated with the OpenOffice.org product, regardless of the size of the contribution (e.g., including contributions of 10 lines or less). However we encourage all contributors to the OpenOffice.org website to fill out the JCA, as it makes accounting for contributions easier.
+      
+      
+      
+      Back to main question page
+      
+      Back to top
+      
+      
+      
+      3. What do I do if I already signed the old form, but I like this one better and want to change?
+      
+      
+      
+      Signing the JCA supersedes the Copyright Assignment form.
+      
+      
+      
+      Back to main question page
+      
+      Back to top
+      
+      
+      
+      4. How do I file a completed JCA?
+      
+      
+      
+      The process will be the same as for the old Copyright Assignment form. Please consult our Contributing page. We must have FAX or hard copy on file before we will assign an SSH key and update the list of accepted Copyright Assignments.
+      
+      
+      
+      Back to main question page
+      
+      Back to top
+      
+      
+      
+      5.
+      
+      
+      
+      I already have a form on file, but I』ve changed my mind and now I don』t want to sign either form. Can I cancel?
+      
+      
+      
+      There is no process to cancel an assignment once made for previously contributed technology. This is to protect the code base so everyone who uses it can depend on its continued functionality. However, you are never obligated to make further contributions.
+      
+      
+      
+      Back to main question page
+      
+      Back to top
+      
+      
+      
+      6. I tried to make a contribution to OpenOffice.org and signed a Copyright Assignment form, but my contribution wasn』t accepted. Who 「owns」 my code now?
+      
+      
+      
+      For all unaccepted contributions, ownership simply reverts to the contributor.
+      
+      
+      
+      Back to main question page
+      
+      Back to top
+      
+      
+      
+      7. I have a copyright assignment on file and I』ve made a code contribution to OpenOffice.org. Can I get listed on the copyright notice?
+      
+      
+      
+      It is impractical to include all contributors』 names in the copyright notice and its not legally necessary. Instead, we credit all contributors to the OpenOffice.org product on the Credits page. If you are not listed and should be you can of course request that your Project Lead add your name.
+      
+      
+      
+      Back to main question page
+      
+      Back to top
+      
+      
+      
+      8. I』m not a Sun employee but I』ve contributed content to the OpenOffice.org website. Why does the website copyright notice at the bottom of each web page only list Sun?
+      
+      
+      
+      It is impractical to include all contributors』 names in the copyright notice and its not legally necessary. Instead, each project is responsible for honoring all contributors to that project's website; a list of contributors to the general OpenOffice.org website is maintained by the Website project. If you are not listed and should be you can of course request that your Project Lead add your name.
+      
+      
+      
+      Back to main question page
+      
+      Back to top
+      
+      
+      
+      9. The JCA appears to address a grant of moral rights, but my country does not allow the grant of moral rights in any way.
+      
+      
+      
+      Yes, the JCA accommodates for local differences in the treatment of moral rights. Depending on local law, the part of the JCA related to moral rights may be not applicable in some European countries.
+      
+      
+      
+      Back to main question page
+      
+      Back to top
+      
+      
+      
+      10. I have GPL software, or other contributions which I would like to contribute to OpenOffice.org, but I cannot put them under the JCA or the PDL as I do not control the copyright of these items. What should I do?
+      
+      
+      
+      If you are certain that you have been granted the right to post the contribution (either because you wrote it or because it is licensed in a way that allows you to redistribute), there are a number of community websites that focus on OpenOffice.org related materials which may be willing to post such materials. Among them are:
+      
+      OOoDocs;
+      
+      OO Extras; and
+      
+      Evolved OpenOffice
+      
+      
+      
+      Back to main question page
+      
+      Back to top
+      
+      The Public Documentation License: Answers
+      
+      
+      
+      1. What is the Public Documentation License (PDL)?
+      
+      
+      
+      The PDL (Public Documentation License) PDF | HTML | RTF (text) is a new license authored by Sun to address the need for a license that allows Open Source communities to collaborate on documentation which isn』t intended for inclusion or integration in the project code base or in packaged distributions (e.g., 「product」).
+      
+      
+      
+      Back to main question page
+      
+      Back to top
+      
+      
+      
+      2. How do I use the PDL?
+      
+      
+      
+      The PDL is designed to be attached as a copy to a specific document, completing the information identifying the document and original author. The last page of the PDL is a log of changes to the document. All donors of edits must append a description of their contribution(s) to this page. For this reason the PDL is posted in an editable form (HTML | RTF [text]), however modifications other than to complete information to specify the document under license and to list contributors is prohibited as it is a standard legal contract.
+      
+      
+      
+      Back to main question page
+      
+      Back to top
+      
+      
+      
+      3. Do I have to attach a physical copy of the PDL to a document I wish covered by it?
+      
+      
+      
+      No. You may attach a link to the PDL in that document. But because every contributor to the document must log their changes on the license, it is actually more practical to just append it to the document as an editable file.
+      
+      
+      
+      Back to main question page
+      
+      Back to top
+      
+      
+      
+      4. When would I use the PDL instead of the JCA?
+      
+      
+      
+      The PDL was designed for Open Source documentation which isn』t intended for inclusion in the OpenOffice.org product. Before a document donated under the PDL can be included in the OpenOffice.org product, it must be converted to a JCA contribution. For this reason it is generally preferable to make all contributions to OpenOffice.org under the JCA.
+      
+      
+      
+      Back to main question page
+      
+      Back to top
+      
+      The Terms of Use: Answers
+      
+      
+      
+      1. Why does the OpenOffice.org website have a Terms of Use license?
+      
+      
+      
+      It is common practice to host a Terms of Use statement for corporate sponsored websites to catch any content that isn』t already covered by either a copyright assignment or a license so that the sponsor can legally police the site if undesirable content appears (if for instance someone posts content that is defamatory or content which the donor has no right to donate).
+      
+      
+      
+      Back to main question page
+      
+      Back to top
+      
+      
+      
+      2. Are all my contributions covered by the Terms of Use?
+      
+      The Terms of Use is superceded by all the licenses under which a donor can contribute (on OpenOffice.org this includes the JCA and PDL). The Terms of Use is intended as a catch all for contributions which are not specifically covered by the JCA or PDL, such as comments on a mail list or in a bug report.
+      
+      Back to main question page
+      
+      Back to top</td>
+    <td class="zhMenu"><!-- zh Menu Start -->
+      <a href="http://zh.OpenOffice.org"><img src="../../zh_ooo_logo_nav.png" alt="zh.OpenOffice.org" border="0" /></a>
+      <table class="zh_menu">
+        <tr>
+          <th>幫助</th>
+        </tr>
+        <tr>
+          <td><a href="../help-faq.html">常見問題</a> <br />
+            ∟各種常見問題</td>
+        </tr>
+      </table>
+      <!-- zh Menu End -->
+    </td>
+     </tr>
+</table>
+
+  </div>
+
+<!--#include virtual="/footer.html" -->
+
+</body>
+</html>