Results of 0 - 1 of about 0 (0.000 sec.)
- license-recommendations.zh-tw.po
- @digest: b98cf11a6c07576683d3502ba71a8263
- @id: 180286
- @mdate: 2022-01-02T17:38:03Z
- @size: 10804
- @type: text/html
- content-type: text/html; charset=utf-8
- #keywords: 權條 (22765), 授權 (21278), 條款 (18859), 們建 (18553), 的授 (17239), 作傳 (17189), 建議 (9473), 用< (8926), 用不 (8605), 始碼 (8605), 原始 (7433), 式碼 (7367), apache2 (7008), 專案 (6949), 發行 (6828), 專利 (6591), 著作 (5811), 來說 (5742), 說, (5544), 我們 (5069), 程式 (4379), 同的 (4116), 軟體 (3989), 包含 (3898), copyleft (3685), 的作 (3500), copylefting (3121), 使用 (3064), 翻譯 (2955), apache (2832), recommendations (2477), 不同 (2439)
- license-recommendations.zh-tw.po Mismatched links: 12. Mismatched ids: 0. # text 10 | One case where using a different license can be justified is when you make | major changes to a work under a non-copyleft license. If the version | you've created is considerably more useful than the original, then it's | worth copylefting your work, for all the same <a | [-href="/copyleft/copyleft.html">reasons-] | {+href="/licenses/copyleft.html">reasons+} we normally recommend | copyleft</a>. If you are in this situation, please follow the | recommendations below for licensing a new project. One case where using a different license can be justified is when you make major changes to a work under a non-copyleft license. If the version you've created is considerably more useful than the original, then it's worth copylefting your work, for all the same <a href=" /licenses/copyleft.html ">reasons we normally recommend copyleft</a>. If you are in this situation, please follow the recommendations below for licensing a new project. 當你對非「著作傳」式授權條款的作品進行重大變更時,使用不同的授權條款可能會是一個好選擇。特別是你的版本可能比原始版本更有用時,此時就非常值得讓你的作品「著作傳化」,正如<a href=" /copyleft/copyleft.html ">我們通常建議著作傳的理由那樣</a>。如果你遇到這種情況,請按照以下對新專案進行授權的建議。 13 | We recommend different licenses for different projects, depending mostly | on the software's purpose. In general, we recommend using the strongest | copyleft license that doesn't interfere with that purpose. Our essay [-<a | href="/copyleft/copyleft.html">“What-] {+“<a | href="/licenses/copyleft.html">What+} is [-Copyleft?”</a>-] | {+Copyleft?</a>”+} explains the concept of copyleft in more detail, | and why it is generally the best licensing strategy. We recommend different licenses for different projects, depending mostly on the software's purpose. In general, we recommend using the strongest copyleft license that doesn't interfere with that purpose. Our essay “<a href=" /licenses/copyleft.html ">What is Copyleft?</a>” explains the concept of copyleft in more detail, and why it is generally the best licensing strategy. 我們建議不同的專案使用不同的授權條款,主要取決於軟體的用途。一般來說,我們建議使用不會干擾用途的最強著作傳授權條款。我們的文章<a href=" /copyleft/copyleft.html ">《著作傳是什麼?》</a>對著作傳的概念有更詳細的解釋,以及為什麼它通常會是最佳的授權條款方案。 19 | For those programs, we recommend the <a | [-href="http://www.apache.org/licenses/LICENSE-2.0">Apache-] | {+href="https://directory.fsf.org/wiki/License:Apache2.0">Apache+} | License 2.0</a>. This is a weak, lax, “pushover” | (non-copyleft) software license that has terms to prevent contributors | and distributors from suing for patent infringement. This doesn't make | the software immune to threats from patents (no software license can | achieve that), but it does prevent patent holders from setting up a | “bait and switch” where they release the software under free | terms then require recipients to agree to nonfree terms in a patent | license. For those programs, we recommend the <a href=" https://directory.fsf.org/wiki/License:Apache2.0 ">Apache License 2.0</a>. This is a weak, lax, “pushover” (non-copyleft) software license that has terms to prevent contributors and distributors from suing for patent infringement. This doesn't make the software immune to threats from patents (no software license can achieve that), but it does prevent patent holders from setting up a “bait and switch” where they release the software under free terms then require recipients to agree to nonfree terms in a patent license. 對這些程式來說,我們建議使用 <a href=" http://www.apache.org/licenses/LICENSE-2.0 ">Apache 授權條款 2.0</a>。這是一個寬鬆、放任的、「聽從」式（非著作傳）軟體授權條款,其中包含了避免貢獻者與散布者因專利侵權而遭遇訴訟的條款。這無法讓軟體免除專利的威脅（從法律上軟體授權沒辦法辦到）,但它確實避免了專利持有者「上鉤後掉包」的作法,也就是先以自由授權條款發行軟體,但接著要求對方同意專利授權條款中的非自由條款。 24 | In these special situations, if you are aiming to convince proprietary | application developers to use the library for the free format, you would | need to make that easy by licensing the library under a weak license, such | as the <a [-href="http://www.apache.org/licenses/LICENSE-2.0">Apache-] | {+href="https://directory.fsf.org/wiki/License:Apache2.0">Apache+} | License 2.0</a>. In these special situations, if you are aiming to convince proprietary application developers to use the library for the free format, you would need to make that easy by licensing the library under a weak license, such as the <a href=" https://directory.fsf.org/wiki/License:Apache2.0 ">Apache License 2.0</a>. 在這類特殊情況下,如果你打算說服專有應用程式開發者使用自由格式的函式庫,就需要讓函式庫採用寬鬆的授權才會讓事情變得簡單,例如用 <a href=" http://www.apache.org/licenses/LICENSE-2.0 ">Apache Licence 2.0</a>。 36 | Some documentation includes software source code. For instance, a manual | for a programming language might include examples for readers to follow. | You should both include these in the manual under the FDL's terms, and | release them under another license that's appropriate for software. Doing | so helps make it easy to use the code in other projects. We recommend | that you dedicate small pieces of code to the public domain using <a | [-href="http://creativecommons.org/about/cc0">CC0</a>,-] | {+href="https://creativecommons.org/share-your-work/public-domain/cc0">CC0</a>,+} | and distribute larger pieces under the same license that the associated | software project uses. Some documentation includes software source code. For instance, a manual for a programming language might include examples for readers to follow. You should both include these in the manual under the FDL's terms, and release them under another license that's appropriate for software. Doing so helps make it easy to use the code in other projects. We recommend that you dedicate small pieces of code to the public domain using <a href=" https://creativecommons.org/share-your-work/public-domain/cc0 ">CC0</a>, and distribute larger pieces under the same license that the associated software project uses. 有一些文件包含軟體的原始碼。舉例來說,程式語言的手冊可能會包含讀者可以使用的範例。你應該使用 GFDL 的條款來將這些原始碼包含在手冊裡,另外又使用其他適當的授權條款同時也發行軟體原始碼。這樣做可以讓在其他專案中使用此段程式碼更簡單。我們建議將小段的程式碼透過 <a href=" http://creativecommons.org/about/cc0 ">CC0</a> 貢獻到公有領域,並使用與相關的軟體專案相同的授權條款來將大段的程式碼發行。 43 Please see the <a href="/server/standards/README.translations.html">Translations README</a> for information on coordinating and contributing translations of this article. 我們努力盡所能提供貼切、品質良善的翻譯。然而,我們無法十全十美,還請將你的意見評述與一般建議寄給 <a href=" mailto:web-translators@gnu.org "><web-translators@gnu.org></a></p><p>請參照 <a href="/server/standards/README.translations.html">翻譯讀我 README</a> 來瞭解協調和提交網頁翻譯等相關事宜。 45 This page is licensed under a <a rel="license" href=" http://creativecommons.org/licenses/by-nd/4.0/ ">Creative Commons Attribution-NoDerivatives 4.0 International License</a>. 本頁面採用<a rel="license" href=" https://creativecommons.org/licenses/by-nd/4.0/deed.zh_TW ">創用 CC 姓名標示-禁止改作 4.0 國際</a>條款給予授權。
...
-
http://www.gnu.org/savannah-checkouts/gnu/gnun/reports/zh-tw/licenses/license-recommendations.html
- [detail]
- [similar]
PREV
NEXT