Return-Path: X-Original-To: apmail-incubator-ooo-commits-archive@minotaur.apache.org Delivered-To: apmail-incubator-ooo-commits-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B81667A29 for ; Tue, 1 Nov 2011 04:17:27 +0000 (UTC) Received: (qmail 72296 invoked by uid 500); 1 Nov 2011 04:17:27 -0000 Delivered-To: apmail-incubator-ooo-commits-archive@incubator.apache.org Received: (qmail 72152 invoked by uid 500); 1 Nov 2011 04:17:26 -0000 Mailing-List: contact ooo-commits-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ooo-dev@incubator.apache.org Delivered-To: mailing list ooo-commits@incubator.apache.org Received: (qmail 71941 invoked by uid 99); 1 Nov 2011 04:17:26 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Nov 2011 04:17:26 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Nov 2011 04:17:23 +0000 Received: from eris.apache.org (localhost [127.0.0.1]) by eris.apache.org (Postfix) with ESMTP id 3B97B2388C7C for ; Tue, 1 Nov 2011 04:16:06 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: svn commit: r797836 [22/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 -0000 To: ooo-commits@incubator.apache.org From: buildbot@apache.org X-Mailer: svnmailer-1.0.8-patched Message-Id: <20111101041606.3B97B2388C7C@eris.apache.org> Added: websites/staging/ooo-site/trunk/content/zh/new/zh_tw/faq/licensingFAQ.html ============================================================================== --- websites/staging/ooo-site/trunk/content/zh/new/zh_tw/faq/licensingFAQ.html (added) +++ websites/staging/ooo-site/trunk/content/zh/new/zh_tw/faq/licensingFAQ.html Tue Nov 1 04:15:53 2011 @@ -0,0 +1,596 @@ + + + + + + +OpenOffice.org 中文網站 + + + + + + + + + +
+ +
+ + + + + + + +  +

軟件授權常見問題

+

一般問題

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
一、OpenOffice.org 計劃用哪些授權聲明？
二、我該採用哪種授權聲明呢？
三、我可以在哪裡找到更多關於授權聲明的資料呢？
四、OpenOffice.org 的原始程序碼為何用雙重授權法？
五、若我貢獻原始程序碼給 OpenOffice.org 的話，我在授權聲明方面需要做什麼呢？
六、為何 OpenOffice.org 用 GNU 次通用公共授權 (LGPL)？
七、升陽的 Sun Industry Standards Source License (SISSL) 是什麼？
八、我可否用 OpenOffice.org 的部分原始程序碼來改進其他程序？
九、這授權結構是如何定下的？
十、以 OpenOffice.org 的程序作商業用途是否合法？
十一、OpenOffice.org 會否授權讓我修改及分發 StarOffice？
十二、升陽能否將 OpenOffice.org 奪去？
十三、GPL 和 LGPL 的主要分別是什麼？
+

Joint Copyright Assignment (JCA)

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
一、Joint Copyright Assignment (JCA) 與舊的 Copyright Assignment 有何分別？
二、我是否必須填寫 JCA？
三、若我已簽了舊合約，但卻較喜歡新合約，我該怎麼做？
四、我如何以填寫了的 JCA 完成申請程序？
五、我已用 JCA 申請成功了，但我現在不再想簽署這些表格。我可否取消這些簽署了的表格？
六、我已簽署了 JCA，且已貢獻了一些原始程序碼，但我的原始程序碼沒被接納。那現在誰是我的原始程序碼的擁有者？
七、我已簽署了版權合約，且已貢獻了一些原始程序碼。你們可否在版權佈告中把我的姓名列出來？
八、我並非升陽員工，但我貢獻了一些 OpenOffice.org 網站內容。為何網頁底部的版權佈告只列出升陽？
九、JCA 中給予我道義上的權力，然而我的國家並不容許國民擁有這種權力。那該怎麼辦？
十、我有 GPL 軟件，或其他我想貢獻給 OpenOffice.org 的程序。然而，因為我不擁有這些軟件的版權，所以我不能讓這些程序在 JCA 或 PDL 授權聲明下貢獻出來。我該怎樣做？
+

Public Documentation License (PDL)

+ + + + + + + + + + + + + + + + + +
一、PDL 是什麼？
二、我該怎樣用 PDL？
三、若我想以 PDL 來授權某一份文件，我是否需要將一份 PDL 放在文件中？
四、我什麼時侯才該用 PDL 而不用 JCA？
+

使用規定

+ + + + + + + + + +
一、為何 OpenOffice.org 網站會有使用規定聲明？
二、使用規定聲明的效力是否包括了所有我貢獻了給 OpenOffice.org 的文件和原始程序碼？
+
+
+
+

一般問題：解答

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
一、
+
OpenOffice.org 計劃用哪些授權聲明？
+
OpenOffice.org 原始程序碼用的是雙重授權聲明策略。這兩個授權聲明就是 GNU 次通用公共授權 (LGPL) 及 Sun Industry Standards Source License (SISSL)。另外，OpenOffice.org 以 Public Documentation License (PDL) 作為為用戶而設，且並非 OpenOffice.org 軟件一部分的文件的授權聲明。詳情請看下面相關的部分。
+
+

回一般問題

二、
+
我該採用哪種授權聲明呢？
+
這要看您想做什麼。若您想將您的原始程序碼包括在 OpenOffice.org 軟件內，那您就必須用其中一個原始程序碼授權聲明。否則，如放在網站上的常見問題集等不包括在 OpenOffice.org 軟件內的原始程序碼，都可以用 PDL 為授權聲明。若您想用原始程序碼授權聲明，您必須簽署 Joint Copyright Assignment (JCA)。若您想用 PDL 的話，就只需將 PDL 放在您的文件內。詳情請看下面 JCA 與 PDL 的部分。
+
+

回一般問題

三、
+
我可以在哪裡找到更多關於授權聲明的資料呢？
+
您可以到這網站中的授權聲明一頁中找到更多關於 GNU 次通用公共授權 (LGPL)，Sun Industry Standards Source License (SISSL)，與 Public Documentation License (PDL) 的資料。這網頁中也有相關的資料可供參考。
+
+

回一般問題

四、
+
OpenOffice.org 的原始程序碼為何用雙重授權法？
+
雙重授權法給予開發者很大的自由度，讓自由軟件社區與其他不願或不能使用 GNU 通用公共許可證 (GPL) 的開發者與公司都可以自由取用 OpenOffice.org 的原始程序碼。雙重授權法於自由軟件社區中頗為普遍，其中較出名的有 Mozilla 及 Perl 等計劃。
+
+

回一般問題

五、
+
若我貢獻原始程序碼給 OpenOffice.org 的話，我需要在原始程序碼授權方面做什麼呢？
+
您若將原始程序碼貢獻給 OpenOffice.org，LGPL 與 SISSL 會自動對您的原始程序碼產生效力。為了統一版權，所有開發者都需要填寫 Joint Copyright Assignment (JCA)。若您只是想貢獻一些並不會包括在 OpenOffice.org 軟件內的文件，則可以使用 Public Documentation Licence (PDL)。
+
+

回一般問題

六、
+
為何 OpenOffice.org 用 LGPL 授權聲明？
+
OpenOffice.org 原始程序碼的授權聲明是 GNU 通用公共授權 (GPL) 系列中的 GNU 次通用公共授權 (LGPL)。LGPL 基本上與 GPL 完全一樣。它們唯一的不同之處就是 LGPL 准許您自由使用 OpenOffice.org 的原始程序碼，且不需以 GNU 通用公共授權 (GPL) 來公開自己的原始程序碼。詳情請看升陽的白皮書
+
+

回一般問題

七、
+
Sun Industry Standards Source License (SISSL) 是什麼？
+
Sun Industry Standards Source License (SISSL) 是 OpenOffice.org 原始程序碼的授權聲明，與 GNU 次通用公共授權 (LGPL) 一同生效。這授權聲明讓用戶可以自由運用、修改、及延伸 OpenOffice.org 的原始程序碼。不過開發者一定要保持 OpenOffice.org 語言中立的 API 及以 XML 為基礎的文件格式。
+
+

回一般問題

+ 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		 + zh.OpenOffice.org + + + + + + + +
幫助
常見問題
+ ∟各種常見問題
+ +
+ + +
+ +
+
+


Powered by the Apache CMS.

+
+
+

+ 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.

+

+ Contact Us | + Terms of Use +
Apache and the Apache feather logos are trademarks of The Apache Software Foundation. +
OpenOffice.org and the seagull logo are registered trademarks of The Apache Software Foundation. +
Other names appearing on the site may be trademarks of their respective owners. +

+
+
+ + + Added: websites/staging/ooo-site/trunk/content/zh/new/zh_tw/faq/mFAQ.html ============================================================================== --- websites/staging/ooo-site/trunk/content/zh/new/zh_tw/faq/mFAQ.html (added) +++ websites/staging/ooo-site/trunk/content/zh/new/zh_tw/faq/mFAQ.html Tue Nov 1 04:15:53 2011 @@ -0,0 +1,273 @@ + + + + + + +OpenOffice.org 中文網站 + + + + + + + + + +
+ +
+ + + + + + + +  +

最常見問題

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
一、OpenOffice.org 的版權以及其版權內容是什麼？
二、我該到何處註冊 OpenOffice.org ？
三、我可以在我的工作上使用 OpenOffice.org 嗎？
四、哪裡可以買到 OpenOffice.org ？
五、OpenOffice.org 有提供一般支持嗎？
六、OpenOffice.org 可以打開 Microsoft Word、Excel、PowerPoint 文件嗎？
七、OpenOffice.org 可在 Windows 95、Windows 98、Windows 2000、Windows XP 上執行嗎？
八、OpenOffice.org 的公開源授權證書有否賦予我權利去修改和分發任何版本的 StarOffice？
九、升陽有沒有可能沒收 OpenOffice.org 的原始程序碼？
十、打印和 PDF Filters 的發展情況如何？
十一、支持系統在何處？
十二、我如何取得其他語言的 OpenOffice.org ？
十三、StarOffice/StarSuite 與 OpenOffice.org 有什麼分別？
十四、我的字體顯示有問題，有沒有解決的辦法？
十五、我可否附加文件於問題 (issue) 上？
+
+

解答

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
一、
+
OpenOffice.org的版權以及其版權內容是什麼？
+
OpenOffice.org 採用 SISSL 與 LGPL 版權。您可通過簽署授權書方式對 OpenOffice.org 盡一已之力；您也可以免費複製與推廣 OpenOffice.org 軟件。
+
+

回目錄

二、
+
我該到何處註冊 OpenOffice.org？
+
您並不需要註冊，請盡情下載並使用 OpenOffice.org。若使用上發現任何問題，我們希望您可以通過通信論壇 (mailing lists) 或在 IssueZilla 填寫問題單，將問題清楚地告知我們。
+
+

回目錄

三、
+
我可以在商業用途上使用 OpenOffice.org 嗎？
+
可以，您可在商業用途上使用 OpenOffice.org 軟件。在使用前，請確認您已清楚瞭解 OpenOffice.org 仍在開發中，且功能未必很完整。假如您對 OpenOffice.org 的商品化版本有興趣的話，可以鏈接到我們的商品化版本網頁一看，以獲得更多信息。
+
+

回目錄

四、
+
哪裡可以買到 OpenOffice.org ？
+
您可在網上免費下載 OpenOffice.org 軟件，OpenOffice.org 組織不銷售 OpenOffice.org。您若想購買 CD-ROM 分發者所銷售的光碟，請一看光碟銷售商列表。
+
+

回目錄

五、
+
OpenOffice.org 有提供一般支持嗎？
+
您或許可以從獨立供應商那裡取得支持，OpenOffice.org 不提供任何官方支持。另外，您也可在我們的通信論壇與一些其他 OpenOffice.org 討論版得到一些技術支持。
+
+

回目錄

六、
+
OpenOffice.org 可以打開 Microsoft Word、Excel、PowerPoint 文件嗎？
+
可以。您可以通過「文件」-->「打開文檔」的方式打開您的 Microsoft Office 文件。同樣的，您也可以在存檔時選擇以 Microsoft Office 文件格式存檔，讓 Microsoft Office 使用者來打開您的文件。
+
+

回目錄

七、
+
OpenOffice.org 可在 Windows 95、Windows 98、Windows 2000、Windows XP 上執行嗎？
+
可以。
+
+

回目錄

八、
+
OpenOffice.org 的公開源授權證書有否賦予我權利去修改和分發任何版本的 StarOffice？
+
StarOffice/StarSuite 的版權並不屬於 OpenOffice.org，而是屬於升陽的。這類商業化版本的 OpenOffice.org 的版權都屬於其銷售商，所以在沒有該軟件銷售商的同意之前，任何人都不能修改、再包裝、或再分發任何商業化版本的 OpenOffice.org 原始碼。
+
+

回目錄

九、
+
升陽有沒有可能沒收 OpenOffice.org 的原始程序碼？
+
沒可能。一旦原始程序碼根據 GNU 次通用公共授權 (LGPL) 發行，就不可能被沒收。升陽也沒有打算恢復非公開的發展模式。升陽與其他人及團體都受到同樣的條規所約束，因此升陽並不可能取去原始程序碼和社區對原始程序碼所作出的的貢獻。GNU 次通用公共授權 (LGPL) 與 SISSL 確保原始程序碼屬於社區。
+
+

回目錄

十、
+
打印和 PDF Filters 的發展情況如何？
+
最新發行的 OpenOffice.org 產品都能夠在多個平台上打印。如果打印出現問題，請到下載區下載並升級至最新的推薦版本。
+
+

回目錄

十一、
+
支持系統在何處？
+
最新版本的 OpenOffice.org 上附有支持系統。如果無法使用支持系統，請到下載區下載並升級至最新版本。
+
+

回目錄

十二、
+
我如何取得其他語言的 OpenOffice.org？
+
我們中文計劃的下載區列出了中文與英文版的 OpenOffice.org。至於其他語言版本，請到 OpenOffice.org 的下載區。那裡列出了擁有原碼的語言。有關本地化的詳情，請參考 http://l10n.openoffice.org。
+
+

回目錄

十三、
+
StarOffice/StarSuite 與 OpenOffice.org 有什麼分別？
+
+
    +
  • OpenOffice.org 原始程序碼並不包括 StarOffice/StarSuite 的全部原始程序碼。這通常是因為升陽需要付款以獲得授權，才可將第三方原始程序碼包含於 StarOffice 內。升陽並沒得到公開那些原始程序碼的授權，所以不能將之包含在 OpenOffice.org 內。這些項目包括：
    +
      +
    • 某些字體，特別是亞洲語言的字體
      • +
    • 資料庫模塊 (Adabas D)
      • +
    • 某些文件樣板
      • +
    • 大型 Clip Art 圖庫
      • +
    • 某些排序功能 (亞洲版本)
      • +
    • 某些文件過濾器 (filter)
      • +
    + 詳細資料請參考 OpenOffice.org 重要特性一頁。升陽的網頁則備有關於 OpenOffice.org 的產品對照表以供參考。
    • +
+
+
+

回目錄

十四、
+
我的字體顯示有問題，有沒有解決的辦法？
+
有，請查閱 OpenOffice.org 網頁上 Christof Pintaske 編寫的字體疑難排解指南．
+
+

回目錄

十五、
+
我可否附加文件於問題 (issue) 上？
+
可以。現在文件大小上限是 10 MB。附加文件需要兩個步驟：首先你必須提交問題，或是找出問題的位置，然後就可以把文件附加於問題上。上傳文件時請盡量把文件縮小。同時，請謹記把 HTML 文件壓縮，以免文件在下載過程中損壞。
+
+

回目錄

+

 

 + zh.OpenOffice.org + + + + + + + +
幫助
常見問題
+ ∟各種常見問題
+ +
+ + +
+ +
+
+


Powered by the Apache CMS.

+
+
+

+ 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.

+

+ Contact Us | + Terms of Use +
Apache and the Apache feather logos are trademarks of The Apache Software Foundation. +
OpenOffice.org and the seagull logo are registered trademarks of The Apache Software Foundation. +
Other names appearing on the site may be trademarks of their respective owners. +

+
+
+ + + Added: websites/staging/ooo-site/trunk/content/zh/new/zh_tw/faq/mostfaqs.html ============================================================================== --- websites/staging/ooo-site/trunk/content/zh/new/zh_tw/faq/mostfaqs.html (added) +++ websites/staging/ooo-site/trunk/content/zh/new/zh_tw/faq/mostfaqs.html Tue Nov 1 04:15:53 2011 @@ -0,0 +1,224 @@ + + + + + + +OpenOffice.org 中文網站 + + + + + + + + + +
+ +
+ + + + + + + +  +

軟件授權 FAQ

+

原文：http://www.openoffice.org/FAQs/mostfaqs.html

+

翻譯：Jacky Woo 校對：Chen Lishuang, Cheng Lin     Aug, 2007

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
一、將 Openoffice.org 軟件用於商業目的是否合法？
二、OpenOffice.org 的開源許可(open source license)是否給予我權力對於任何版本的 StarOffice 進行修改和發佈？
三、我是否可以銷售或者自行發佈 OpenOffice.org？
四、Sun 是否會收回源代碼？
五、我如何獲得 OpenOffice.org 的非英語版本軟件？
六、StarOffice 和 OpenOffice.org 之間有什麼區別？
七、我在變換使用字體的時候遇到了麻煩，有方法解決麼？
八、我可以在一個 Issue 上添加文件麼？
九、我是否能用 OpenOffice.org 打開編輯 Microsoft Access 文檔？
+
+
+

解答

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
一、
+
將Openoffice.org軟件用於商業目的是否合法？
+
是的，您可以以商業目的使用OpenOffice.org出品的軟件。詳細情況，請參考我們的軟件下載頁面。
+
+ 或者，如果您對於StarOffice的商業用途有興趣，請閱讀一下地址：http://www.sun.com/staroffice/
+
+

回目錄

二、
+
OpenOffice.org的開源許可(open source license)是否給予我權力對於任何版本的Staroffice進行修改和發佈？
+
不可以。OpenOffice.org的開源許可不允許任何人對任何版本的Staroffice進行修改、重新打包壓縮或者重新發佈，也不允許在沒有銷售方指派的情況下，對任何商業版的OpenOffice.org開源軟件進行修改、重新打包壓縮及重新發佈。
+
+ 對於StarOffice來說，唯一銷售方是Sun Mivrosyste
+
+

回目錄

三、
+
我是否可以銷售或者自行發佈OpenOffice.org？
+
可以。
+
+ 我們的LGPL許可允許任何人對OpenOffice.org軟件（可執行安裝程序和可以供人們使用的應用程序）進行銷售或者發佈，但應遵循的條件是通過鏈接（到www.openoffice.org/）或通過其內含物使源代碼對所有人公開。
+
+ 如果您對於銷售 OpenOffice.org 安裝光盤或者通過 OEM 電腦發佈軟件感興趣，請訪 問 CDROM 和 OEM 工作項目。
+
+

回目錄

四、
+
Sun是否會收回源代碼？
+
答案很簡單：不會。一旦源代碼在LGPL協議下被發佈，代碼就永遠不會被收回。一旦加入LGPL的大家庭，就永遠是LGPL的人了。
+
+ Sun沒有計劃將自身變回一個封閉開發的公司。
+
+ Sun和社區的其他成員一樣，服從其規則，包括在LGPL協議下公佈所做的修改。因此，SUN永遠不會收回源代碼和社區對代碼做出的貢獻。
+
+ 正如LGPL協議所保證的那樣，源代碼屬於社區。
+
+
+
+

回目錄

五、
+
我如何獲得OpenOffice.org的非英語版本軟件？
+
OpenOffice.org已經被翻譯並配置成為至少45種除英語以外的語言。我們在 Native-Language Confederation projects page 中詳細列出了軟件所支持的各種語言。這些語言在下載頁面也被羅列了出來。
+
+

回目錄

六、
+
StarOffice和OpenOffice.org之間有什麼區別？
+
StarOffice的源代碼包含OpenOffice.org源代碼所沒有的部分。通常情況下，其原因是Sun通過付費方式取得第三方代碼。這些第三方代碼可以被添加進StarOffice，卻並不能加入開放源代碼的OpenOffice.org中，否則會被視為侵權行為。
+
+ 這其中包括：
+
+
  • 某些特殊字體（包括特別是亞洲語言字體）
    +
  • 數據庫構件（Adabas D）
    +
  • 一些模板
    +
  • 大量的Clip Art Gallery
    +
  • 一些搜索功能（亞洲版本）
    +
  • 特定的文檔過濾器
    +
  • 商業性質的拼寫檢查、同義字字典
    +
  • 管理工具
    +
    + 如果需要瞭解更多關於OpenOffice.org目前的特色功能，請閱讀「Feature」頁面。在Sun Microsystems關於 OpenOffice.org 的官方網站上可以查閱詳細的OpenOffice.org與StarOffice的比較清單。
    • +
    +

    回目錄

    七、
    +
    我在變換使用字體的時候遇到了麻煩，有方法解決麼？
    +
    是的。我們很高興的告訴您，Chirstop Pintaske已經發佈了一篇出色的字體問題解決指南。請詳細閱讀。
    +
    +

    回目錄

    八、
    +
    我可以在一個Issue上添加文件麼？
    +
    是的。我們當前的流量限制是10MB（10兆字節）。將一個文件添加到一個issue上需要兩步並且添加後是不明顯的。首先，您必須提交一個issue或者找到你想添加附件的issue，然後，你就可以將文件以附件的形式添加到這個issue上。
    +
    + 注意：您不能在本地添加OpenOffice.org 文件。
    +
    + 提示：盡可能壓縮您的文件大小。而且，如果您正在上傳一個HTML 文檔，一定要保證先將其壓縮成(Zip 或tar )，否則當其他人試圖下載時文檔將會崩潰。
    +
    +

    回目錄

    九、
    +
    我是否能用OpenOffice.org打開編輯Microsoft Access文檔？
    +
    是的。這非常簡單，尤其是當您按照John McCreesh的詳細指南進行操作。你可以在線閱讀指南，也可以下載PDF格式(325k)。
    +
    +

    回目錄

    +

     

    		 + zh.OpenOffice.org + + + + + + + +
    幫助
    常見問題
    + ∟各種常見問題
    + +
    + + +
    + +
    +
    +


    Powered by the Apache CMS.

    +
    +
    +

    + 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.

    +

    + Contact Us | + Terms of Use +
    Apache and the Apache feather logos are trademarks of The Apache Software Foundation. +
    OpenOffice.org and the seagull logo are registered trademarks of The Apache Software Foundation. +
    Other names appearing on the site may be trademarks of their respective owners. +

    +
    +
    + + +