Return-Path: Delivered-To: apmail-xml-cocoon-users-archive@xml.apache.org Received: (qmail 8955 invoked by uid 500); 12 Apr 2002 11:12:45 -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 8944 invoked from network); 12 Apr 2002 11:12:45 -0000 From: "Marc Portier" To: Subject: RE: How to get HTML (not XHTML) from the HTMLSerializer (C2.0.1) Date: Fri, 12 Apr 2002 13:12:44 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-Mimeole: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal In-Reply-To: <20020412103746.1BE1719A97@localhost.localdomain> X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hi, [1] I thought
was the classic tric for all elder browsers? as in: less_then letter_b letter_r [[[SPACE]]] slash biggert_then those elder browsers consider /-es appended to the tagname to be part of the tagname, and the br/ tag is as meaninless as your own invention to it (and thus ignored) [2] as for you remark to 'easier' I guess the serializer idea comes from the separation of concerns philosophy... the one that writes an XSLT can not be sure that it will (at all times) be the last step in the show, not even if it's output is XHTML (think about post-processing with another XSLT step that e.g. would change all background color attributes?) Should check the code, but I expect the output property 'method' of the xsl to be overriden to 'xml' anyway when used in a transformer... [3] in every case I do live under the impression that the html serializer will create
for you instead of
did you check your sitemap? And for this I did check the code: as expected the html serializer is precisely an empty TRaX transformer that gets an output property method="html" handler = getTransformerFactory().newTransformerHandler(); format.put(OutputKeys.METHOD,"html"); handler.setResult(new StreamResult(this.output)); handler.getTransformer().setOutputProperties(format); which boils down to checking your sitemap again? -marc= > -----Original Message----- > From: Peter Robins [mailto:cocoon@peterrobins.co.uk] > Sent: vrijdag 12 april 2002 12:38 > To: cocoon-users@xml.apache.org > Subject: Re: How to get HTML (not XHTML) from the HTMLSerializer > (C2.0.1) > > > excuse me if I'm missing the point but, if the objective is to get
> instead of
, wouldn't it be far easier to use the html > output method in > the xslt script directly, and not use the HTML serializer? > > > On Friday 12 Apr 2002 7:59, Nicola Ken Barozzi wrote: > > From: "Yuri Gadow" > > > > > > Try with
> > > > > > If you mean an XSLT using that syntax (otherwise, I guess I'm missing > > > something), I'm afraid that doesn't help. > > > > It's a hack to get Netscape 4 to use that tag. > > > > If I write: > > > > > > > > ciao
> > ciao > > > > > > in Netscape 4.7 I get: > > > > ciaociao > > > > but if I write this: > > > > > > > > ciao
> > ciao > > > > > > I get: > > > > ciao > > ciao > > > > I can also write
and it's the same, the > > trick is putting in an attribute. > > > > In this way Netscape 4 can show valid XHTML, which is IMHO > better anyways > > than
. > > > > Just write a stylesheet that converts adds an attribute to
s and > > copies all other stuff, and you're done. > > --------------------------------------------------------------------- > Please check that your question has not already been answered in the > FAQ before posting. > > To unsubscribe, e-mail: > For additional commands, e-mail: > --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. To unsubscribe, e-mail: For additional commands, e-mail: