Bill> SL Baur <steve(a)xemacs.org&gt; writes: Bill> [...] Bill> This is all well and good for XEmacs' internal stuff to be all PNG, but Bill> this is going to essentially cripple Emacs/W3 for displaying images. And Bill> VM for displaying attached GIFs, as well as TM, etc. Could we _please_ Bill> investigate either crippling GIFlib so that it cannot _create_ GIFs, but Bill> can still decode them, or using the bogus-encoding that Ghostscript uses? I also vote for continuing to include GIF-reading capability in XEmacs. If Unisys decides to go after the `Open Source' community, they're not going to start with XEmacs. They'll likely choose a bigger corporate target, such as RedHat, and a more visible program, such as gzip (for its .Z decompression code). In that case the whole community will have to de-GIF/LZW their programs. We should follow along in that case and issue emergency GIF-free releases of XEmacs. My feeling is that Unisys will not do this - there isn't enough money in it, and there isn't much of a claim on GIF-reading technology. Martin