Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

Create Account  |  Retrieve Password

GIF Slips Away From Unisys; Your Move, IBM

Posted by jamie on Wed Jul 07, 2004 08:00 AM
from the do-the-right-thing dept.
Twenty years ago, Terry Welch's improvement on Lempel-Ziv compression appeared in IEEE Computer magazine. The authors of unix 'compress' and the GIF standard incorporated that algorithm without realizing it was patent-pending. When the submarine patent surfaced ten years later, its new owner Unisys intimidated developers and web authors into moving away from GIFs, inspiring the creation of a better standard, though sadly still a less popular one. Today, July 7, 2004, Unisys's last LZW patent (in Canada) expires, leaving GIF once again free... almost. See, there's the small matter of IBM's patent, granted on the same algorithm, which is valid for another two years. That still has a chilling effect on GIF development, though the consensus seems to be that IBM would lose any court action it tried to bring. So how about it, IBM? You've got nothing to lose! Want to make a lot of geeks happy and release that final patent into the public domain?
+ -
unknown

Related Stories

[+] The GIF Format is Finally Patent-Free 369 comments
tonymercmobily writes "Not many people noticed that the GIF file format is only now free from patents, as of the 1st of October 2006. Quick recap: first in 1999 Unisys tried to extort money from users and developers. Then, in 2003 the world hoped that the saga would finally be over. Then, in 2004, it was IBM's turn. Now, the SAGA seems to be over for real! Does anybody find Unisys' page on GIF as hilarious as I do...?"
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More
Loading... please wait.
  • GO IBM! (Score:5, Insightful)

    by berny@work (57298) * <bstapleton@NOSpam.gmail.com> on Wednesday July 07 2004, @08:02AM (#9630886) Journal
    Do it for the common good. Aside from business, really what open source is for!
    • by r00t (33219) on Wednesday July 07 2004, @09:59AM (#9632067) Journal
      UnixWare's compress program (for *.Z files) is
      infringing on this patent.
      • Indeed they do. (Score:5, Insightful)

        by Xenographic (557057) on Wednesday July 07 2004, @11:12AM (#9632826) Homepage Journal
        He's right; it's one of IBM's counterclaims against SCO. Of course, if any part of SCO's motion to bifurcate (split off the patent suits), IBM could elect to drop it and later dispose of the patent somehow. You can read a transcript of the relevant hearing here on Groklaw [groklaw.net].

        SCO's answer to IBM's counterclaims accuses it, among other things, of selectively enforcing it. I'm not quite sure what basis there is in law for using that as a defense, however, or if that was just boilerplate text in SCO's reply.
  • by Timesprout (579035) on Wednesday July 07 2004, @08:02AM (#9630887)
    and png truly is a better standard why should geeks care what happens to gif?
    • by I confirm I'm not a (720413) on Wednesday July 07 2004, @08:05AM (#9630915) Journal

      Well, one reason is that, once-upon-a-time, we had to build apps for browsers that didn't support .png, so even though we could handle .pngs, we had to consider our clients who were stuck with .gifs. Thankfully, even the lowliest [microsoft.com] of browser almost supports .png these days.

      • not even close! (Score:5, Informative)

        by Ender Ryan (79406) <MENCKEN minus author> on Wednesday July 07 2004, @08:16AM (#9631037) Journal
        IE does not support the #1 most useful aspect of PNG, namely, alpha transparency. Without alpha transparency, you may as well use JPEG or GIF in most circumstances.

        Indeed, the web would be much more beautiful if IE supported alpha transparency in PNGs.

        • Its become received wisdom the IE6 sux for (among other reasons) "not supporting PNG".

          Wrong.

          That's a techie urban-legend. The truth is that IE6 does support all required PNG features. Therefore it "supports PNG".

          Yes, IE6 doesn't support PNG transparency, at least not in any easy way. However PNG transparency is an optional part of the PNG spec. That IE6 doesn't support transparency properly is unfortunate but doesn't invalidate their meeting the required PNG spec.

          Furthermore as others have pointed out there are indeed work-arounds (ugly ones) that will enable reliable PNG transparency on IE6. Also as others have pointed out (including MS staffers) even if IE7 were to ship tomorrow and support PNG et al we'd still be stuck with a huge IE6-using population for years to come.

          It would be great if IE, and indeed all of the browsers, were to fully meet all relevant standards. It would also be great if they were to then go on and meet more of the optional parts of those standards, including PNG transparency. However lets hold everyone's feet to the fire on these, not pick on one author's neglecting a feature many would like while they and others are still missing more fundamental required parts of specs.

          • Re:in any case (Score:5, Insightful)

            by Ender Ryan (79406) <MENCKEN minus author> on Wednesday July 07 2004, @08:46AM (#9631302) Journal
            It supports PNG enough as to substitute GIF in any case.

            Your comment makes no sense in this context.

            IE doesn't support alpha transparency in PNGs, and that's substandard on their part, but I don't think the web would change much if it did unless everybody started bloating their sites with transparent effects where it is not needed.

            You couldn't be more wrong. If people could use PNG the way it's supposed to be used, we could have rounded corner graphics that don't suck, change background colors without having to modify all images to match, have different background colors on different pages without the need for extra graphics for each different color background, allow user-selectable page colors, et cetera. It would actually save a lot of bandwidth.

            As it is, there is very little benefit to using PNG in most cases, so people don't switch.

            And PNGs with alpha-transparency are not "bloated" by any means.

            • Re:in any case (Score:5, Informative)

              by photon317 (208409) on Wednesday July 07 2004, @09:07AM (#9631492)
              Exactly. I'm not a full-time web developer, so I don't even think on these issues too hard most of the time. Recently I had to write a little network-monitoring app. I coded the output in standards-compliant XHTML 1.1, standards-compliant CSS for styling stuff, and I used PNGs with transparent backgrounds for certain little icons. I only tested my app in Firefox (yeah, my mistake). Later someone who actually uses IE tried to use my little web app, and found gray background squares around all my supposedly transparent-backgrounded images. Sucked. Now I know what all you web developers already knew - I have to put a background color on these pngs which matches the background they're placed on that I specified in my stylesheet. How redundant and stupid.
            • Re:in any case (Score:5, Interesting)

              by Venner (59051) on Wednesday July 07 2004, @08:48AM (#9631321)
              I think the previous poster meant that IE lacks support for PNG-24's 8 bit alpha.
              See, PNG supports 256 levels of transparency. Gradients. Oh, the joy of no jagged edges.

              The problem is, yes, a 24 bit PNG with 8 bits of alpha can get rather large, especially when they are used for what they weren't intended for; replacing JPGs.

              Open up this link [mozilla.org] in anything but IE (I tested it with Mozilla and Opera) to see some 8-bit alpha. And a cool little demo to boot.
              • Re:not even close! (Score:5, Insightful)

                by I confirm I'm not a (720413) on Wednesday July 07 2004, @09:11AM (#9631537) Journal

                Some people don't have the option to live in an ideological world and must live in a realistic one.

                Elsewehere in this thread I've mentioned that I continue to use .gifs, because it's not realistic to ditch them. Regardless; I'd hardly descibe my position as "ideological" or "unrealistic" - it's one based on:

                1. Portable Network Graphics work with all major browsers - now (IE doesn't support one area of PNGs, but it doesn't lose any functionality over GIFs, as GIFs don't provide 8-bit alpha-blending anyway);

                2. GIFs may - as this article is about - still be patent-encumbered.

                In what way is promoting increased use of PNGs unrealistic?

                  • Re:not even close! (Score:5, Insightful)

                    by I confirm I'm not a (720413) on Wednesday July 07 2004, @09:55AM (#9632031) Journal

                    Switching to PNG because 5% or browsers will benefit is the unrealistic part.

                    Well, all browsers, including IE, can use PNGs. I presume you're refering to alpha-blending, which IE can't - currently - use? Use of non-IE browsers is steadily rising, as support for IE seems either non-existent or focused on "IE7" or whatever it'll be called. This suggusts - to me - two things:

                    1. Increasing numbers of people are using browsers - now - that do support alpha-blending;

                    2. The next iteration of IE is likely to support alpha-blending and is probably due soon (maybe soon like Longhorn, but soon, anyway...);

                    Either way, catering for the present-and-the-not-too-distant future doesn't seem that unrealistic.

                • by Throtex (708974) on Wednesday July 07 2004, @09:35AM (#9631773)
                  You do realize we were talking about a file format for displaying images, right? You sound like you're willing to lay your life down for the cause of alpha transparency!
      • by SiMac (409541) on Wednesday July 07 2004, @09:07AM (#9631497) Homepage
        PNG transparency works just fine in Internet Explorer. It's just a pain in the ass.

        This website [eae.net] will tell you how to turn it on. You can see it working on my website.

        No idea why it's not on by default, but if it works...
    • by Ghengis (73865) <SLowLaRIS.xNIX@Rules> on Wednesday July 07 2004, @08:06AM (#9630922) Homepage Journal
      Because GIF is used MUCH more, so people writing software that make use of images in general (browsers, image editors, etc.) have to deal with this patented algorithm, or risk losing users because their software doesn't support one of the most widely used formats.
          • by Jabes (238775) on Wednesday July 07 2004, @08:53AM (#9631356) Homepage
            GIF is pronounced JIF.

            Bob Berry, the developer of CompuShow for CompuServe (remember them - the people that invented the GIF format?) included with it an animated GIF89 format file that had a picture of him. It had a speach bubble with him saying:

            Oh, incidentally, it's pronounced "JIF"

            A quick google later and I've found a web site which has this, and other evidence that .GIF files are pronounced JIF

            http://www.olsenhome.com/gif/

            Thanks for playing
    • by Anonymous Coward on Wednesday July 07 2004, @08:06AM (#9630926)
      It's hard to do away with GIF because GIF's are animated. PNG's are not. There's the MNG standard, which is basically an animated PNG, but it isn't widely supported yet.
      • by DVega (211997) on Wednesday July 07 2004, @09:57AM (#9632056)
        Mozilla used to support MNGs, but that support was removed in orther to reduce "cruft".

        If you would like to get MNG back into Mozilla, then you can follow/vote/contribute to Bugzilla bug 18574

        http://bugzilla.mozilla.org/show_bug.cgi?id=1857 4

        (Please don't post useless comments on that bug)

    • by Davak (526912) on Wednesday July 07 2004, @08:08AM (#9630956) Homepage
      Quick source view of the main slashdot page shows that "gif" is found about 50 times.

      "png" is found twice -- both of which are related to the original post.

      Now you know why we care. The web community uses gif more than png. For better or worse...

      Davak
    • by DrEldarion (114072) on Wednesday July 07 2004, @08:09AM (#9630959) Homepage
      There are many "better" things that, for whatever reason, just aren't as popular compared to other "inferior" things.

      The PNG and GIF situation is like the OGG and MP3 situation. Sure, OGG may be better, but everyone already knows what MP3 is, has all their songs in MP3 format, has programs that know what do wo with MP3s, has players that know what MP3s are, etc. etc.
  • by NoMercy (105420) on Wednesday July 07 2004, @08:04AM (#9630907)
    I'm not sure on the merits of the GIF format after all these years, the only thing it brings to the web expierence is flashing adverts, PNG provides full alpha-transparency which is really required for the future of web design.
    • by AuraBorealis (772837) on Wednesday July 07 2004, @08:07AM (#9630934)
      Yes, because what we really need is alpha-transparent flashing adverts!
      • by ajs (35943) <ajs AT ajs DOT com> on Wednesday July 07 2004, @09:50AM (#9631953) Homepage Journal
        Alpha transparency is critical to good Web site design for many reasons. Among them:

        1. Blending with any background means you can change the background globally and not worry about re-blending all of the images.
        2. An image which is produced externally (e.g. by a partner) can blend with your layout cleanly without being customized.

        However, MOST uses of alpha blending in web design would ACTUALLY be better done in SVG if SVG in browsers could finally get first-class status.

        Why? Well, just for starters, LCDs and CRTs have different optimial anti-aliasing strategies. If I want to put a circle on a Web page, right now I have to choose one of those strategies ahead of time (or resort to a plug-in). If we allow SVG "images", then we can simply render that circle however the user directs it to be (presumably because they've selected a "CRT-friendly" or "LCD-friendly" preference in their browser or desktop).

        Once you eliminate anti-aliasing as a concern, there are still reasons to do alpha-blending in regular images (such as those above), but the general case (logos, text, shapes, etc) will be handled more cleanly.
        • by AnotherBlackHat (265897) on Wednesday July 07 2004, @10:44AM (#9632530) Homepage

          Alpha transparency is critical to good Web site design ...


          The quality of a web site is determined more by it's substance than by it's appearance.
          Good web site design doesn't even require images.

          Alpha blending is not critical.
          It's nice, but IMO it's ranks below "spell checker" in the hierarchy of good web site design tools.

          -- less is better.

    • by julesh (229690) on Wednesday July 07 2004, @08:14AM (#9631013)
      Compatibility. A huge number of existing web sites still use GIF as their primary image format. We need to be able to produce software that can manipulate these images if we want any hope of penetrating the web authoring market. This has prompted many workarounds in the past (such as libungif, a piece of software that produces GIF files without using the patented algorithm -- but unfortunately this means not having any compression) which will become obsolete once all patent issues have been cleared up.

      • by NoMercy (105420) on Wednesday July 07 2004, @08:16AM (#9631036)
        Everything which supports modern CSS styling supports PNG... it's just not everything supports all the features of PNG, the most noted case being IE doesn't support alpha-transparency.

        Many people also believe PNG's to generally produce larger images to GIF, if youre generating PNG's using the 'recomended settings' then yes for many images this is the case, but if your image doesn't need 16.7 milion colors and full alpha-transparency, don't enable them switch to pallete based with no-transparnecy.
        • by griblik (237163) on Wednesday July 07 2004, @09:01AM (#9631436) Homepage
          Actually, I think the reason most people think pngs produce larger filesize images is that most professional graphics bods use photoshop, which, despite being a fantastic bit of software, is shit at optimising pngs.

          The GIMP does a much better job of it.
  • Why should we care (Score:5, Insightful)

    by ultrabot (200914) on Wednesday July 07 2004, @08:06AM (#9630919)
    What would be the benefit of giving up the patent? We've already got .png, right?

    What would be more interesting is suing someone over it. This patent "cold war" is annoying - it would be more beneficial to see an all-out war where large companies crumble, and the idiocy of software patents is demonstrated once and for all. Cold war only server to suffocate, and masses never learn of the damage being done, because it's so invisible.

    Interesting article on how IP law conflicts with ancient chinese tradition is here [slashdot.org]
  • Not in the old days (Score:4, Interesting)

    by DrDebug (10230) on Wednesday July 07 2004, @08:07AM (#9630932) Journal
    In the 1980's I'm pretty sure that IBM would fight tooth and nail for any patent infringement. But those were the days when IBM was the 800 pound gorilla and what Microsoft wanted to be (and eventually became).

    Nowadays IBM is on the rebound, and wants to put forth a kinder and gentler face. In as such, along with the almost impossible task of enforcing a practically public domain standard, it would be politically correct for them to just look the other way on GIFs.
  • by WormholeFiend (674934) on Wednesday July 07 2004, @08:13AM (#9631000)
    Beware of Geeks bearing GIF's
  • PNG (Score:5, Insightful)

    by HungSquirrel (790165) on Wednesday July 07 2004, @08:16AM (#9631041) Homepage
    Internet Explorer still fails to correctly support PNG's superior transparency capabilities. Otherwise I would have adopted it much sooner in my web development. Can't run round incorporating standards into your websites that the browser that holds 95% market dominance does not support.

    </TokenMicroSuckJab>
  • by solarmist (313127) * <joshua@olson.gmail@com> on Wednesday July 07 2004, @08:20AM (#9631074)
    Is there a reason that the writer of this topic chose to talk about the implications about having GIF open to the public rather than talk about having LZW open?

    I personally think having LZW is of much more significance than GIF.
  • by yourruinreverse (564043) on Wednesday July 07 2004, @08:29AM (#9631161)
    So how about it, IBM? You've got nothing to lose! Want to make a lot of geeks happy and release that final patent into the public domain?

    Actually that patent is being used in IBM's (second amended) counterclaims [groklaw.net] in the SCO v IBM case.

    • This is true. It is counterclaim #175:

      175. IBM is the lawful owner, by assignment, of the entire right, title and interest in United States Patent No. 4814746 ("the '746 Patent"), duly and legally issued on March 21, 1989 to Miller et aI., entitled "Data Compression Method". A copy of the ' 746 Patent is attached hereto as Exhibit X.


      176. Upon information and belief, SCO has infringed, contributorily infringed and/or actively induced others to infringe the '746 Patent within this judicial district and elsewhere in violation of35 U. C. 9271 by, without authority or license from IBM, (a) making, using, selling and/or offering to sell products, including Unix Ware and Open Server, that practice one or more claims of the '746 Patent and (b) actively, knowingly and intentionally causing and assisting others to infringe one or more claims of the' 746 Patent.

      While it would be nice for IBM to release the patent to the public domain, they would have to drop this particular claim from the SCO lawsuit if they did.
  • Alpha-Transparency (Score:5, Interesting)

    by The-Bus (138060) on Wednesday July 07 2004, @08:49AM (#9631328) Homepage
    So people know what an "alpha-transparency is" -- it's this very beautiful flower [swri.edu]... which is also on this page [libpng.com], unless you're using IE, in which case it's just blank. Some examples are also available here [tephras.com]. Basically it's just a much nicer version of GIF's transparency.
  • by callipygian-showsyst (631222) on Wednesday July 07 2004, @08:54AM (#9631361) Homepage
    It never really bothered me that these compression algorithms were patented.

    It was a big breakthrough when algorithms like LZW, which compressed data that contained repeated multi-byte patterns (like text, or bitmap drawings), were developed. The previous state of the art was to pre-analyze the data and build a table that would have to be exchanged before the data could be decompressed (like Huffman encoding). LZW lets you built the table on-the-fly as the data is compressed, and exchange it on-the-fly as its being decoded (because the compression "table" and the data stream are actually the same.)

    LZW does seem simple to us now; in fact one standard Job Interview question I ask is to put the LZW algorithm on the whiteboard! However, for those of use who have been around for more than 20 years, it was a significant breakthrough.

  • by Thagg (9904) <thadbeier@gmail.com> on Wednesday July 07 2004, @09:24AM (#9631668) Journal
    In the JPEG standard, there are two possible compression modes for the DCT coefficients, Huffman and Arithmetic encoding. The arithmetic coding is about 10% smaller, far faster to compute, but is unfortunately proscribed by the IBM patent.

    If IBM would release this patent, we could change some #defines in the JPEG code and get 10% smaller pictures with no change in quality.

    Thad Beier
  • by hugesmile (587771) on Wednesday July 07 2004, @10:10AM (#9632170)
    Found this on Usenet [google.com], proving that geeks have too much time on their hands:

    OK.. I have been watching the debate for several years (it's like watching the grass grow). Here's where things are:

    There are several arguments for GIF being pronounced with a HARD G:

    1) "G" stands for Graphical. Graphical has a hard G.
    2) The majority of people pronounce it that way.
    3) Most words that start with G have a hard G.

    The main case for Soft G is that the designers of the file format specifically stated in their specification document that it's a soft G.

    Item 1 has been shot down as follows: Yes, G stands for graphical (*as specified by the designers of the file format*). Three problems with that:

    a) The technical pronounciation of Graphical is gha-raf-i-cal. So it's not the same phonetical sound as hard G. You would need to then pronounce it Gh-IF, NOT hard G "GIF".

    b) What something stands for has nothing to do with how an acronym is pronounced. Modem, for example, stands for modulation/demodulation. Is it pronounced "mah-deem"? Laser would be pronounced as if it rhymes with brassiere... etc. The fact that g stands for graphical has nothing to do with the pronounciation of the acronym.

    c) If you are referring to the word "graphical" as the basis for the argument, then you are basing your argument on the the words picked by the designers, and used in the specification. And in that specification, the designers said that it's pronounced JIFF like the peanut butter. So for consistency, if you go back to the specification to determine what it stands for, then you must live by their specified pronounciation.

    Item 2 has been shot down because the majority doesn't rule on matters of punctuation. (pronounciation?)

    Item 3 has been shot down because there is no rule. There are MANY words that have a soft G pronounciation. People have even argued that GIF is part of Gift, and so they should sound the same. (Gin (soft g) and gink (hard g) are examples that shoot down that logic.)

    So we go back to the specification... no one seems to be able to logically shoot this down. The folks who invented the file format decided what it would be called, and how to pronounce it. If you want to invent your own file format, you can pronounce it any way you want. You can even pick a symbol, and then be referred to as "The file format formerly known as Prince". But as inventor, it's your call.

    I want to say this in a *gentle* way... the *gist* of my message is that most GIF pronounciation arguments amount to *gibberish*, when you consider the *general* logic behind them. I'll let the *genie* out of the bottle here: Have a *gin* and tonic, and cool your *genitals*. You have to go back to the *genesis* of the file format, at the *germination* of the idea, when they first *generated* the specification. to determine the correct pronounciation. It is soft G, like JIFF.

    (it's really fun to read the posts where people write.. "Those who pronounce GIF as JIF..." and correctly read that aloud ("Those who pronounce JIF as JIF"))

    OK.. let this be the definitive guide to pronouncing GIF. You can pronounce it any way you want, but if you are one who insists on being "correct", get used to saying JIF. And I haven't read a logical, solid argument YET for pronouncing it with a hard G. Right now, Soft G is winning the debate, and it's not even close!

    • by I confirm I'm not a (720413) on Wednesday July 07 2004, @08:09AM (#9630962) Journal

      You're talking about an obsolete technology [GIF] that nobody cares about.

      I'd question that. Check Google images [google.com] and see how many web sites still exclusively use .gifs. Not to mention a certain main-stream browser whose support for .pngs is still patchy.

      I guess you and I have different definitions of "obsolete".

    • Re:PNG's..... (Score:5, Informative)

      by eddy (18759) on Wednesday July 07 2004, @08:13AM (#9630997) Homepage Journal

      You can't make animations with PNG files....

      Sure you can, only the result is called MNG [libpng.org].

      • by Kjella (173770) on Wednesday July 07 2004, @08:36AM (#9631215) Homepage
        ...MNG code is not very good to begin with, I believe MNG support was ditched from Mozilla as well, which makes it supported in approximately 0% of the web browsers out there.

        I use PNG quite a bit, but mainly as a competitor to TIF files, but I do prefer to use PNG over GIF in websites too. However, I'm only using non-transparent, plain PNGs for maximum compatibility.

        Animated GIFs? Oh, right. I turned those off, along with pop-ups. If I wanted that, I'd actually use flash or something like that. I figure either you don't block stuff (which means GIF + flash) or you block stuff, in which case you don't see either. Either way, I don't see much room for GIF files...

        Kjella
    • Re:PNG's..... (Score:5, Informative)

      by boutell (5367) on Wednesday July 07 2004, @09:10AM (#9631529) Homepage
      Just to set the record straight:

      When I led the process of drafting the PNG specification, GIF animation did not yet exist. Animation was not part of the original GIF specification. The GIF89a specification *did* offer a mechanism for including multiple images in a single file, and a very basic (but, in retrospect, effective) mechanism for replacing only a specified part of the preceding image. But whether this was supposed to be animation with a time component was never defined, and there was in fact no way to specify how long each frame was supposed to appear, probably because the real intent was to be able to compose a single final still image from many sections. Multiple image GIFs were a footnote to the GIF specification which hardly anybody used until Netscape stepped in.

      Netscape's animated GIF format was a clever hack on top of this: they defined a new GIF chunk to specify the pause between frames.

      Here's the kicker: Netscape was repeatedly invited to participate in the PNG design process. They had someone reading the list, I gather, but they never offered any suggestions or contributions. If they had, they would likely have been considered very seriously.

      But instead, the first we heard of GIF animation was its public release in Netscape (2.0 beta, if I recall correctly). They could have contributed to the design of a PNG or MNG that did include animation and, by way of that compelling feature, would have been more likely to quickly replace GIF. But they didn't.

      We (the PNG designers) did consider retrofitting animation into PNG when Netscape's animated GIF appeared. In fact, I lobbied for that at one point. Unfortunately we had already finalized the functional specification and there was no hope of reaching agreement on how to "jam in" the animation feature at the last minute on top of an otherwise pretty elegant image format.

      Instead, the MNG group was formed to create a specification for a powerful lossless animation format. And they succeeded -- but MNG has yet to really catch fire, and animated vector formats like SWF and SVG are gradually replacing animated GIF anyway for most purposes. At the end of the day, lossless bitmap animation is a pretty bandwidth-intensive proposition.
    • by djmurdoch (306849) on Wednesday July 07 2004, @08:21AM (#9631080)
      The original Welch paper is pretty readable:

      Terry A. Welch, "A Technique for High Performance Data Compression", IEEE Computer, Vol. 17, No. 6, 1984, pp. 8-19.

      If you don't want to go to a library and look that up, then Google will find you about 12000 hits on "Welch LZW", and the first few all seem to be exactly what you want.
    • by gl4ss (559668) on Wednesday July 07 2004, @08:28AM (#9631148) Homepage Journal
      the whole ruckus was because they did publish the algorithm widely and it got used widely - and only then did they reveal their submarine.

      the algo is/was very widely known.
    • Re:PNG vs. JPEG (Score:5, Informative)

      by julesh (229690) on Wednesday July 07 2004, @09:19AM (#9631616)
      No. JPEG at max quality looks perfect to the human eye, but it still has differences from the original image. Lossy compression should be avoided in situations where images are going to be decoded and recoded many times, as these errors build up to the point where they can become noticeable.

      Also: make sure your PNG encoder is configured correctly. In most cases you want to be using the 'adaptive' filter.
    • Re:PNG vs. JPEG (Score:5, Informative)

      by RAMMS+EIN (578166) on Wednesday July 07 2004, @09:49AM (#9631938) Homepage Journal
      I'll bite.

      JPEG, like MPEG (and Vorbis, Theora, ...) changes an image in such a way that humans don't percieve the difference, but it can be stored more efficiently. At lower qualities, you will begin to notice some artifacts. It can go all the way down to a completely useless collection of pixels. It's a common misconception that 100% quality JPEG images are not distorted in any way. I don't know what 100% means, other than the lowest compression your encoder supports.

      PNG images, on the other hand, encode the image exactly as it looks. Basically, a PNG image is a collection of pixels, some metadata, optionally compressed with deflate (same algorithm used by gzip).

      JPEG images are the better choice for photograpic images (which is what they are intended for), where the exact pixel colors don't matter that much. PNG is better for line drawings, text, high contrast images; basically anything that doesn't bear slight changes to the colors. For large images, JPEG can be significantly smaller, making the case for using JPEG for screen dumps and such.
    • by jamie (78724) <jamie@slashdot.org> on Wednesday July 07 2004, @09:51AM (#9631971) Homepage Journal
      "No offense jamie, but you should really refrain from making things up like this. There is no one anywhere with any sort of legal background that would agree with this. Hell, it's probably libel to say that."

      I traded email with several people who know the history of this algorithm and its patents fairly well. I wasn't able to get a quote from a legal expert backing this up by press time, but it hardly matters because this opinion indeed is the consensus of those I have talked to. And I mentioned the duplicate-patent issue to an IBM PR rep, who had plenty of time but didn't offer a correction.

      I stand by what I wrote.