Return-Path: Delivered-To: apmail-xml-cocoon-users-archive@xml.apache.org Received: (qmail 47256 invoked by uid 500); 4 Jul 2001 21:46:31 -0000 Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-users@xml.apache.org Delivered-To: mailing list cocoon-users@xml.apache.org Received: (qmail 47245 invoked from network); 4 Jul 2001 21:46:30 -0000 Date: Wed, 4 Jul 2001 23:45:49 +0200 (MET DST) From: Uli Mayring To: cocoon-users@xml.apache.org Subject: Re: [C2] Possible Solution for PDF Bug with IE 5.x !?? In-Reply-To: <8CB263A54D013842A2AF262CE9952ACB01A039@feanor.pro-vision.de> Message-ID: "X-Ncc-RegID: de.denic" MIME-Version: 1.0 X-MIMETrack: Itemize by SMTP Server on notes/Denic(Release 5.0.6a |January 17, 2001) at 04.07.2001 23:45:40, Serialize by Router on notes/Denic(Release 5.0.6a |January 17, 2001) at 04.07.2001 23:45:41, Serialize complete at 04.07.2001 23:45:41 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N On Wed, 4 Jul 2001, Stefan Seifert wrote: > Hello (especially Ulrich...). > > I've took a close look at the Problem with wrong displayed PDFs in IE > 5.x. generatet by Coccon-FOP. I had no explanation why it did not work > generatet from cocoon directly, but worked perfectly when the same > stream saved as a file was served from the file system. IE does some checks, when it receives something over the web and possibly even alters the data. See http://ulim.cocoonhost.com/iebug for an example, where it even alters the data. Recently I posted an URL to a page, that explains some of these checks performed by IE. The bottom-line is: IE does weird stuff and doesn't comply to the HTTP standard. No user, especially not users of OpenSource software, should support this software. You are undermining the OpenSource and standards efforts, if you use this browser or develop for customers using this browser. That being said, there are two currently known workarounds, both posted to the list recently (setting a content-disposition header or configuring Acrobat as external application). Perhaps you have discovered a third workaround. But it is not ok to use these workarounds, instead we all should discourage people from using IE by *NOT* supporting its bugs. We are talking about intentional bugs here, introduced to undermine the OpenSource and standards movement. Plus, it's happened three or four times before: every time we find a workaround, Microsoft will change IE in the next version to not support this workaround anymore. Then we have to find a new workaround, which will work until the next version - but the users of the older versions of IE will not be supported anymore. We are not helping users if we go into a coding competition with Microsoft. Ulrich --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. To unsubscribe, e-mail: For additional commands, e-mail: