From xemacs-m  Mon Mar 17 13:51:09 1997
Received: from neal.ctd.comsat.com (exim@neal.ctd.comsat.com [134.133.40.21])
	by xemacs.org (8.8.5/8.8.5) with SMTP id NAA13654
	for <xemacs-beta@xemacs.org>; Mon, 17 Mar 1997 13:51:08 -0600 (CST)
Received: from neal by neal.ctd.comsat.com with local (Exim 1.61 #1)
	id 0w6iR1-0005yV-00; Mon, 17 Mar 1997 14:51:07 -0500
To: wmperry@aventail.com
Cc: xemacs-beta@xemacs.org
Subject: Re: WE NEED NEW GIF CODE...
References: <199703171912.LAA01741@newman>
Mime-Version: 1.0 (generated by tm-edit 7.105)
Content-Type: text/plain; charset=US-ASCII
From: Neal Becker <neal@ctd.comsat.com>
Date: 17 Mar 1997 14:51:07 -0500
In-Reply-To: "William M. Perry"'s message of Mon, 17 Mar 1997 11:12:38 -0800
Message-ID: <u9hgiaguvo.fsf@neal.ctd.comsat.com>
Lines: 16
X-Mailer: Gnus v5.4.26/XEmacs 20.1(beta7)

>>>>> "William" == William M Perry <wmperry@aventail.com> writes:

    William> Ok, so enough screaming.  But I've been digging around the GIF code and it
    William> does appear to be something wonky with animated GIFS.  A 100% repeatable
    William> problem for me is http://www.aventail.com/img/ndownld.gif

    William> Does this crash for everyone else?  The DGIF code is giving me a headache.
    William> And does anyone know of freely available GIF decoding libraries that are
    William> not eligible for obfuscated C '98?

    William> -Bill P.


The interesting part is that since this gif stuff is part of the
standard jpeg lib, and since xemacs already supports jpeg, it looks
like this might be easier than I thought!

