www/licenses/po gcc-exception-3.0-faq.pot

[Yavor Doganov]

CVSROOT:        /web/www
Module name:    www
Changes by:     Yavor Doganov <yavor>   09/04/01 07:47:57

Removed files:
        licenses/po    : gcc-exception-3.0-faq.pot 

Log message:
        Delete.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/gcc-exception-3.0-faq.pot?cvsroot=www&r1=1.1&r2=0

Patches:
Index: gcc-exception-3.0-faq.pot
===================================================================
RCS file: gcc-exception-3.0-faq.pot
diff -N gcc-exception-3.0-faq.pot
--- gcc-exception-3.0-faq.pot   24 Mar 2009 08:26:44 -0000      1.1
+++ /dev/null   1 Jan 1970 00:00:00 -0000
@@ -1,385 +0,0 @@
-# SOME DESCRIPTIVE TITLE
-# Copyright (C) YEAR Free Software Foundation, Inc.
-# This file is distributed under the same license as the PACKAGE package.
-# FIRST AUTHOR <address@hidden>, YEAR.
-#
-#, fuzzy
-msgid ""
-msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2009-03-24 04:26-0300\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <address@hidden>\n"
-"Language-Team: LANGUAGE <address@hidden>\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=CHARSET\n"
-"Content-Transfer-Encoding: ENCODING"
-
-# type: Content of: <title>
-msgid ""
-"GCC Runtime Library Exception Rationale and FAQ - GNU Project - Free "
-"Software Foundation"
-msgstr ""
-
-# type: Content of: <h2>
-msgid "GCC Runtime Library Exception Rationale and FAQ"
-msgstr ""
-
-# type: Content of: <h3>
-msgid "Introduction"
-msgstr ""
-
-# type: Content of: <p>
-msgid ""
-"A year and a half ago, 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 ""
-
-# 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:address@hidden";>&lt;address@hidden&gt;</a>."
-msgstr ""
-
-# 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 2:"
-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 ""
-
-# 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 "
-"exception?"
-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 "
-"program."
-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 ""
-
-# 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 "
-"program."
-msgstr ""
-
-# type: Content of: <dl><dt>
-msgid ""
-"Why is compiler intermediate representation excluded from the definition of "
-"&ldquo;Target Code?&rdquo;"
-msgstr ""
-
-# 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 "Will Classpath use this new exception?"
-msgstr ""
-
-# 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>
-msgid "*GNUN-SLOT: TRANSLATOR'S NOTES*"
-msgstr ""
-
-# type: Content of: <div><p>
-msgid ""
-"Please send FSF &amp; GNU inquiries to <a "
-"href=\"mailto:address@hidden";><em>address@hidden</em></a>.  There are also <a 
"
-"href=\"/contact/\">other ways to contact</a> the FSF.  <br /> Please send "
-"broken links and other corrections or suggestions to <a "
-"href=\"mailto:address@hidden";><em>address@hidden</em></a>."
-msgstr ""
-
-# type: Content of: <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; 2008 Free Software Foundation, Inc.,"
-msgstr ""
-
-# type: Content of: <div><address>
-msgid "51 Franklin St, Fifth Floor, Boston, MA 02110, USA"
-msgstr ""
-
-# type: Content of: <div><p>
-msgid ""
-"Verbatim copying and distribution of this entire article are permitted "
-"worldwide, without royalty, in any medium, provided this notice, and the "
-"copyright notice, are preserved."
-msgstr ""
-
-#. TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.
-# type: Content of: <div><div>
-msgid "*GNUN-SLOT: TRANSLATOR'S CREDITS*"
-msgstr ""
-
-#.  timestamp start 
-# type: Content of: <div><p>
-msgid "Updated:"
-msgstr ""
-
-# type: Content of: <div><h4>
-msgid "Translations of this page"
-msgstr ""