gpl-2.0-faq.ko.po

Mismatched links: 105.

Mismatched ids: 77.

#text
3 | [-Translator's note which should be moved-]{+This page contains answers+}
| to {+commonly asked questions about+} the [-end.-] {+GNU General Public
| License (GPL), version 2. The FAQ for the current version of the GPL is <a
| href="/licenses/gpl-faq.html">here</a>. To learn more about the Free
| Software Foundation's other licenses, please see <a
| href="/licenses/licenses.html">our licenses page</a>.+} 
This page contains answers to commonly asked questions about the GNU General Public License (GPL), version 2. The FAQ for the current version of the GPL is <a href="/licenses/gpl-faq.html">here</a>. To learn more about the Free Software Foundation's other licenses, please see <a href="/licenses/licenses.html">our licenses page</a>. 
이 번역문은 가능한 한도 내에서 대한민국 저작권법과 컴퓨터 프로그램 보호법에서 정의하고 있는 용어를 사용하고 있습니다. 현행 대한민국 법률에 포함되어 있지 않은 내용과 용어들에 대해서는 저작권 심의 조정 위원회와 컴퓨터 법률 관련 논문들에서 제안하고 있는 용어를 사용했습니다. 
4  
After you read this FAQ, <a href="/cgi-bin/license-quiz.cgi">you can test your knowledge of Free Software licensing with our quiz</a>. 
 
16  
<a href="#ModifyGPL" id="TOCModifyGPL">Can I modify the GPL and make a modified license?</a> 
 
20  
<a href="#GPLAndNonfreeOnSameMachine" id="TOCGPLAndNonfreeOnSameMachine"> Can I have a GPL-covered program and an unrelated nonfree program on the same computer?</a> 
 
21  
<a href="#CanIDemandACopy" id="TOCCanIDemandACopy">If I know someone has a copy of a GPL-covered program, can I demand he give me a copy?</a> 
 
25  
<a href="#DoesTheGPLAllowDownloadFee" id="TOCDoesTheGPLAllowDownloadFee"> Does the GPL allow me to charge a fee for downloading the program from my distribution site?</a> 
 
27  
<a href="#DoesTheGPLRequireAvailabilityToPublic" id="TOCDoesTheGPLRequireAvailabilityToPublic">If I distribute GPL'd software for a fee, am I required to also make it available to the public without a charge?</a> 
 
28  
<a href="#DoesTheGPLAllowNDA" id="TOCDoesTheGPLAllowNDA">Does the GPL allow me to distribute a copy under a nondisclosure agreement?</a> 
 
29  
<a href="#DoesTheGPLAllowModNDA" id="TOCDoesTheGPLAllowModNDA">Does the GPL allow me to distribute a modified or beta version under a nondisclosure agreement?</a> 
 
30  
<a href="#DevelopChangesUnderNDA" id="TOCDevelopChangesUnderNDA">Does the GPL allow me to develop a modified version under a nondisclosure agreement?</a> 
 
31  
<a href="#RequiredToClaimCopyright" id="TOCRequiredToClaimCopyright">Am I required to claim a copyright on my modifications to a GPL-covered program?</a> 
 
32  
<a href="#CombinePublicDomainWithGPL" id="TOCCombinePublicDomainWithGPL">If a program combines public-domain code with GPL-covered code, can I take the public-domain part and use it as public domain code?</a> 
 
38  
<a href="#LGPLJava" id="TOCLGPLJava">How does the LGPL work with Java?</a> 
 
49  
<a href="#GPLUSGov" id="TOCGPLUSGov">Can the US Government release a program under the GNU GPL?</a> 
 
51  
<a href="#FontException" id="TOCFontException">How does the GPL apply to fonts?</a> 
 
52  
<a href="#WMS" id="TOCWMS">What license should I use for website maintenance system templates?</a> 
 
53  
<a href="#NonFreeTools" id="TOCNonFreeTools">Can I release a program under the GPL which I developed using nonfree tools?</a> 
 
55  
<a href="#ModifiedJustBinary" id="TOCModifiedJustBinary">Can I release a modified version of a GPL-covered program in binary form only?</a> 
 
56  
<a href="#UnchangedJustBinary" id="TOCUnchangedJustBinary">I downloaded just the binary from the net. If I distribute copies, do I have to get the source and distribute that too?</a> 
 
58  
<a href="#RedistributedBinariesGetSource" id="TOCRedistributedBinariesGetSource">My friend got a GPL-covered binary with an offer to supply source, and made a copy for me. Can I use the offer to obtain the source?</a> 
 
64  
<a href="#ReleaseNotOriginal" id="TOCReleaseNotOriginal"> Can I release a program with a license which says that you can distribute modified versions of it under the GPL but you can't distribute the original itself under the GPL?</a> 
 
65  
<a href="#UnreleasedMods" id="TOCUnreleasedMods"> A company is running a modified version of a GPL'ed program on a web site. Does the GPL say they must release their modified sources?</a> 
 
66  
<a href="#InternalDistribution" id="TOCInternalDistribution"> Is use within one organization or company &ldquo;distribution&rdquo;?</a> 
 
67  
<a href="#StolenCopy" id="TOCStolenCopy"> If someone steals a CD containing a version of a GPL-covered program, does the GPL give him the right to redistribute that version?</a> 
 
68  
<a href="#TradeSecretRelease" id="TOCTradeSecretRelease"> What if a company distributes a copy of some other developers' GPL-covered work to me as a trade secret?</a> 
 
69  
<a href="#TradeSecretRelease2" id="TOCTradeSecretRelease2"> What if a company distributes a copy of its own GPL-covered work to me as a trade secret?</a> 
 
70  
<a href="#DistributeSubsidiary" id="TOCDistributeSubsidiary"> Does moving a copy to a majority-owned, and controlled, subsidiary constitute distribution?</a> 
 
71  
<a href="#ClickThrough" id="TOCClickThrough"> Can software installers ask people to click to agree to the GPL? If I get some software under the GPL, do I have to agree to anything?</a> 
 
72  
<a href="#GPLCompatInstaller" id="TOCGPLCompatInstaller">I would like to bundle GPLed software with some sort of installation software. Does that installer need to have a GPL-compatible license?</a> 
 
78  
<a href="#LibGCCException" id="TOCLibGCCException">Does the libstdc++ exception permit dynamic linking?</a> 
 
82  
<a href="#GPLUSGovAdd" id="TOCGPLUSGovAdd">Can the US Government release improvements to a GPL-covered program?</a> 
 
83 | [-<b><a href="#TOCIfLibraryIsGPL" id="IfLibraryIsGPL">If-]{+<a
| href="#IfLibraryIsGPL" id="TOCIfLibraryIsGPL">If+} a library is
| released under the GPL (not the LGPL), does that mean that any program
| which uses it has to be under the [-GPL?</a></b>-] {+GPL?</a>+} 
<a href="#IfLibraryIsGPL" id="TOCIfLibraryIsGPL">If a library is released under the GPL (not the LGPL), does that mean that any program which uses it has to be under the GPL?</a> 
<b><a href="#TOCIfLibraryIsGPL" id="IfLibraryIsGPL">만약 라이브러리가 LGPL이 아닌 GPL로 공표되어 있다면 이 라이브러리를 사용하는 프로그램은 GPL 프로그램이 되어야 합니까?</a></b> 
90  
<a href="#GPLPlugins" id="TOCGPLPlugins"> When are a program and its plug-ins considered a single combined program?</a> 
 
93  
<a href="#NFUseGPLPlugins" id="TOCNFUseGPLPlugins">Can I release a nonfree program that's designed to load a GPL-covered plug-in?</a> 
 
95  
<a href="#GPLWrapper" id="TOCGPLWrapper">I'd like to incorporate GPL-covered software in my proprietary system. Can I do this by putting a &ldquo;wrapper&rdquo; module, under a GPL-compatible lax permissive license (such as the X11 license) in between the GPL-covered part and the proprietary part?</a> 
 
96 | <a [-href="#WritingFSWithNFLibs"-] {+href="#FSWithNFLibs"+}
| id="TOCFSWithNFLibs"> {+Can+} I [-am writing-] {+write+} free software
| that uses nonfree [-libraries. What legal issues come up if I use the
| GPL?</a>-] {+libraries?</a>+} 
<a href="#FSWithNFLibs" id="TOCFSWithNFLibs"> Can I write free software that uses nonfree libraries?</a> 
<a href="#WritingFSWithNFLibs" id="TOCWritingFSWithNFLibs">자유 소프트웨어가 아닌 라이브러리를 사용하는 자유 소프트웨어를 개발하고 있습니다. 이 경우, GPL을 라이선스로 사용하게 되면 어떠한 법적 문제가 일어날 수 있습니까?</a> 
97  
<a href="#GPLIncompatibleLibs" id="TOCGPLIncompatibleLibs"> What legal issues come up if I use GPL-incompatible libraries with GPL software?</a> 
 
100  
<a href="#GPLIncompatibleAlone" id="TOCGPLIncompatibleAlone">If license for a module Q has a requirement that's incompatible with the GPL, but the requirement applies only when Q is distributed by itself, not when Q is included in a larger program, does that make the license GPL-compatible? Can I combine or link Q with a GPL-covered program?</a> 
 
102  
<a href="#LinkingOverControlledInterface" id="TOCLinkingOverControlledInterface">How can I allow linking of proprietary modules with my GPL-covered library under a controlled interface only?</a> 
 
121  
Making the program a GNU software package means explicitly contributing to the GNU Project. This happens when the program's developers and the GNU Project agree to do it. If you are interested in contributing a program to the GNU Project, please write to <a href="mailto:maintainers@gnu.org">&lt;maintainers@gnu.org&gt;</a>. 
자신의 프로그램을 GNU 소프트웨어 패키지로 만든다는 것은 명시적으로 GNU 프로젝트에 참여하고 기여하게 된다는 것을 의미합니다. 이것은 프로그램의 개발자와 GNU 프로젝트 양자가 서로 동의했을 때만 가능한 것입니다. 만약 여러분이 만든 프로그램을 GNU 프로젝트에 제공하고자 한다면 &lt;<a href="mailto:maintainers@gnu.org">maintainers@gnu.org</a>&gt; 앞으로 영문 메일을 주시기 바랍니다. 한국어 메일의 경우에는 &lt;<a href="mailto:maintainers@korea.gnu.org">maintainers@korea.gnu.org</a>&gt; 앞으로 보내 주시면 됩니다. 
123  
You should <a href="/licenses/gpl-violation.html">report it</a>. First, check the facts as best you can. Then tell the publisher or copyright holder of the specific GPL-covered program. If that is the Free Software Foundation, write to <a href="mailto:license-violation@gnu.org">&lt;license-violation@gnu.org&gt;</a>. Otherwise, the program's maintainer may be the copyright holder, or else could tell you how to contact the copyright holder, so report it to the maintainer. 
<a href="/licenses/gpl-violation.html">신고해야 합니다!</a> 먼저, 여러분이 할 수 있는 최선의 범위에서 GPL 위반 여부를 판단해 본 뒤에 그 사실을 해당 GPL 프로그램의 저작권자나 출판자에게 알려주시기 바랍니다. 저작권자가 자유 소프트웨어 재단 즉, Free Software Foundation으로 표시되어 있다면 &lt;<a href="mailto:license-violation@gnu.org">license-violation@gnu.org</a>&gt; 앞으로 영문 메일을 주시기 바랍니다. 영어에 익숙하지 않다면 &lt;<a href="mailto:license-violation@korea.gnu.org">license-violation@korea.gnu.org</a>&gt; 앞으로 한국어 메일을 주시기 바랍니다. 저작권자를 명확히 알 수 없는 경우에는 프로그램의 메인테이너에게 연락하시면 됩니다. 대부분의 경우에 있어서 메인테이너는 저작권자 자신이거나 저작권자에게 연락할 수 있는 방법을 알고 있는 사람입니다. 
132  
<b><a href="#TOCGPLAndNonfreeOnSameMachine" id="GPLAndNonfreeOnSameMachine"> Can I have a GPL-covered program and an unrelated nonfree program on the same computer?</a></b> 
 
134  
<b><a href="#TOCCanIDemandACopy" id="CanIDemandACopy">If I know someone has a copy of a GPL-covered program, can I demand he give me a copy?</a></b> 
 
142  
<b><a href="#TOCRequiredToClaimCopyright" id="RequiredToClaimCopyright">Am I required to claim a copyright on my modifications to a GPL-covered program?</a></b> 
 
144  
Whether you claim a copyright on your changes or not, either way you must release the modified version, as a whole, under the GPL. (<a href="#GPLRequireSourcePostedPublic">if you release your modified version at all</a>) 
 
145  
<b><a href="#TOCCombinePublicDomainWithGPL" id="CombinePublicDomainWithGPL">If a program combines public-domain code with GPL-covered code, can I take the public-domain part and use it as public domain code?</a></b> 
 
149  
<b><a href="#TOCDoesTheGPLAllowDownloadFee" id="DoesTheGPLAllowDownloadFee"> Does the GPL allow me to charge a fee for downloading the program from my distribution site?</a></b> 
 
154  
You <em>can</em> charge people a fee to <a href="#DoesTheGPLAllowMoney">get a copy <em>from you</em></a>. You can't require people to pay you when they get a copy <em>from someone else</em>. 
 
155  
<b><a href="#TOCDoesTheGPLRequireAvailabilityToPublic" id="DoesTheGPLRequireAvailabilityToPublic">If I distribute GPL'd software for a fee, am I required to also make it available to the public without a charge?</a></b> 
 
157  
<b><a href="#TOCDoesTheGPLAllowNDA" id="DoesTheGPLAllowNDA"> Does the GPL allow me to distribute copies under a nondisclosure agreement?</a></b> 
 
159  
If someone asks you to sign an NDA for receiving GPL-covered software copyrighted by the FSF, please inform us immediately by writing to <a href="mailto:license-violation@fsf.org">license-violation@fsf.org</a>. 
 
161  
<b><a href="#TOCDoesTheGPLAllowModNDA" id="DoesTheGPLAllowModNDA"> Does the GPL allow me to distribute a modified or beta version under a nondisclosure agreement?</a></b> 
 
163  
<b><a href="#TOCDevelopChangesUnderNDA" id="DevelopChangesUnderNDA"> Does the GPL allow me to develop a modified version under a nondisclosure agreement?</a></b> 
 
176 | The preamble and instructions are integral parts of the GNU GPL and may
| not be omitted. In fact, the GPL is copyrighted, and its license permits
| only verbatim copying of the entire GPL. {+(You can use the legal terms
| to make <a href="#ModifyGPL">another license</a> but it won't be the GNU
| GPL.)+} 
The preamble and instructions are integral parts of the GNU GPL and may not be omitted. In fact, the GPL is copyrighted, and its license permits only verbatim copying of the entire GPL. (You can use the legal terms to make <a href="#ModifyGPL">another license</a> but it won't be the GNU GPL.) 
전문과 GPL을 실무에 적용하는 방법은 GPL 전체를 구성하는 하나의 통합된 부분입니다. 따라서 생략될 수 없습니다. 실제로 GPL 그 자체는 카피레프트가 아니라 저작권이 설정된 카피라이트이기 때문에 단지 GPL을 있는 그대로 복제하는 것만이 허용됩니다. 
185 | <b><a [-href="#TOCWritingFSWithNFLibs id="WritingFSWithNFLibs">-]
| {+href="#TOCFSWithNFLibs" id="FSWithNFLibs">Can+} I [-am writing-]
| {+write+} free software that uses nonfree [-libraries. What legal issues
| come up if I use the GPL?</a></b>-] {+libraries?</a></b>+} 
<b><a href="#TOCFSWithNFLibs" id="FSWithNFLibs">Can I write free software that uses nonfree libraries?</a></b> 
<b><a href="#TOCWritingFSWithNFLibs" id="WritingFSWithNFLibs">자유 소프트웨어가 아닌 라이브러리를 사용하는 자유 소프트웨어를 개발하고 있습니다. 이 경우, GPL을 라이선스로 사용하게 되면 어떠한 법적 문제가 일어날 수 있습니까?</a></b> 
189  
Note that there may also be legal issues with combining certain nonfree libraries with GPL-covered Free Software. Please see <a href="#GPLIncompatibleLibs">the question on GPL software with GPL-incompatible libraries</a> for more information. 
 
190  
<b><a href="#TOCGPLIncompatibleLibs" id="GPLIncompatibleLibs">What legal issues come up if I use GPL-incompatible libraries with GPL software?</a></b> 
 
205  
If the libraries you intend to link with are nonfree, please also see <a href="#FSWithNFLibs">the section on writing Free Software which uses nonfree libraries</a>. 
 
234  
<b><a href="#TOCGPLUSGov" id="GPLUSGov">Can the US Government release a program under the GNU GPL?</a></b> 
 
235  
If the program is written by US federal government employees in the course of their employment, it is in the public domain, which means it is not copyrighted. Since the GNU GPL is based on copyright, such a program cannot be released under the GNU GPL. (It can still be <a href="/philosophy/free-sw.html"> free software</a>, however; a public domain program is free.) 
 
237  
<b><a href="#TOCGPLUSGovAdd" id="GPLUSGovAdd">Can the US Government release improvements to a GPL-covered program?</a></b> 
 
242  
So the only way you have a say in the use of the output is if substantial parts of the output are copied (more or less) from text in your program. For instance, part of the output of Bison (see above) would be covered by the GNU GPL, if we had not made an exception in this specific case. 
따라서 출력물의 사용에 대해서 여러분이 어떠한 영향력을 행사할 수 있는 유일한 경우는 출력물의 핵심 부분이 여러분이 만든 프로그램의 일부분을 복사하는 형태로 만들어 지는 경우입니다. 예를 들면, <a href="#CanIUseGPLToolsForNF">이전 질문에 대한 답변과 같이 Bison</a>을 사용해서 만들어진 결과물은 모두 GPL이 됩니다. 하지만 Bison의 경우에는 전략상의 이유로 우리가 특별한 예외 기준을 설정해 놓았다는 것을 이미 말한 바 있습니다. 
250 | Yes, because the program {+actually links to the library. As such, the
| terms of the GPL apply to the entire combination. The software modules
| that link with the library may be under various GPL compatible licenses,
| but the work+} as {+a whole must be licensed under the GPL. See also: <a
| href="#WhatDoesCompatMean">What does+} it {+mean to say a license+} is
| [-actually run includes-] {+&ldquo;compatible with+} the [-library.-]
| {+GPL&rdquo;?</a>+} 
Yes, because the program actually links to the library. As such, the terms of the GPL apply to the entire combination. The software modules that link with the library may be under various GPL compatible licenses, but the work as a whole must be licensed under the GPL. See also: <a href="#WhatDoesCompatMean">What does it mean to say a license is &ldquo;compatible with the GPL&rdquo;?</a> 
그렇습니다. 실제적으로 프로그램이 라이브러리를 포함한 상태로 실행되기 때문에 GPL이 되어야 합니다. 
253 | However, when the interpreter is extended to provide
| &ldquo;bindings&rdquo; to other facilities (often, but not necessarily,
| libraries), the interpreted program is effectively linked to the
| facilities it uses through these bindings. So if these facilities are
| released under the GPL, the interpreted program that uses them must be
| released in a GPL-compatible way. The JNI or Java Native Interface is an
| example of such a [-facility;-] {+binding mechanism;+} libraries that are
| accessed in this way are linked dynamically with the Java programs that
| call them. {+These libraries are also linked with the interpreter. If
| the interpreter is linked statically with these libraries, or if it is
| designed to <a href="#GPLPluginsInNF"> link dynamically with these
| specific libraries</a>, then it too needs to be released in a
| GPL-compatible way.+} 
However, when the interpreter is extended to provide &ldquo;bindings&rdquo; to other facilities (often, but not necessarily, libraries), the interpreted program is effectively linked to the facilities it uses through these bindings. So if these facilities are released under the GPL, the interpreted program that uses them must be released in a GPL-compatible way. The JNI or Java Native Interface is an example of such a binding mechanism; libraries that are accessed in this way are linked dynamically with the Java programs that call them. These libraries are also linked with the interpreter. If the interpreter is linked statically with these libraries, or if it is designed to <a href="#GPLPluginsInNF"> link dynamically with these specific libraries</a>, then it too needs to be released in a GPL-compatible way. 
그러나 인터프리터가 라이브러리와 같은 요소와 바인딩되도록 확장되어 있을 경우에는, 인터프리트된 결과로 만들어진 프로그램이 바인딩을 통해서 라이브러리와 링크될 것입니다. 만약 라이브러리가 GPL로 공표된 것이었다면, 인터프리트 되어 만들어진 프로그램은 GPL과 호환되는 형태로 공표되어야 합니다. 이러한 예로 JNI와 자바 네이티브 인터페이스를 들 수 있습니다. 이러한 방법으로 접근되는 라이브러리들은 이들을 호출하는 자바 프로그램과 다이나믹하게 링크됩니다. 
258  
That doesn't mean it is a good idea to write the program so that it only runs on Windows. Doing so results in a program that is free software but <a href="/philosophy/java-trap.html">&ldquo;trapped&rdquo;</a> (in this case, trapped by Windows instead of by Java, but the effect is the same). (Historical note: As of December 2006 Sun is in the middle of <a href="http://www.fsf.org/news/fsf-welcomes-gpl-java.html">rereleasing its Java platform under GNU GPL</a>.) 
 
264  
<b><a href="#TOCGPLPlugins" id="GPLPlugins"> When are a program and its plug-ins considered a single combined program? </a></b> 
 
269  
Please see this question <a href="#GPLPlugins">for determining when plug-ins and a main program are considered a single combined program and when they are considered separate works</a>. 
 
272  
Please see this question <a href="#GPLPlugins">for determining when plug-ins and a main program are considered a single combined program and when they are considered separate programs</a>. 
 
274 | [-For more details, see-]{+See also+} the question [-above that starts
| with, &ldquo;I-] {+<a href="#FSWithNFLibs">I+} am writing free software
| that uses a nonfree [-library.&rdquo;-] {+library.</a>+} 
See also the question <a href="#FSWithNFLibs">I am writing free software that uses a nonfree library.</a> 
보다 구체적인 사항에 대해서는 &ldquo;자유 소프트웨어가 아닌 라이브러리를 사용하는 자유 소프트웨어의 개발&rdquo;과 관련된 <a href="#WritingFSWithNFLibs">질문 부분을 참고</a>하시기 바랍니다. 
275 | <b><a [-href="#TOCGPLPluginsInNF" id="GPLPluginsInNF">Can-]
| {+href="#TOCNFUseGPLPlugins" id="NFUseGPLPlugins">Can+} I [-use the
| GPL for a plug-in for-] {+release+} a nonfree [-program?</a></b>-]
| {+program that's designed to load a GPL-covered plug-in?</a></b>+} 
<b><a href="#TOCNFUseGPLPlugins" id="NFUseGPLPlugins">Can I release a nonfree program that's designed to load a GPL-covered plug-in?</a></b> 
<b><a href="#TOCGPLPluginsInNF" id="GPLPluginsInNF">자유 소프트웨어가 아닌 프로그램을 대상으로 하는 플러그인을 GPL로 만드는 것이 가능합니까?</a></b> 
283  
<b><a href="#TOCLinkingOverControlledInterface" id="LinkingOverControlledInterface">How can I allow linking of proprietary modules with my GPL-covered library under a controlled interface only?</a></b> 
 
301  
<b><a href="#TOCModifyGPL" id="ModifyGPL">Can I modify the GPL and make a modified license?</a></b> 
 
303  
If you want to use our preamble in a modified license, please write to <a href="mailto:licensing@gnu.org">&lt;licensing@gnu.org&gt;</a> for permission. For this purpose we would want to check the actual license requirements to see if we approve of them. 
 
304  
Although we will not raise legal objections to your making a modified license in this way, we hope you will think twice and not do it. Such a modified license is almost certainly <a href="#WhatIsCompatible"> incompatible with the GNU GPL</a>, and that incompatibility blocks useful combinations of modules. The mere proliferation of different free software licenses is a burden in and of itself. 
 
311  
<b><a href="#TOCLGPLJava" id="LGPLJava">How does the LGPL work with Java?</a></b> 
 
312  
<a href="/licenses/lgpl-java.html">See this article for details.</a> It works as designed, intended, and expected. 
 
322  
<b><a href="#TOCGPLWrapper" id="GPLWrapper"> I'd like to incorporate GPL-covered software in my proprietary system. Can I do this by putting a &ldquo;wrapper&rdquo; module, under a GPL-compatible lax permissive license (such as the X11 license) in between the GPL-covered part and the proprietary part?</a></b> 
 
325  
<b><a href="#TOCLibGCCException" id="LibGCCException"> Does the libstdc++ exception permit dynamic linking?</a></b> 
 
332  
<b><a href="#TOCGPLIncompatibleAlone" id="GPLIncompatibleAlone">If license for a module Q has a requirement that's incompatible with the GPL, but the requirement applies only when Q is distributed by itself, not when Q is included in a larger program, does that make the license GPL-compatible? Can I combine or link Q with a GPL-covered program?</a></b> 
 
336  
<b><a href="#TOCModifiedJustBinary" id="ModifiedJustBinary">Can I release a modified version of a GPL-covered program in binary form only?</a></b> 
 
337 | [-No, you must supply-]{+No. The whole point of+} the [-source code-]
| {+GPL is that all modified versions must be <a
| href="/philosophy/free-sw.html"> free software</a>&mdash;which means, in
| particular,+} that [-corresponds to-] the [-binary. Corresponding-]
| source [-means-] {+code of+} the [-source from which users can rebuild-]
| {+modified version is available to+} the [-same binary.-] {+users.+} 
No. The whole point of the GPL is that all modified versions must be <a href="/philosophy/free-sw.html"> free software</a>&mdash;which means, in particular, that the source code of the modified version is available to the users. 
안됩니다. 바이너리와 동일한 버전에 대한 소스 코드를 제공해야 합니다. 동일한 버전이란, 사용자들이 빌드했을 때 배포된 바이너리와 동일한 바이너리를 생성할 수 있는 코드를 의미합니다. 
338  
<b><a href="#TOCUnchangedJustBinary" id="UnchangedJustBinary">I downloaded just the binary from the net. If I distribute copies, do I have to get the source and distribute that too?</a></b> 
 
345  
If you distribute binaries via FTP, <a href="#AnonFTPAndSendSources">you should distribute source via FTP.</a> 
 
346  
<b><a href="#TOCRedistributedBinariesGetSource" id="RedistributedBinariesGetSource">My friend got a GPL-covered binary with an offer to supply source, and made a copy for me. Can I use the offer myself to obtain the source?</a></b> 
 
366  
<b><a href="#TOCUnreleasedMods" id="UnreleasedMods">A company is running a modified version of a GPL'ed program on a web site. Does the GPL say they must release their modified sources?</a></b> 
 
369  
In the mean time, you might want to use the <a href="http://www.affero.org/oagpl.html">Affero GPL</a> for programs designed for network server use. 
 
370  
<b><a href="#TOCInternalDistribution" id="InternalDistribution">Is making and using multiple copies within one organization or company &ldquo;distribution&rdquo;?</a></b> 
 
373  
<b><a href="#TOCStolenCopy" id="StolenCopy"> If someone steals a CD containing a version of a GPL-covered program, does the GPL give him the right to redistribute that version?</a></b> 
 
376  
<b><a href="#TOCTradeSecretRelease" id="TradeSecretRelease">What if a company distributes a copy of some other developers' GPL-covered work to me as a trade secret?</a></b> 
 
378  
<b><a href="#TOCTradeSecretRelease2" id="TradeSecretRelease2">What if a company distributes a copy of its own GPL-covered work to me as a trade secret?</a></b> 
 
379  
If the program distributed does not incorporate anyone else's GPL-covered work, then the company is not violating the GPL (see &ldquo;<a href="#DeveloperViolate">Is the developer of a GPL-covered program bound by the GPL?</a>&rdquo; for more information). But it is making two contradictory statements about what you can do with that program: that you can redistribute it, and that you can't. It would make sense to demand clarification of the terms for use of that program before you accept a copy. 
 
384  
So we decide which license to use for each library on a case-by-case basis. There is a <a href="/licenses/why-not-lgpl.html"> long explanation</a> of how we judge the question. 
라이브러리 별로 어떤 라이선스를 사용했는 지에 대한 우리의 결정에 대해서는 보다 자세한 문서를 통해서 참고할 수 있습니다. 
402  
<b><a href="#TOCFontException" id="FontException">How does the GPL apply to fonts?</a></b> 
 
403  
Font licensing is a complex issue which needs serious consideration. The following license exception is experimental but approved for general use. We welcome suggestions on this subject&mdash;please see this <a href="http://www.fsf.org/blogs/licensing/20050425novalis">explanatory essay</a> and write to <a href="mailto:licensing@gnu.org">&lt;licensing@gnu.org&gt;</a>. 
 
406  
<b><a href="#TOCWMS" id="WMS"> I am writing a website maintenance system</a> (called a &ldquo;<a href="/philosophy/words-to-avoid.html">content management system</a>&rdquo; by some), or some other application which generates web pages from templates. What license should I use for those templates?</b> 
 
414  
<b><a href="#TOCNonFreeTools" id="NonFreeTools">Can I release a program under the GPL which I developed using nonfree tools?</a></b> 
 
440 | Since the GPL is a copyright license, the copyright holders of the
| software are the ones who have the power to enforce the GPL. If you see a
| violation of the GPL, you should inform the developers of the GPL-covered
| software involved. They either are the copyright holders, or are
| connected with the copyright holders. {+<a
| href="#ReportingViolation">Learn more about reporting GPL
| violations.</a>+} 
Since the GPL is a copyright license, the copyright holders of the software are the ones who have the power to enforce the GPL. If you see a violation of the GPL, you should inform the developers of the GPL-covered software involved. They either are the copyright holders, or are connected with the copyright holders. <a href="#ReportingViolation">Learn more about reporting GPL violations.</a> 
GPL은 저작권에 관련된 라이선스이기 때문에 소프트웨어의 저작권자가 GPL을 법률적으로 강제할 수 있는 사람 중 하나입니다. 만약 여러분이 GPL 위반을 목격하게 되면 해당 소프트웨어의 개발자들에게 그 사실을 알려주시기 바랍니다. 그들은 저작권자 자신이거나 저작권자와 연락할 수 있는 사람들입니다. 
451  
<b><a href="#TOCReleaseNotOriginal" id="ReleaseNotOriginal"> Can I release a program with a license which says that you can distribute modified versions of it under the GPL but you can't distribute the original itself under the GPL?</a></b> 
 
455  
<b><a href="#TOCDistributeSubsidiary" id="DistributeSubsidiary"> Does moving a copy to a majority-owned, and controlled, subsidiary constitute distribution?</a></b> 
 
458  
<b><a href="#TOCClickThrough" id="ClickThrough"> Can software installers ask people to click to agree to the GPL? If I get some software under the GPL, do I have to agree to anything?</a></b> 
 
461  
<b><a href="#TOCGPLCompatInstaller" id="GPLCompatInstaller">I would like to bundle GPLed software with some sort of installation software. Does that installer need to have a GPL-compatible license?</a></b>