[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

www/licenses/po gcc-exception-3.1-faq.zh-cn.po

From: Wensheng XIE
Subject: www/licenses/po gcc-exception-3.1-faq.zh-cn.po
Date: Fri, 30 Nov 2018 22:06:17 -0500 (EST)

CVSROOT:        /web/www
Module name:    www
Changes by:     Wensheng XIE <wxie>     18/11/30 22:06:17

Added files:
        licenses/po    : gcc-exception-3.1-faq.zh-cn.po 

Log message:
        zh-cn: new translation


Index: gcc-exception-3.1-faq.zh-cn.po
RCS file: gcc-exception-3.1-faq.zh-cn.po
diff -N gcc-exception-3.1-faq.zh-cn.po
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ gcc-exception-3.1-faq.zh-cn.po      1 Dec 2018 03:06:17 -0000       1.1
@@ -0,0 +1,576 @@
+# Simplified Chinese translation of 
+# Copyright (C) 2018 Free Software Foundation, Inc.
+# This file is distributed under the same license as the original article.
+# Wensheng Xie <address@hidden>, 2018.
+msgid ""
+msgstr ""
+"Project-Id-Version: gcc-exception-3.1-faq.html\n"
+"POT-Creation-Date: 2014-04-05 00:01+0000\n"
+"PO-Revision-Date: 2018-12-01 11:03+0800\n"
+"Last-Translator: Wensheng Xie <address@hidden>\n"
+"Language-Team: Chinese <address@hidden>\n"
+"Language: zh_CN\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit"
+#. type: Content of: <title>
+msgid ""
+"GCC Runtime Library Exception Rationale and FAQ - GNU Project - Free "
+"Software Foundation"
+msgstr "GCC运行库例外的理由和常见问题解答 - GNU工程 - 
+#. type: Content of: <h2>
+msgid "GCC Runtime Library Exception Rationale and FAQ"
+msgstr "GCC运行库例外的理由和常见问题解答"
+#. type: Content of: <h3>
+msgid "Introduction"
+msgstr "引言"
+#. type: Content of: <p>
+msgid ""
+"On June 29th, 2007 the Free Software Foundation released GPLv3.  It was "
+"immediately adopted by fifteen GNU projects, and more made the switch in the "
+"following months.  Most of the GCC codebase migrated to the new license in "
+"the 4.2.2 release, and now we are preparing to finish that process."
+msgstr ""
+#. type: Content of: <p>
+msgid ""
+"The licenses for some libraries that accompany GCC have not been changed "
+"yet.  These libraries are automatically used by the object code that GCC "
+"produces.  Because of that, if these libraries were simply distributed only "
+"under the terms of the GPL, all the object code that GCC produces would have "
+"to be distributed under the same terms.  However, the FSF decided long ago "
+"to allow developers to use GCC's libraries to compile any program, "
+"regardless of its license.  Developing nonfree software is not good for "
+"society, and we have no obligation to make it easier.  We decided to permit "
+"this because forbidding it seemed likely to backfire, and because using "
+"small libraries to limit the use of GCC seemed like the tail wagging the dog."
+msgstr ""
 ‡ä»£ç ä½¿"
+#. type: Content of: <p>
+msgid ""
+"Therefore, these libraries have always had license exceptions that allow "
+"people to distribute the object code GCC produces under any license.  We are "
+"now moving these libraries to GPLv3 and updating their exceptions.  Our "
+"fundamental policy has not changed; the new license is meant to permit all "
+"the uses of GCC that were permitted before.  However, we have decided to use "
+"this opportunity to update the exception to accomplish three goals:"
+msgstr ""
+#. type: Content of: <ul><li><p>
+msgid ""
+"Take advantage of GPLv3's new provisions.  GPLv3 features a number of new "
+"terms which benefit all software.  These include section 7, which "
+"establishes a framework for providing license exceptions.  In order for GCC "
+"to get the most benefit from GPLv3, we need to update the exception to take "
+"these new terms into account, and work within the parameters of section 7."
+msgstr ""
+#. type: Content of: <ul><li><p>
+msgid ""
+"Lay the groundwork for a plugin infrastructure in GCC.  For a while now, the "
+"GCC developers have considered adding a plugin framework to the compiler.  "
+"This would make it easier for others to contribute to the project, and "
+"accelerate the development of new compilation techniques for GCC.  However, "
+"there have also been concerns that unscrupulous developers could write "
+"plugins that called out to proprietary software to transform the compiled "
+"code&mdash;effectively creating proprietary extensions to GCC and defeating "
+"the purpose of the GPL.  The updated exception prevents such abuse, enabling "
+"the GCC team to look forward to plugin developments."
+msgstr ""
+#. type: Content of: <ul><li><p>
+msgid ""
+"Make exceptions throughout the GCC code base consistent.  Over the years, as "
+"new files were added to GCC that needed to carry this license exception, we "
+"reviewed and updated the language to help clarify it and address new "
+"concerns.  As a result, there are now many different exception texts in GCC "
+"that provide the same basic permissions.  Now all of those files will be "
+"able to use the single new exception text that we've prepared, making it "
+"easier to perform legal reviews on the code."
+msgstr ""
+#. type: Content of: <p>
+msgid ""
+"As with GPLv3, we worked hard to listen to various users' concerns while we "
+"drafted this, and address them appropriately.  All told, we have spent more "
+"than a year on this process.  The Free Software Foundation and the GCC "
+"Steering Committee would like to thank Richard Fontana, Bradley Kuhn, and "
+"Karen Sandler at the Software Freedom Law Center for all their hard work and "
+"assistance with the exception.  The changes here will strengthen the GCC "
+"community, and we look forward to the compiler developments it will enable."
+msgstr ""
+"软件自由法律中心的Richard Fontana、Bradley Kuhn和Karen 
+#. type: Content of: <p>
+msgid ""
+"Because GCC is such a crucial part of developers' lives, we're expecting "
+"lots of questions about these changes, and we want to make sure that they're "
+"addressed.  Below we've addressed specific concerns that we expect users "
+"will have.  If you have questions about the new exception that aren't "
+"mentioned here, please feel free to contact us at <a href=\"mailto:";
+msgstr ""
+"时通过<a href=\"mailto:address@hidden";>&lt;address@hidden&gt;</a>联系"
+#. type: Content of: <h3>
+msgid "How the Exception Works"
+msgstr "例外是怎么回事"
+#. type: Content of: <p>
+msgid ""
+"The permission you need&mdash;to convey the object code from these GCC "
+"libraries under your own project's license&mdash;is primarily contained in "
+"section 1:"
+msgstr ""
+#. type: Content of: <blockquote><p>
+msgid ""
+"You have permission to propagate a work of Target Code formed by combining "
+"the Runtime Library with Independent Modules, even if such propagation would "
+"otherwise violate the terms of GPLv3, provided that all Target Code was "
+"generated by Eligible Compilation Processes.  You may then convey such a "
+"combination under terms of your choice, consistent with the licensing of the "
+"Independent Modules."
+msgstr ""
ä½œå“ï¼Œå³ä½¿è¯¥ä¼ æ’­ä»Žå…¶ä»–方面来看"
+#. type: Content of: <p>
+msgid ""
+"This section uses many defined terms, and their specific meanings are "
+"integral to how the exception works.  This section looks at how these terms "
+"relate to common scenarios."
+msgstr ""
+#. type: Content of: <p>
+msgid ""
+"When you write your software, it consists of a set of source code files.  "
+"Each file is an &ldquo;Independent Module,&rdquo; as long as it doesn't "
+"contain any source from the GCC libraries."
+msgstr ""
+#. type: Content of: <p>
+msgid ""
+"When you compile those source code files, they usually go through a series "
+"of steps: source code generation, preprocessing, compilation to low-level "
+"code, assembling, and linking.  Not all projects follow all these steps, "
+"depending on what language you're using and how it's written, but they'll "
+"always go in this order, and everyone using GCC will go through the process "
+"of compiling high-level code into some low-level language such as assembly "
+"code or Java bytecode.  This phase is when GCC combines or links your own "
+"code with code from the GCC libraries.  We call it the &ldquo;Compilation "
+"Process.&rdquo; The output you get from it is called &ldquo;Target Code,"
+"&rdquo; as long as that output is not used as compiler intermediate "
+"representation, or to create such an intermediate representation."
+msgstr ""
+"编译到诸如汇编或Java bytecode<sup><a 
+#. type: Content of: <p>
+msgid ""
+"In order to take advantage of this permission, the Compilation Process that "
+"you use to create Target Code has to be &ldquo;Eligible,&rdquo; which means "
+"that it does not involve both GCC and GPL-incompatible software.  It's "
+"important to remember that the Compilation Process starts when you feed "
+"<em>any</em> high-level code to GCC, and ends as soon as it generates "
+"anything that can be considered Target Code.  Because of that, as long as "
+"GCC isn't writing out intermediate representation, your Compilation Process "
+"can still be Eligible even if you use GCC in conjunction with GPL-"
+"incompatible assemblers, linkers, or high-level source generators: those "
+"programs aren't involved in the Compilation Process as it's defined here.  "
+"The only place you can't use GPL-incompatible software with GCC is when it's "
+"performing the core compilation work."
+msgstr ""
+#. type: Content of: <p>
+msgid ""
+"So, if you use GCC, with or without GPL-compatible enhancements, that would "
+"be an Eligible Compilation Process.  If you only use GPL-incompatible "
+"compiler tools, that would be an Eligible Compilation Process as well.  "
+"(It's not uncommon for people who build software for GNU/Linux to link "
+"against the GCC libraries even if they're using a different compiler.)  "
+"However, if you used GCC in conjunction with GPL-incompatible software "
+"during the process of transforming high-level code to low-level code, that "
+"would <em>not</em> be an Eligible Compilation Process.  This would happen "
+"if, for example, you used GCC with a proprietary plugin."
+msgstr ""
+#. type: Content of: <p>
+msgid ""
+"As long as you use an Eligible Compilation Process, then you have permission "
+"to take the Target Code that GCC generates and propagate it &ldquo;under "
+"terms of your choice.&rdquo;"
+msgstr ""
+#. type: Content of: <p>
+msgid ""
+"If you did use GPL-incompatible software in conjunction with GCC during the "
+"Compilation Process, you would not be able to take advantage of this "
+"permission.  Since all of the object code that GCC generates is derived from "
+"these GPLed libraries, that means you would be required to follow the terms "
+"of the GPL when propagating any of that object code.  You could not use GCC "
+"to develop your own GPL-incompatible software."
+msgstr ""
+#. type: Content of: <h3>
+msgid "Frequently Asked Questions"
+msgstr "常见问题解答"
+#. type: Content of: <dl><dt>
+msgid ""
+"I am using a standard release of GCC (such as one provided by the FSF, or "
+"with my operating system) to compile GPL-incompatible software.  How does "
+"this change affect me?"
+msgstr ""
+#. type: Content of: <dl><dd><p>
+msgid ""
+"It should not affect you at all.  Unless you've configured GCC to output "
+"intermediate representation&mdash;which is rare&mdash;the new exception is "
+"designed to ensure that you have no license obligations when you do this, "
+"just as the old exceptions were."
+msgstr ""
+#. type: Content of: <dl><dt>
+msgid "Who does this change affect?"
+msgstr "这个变更会影响哪些人?"
+#. type: Content of: <dl><dd><p>
+msgid ""
+"Nobody who is currently using GCC should be affected by this change.  The "
+"only changes in policy are meant to prevent developers from making certain "
+"modifications to GCC that <em>will</em> become feasible in the future.  The "
+"FSF has been working closely with GCC developers to learn more about the "
+"many different ways people use GCC today, and ensure that they will all be "
+"able to continue those activities under the new exception."
+msgstr ""
+#. type: Content of: <dl><dt>
+msgid ""
+"I use GCC in conjunction with proprietary preprocessors and/or source "
+"generators to compile my program.  Can I still take advantage of the "
+msgstr ""
+#. type: Content of: <dl><dd><p>
+msgid ""
+"Yes.  The Compilation Process can start with any &ldquo;code entirely "
+"represented in a high-level, non-intermediate language.&rdquo; This includes "
+"code generated by a preprocessor or other proprietary software.  As such, "
+"the Compilation Process in this case does not involve any proprietary "
+"software; it qualifies as Eligible, and the exception is available for this "
+msgstr ""
ï¼Œè€Œä¸æ˜¯è¿‡æ¸¡ä»£ç è¯­è¨€ã€‚"
+#. type: Content of: <dl><dt>
+msgid ""
+"I use GCC in conjunction with proprietary assemblers and/or linkers to "
+"compile my program.  Can I still take advantage of the exception?"
+msgstr "我使用GCC加
+#. type: Content of: <dl><dd><p>
+msgid ""
+"Yes.  The Compilation Process ends when the compiler generates Target Code, "
+"which includes output that is &ldquo;suitable for input to an assembler, "
+"loader, linker and/or execution phase.&rdquo; In other words, the "
+"Compilation Process in this case is over when you have assembly code or "
+"unlinked object files from GCC, and so it does not involve any proprietary "
+"software.  It qualifies as Eligible, and the exception is thus available for "
+"this program."
+msgstr ""
+#. type: Content of: <dl><dt>
+msgid ""
+"I use GCC to compile parts of my program, and a proprietary compiler to "
+"compile other parts.  The pieces are combined afterward, during assembler or "
+"linking phases.  Can I still take advantage of the exception?"
+msgstr ""
+#. type: Content of: <dl><dd><p>
+msgid ""
+"Yes.  In this case, each Independent Module is turned into Target Code "
+"through an Eligible Compilation Process.  Even though different modules will "
+"go through different processes, the exception is still available for this "
+msgstr ""
+#. type: Content of: <dl><dt>
+msgid ""
+"I use a proprietary compiler toolchain without any parts of GCC to compile "
+"my program, and link it with libstdc++.  My program itself does not include "
+"any runtime library code the same way that GCC-compiled programs include "
+"libgcc.  Can I still take advantage of the exception?"
+msgstr ""
+#. type: Content of: <dl><dd><p>
+msgid ""
+"Yes.  While combining libgcc with GCC-compiled object code is probably the "
+"most common way the exception is used, neither the GPL nor the GCC Runtime "
+"Library Exception distinguish between static linking, dynamic linking, and "
+"other methods for combining code in their conditions.  The same permissions "
+"are available to you, under the same terms, no matter which method you use."
+msgstr ""
 ‡ä»£ç åˆåœ¨ä¸€èµ·ï¼Œä½†"
+#. type: Content of: <dl><dd><p>
+msgid ""
+"Note that if you distribute libstdc++ as an independent library, you will "
+"need to follow the terms of the GPL when doing so.  For example, if you "
+"distribute the library itself in object code form, you will need to provide "
+"source code to your recipients using one of the methods listed in section 6 "
+"of GPLv3.  But as long as you are eligible to take advantage of the GCC "
+"Runtime Library Exception's permissions for your own program, the GPL's "
+"terms do not extend to it."
+msgstr ""
+#. type: Content of: <dl><dt>
+msgid ""
+"Why is compiler intermediate representation excluded from the definition of "
+"&ldquo;Target Code?&rdquo;"
+msgstr "为什么编译器过渡代码不在&ldquo;目标代ç 
+#. type: Content of: <dl><dd><p>
+msgid ""
+"When we first considered adding a plugin infrastructure to GCC, we were "
+"deeply concerned about the possibility that someone would write a plugin "
+"that would merely save GCC's internal, low-level compilation data structures "
+"to disk.  With that done, other software would be able to optimize or "
+"otherwise improve that code without being directly connected to GCC.  It may "
+"have been difficult for us to argue that those programs should be subject to "
+"the GPL's copyleft, so we wanted to discourage these sorts of arrangements."
+msgstr ""
+#. type: Content of: <dl><dd><p>
+msgid ""
+"We do that by excluding such output from the definition of Target Code.  "
+"Because of this, even if someone writes a plugin that saves this information "
+"to disk, any programs that change the structures before GCC writes out "
+"Target Code will be involved in the Compilation Process.  If that program is "
+"proprietary, the exception will not be available to any software compiled "
+"with it; the object code that GCC ultimately creates will have to be "
+"distributed under the terms of the GPL."
+msgstr ""
+#. type: Content of: <dl><dt>
+msgid ""
+"If I write some code in assembly language, can I combine that with other "
+"object code compiled normally, and still take advantage of the exception?"
+msgstr ""
+#. type: Content of: <dl><dd><p>
+msgid ""
+"Yes, as long as all of the object code was compiled through an Eligible "
+"Compilation Process.  The process of running hand-written assembly through "
+"an assembler is a Compilation Process, since it &ldquo;transforms code "
+"entirely represented in [a] non-intermediate language[] designed for human-"
+"written code... into Target Code.&rdquo;"
+msgstr ""
+#. type: Content of: <dl><dt>
+msgid "What libraries does the GCC Runtime Library Exception cover?"
+msgstr "GCC运行库例外包含哪些库?"
+#. type: Content of: <dl><dd><p>
+msgid ""
+"The GCC Runtime Library Exception covers any file that has a notice in its "
+"license headers stating that the exception applies.  This includes libgcc, "
+"libstdc++, libfortran, libgomp, libdecnumber, libgcov, and other libraries "
+"distributed with GCC."
+msgstr ""
+#. type: Content of: <dl><dt>
+msgid "Will Classpath use this new exception?"
+msgstr "Classpath会使用该例外吗?"
+#. type: Content of: <dl><dd><p>
+msgid ""
+"Even though Classpath's current exception serves a similar purpose, we are "
+"not updating it at this time.  Because of recent developments in the free "
+"software Java community, the priorities for Classpath's licensing policies "
+"are different from other GCC libraries, and we are evaluating it separately."
+msgstr ""
+#. TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.
+#. type: Content of: <div>
+msgstr ""
+"<li id=\"TransNote1\">Java 
+#. type: Content of: <div><div><p>
+msgid ""
+"Please send general FSF &amp; GNU inquiries to <a 
+"\">&lt;address@hidden&gt;</a>.  There are also <a href=\"/contact/\">other 
ways "
+"to contact</a> the FSF.  Broken links and other corrections or suggestions "
+"can be sent to <a href=\"mailto:address@hidden";>&lt;address@hidden"
+msgstr ""
¶ä»–错误或建议发送给<a href="
+#.  TRANSLATORS: Ignore the original text in this paragraph,
+#.         replace it with the translation of these two:
+#.         We work hard and do our best to provide accurate, good quality
+#.         translations.  However, we are not exempt from imperfection.
+#.         Please send your comments and general suggestions in this regard
+#.         to <a href="mailto:address@hidden";>
+#.         &lt;address@hidden&gt;</a>.</p>
+#.         <p>For information on coordinating and submitting translations of
+#.         our web pages, see <a
+#.         href="/server/standards/README.translations.html">Translations
+#.         README</a>. 
+#. type: Content of: <div><div><p>
+msgid ""
+"Please see the <a href=\"/server/standards/README.translations.html"
+"\">Translations README</a> for information on coordinating and submitting "
+"translations of this article."
+msgstr ""
+#. type: Content of: <div><p>
+msgid "Copyright &copy; 2014 Free Software Foundation, Inc."
+msgstr "Copyright &copy; 2014 Free Software Foundation, Inc."
+#. type: Content of: <div><p>
+msgid ""
+"This page is licensed under a <a rel=\"license\" href=\"http://";
+"creativecommons.org/licenses/by-nd/3.0/us/\">Creative Commons Attribution-"
+"NoDerivs 3.0 United States License</a>."
+msgstr ""
+"本页面使用<a rel=\"license\" 
+"nd/3.0/us/\">Creative Commons Attribution-NoDerivs 3.0 United States "
+#. TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.
+#. type: Content of: <div><div>
+msgstr ""
+"<b>翻译团队</b>:<a rel=\"team\" 
+#.  timestamp start 
+#. type: Content of: <div><p>
+msgid "Updated:"
+msgstr "最后更新:"

reply via email to

[Prev in Thread] Current Thread [Next in Thread]