incubator-ooo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From w...@apache.org
Subject svn commit: r1195809 [9/23] - in /incubator/ooo/ooo-site/trunk/content/zh: ./ css/ doc/ faq/ images/ images/doc/ new/ new/css/ new/ico/ new/pic/ new/zh_cn/ new/zh_cn/faq/ new/zh_cn/products/ new/zh_tw/ new/zh_tw/faq/ new/zh_tw/products/ products/
Date Tue, 01 Nov 2011 04:14:33 GMT
Added: incubator/ooo/ooo-site/trunk/content/zh/faq/apifaq_gb.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/zh/faq/apifaq_gb.html?rev=1195809&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/zh/faq/apifaq_gb.html (added)
+++ incubator/ooo/ooo-site/trunk/content/zh/faq/apifaq_gb.html Tue Nov  1 04:14:27 2011
@@ -0,0 +1,313 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
+    "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
+
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="zh-TW" >
+  <head>
+    <title>OpenOffice.org 中文网站</title>
+  
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+<style type="text/css">
+<!--
+.STYLE1 {font-size: 12px}
+-->
+</style>
+</head>
+
+  <body>
+
+    <link rel="stylesheet" type="text/css" href="../css/menuStyle.css" />
+    <link rel="stylesheet" type="text/css" href="../css/gen.css" />
+
+    <table id="zh_top" class="zhCore">
+
+      <tr>
+        <td class="zhContent">
+
+          <h1 id="faq_gen">关于 OpenOffice.org API 的常见问题</h1>
+<p><span class="STYLE1">原文:<a href="http://api.openoffice.org/faq.html">http://api.openoffice.org/faq.html</a></span></p>
+<p class="STYLE1">翻译:<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>
+
+          <br /><br />
+          <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_gb.html">下载区</a>下载并升级至最新版本。                    </dd>
+                  </dl>
+
+                  <p class="zh_toTop"><a href="#faq_gen">回目录</a></p>              </td>
+            </tr>
+          </table>        
+          <p>&nbsp;</p>
+        <p>&nbsp;</p>
+
+        </td>
+
+        <td class="zhMenu">
+
+        <!-- zh Menu Start -->
+
+          <table class="zh_menu" >
+
+            <tr>
+              <th>OpenOffice.org</th>
+            </tr>
+
+            <tr>
+              <td>
+                <a href="http://www.openoffice.org/">英文总站首页</a><br />
+                <a href="../index.html">繁体中文版首页</a><br />
+                <a href="../index_gb.html">简体中文版首页</a>
+              </td>
+            </tr>
+
+            <tr>
+              <th>关于我们</th>
+            </tr>
+
+            <tr>
+              <td>
+                <a href="../about-ooo_gb.html">关于 OpenOffice.org</a><br />
+                <a href="../about_zhProject_gb.html">关于中文计划</a>
+              </td>
+            </tr>
+
+            <tr>
+              <th>产品</th>
+            </tr>
+
+            <tr>
+              <td>
+                <a href="../about-product_gb.html">简介</a><br />
+                <a href="../features_gb.html">重要功能</a><br />
+                 <a href="../downloads_gb.html">下载</a><br />
+                <a href="../addons_gb.html">功能强化套件</a><br />
+                 <a href="../about-cdrom_gb.html">光碟</a><br />
+                 <a href="../about-businesses_gb.html">商品化版本</a>
+              </td>
+            </tr>
+
+            <tr>
+              <th>支援</th>
+            </tr>
+
+            <tr>
+              <td>
+                <a href="../doc_gb.html">说明文件</a><br />
+                <a href="../mailinglist_gb.html">通信论坛</a><br />
+                <a href="../faq_gb.html">常见问题</a>
+              </td>
+            </tr>
+
+            <tr>
+              <th>参与计划</th>
+            </tr>
+
+            <tr>
+              <td>
+                <a href="../help_ooo_gb.html">参与开发</a><br />
+                <a href="../help_zh_gb.html">参与中文计划</a><br />
+                <a href="../zh_tasks_gb.html">中文计划工作一览表</a><br />
+                <a href="http://www.openoffice.org/project_issues.html" target="_new">报告错误(英)</a><a href="../mailinglist_gb.html">(中)</a><br />
+              </td>
+            </tr>
+
+            <tr>
+              <th>其他</th>
+            </tr>
+
+            <tr>
+              <td>
+                <a href="../zh_members_gb.html">中文计划成员</a><br />
+                <a href="../zh_licenses_gb.html">授权声明</a>
+              </td>
+            </tr>
+
+            <tr>
+              <th>联络我们</th>
+            </tr>
+
+            <tr>
+              <td>
+                <a href="mailto:webmasters@openoffice.org">联络 OpenOffice.org</a><br />
+                <a href="mailto:pplwong@openoffice.org">联络中文计划</a>
+              </td>
+            </tr>
+
+          </table>
+
+        <!-- zh Menu End -->
+
+        </td>
+
+      </tr>
+    </table>
+  </body>
+</html>

Propchange: incubator/ooo/ooo-site/trunk/content/zh/faq/apifaq_gb.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/zh/faq/buildfaq_gb.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/zh/faq/buildfaq_gb.html?rev=1195809&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/zh/faq/buildfaq_gb.html (added)
+++ incubator/ooo/ooo-site/trunk/content/zh/faq/buildfaq_gb.html Tue Nov  1 04:14:27 2011
@@ -0,0 +1,408 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
+    "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
+
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="zh-TW" >
+  <head>
+    <title>OpenOffice.org 中文网站</title>
+  
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+<style type="text/css">
+<!--
+.STYLE1 {font-size: 12px}
+-->
+</style>
+</head>
+
+  <body>
+
+    <link rel="stylesheet" type="text/css" href="../css/menuStyle.css" />
+    <link rel="stylesheet" type="text/css" href="../css/gen.css" />
+
+    <table id="zh_top" class="zhCore">
+
+      <tr>
+        <td class="zhContent">
+
+          <h1 id="faq_gen">OpenOffice.org 开发构建常见问题</h1>
+<p><span class="STYLE1">原文:<a href="http://www.openoffice.org/FAQs/build_faq.html">http://www.openoffice.org/FAQs/build_faq.html</a></span></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>
+
+          <br /><br />
+          <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>        <p>&nbsp;</p>
+        <p>&nbsp;</p>
+
+        </td>
+
+        <td class="zhMenu">
+
+        <!-- zh Menu Start -->
+
+          <table class="zh_menu" >
+
+            <tr>
+              <th>OpenOffice.org</th>
+            </tr>
+
+            <tr>
+              <td>
+                <a href="http://www.openoffice.org/">英文总站首页</a><br />
+                <a href="../index.html">繁体中文版首页</a><br />
+                <a href="../index_gb.html">简体中文版首页</a>
+              </td>
+            </tr>
+
+            <tr>
+              <th>关于我们</th>
+            </tr>
+
+            <tr>
+              <td>
+                <a href="../about-ooo_gb.html">关于 OpenOffice.org</a><br />
+                <a href="../about_zhProject_gb.html">关于中文计划</a>
+              </td>
+            </tr>
+
+            <tr>
+              <th>产品</th>
+            </tr>
+
+            <tr>
+              <td>
+                <a href="../about-product_gb.html">简介</a><br />
+                <a href="../features_gb.html">重要功能</a><br />
+                 <a href="../downloads_gb.html">下载</a><br />
+                <a href="../addons_gb.html">功能强化套件</a><br />
+                 <a href="../about-cdrom_gb.html">光碟</a><br />
+                 <a href="../about-businesses_gb.html">商品化版本</a>
+              </td>
+            </tr>
+
+            <tr>
+              <th>支援</th>
+            </tr>
+
+            <tr>
+              <td>
+                <a href="../doc_gb.html">说明文件</a><br />
+                <a href="../mailinglist_gb.html">通信论坛</a><br />
+                <a href="../faq_gb.html">常见问题</a>
+              </td>
+            </tr>
+
+            <tr>
+              <th>参与计划</th>
+            </tr>
+
+            <tr>
+              <td>
+                <a href="../help_ooo_gb.html">参与开发</a><br />
+                <a href="../help_zh_gb.html">参与中文计划</a><br />
+                <a href="../zh_tasks_gb.html">中文计划工作一览表</a><br />
+                <a href="http://www.openoffice.org/project_issues.html" target="_new">报告错误(英)</a><a href="../mailinglist_gb.html">(中)</a><br />
+              </td>
+            </tr>
+
+            <tr>
+              <th>其他</th>
+            </tr>
+
+            <tr>
+              <td>
+                <a href="../zh_members_gb.html">中文计划成员</a><br />
+                <a href="../zh_licenses_gb.html">授权声明</a>
+              </td>
+            </tr>
+
+            <tr>
+              <th>联络我们</th>
+            </tr>
+
+            <tr>
+              <td>
+                <a href="mailto:webmasters@openoffice.org">联络 OpenOffice.org</a><br />
+                <a href="mailto:pplwong@openoffice.org">联络中文计划</a>
+              </td>
+            </tr>
+
+          </table>
+
+        <!-- zh Menu End -->
+
+        </td>
+
+      </tr>
+    </table>
+  </body>
+</html>

Propchange: incubator/ooo/ooo-site/trunk/content/zh/faq/buildfaq_gb.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/zh/faq/licensingFAQ.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/zh/faq/licensingFAQ.html?rev=1195809&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/zh/faq/licensingFAQ.html (added)
+++ incubator/ooo/ooo-site/trunk/content/zh/faq/licensingFAQ.html Tue Nov  1 04:14:27 2011
@@ -0,0 +1,444 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
+    "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
+
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="zh-TW" >
+  <head>
+    <title>OpenOffice.org 中文網站</title>
+  
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+
+  <body>
+
+    <link rel="stylesheet" type="text/css" href="../css/menuStyle.css" />
+    <link rel="stylesheet" type="text/css" href="../css/gen.css" />
+
+    <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="../zh_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
+        <p>&nbsp;</p>
+        <p>&nbsp;</p>
+
+        </td>
+
+        <td class="zhMenu">
+
+        <!-- zh Menu Start -->
+
+          <table class="zh_menu" >
+
+            <tr>
+              <th>OpenOffice.org</th>
+            </tr>
+
+            <tr>
+              <td>
+                <a href="http://www.openoffice.org/">英文總站首頁</a><br />
+                <a href="../index.html">正體中文版首頁</a><br />
+                <a href="../index_gb.html">簡體中文版首頁</a>
+              </td>
+            </tr>
+
+            <tr>
+              <th>關於我們</th>
+            </tr>
+
+            <tr>
+              <td>
+                <a href="../about-ooo.html">關於 OpenOffice.org</a><br />
+                <a href="../about_zhProject.html">關於中文計劃</a>
+              </td>
+            </tr>
+
+            <tr>
+              <th>產品</th>
+            </tr>
+
+            <tr>
+              <td>
+                <a href="../about-product.html">簡介</a><br />
+                <a href="../features.html">重要功能</a><br />
+                 <a href="../downloads.html">下載</a><br />
+                <a href="../addons.html">功能強化套件</a><br />
+                 <a href="../about-cdrom.html">光碟</a><br />
+                 <a href="../about-businesses.html">商品化版本</a>
+              </td>
+            </tr>
+
+            <tr>
+              <th>支援</th>
+            </tr>
+
+            <tr>
+              <td>
+                <a href="../doc.html">說明文件</a><br />
+                <a href="../mailinglist.html">通信論壇</a><br />
+                <a href="../faq.html">常見問題</a>
+              </td>
+            </tr>
+
+            <tr>
+              <th>參與計劃</th>
+            </tr>
+
+            <tr>
+              <td>
+                <a href="../help_ooo.html">參與開發</a><br />
+                <a href="../help_zh.html">參與中文計劃</a><br />
+                <a href="../zh_tasks.html">中文計劃工作一覽表</a><br />
+                <a href="http://www.openoffice.org/project_issues.html" target="_new">報告錯誤(英)</a><a href="../mailinglist.html">(中)</a><br />
+              </td>
+            </tr>
+
+            <tr>
+              <th>其他</th>
+            </tr>
+
+            <tr>
+              <td>
+                <a href="../zh_members.html">中文計劃成員</a><br />
+                <a href="../zh_licenses.html">授權聲明</a>
+              </td>
+            </tr>
+
+            <tr>
+              <th>聯絡我們</th>
+            </tr>
+
+            <tr>
+              <td>
+                <a href="mailto:webmasters@openoffice.org">聯絡 OpenOffice.org</a><br />
+                <a href="mailto:pplwong@openoffice.org">聯絡中文計劃</a>
+              </td>
+            </tr>
+
+          </table>
+
+        <!-- zh Menu End -->
+
+        </td>
+
+      </tr>
+    </table>
+  </body>
+</html>

Propchange: incubator/ooo/ooo-site/trunk/content/zh/faq/licensingFAQ.html
------------------------------------------------------------------------------
    svn:eol-style = native



Mime
View raw message