Return-Path: Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm Delivered-To: mailing list cocoon-users@xml.apache.org Received: (qmail 87927 invoked from network); 1 Aug 2000 12:48:27 -0000 Received: from d1o64.telia.com (root@195.67.205.241) by locus.apache.org with SMTP; 1 Aug 2000 12:48:27 -0000 Received: from idun (t1o64p8.telia.com [195.67.205.8]) by d1o64.telia.com (8.8.8/8.8.8) with SMTP id OAA29030 for ; Tue, 1 Aug 2000 14:48:23 +0200 (CEST) From: "Martin Erlandsson" To: Subject: SV: Cocoon and IE 5.5 Date: Tue, 1 Aug 2000 14:43:22 +0200 Message-ID: <000301bffbb6$147c18c0$1200a8c0@idun> X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <3986BE26.8AB118F2@infoplanning.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N >Martin Erlandsson wrote: >> >> Greetings fellow Cocooners! >> >> I upgraded to IE 5.5 and now I am having troubles viewing my >Cocoon files. >> IE 5.5 seems more picky about file extentions than IE 5.01. >> >> Example: >> >> When requesting the fo sample darkness-novel.xml like this: >> >> .../samples/fo/darkness-novel.xml >> and also >> .../samples/fo/darkness-novel.xml? >> >> I get a blank page. >> >> However, >> >> .../samples/fo/darkness-novel.xml?.pdf >> >> works, but is not a clean solution in the long run (I think). >> >> While waiting for Cocoon 2 to solve this, does anyone have a >suggestion how >> to solve this nicely with Cocoon 1.x ? > >Save your xml files with the PDF extension and have Cocoon >process them. > >Cocoon doesn't have a problem with extensions--IE does (not >following spec >and forcing everyone to work around their stupidity). > >The only problem with that solution is that you cannot store real PDF >documents in the same context as Cocoon. > >So it would work like this: > >rename darkness-novel.xml to darkness-novel.pdf, and set the >servlet mapping >to have Cocoon process "*.pdf" as well as "*.xml". Thanks for your prompt answer! I agree, that is *usually* a better solution than the "?.pdf". However, I often use parameters to output one xml file to several different stylesheets, like: .../document.xml?output=pdf or .../document.xml?output=html or .../document.xml?output=wap I port this through a parameter-testing stylesheet with dynamic processing instructions. It would take one copy of the xml file for every type of stylesheet I want to use, and that kind of kills the idea of parallel publishing. :) More suggestions, anyone? Or do we have to wait for Cocoon 2 to come and save the day? /Martin Erlandsson