You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Marcin Stefaniuk <ma...@vanart.com.pl> on 2002/08/25 16:43:51 UTC

How force HTMLGenerator to leave elements?

Hello!
In my new company graphic design of a site is authored in
Adobe goLive. I want to simply combine work of designers and mine (in databases and Cocoon2.1). I decided to put some <xi:include> elements in html source and join it in pipeline, but jTidy strips all non html tags including goLive special and xi:include (namespace is defined).

I've tried to fix it rebuilding HTMLGenerator to use jTidy with config file on disk (with defined tags) and with setting setXmlInput property to true. No effect.

Thanks for any help.
Marcin Stefaniuk

---------------------------------------------------------------------
Please check that your question  has not already been answered in the
FAQ before posting.     <http://xml.apache.org/cocoon/faq/index.html>

To unsubscribe, e-mail:     <co...@xml.apache.org>
For additional commands, e-mail:   <co...@xml.apache.org>


RE: How force HTMLGenerator to leave elements?

Posted by Conal Tuohy <co...@paradise.net.nz>.
I've done something similar ... but I haven't hacked the HTMLGenerator ... I
simply added custom ATTRIBUTES to the HTML elements, and transformed those. 

> -----Original Message-----
> From: Marcin Stefaniuk [mailto:marcins@vanart.com.pl]
> Sent: Monday, 26 August 2002 02:44
> To: Cocoon Users (E-mail)
> Subject: How force HTMLGenerator to leave <xi:include> elements?
> 
> 
> Hello!
> In my new company graphic design of a site is authored in
> Adobe goLive. I want to simply combine work of designers and 
> mine (in databases and Cocoon2.1). I decided to put some 
> <xi:include> elements in html source and join it in pipeline, 
> but jTidy strips all non html tags including goLive special 
> and xi:include (namespace is defined).
> 
> I've tried to fix it rebuilding HTMLGenerator to use jTidy 
> with config file on disk (with defined tags) and with setting 
> setXmlInput property to true. No effect.
> 
> Thanks for any help.
> Marcin Stefaniuk
> 
> ---------------------------------------------------------------------
> Please check that your question  has not already been answered in the
> FAQ before posting.     <http://xml.apache.org/cocoon/faq/index.html>
> 
> To unsubscribe, e-mail:     <co...@xml.apache.org>
> For additional commands, e-mail:   <co...@xml.apache.org>
> 
>