incubator-ooo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r797836 [17/25] - in /websites/staging/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:15:58 GMT
Added: websites/staging/ooo-site/trunk/content/zh/new/zh_cn/faq/buildfaq.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/zh/new/zh_cn/faq/buildfaq.html (added)
+++ websites/staging/ooo-site/trunk/content/zh/new/zh_cn/faq/buildfaq.html Tue Nov  1 04:15:53 2011
@@ -0,0 +1,325 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<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>
+  <div id="banner">
+    <div id="bannerleft"><a alt="Apache OpenOffice.org (incubating)" href="/">
+      <img id="ooo-logo alt="Apache OpenOffice.org (Incubating)" src="/images/ooo-logo.png"/></a></div>
+    <div id="bannerright"><a alt="Apache Incubator" href="http://incubator.apache.org">
+      <img id="asf-logo" alt="Apache Incubator" src="/images/apache-incubator-logo.png"/></a></div>
+   <div id="bannercenter"><br/>(incubating)&nbsp;|&nbsp;The Free and Open Productivity Suite</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>
+
+  <div id="footera">
+    <div id="poweredbya">
+      <p><img src="/images/feather-small.gif"/><br/>Powered by the Apache CMS.</p>
+    </div>
+    <div id="copyrighta">
+      <p>
+	Apache "OpenOffice.org" is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator.
+	Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and
+	decision making process	have stabilized in a manner consistent with other successful ASF projects. While incubation status is
+	not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has
+	yet to be fully endorsed by the ASF.</p>
+      <p>
+	<a href="/contact.html">Contact Us</a> |
+	<a href="/terms.html">Terms of Use</a>
+	<br />Apache and the Apache feather logos are trademarks of The Apache Software Foundation.
+	<br />OpenOffice.org and the seagull logo are registered trademarks of The Apache Software Foundation.
+	<br />Other names appearing on the site may be trademarks of their respective owners.
+      </p>
+    </div>
+  </div>
+
+</body>
+</html>

Added: websites/staging/ooo-site/trunk/content/zh/new/zh_cn/faq/licensingFAQ.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/zh/new/zh_cn/faq/licensingFAQ.html (added)
+++ websites/staging/ooo-site/trunk/content/zh/new/zh_cn/faq/licensingFAQ.html Tue Nov  1 04:15:53 2011
@@ -0,0 +1,596 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<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>
+  <div id="banner">
+    <div id="bannerleft"><a alt="Apache OpenOffice.org (incubating)" href="/">
+      <img id="ooo-logo alt="Apache OpenOffice.org (Incubating)" src="/images/ooo-logo.png"/></a></div>
+    <div id="bannerright"><a alt="Apache Incubator" href="http://incubator.apache.org">
+      <img id="asf-logo" alt="Apache Incubator" src="/images/apache-incubator-logo.png"/></a></div>
+   <div id="bannercenter"><br/>(incubating)&nbsp;|&nbsp;The Free and Open Productivity Suite</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>
+
+  <div id="footera">
+    <div id="poweredbya">
+      <p><img src="/images/feather-small.gif"/><br/>Powered by the Apache CMS.</p>
+    </div>
+    <div id="copyrighta">
+      <p>
+	Apache "OpenOffice.org" is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator.
+	Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and
+	decision making process	have stabilized in a manner consistent with other successful ASF projects. While incubation status is
+	not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has
+	yet to be fully endorsed by the ASF.</p>
+      <p>
+	<a href="/contact.html">Contact Us</a> |
+	<a href="/terms.html">Terms of Use</a>
+	<br />Apache and the Apache feather logos are trademarks of The Apache Software Foundation.
+	<br />OpenOffice.org and the seagull logo are registered trademarks of The Apache Software Foundation.
+	<br />Other names appearing on the site may be trademarks of their respective owners.
+      </p>
+    </div>
+  </div>
+
+</body>
+</html>

Added: websites/staging/ooo-site/trunk/content/zh/new/zh_cn/faq/mFAQ.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/zh/new/zh_cn/faq/mFAQ.html (added)
+++ websites/staging/ooo-site/trunk/content/zh/new/zh_cn/faq/mFAQ.html Tue Nov  1 04:15:53 2011
@@ -0,0 +1,273 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<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>
+  <div id="banner">
+    <div id="bannerleft"><a alt="Apache OpenOffice.org (incubating)" href="/">
+      <img id="ooo-logo alt="Apache OpenOffice.org (Incubating)" src="/images/ooo-logo.png"/></a></div>
+    <div id="bannerright"><a alt="Apache Incubator" href="http://incubator.apache.org">
+      <img id="asf-logo" alt="Apache Incubator" src="/images/apache-incubator-logo.png"/></a></div>
+   <div id="bannercenter"><br/>(incubating)&nbsp;|&nbsp;The Free and Open Productivity Suite</div>
+  </div>
+  <div id="clear"></div>
+  
+  <div id="content">
+  
+    
+    
+<table id="zh_top" class="zhCore">
+  <tr>
+    <td class="zhContent"><h1 id="faq_gen">最常见问题</h1>
+      <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">我该到何处注册 OpenOffice.org ?</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.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 可以打开 Microsoft Word、Excel、PowerPoint 文件吗?</a></td>
+        </tr>
+        <tr>
+          <td class="num">七、</td>
+          <td><a href="#gen_7">OpenOffice.org 可在 Windows 95、Windows 98、Windows 2000、Windows XP 上执行吗?</a></td>
+        </tr>
+        <tr>
+          <td class="num">八、</td>
+          <td><a href="#gen_8">OpenOffice.org 的公开源授权证书有否赋予我权利去修改和分发任何版本的 StarOffice?</a></td>
+        </tr>
+        <tr>
+          <td class="num">九、</td>
+          <td><a href="#gen_9">升阳有没有可能没收 OpenOffice.org 的原始程序码?</a></td>
+        </tr>
+        <tr>
+          <td class="num">十、</td>
+          <td><a href="#gen_10">打印和 PDF Filters 的发展情况如何?</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">我如何取得其他语言的 OpenOffice.org ?</a></td>
+        </tr>
+        <tr>
+          <td class="num">十三、</td>
+          <td><a href="#gen_13">StarOffice/StarSuite 与 OpenOffice.org 有什么分别?</a></td>
+        </tr>
+        <tr>
+          <td class="num">十四、</td>
+          <td><a href="#gen_14">我的字体显示有问题,有没有解决的办法?</a></td>
+        </tr>
+        <tr>
+          <td class="num">十五、</td>
+          <td><a href="#gen_15">我可否附加文件于问题 (issue) 上?</a></td>
+        </tr>
+      </table>
+      <hr />
+      <h2>解答</h2>
+      <table class="zh_num">
+        <tr id="gen_1">
+          <td class="num">一、</td>
+          <td><dl>
+              <dt>OpenOffice.org的版权以及其版权内容是什么?</dt>
+              <dd> OpenOffice.org 采用 <a href="http://www.openoffice.org/licenses/sissl_license.html" target="_new">SISSL</a> 与 <a href="http://www.openoffice.org/licenses/lgpl_license.html"  target="_new">LGPL</a> 版权。您可通过签署<a href="http://www.openoffice.org/contributing.html" target="_new">授权书</a>方式对 OpenOffice.org 尽一已之力;您也可以免费复制与推广 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.org?</dt>
+              <dd> 您并不需要注册,请尽情下载并使用 OpenOffice.org。若使用上发现任何问题,我们希望您可以通过通信论坛 (mailing lists) 或在 IssueZilla 填写问题单,将问题清楚地告知我们。 </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>我可以在商业用途上使用 OpenOffice.org 吗?</dt>
+              <dd> 可以,您可在商业用途上使用 OpenOffice.org 软件。在使用前,请确认您已清楚了解 OpenOffice.org 仍在开发中,且功能未必很完整。假如您对 OpenOffice.org 的商品化版本有兴趣的话,可以链接到我们的<a href="../downloads-businesses.html">商品化版本网页</a>一看,以获得更多信息。 </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> 您可在网上免费<a href="../downloads.html">下载 OpenOffice.org 软件</a>,OpenOffice.org 组织不销售 OpenOffice.org。您若想购买 CD-ROM 分发者所销售的光碟,请一看<a href="../downloads-cdrom.html">光碟销售商列表</a>。 </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 不提供任何官方支持。另外,您也可在我们的<a href="../help-mailinglist.html">通信论坛</a>与一些其他 OpenOffice.org 讨论版得到一些技术支持。 </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 可以打开 Microsoft Word、Excel、PowerPoint 文件吗?</dt>
+              <dd> 可以。您可以通过“文件”-->“打开文档”的方式打开您的 Microsoft Office 文件。同样的,您也可以在存档时选择以 Microsoft Office 文件格式存档,让 Microsoft Office 使用者来打开您的文件。 </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 可在 Windows 95、Windows 98、Windows 2000、Windows XP 上执行吗?</dt>
+              <dd> 可以。 </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 的公开源授权证书有否赋予我权利去修改和分发任何版本的 StarOffice?</dt>
+              <dd> StarOffice/StarSuite 的版权并不属于 OpenOffice.org,而是属于升阳的。这类商业化版本的 OpenOffice.org 的版权都属于其销售商,所以在没有该软件销售商的同意之前,任何人都不能修改、再包装、或再分发任何商业化版本的 OpenOffice.org 原始码。 </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>升阳有没有可能没收 OpenOffice.org 的原始程序码?</dt>
+              <dd> 没可能。一旦原始程序码根据 GNU 次通用公共授权 (LGPL) 发行,就不可能被没收。升阳也没有打算恢复非公开的发展模式。升阳与其他人及团体都受到同样的条规所约束,因此升阳并不可能取去原始程序码和社区对原始程序码所作出的的贡献。GNU 次通用公共授权 (LGPL) 与 SISSL 确保原始程序码属于社区。 </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>打印和 PDF Filters 的发展情况如何?</dt>
+              <dd> 最新发行的 OpenOffice.org 产品都能够在多个平台上打印。如果打印出现问题,请到<a href="../downloads.html">下载区</a>下载并升级至最新的推荐版本。 </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>
+        <tr id="gen_12">
+          <td class="num">十二、</td>
+          <td><dl>
+              <dt>我如何取得其他语言的 OpenOffice.org?</dt>
+              <dd> 我们中文计划的<a href="../downloads.html">下载区</a>列出了中文与英文版的 OpenOffice.org。至于其他语言版本,请到 OpenOffice.org 的<a href="http://download.openoffice.org/" target="_new">下载区</a>。那里列出了拥有原码的语言。有关本地化的详情,请参考 <a href="http://l10n.openoffice.org" target="_new">http://l10n.openoffice.org</a>。 </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>StarOffice/StarSuite 与 OpenOffice.org 有什么分别?</dt>
+              <dd>
+                <ul>
+                  <li> OpenOffice.org 原始程序码并不包括 StarOffice/StarSuite 的全部原始程序码。这通常是因为升阳需要付款以获得授权,才可将第三方原始程序码包含于 StarOffice 内。升阳并没得到公开那些原始程序码的授权,所以不能将之包含在 OpenOffice.org 内。这些项目包括:<br />
+                    <ul>
+                      <li>某些字体,特别是亚洲语言的字体</li>
+                      <li>资料库模块 (Adabas D)</li>
+                      <li>某些文件样板</li>
+                      <li>大型 Clip Art 图库</li>
+                      <li>某些排序功能 (亚洲版本)</li>
+                      <li>某些文件过滤器 (filter)</li>
+                    </ul>
+                    详细资料请参考 OpenOffice.org<a href="../about-features.html"> 重要特性</a>一页。升阳的网页则备有关于 OpenOffice.org 的产品对照表以供参考。 </li>
+                </ul>
+              </dd>
+            </dl>
+            <p class="zh_toTop"><a href="#faq_gen">回目录</a></p></td>
+        </tr>
+        <tr id="gen_14">
+          <td class="num">十四、</td>
+          <td><dl>
+              <dt>我的字体显示有问题,有没有解決的办法?</dt>
+              <dd> 有,请查阅 OpenOffice.org 网页上 <a href="http://www.openoffice.org/FAQs/fontguide.html" target="_new">Christof Pintaske</a> 编写的字体疑难排解指南. </dd>
+            </dl>
+            <p class="zh_toTop"><a href="#faq_gen">回目录</a></p></td>
+        </tr>
+        <tr id="gen_15">
+          <td class="num">十五、</td>
+          <td><dl>
+              <dt>我可否附加文件于问题 (issue) 上?</dt>
+              <dd> 可以。现在文件大小上限是 10 MB。附加文件需要两个步骤:首先你必须提交问题,或是找出问题的位置,然后就可以把文件附加于问题上。上传文件时请尽量把文件缩小。同时,请谨记把 HTML 文件压缩,以免文件在下载过程中损坏。 </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>
+
+  <div id="footera">
+    <div id="poweredbya">
+      <p><img src="/images/feather-small.gif"/><br/>Powered by the Apache CMS.</p>
+    </div>
+    <div id="copyrighta">
+      <p>
+	Apache "OpenOffice.org" is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator.
+	Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and
+	decision making process	have stabilized in a manner consistent with other successful ASF projects. While incubation status is
+	not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has
+	yet to be fully endorsed by the ASF.</p>
+      <p>
+	<a href="/contact.html">Contact Us</a> |
+	<a href="/terms.html">Terms of Use</a>
+	<br />Apache and the Apache feather logos are trademarks of The Apache Software Foundation.
+	<br />OpenOffice.org and the seagull logo are registered trademarks of The Apache Software Foundation.
+	<br />Other names appearing on the site may be trademarks of their respective owners.
+      </p>
+    </div>
+  </div>
+
+</body>
+</html>



Mime
View raw message