Nelze vybrat více než 25 témat Téma musí začínat písmenem nebo číslem, může obsahovat pomlčky („-“) a může být dlouhé až 35 znaků.

170 lines
8.6KB

  1. <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
  2. <html>
  3. <!-- Copyright (C) 1988-2020 Free Software Foundation, Inc.
  4. Permission is granted to copy, distribute and/or modify this document
  5. under the terms of the GNU Free Documentation License, Version 1.3 or
  6. any later version published by the Free Software Foundation; with the
  7. Invariant Sections being "Free Software" and "Free Software Needs
  8. Free Documentation", with the Front-Cover Texts being "A GNU Manual,"
  9. and with the Back-Cover Texts as in (a) below.
  10. (a) The FSF's Back-Cover Text is: "You are free to copy and modify
  11. this GNU Manual. Buying copies from GNU Press supports the FSF in
  12. developing GNU and promoting software freedom." -->
  13. <!-- Created by GNU Texinfo 6.5, http://www.gnu.org/software/texinfo/ -->
  14. <head>
  15. <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  16. <title>Free Documentation (Debugging with GDB)</title>
  17. <meta name="description" content="Free Documentation (Debugging with GDB)">
  18. <meta name="keywords" content="Free Documentation (Debugging with GDB)">
  19. <meta name="resource-type" content="document">
  20. <meta name="distribution" content="global">
  21. <meta name="Generator" content="makeinfo">
  22. <link href="index.html#Top" rel="start" title="Top">
  23. <link href="Concept-Index.html#Concept-Index" rel="index" title="Concept Index">
  24. <link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
  25. <link href="Summary.html#Summary" rel="up" title="Summary">
  26. <link href="Contributors.html#Contributors" rel="next" title="Contributors">
  27. <link href="Free-Software.html#Free-Software" rel="prev" title="Free Software">
  28. <style type="text/css">
  29. <!--
  30. a.summary-letter {text-decoration: none}
  31. blockquote.indentedblock {margin-right: 0em}
  32. blockquote.smallindentedblock {margin-right: 0em; font-size: smaller}
  33. blockquote.smallquotation {font-size: smaller}
  34. div.display {margin-left: 3.2em}
  35. div.example {margin-left: 3.2em}
  36. div.lisp {margin-left: 3.2em}
  37. div.smalldisplay {margin-left: 3.2em}
  38. div.smallexample {margin-left: 3.2em}
  39. div.smalllisp {margin-left: 3.2em}
  40. kbd {font-style: oblique}
  41. pre.display {font-family: inherit}
  42. pre.format {font-family: inherit}
  43. pre.menu-comment {font-family: serif}
  44. pre.menu-preformatted {font-family: serif}
  45. pre.smalldisplay {font-family: inherit; font-size: smaller}
  46. pre.smallexample {font-size: smaller}
  47. pre.smallformat {font-family: inherit; font-size: smaller}
  48. pre.smalllisp {font-size: smaller}
  49. span.nolinebreak {white-space: nowrap}
  50. span.roman {font-family: initial; font-weight: normal}
  51. span.sansserif {font-family: sans-serif; font-weight: normal}
  52. ul.no-bullet {list-style: none}
  53. -->
  54. </style>
  55. </head>
  56. <body lang="en">
  57. <a name="Free-Documentation"></a>
  58. <div class="header">
  59. <p>
  60. Next: <a href="Contributors.html#Contributors" accesskey="n" rel="next">Contributors</a>, Previous: <a href="Free-Software.html#Free-Software" accesskey="p" rel="prev">Free Software</a>, Up: <a href="Summary.html#Summary" accesskey="u" rel="up">Summary</a> &nbsp; [<a href="index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="Concept-Index.html#Concept-Index" title="Index" rel="index">Index</a>]</p>
  61. </div>
  62. <hr>
  63. <a name="Free-Software-Needs-Free-Documentation"></a>
  64. <h3 class="unnumberedsec">Free Software Needs Free Documentation</h3>
  65. <p>The biggest deficiency in the free software community today is not in
  66. the software&mdash;it is the lack of good free documentation that we can
  67. include with the free software. Many of our most important
  68. programs do not come with free reference manuals and free introductory
  69. texts. Documentation is an essential part of any software package;
  70. when an important free software package does not come with a free
  71. manual and a free tutorial, that is a major gap. We have many such
  72. gaps today.
  73. </p>
  74. <p>Consider Perl, for instance. The tutorial manuals that people
  75. normally use are non-free. How did this come about? Because the
  76. authors of those manuals published them with restrictive terms&mdash;no
  77. copying, no modification, source files not available&mdash;which exclude
  78. them from the free software world.
  79. </p>
  80. <p>That wasn&rsquo;t the first time this sort of thing happened, and it was far
  81. from the last. Many times we have heard a GNU user eagerly describe a
  82. manual that he is writing, his intended contribution to the community,
  83. only to learn that he had ruined everything by signing a publication
  84. contract to make it non-free.
  85. </p>
  86. <p>Free documentation, like free software, is a matter of freedom, not
  87. price. The problem with the non-free manual is not that publishers
  88. charge a price for printed copies&mdash;that in itself is fine. (The Free
  89. Software Foundation sells printed copies of manuals, too.) The
  90. problem is the restrictions on the use of the manual. Free manuals
  91. are available in source code form, and give you permission to copy and
  92. modify. Non-free manuals do not allow this.
  93. </p>
  94. <p>The criteria of freedom for a free manual are roughly the same as for
  95. free software. Redistribution (including the normal kinds of
  96. commercial redistribution) must be permitted, so that the manual can
  97. accompany every copy of the program, both on-line and on paper.
  98. </p>
  99. <p>Permission for modification of the technical content is crucial too.
  100. When people modify the software, adding or changing features, if they
  101. are conscientious they will change the manual too&mdash;so they can
  102. provide accurate and clear documentation for the modified program. A
  103. manual that leaves you no choice but to write a new manual to document
  104. a changed version of the program is not really available to our
  105. community.
  106. </p>
  107. <p>Some kinds of limits on the way modification is handled are
  108. acceptable. For example, requirements to preserve the original
  109. author&rsquo;s copyright notice, the distribution terms, or the list of
  110. authors, are ok. It is also no problem to require modified versions
  111. to include notice that they were modified. Even entire sections that
  112. may not be deleted or changed are acceptable, as long as they deal
  113. with nontechnical topics (like this one). These kinds of restrictions
  114. are acceptable because they don&rsquo;t obstruct the community&rsquo;s normal use
  115. of the manual.
  116. </p>
  117. <p>However, it must be possible to modify all the <em>technical</em>
  118. content of the manual, and then distribute the result in all the usual
  119. media, through all the usual channels. Otherwise, the restrictions
  120. obstruct the use of the manual, it is not free, and we need another
  121. manual to replace it.
  122. </p>
  123. <p>Please spread the word about this issue. Our community continues to
  124. lose manuals to proprietary publishing. If we spread the word that
  125. free software needs free reference manuals and free tutorials, perhaps
  126. the next person who wants to contribute by writing documentation will
  127. realize, before it is too late, that only free manuals contribute to
  128. the free software community.
  129. </p>
  130. <p>If you are writing documentation, please insist on publishing it under
  131. the GNU Free Documentation License or another free documentation
  132. license. Remember that this decision requires your approval&mdash;you
  133. don&rsquo;t have to let the publisher decide. Some commercial publishers
  134. will use a free license if you insist, but they will not propose the
  135. option; it is up to you to raise the issue and say firmly that this is
  136. what you want. If the publisher you are dealing with refuses, please
  137. try other publishers. If you&rsquo;re not sure whether a proposed license
  138. is free, write to <a href="mailto:licensing@gnu.org">licensing@gnu.org</a>.
  139. </p>
  140. <p>You can encourage commercial publishers to sell more free, copylefted
  141. manuals and tutorials by buying them, and particularly by buying
  142. copies from the publishers that paid for their writing or for major
  143. improvements. Meanwhile, try to avoid buying non-free documentation
  144. at all. Check the distribution terms of a manual before you buy it,
  145. and insist that whoever seeks your business must respect your freedom.
  146. Check the history of the book, and try to reward the publishers that
  147. have paid or pay the authors to work on it.
  148. </p>
  149. <p>The Free Software Foundation maintains a list of free documentation
  150. published by other publishers, at
  151. <a href="http://www.fsf.org/doc/other-free-books.html">http://www.fsf.org/doc/other-free-books.html</a>.
  152. </p>
  153. <hr>
  154. <div class="header">
  155. <p>
  156. Next: <a href="Contributors.html#Contributors" accesskey="n" rel="next">Contributors</a>, Previous: <a href="Free-Software.html#Free-Software" accesskey="p" rel="prev">Free Software</a>, Up: <a href="Summary.html#Summary" accesskey="u" rel="up">Summary</a> &nbsp; [<a href="index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="Concept-Index.html#Concept-Index" title="Index" rel="index">Index</a>]</p>
  157. </div>
  158. </body>
  159. </html>