How is IE modifying the data when you run this page? Both IE (same version as
you're using) and Netscape behave the same when I access it--that is they run
the Acrobat plugin and open the PDF with the same content. Is the problem
maybe something to do with the interaction between the browser and Acrobat?
I'm using Acrobat 5.0.
I sympathize with your frustration, but I work for an organization that
supports IE and Netscape, so I don't have a choice in coding for one browser
or the other. I imagine that's true for a lot of people....
Hugh
Uli Mayring wrote:
> 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. <http://xml.apache.org/cocoon/faqs.html>
>
> To unsubscribe, e-mail: <[EMAIL PROTECTED]>
> For additional commands, e-mail: <[EMAIL PROTECTED]>
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
