Hi Eric,
I presume you mean Chapter 12, HTML Customizations.  I think the section you 
are referring to needs some clarification.

I'm not sure, but I don't think POST has anything to do with the problem.  Most 
likely the input is not well-formed XML.

In order for an XSLT processor to xsl:copy any content, that content must be 
well-formed XML, and typical HTML is not well-formed XML. If the content has 
HTML markup, then simply wrapping the content in an element does not make it 
well-formed.  That only applies if the content is text such as Javascript.  The 
third paragraph in this section mentions that any HTML markup must be 
well-formed markup:

http://www.sagehill.net/docbookxsl/InsertExtHtml.html

The xsl:output can still be method="html", and the processor will convert your 
well-formed XML back into plain HTML.  

If that still doesn't work, then post an example.

Bob Stayton
Sagehill Enterprises
[email protected]


  ----- Original Message ----- 
  From: Eric Hagemann 
  To: [email protected] 
  Sent: Saturday, July 25, 2009 5:55 PM
  Subject: Re: [docbook-apps] html pass thru


  I have been able to follow the examples in the DocBook XSL guide and have 
inserted the code as per Chapter 11 but I am still having issues since the html 
is a href with POST parameters that is causing the transformation engine to 
choke.  I have treated the HTML as malformed and done as suggested -- wrapped 
the html in proper xml tags <badcode> html </badcode> but still no luck


    ----- Original Message ----- 
    From: Eric Hagemann 
    To: [email protected] 
    Sent: Saturday, July 25, 2009 5:41 PM
    Subject: [docbook-apps] html pass thru


    Hello,
        Seems like a simple thing that I should be able to find in help -- but 
to no avail.

       I am writing contect destined for web output and I want to place some 
html within the docbook xml and have it pass thru unaltered.  I want the html 
to be "live" and thus CDATA will not work

        Is there a processing instruction for such a purpose ?

    Cheers
    Eric

Reply via email to