gif.html (12666B)
1 <!--#include virtual="/server/header.html" --> 2 <!-- Parent-Version: 1.96 --> 3 <!-- This page is derived from /server/standards/boilerplate.html --> 4 <!--#set var="TAGS" value="essays laws patents" --> 5 <!--#set var="DISABLE_TOP_ADDENDUM" value="yes" --> 6 <title>Why There Are No GIF Files on GNU Web Pages 7 - GNU Project - Free Software Foundation</title> 8 <style type="text/css" media="print,screen"><!-- 9 a.ftn { font-size: .94em; } 10 --></style> 11 <!--#include virtual="/philosophy/po/gif.translist" --> 12 <!--#include virtual="/server/banner.html" --> 13 <!--#include virtual="/philosophy/ph-breadcrumb.html" --> 14 <!--GNUN: OUT-OF-DATE NOTICE--> 15 <!--#include virtual="/server/top-addendum.html" --> 16 <div class="article reduced-width"> 17 <h2>Why There Are No GIF Files on GNU Web Pages</h2> 18 <div class="thin"></div> 19 20 <div class="introduction"> 21 <p><em>There is no special patent threat to GIF format nowadays 22 as far as we know; <a href="#venuenote">the patents that were used to 23 attack GIF have expired</a>. Nonetheless, this article will remain 24 pertinent as long as programs can be forbidden by patents, since the 25 same sorts of things could happen in any area of computing. See 26 <a href="/server/standards/gnu-website-guidelines.html#UseofGraphics">our 27 website policies regarding GIFs</a>.</em></p> 28 </div> 29 <hr class="no-display" /> 30 31 <p> 32 There are no GIFs on the GNU web site because of the 33 patents (Unisys and IBM) covering 34 the LZW compression algorithm 35 which is used in making GIF files. These patents make it 36 impossible to have free software to generate proper GIFs. 37 They also apply to the <strong>compress</strong> program, which is why 38 GNU does not use it or its format. 39 </p> 40 41 <p> 42 Unisys and IBM both applied for patents in 1983. Unisys (and perhaps 43 IBM) applied for these patents in a number of countries. Of the 44 places whose patent databases we were able to search, the latest 45 expiration date seems to be 1 October 2006 <a class="ftn" 46 href="#venuenote">[1]</a>. Until then, 47 anyone who releases a free program for making GIF files 48 is likely to be sued. We don't know any reason to think that the 49 patent owners would lose these lawsuits. 50 </p> 51 52 <p> 53 If we released such a program, Unisys and IBM might think it wiser 54 (for public relations reasons) not to sue a charity like the FSF. 55 They could instead sue the users of the program, including the 56 companies who redistribute GNU software. We feel it would not be 57 responsible behavior for us to set up this situation. 58 </p> 59 60 <p> 61 Many people think that Unisys has given permission for distributing 62 free software to make GIF format. Unfortunately that is 63 not what Unisys has actually done. Here is what Unisys actually said 64 about the matter in 1995: 65 </p> 66 67 <blockquote><p>Unisys does not require licensing, or fees to be paid, for 68 non-commercial, non-profit GIF-based applications, 69 including those for use on the on-line services. Concerning 70 developers of software for the Internet network, the same principle 71 applies. Unisys will not pursue previous inadvertent infringement by 72 developers producing versions of software products for the Internet 73 prior to 1995. The company does not require licensing, or fees to be 74 paid for non-commercial, non-profit offerings on the Internet, 75 including “Freeware.”</p></blockquote> 76 77 <p> 78 Unfortunately, this doesn't permit 79 <a href="/philosophy/free-sw.html">free software</a> which can be used 80 in a free operating system such as GNU. It also does not 81 permit <em>at all</em> the use of LZW for other purposes 82 such as compression of files. This is why we think it is still best 83 to reject LZW, and switch to alternatives such 84 as <a href="/software/gzip/gzip.html">GNU Gzip</a> 85 and PNG. 86 </p> 87 88 <p> 89 <a href="/philosophy/selling.html">Commercial redistribution of free 90 software</a> is very important, and we want the GNU system as a whole 91 to be redistributed commercially. This means we can't add 92 a GIF-generating program to GNU, not under the Unisys 93 terms. 94 </p> 95 96 <p> 97 The <a href="https://www.fsf.org">Free Software Foundation</a> is a 98 non-commercial, non-profit organization, so strictly speaking the 99 income from our sales of <a href="https://shop.fsf.org/">CD-ROMs</a> 100 is not “profit.” Perhaps this means we could include 101 a GIF program on our CD-ROM and claim to be acting within 102 the scope of the Unisys permission—or perhaps not. But since we 103 know that other redistributors of GNU would be unable to include it, 104 doing this would not be very useful. 105 </p> 106 107 <p> 108 Shortly after Unisys made its announcement, when the net in general 109 was reassured thinking that Unisys had given permission for 110 free GIF-generating software, we wrote to the Unisys 111 legal department asking for clarification of these issues. We did not 112 receive a response. 113 </p> 114 115 <p> 116 Even if Unisys really did give permission for free software to 117 generate GIFs, we would still have to deal with the IBM 118 patent. Both the IBM and the Unisys patents cover the same 119 “invention”—the LZW compression 120 algorithm. (This could reflect an error on the part of the US Patent 121 and Trademark Office, which is famous for incompetence and poor 122 judgment.) 123 </p> 124 125 <p> 126 Decoding GIFs is a different issue. The Unisys and IBM 127 patents are both written in such a way that they do not apply to a 128 program which can only uncompress LZW format and cannot 129 compress. Therefore we can and will include support for 130 displaying GIF files in GNU software. 131 </p> 132 133 <p> 134 Given this situation, we could still include GIF files in 135 our web pages if we wanted to. Many other people would be happy to 136 generate them for us, and we would not be sued for 137 having GIF files on our server. 138 </p> 139 140 <p> 141 But we feel that if we can't distribute the software to enable people 142 to generate GIF files properly, then we should not have 143 other people run such software for us. Besides, if we can't provide 144 software in GNU to generate GIF files, we have to 145 recommend an alternative. We ourselves should use the alternative 146 that we recommend. 147 </p> 148 149 <p> 150 In 1999, Unisys had the following to say about the issue of their 151 patent: 152 </p> 153 154 <blockquote><p>Unisys has frequently been asked whether a Unisys 155 license is required in order to use LZW software obtained 156 by downloading from the Internet or from other sources. The answer is 157 simple. In all cases, a written license agreement or statement signed 158 by an authorized Unisys representative is required from Unisys for all 159 use, sale or distribution of any software (including so-called 160 “freeware”) and/or hardware providing LZW 161 conversion capability (for example, downloaded 162 software).</p></blockquote> 163 164 <p> 165 With this statement, Unisys is trying to take back what they said in 166 1995 when they gave parts of the patent to the public. The legality of 167 such a move is questionable. 168 </p> 169 170 <p> 171 A further issue is that the LZW patents—and computational idea 172 patents in general—are an offense against the freedom of 173 programmers generally, and all programmers need to work together 174 to <a href="/philosophy/limit-patent-effect.html">protect 175 software from patents.</a> 176 </p> 177 178 <p> 179 So even if we could find a solution to enable the free software 180 community to generate GIFs, that isn't really a solution, 181 not for the problem as a whole. The solution is switching to another 182 format and not using GIF any more. 183 </p> 184 185 <p> 186 Therefore, we don't use GIF, and we hope you won't use it 187 either. 188 </p> 189 190 <p> 191 It is possible to make non-compressed images that act 192 like GIFs, in that they work with programs that 193 decode GIF format. This can be done without infringing 194 patents. These pseudo-GIFs are useful for some purposes. 195 </p> 196 197 <p> 198 It is also possible to create GIFs using a patent-free 199 run length encoding but this doesn't achieve the compression that one 200 normally expects in a GIF. 201 </p> 202 203 <p> 204 We decided not to use these pseudo-GIFs on our web site 205 because they are not a satisfactory solution to the community's 206 problem. They work, but they are very large. What the web needs is a 207 patent-free compressed format, not large pseudo-GIFs. 208 </p> 209 210 <p> 211 The <a href="https://en.wikipedia.org/wiki/Portable_Network_Graphics">PNG 212 format</a> is a patent-free compressed format. We hope it will become 213 widely supported; then we will use it. We do provide PNG versions of 214 most of the <a href="/graphics/graphics.html">images on this server</a>. 215 </p> 216 217 <p> 218 For more information about the GIF patent problems, 219 see <a href="https://web.archive.org/web/20150329143651/http://progfree.org/Patents/patents.html">the League for 220 Programming Freedom GIF page</a>. Through that page you 221 can find more information about the <a 222 href="https://endsoftwarepatents.org/">problem of software patents in 223 general.</a> 224 </p> 225 226 <p> 227 There is a library called libungif that reads gif files and writes 228 uncompressed gifs to circumvent the Unisys patent. 229 </p> 230 231 <p> 232 <a href="https://web.archive.org/web/20171203193534/http://burnallgifs.org/"> 233 burnallgifs.org</a> is a 234 web site devoted to discouraging the use of GIF files on 235 the web. 236 </p> 237 <div class="column-limit"></div> 238 239 <h3 class="footnote">Footnote</h3> 240 <ol> 241 <li id="venuenote"> 242 <p>We were able to search 243 the patent databases of the USA, Canada, Japan, and the European 244 Union. The Unisys patent expired on 20 June 2003 in the USA, in Europe 245 it expired on 18 June 2004, in Japan the patent expired on 20 June 246 2004 and in Canada it expired on 7 July 2004. The U.S. IBM patent 247 expired 11 August 2006. The Software Freedom Law Center says that 248 after 1 October 2006, there will be no significant patent claims 249 interfering with the use of static GIFs.</p> 250 251 <p>Animated GIFs are a different story. We do not know what patents 252 might cover them. However, we have not heard reports of threats 253 against use of animated GIFs. Any software can be threatened by 254 patents, but we have no reason to consider animated GIFs to be in 255 particular danger—no particular reason to shun them.</p> 256 </li> 257 </ol> 258 </div> 259 260 </div><!-- for id="content", starts in the include above --> 261 <!--#include virtual="/server/footer.html" --> 262 <div id="footer" role="contentinfo"> 263 <div class="unprintable"> 264 265 <p>Please send general FSF & GNU inquiries to <a 266 href="mailto:gnu@gnu.org"><gnu@gnu.org></a>. There are also <a 267 href="/contact/">other ways to contact</a> the FSF. Broken links and other 268 corrections or suggestions can be sent to <a 269 href="mailto:webmasters@gnu.org"><webmasters@gnu.org></a>.</p> 270 271 <p><!-- TRANSLATORS: Ignore the original text in this paragraph, 272 replace it with the translation of these two: 273 274 We work hard and do our best to provide accurate, good quality 275 translations. However, we are not exempt from imperfection. 276 Please send your comments and general suggestions in this regard 277 to <a href="mailto:web-translators@gnu.org"> 278 <web-translators@gnu.org></a>.</p> 279 280 <p>For information on coordinating and contributing translations of 281 our web pages, see <a 282 href="/server/standards/README.translations.html">Translations 283 README</a>. --> 284 Please see the <a 285 href="/server/standards/README.translations.html">Translations README</a> for 286 information on coordinating and contributing translations of this article.</p> 287 </div> 288 289 <!-- Regarding copyright, in general, standalone pages (as opposed to 290 files generated as part of manuals) on the GNU web server should 291 be under CC BY-ND 4.0. Please do NOT change or remove this 292 without talking with the webmasters or licensing team first. 293 Please make sure the copyright date is consistent with the 294 document. For web pages, it is ok to list just the latest year the 295 document was modified, or published. 296 297 If you wish to list earlier years, that is ok too. 298 Either "2001, 2002, 2003" or "2001-2003" are ok for specifying 299 years, as long as each year in the range is in fact a copyrightable 300 year, i.e., a year in which the document was published (including 301 being publicly visible on the web or in a revision control system). 302 303 There is more detail about copyright years in the GNU Maintainers 304 Information document, www.gnu.org/prep/maintain. --> 305 306 <p>Copyright © 1997-1999, 2003, 2004, 2006, 2010, 2013, 2021 Free 307 Software Foundation, Inc.</p> 308 309 <p>This page is licensed under a <a rel="license" 310 href="http://creativecommons.org/licenses/by-nd/4.0/">Creative 311 Commons Attribution-NoDerivatives 4.0 International License</a>.</p> 312 313 <!--#include virtual="/server/bottom-notes.html" --> 314 315 <p class="unprintable">Updated: 316 <!-- timestamp start --> 317 $Date: 2021/11/03 13:26:25 $ 318 <!-- timestamp end --> 319 </p> 320 </div> 321 </div><!-- for class="inner", starts in the banner include --> 322 </body> 323 </html>