It has taken me a week of running experiments to get the proper handle on this.
When I am producing unchunked HTML output, it does indeed work as you have described. Unless I am misconstructing a chunked HTML output customization, chunking does not work. <?xml version="1.0"?> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"; version="1.0"> <xsl:import href="html/docbook.xsl"/> <xsl:import href="html/chunk-common.xsl"/> <xsl:include href="html/chunk-code.xsl"/> <xsl:template name="user.preroot"> <xsl:text disable-output-escaping="yes"> <%@ Page language="VB" AutoEventWireup="false" MasterPageFile="~/FANUCRoboticsMasterPageMeta.master"%> </xsl:text> </xsl:template> <xsl:param name="root.filename" select="'default'"/> <xsl:param name="html.ext" select="'.aspx'"/> </xsl:stylesheet> If I pull the lines for chunk-common.xsl and chunk-code.xsl, the first line of the HTML output is: <%@ Page language="VB" AutoEventWireup="false" MasterPageFile="~/FANUCRoboticsMasterPageMeta.master"%> IF I put the lines for chunk-common.xsl and chunk-code.xsl back in, the first line of the HTML output is: <%@ Page language="VB" AutoEventWireup="false" MasterPageFile="~/FANUCRoboticsMasterPageMeta.master"%> Am I doing something wrong or is this a bug in how the stylesheets operate? -----Original Message----- From: Bob Stayton [mailto:[email protected]] Sent: Tuesday, August 24, 2010 4:11 PM To: Merchant, Daniel; [email protected] Subject: Re: [docbook-apps] Server Side Includes for ASP Hi Daniel, Your first example works for me when I use xsltproc. Not clear why it doesn't for you. Your second example actually fails when I try to process it with xsltproc. I get this error message: xsltParseTemplateContent: xslt:text content problem That isn't surprising, since xsl:text is supposed to contain only text, not elements like <title>. I just wonder why you aren't getting that error message. If you convert <title> to <title> and the same for the closing tag, then your code works for me. Or put it in a CDATA: <xsl:text disable-output-escaping="yes"> <asp:Content ID="cntHead" ContentPlaceHolderID="cphHeadContent" Runat="Server"> <![CDATA[<title>Benefits of Flexible Part Feeding</title> ]]> </asp:Content> </xsl:text> That works for me too. Bob Stayton Sagehill Enterprises [email protected] ----- Original Message ----- From: "Merchant, Daniel" <[email protected]> To: <[email protected]> Sent: Tuesday, August 24, 2010 10:35 AM Subject: [docbook-apps] Server Side Includes for ASP I am trying to publish an ASP document. Most of it is working, but there are two parts (both variation of the same thing) that are giving me a hard time. I need to put <%@ Page language="VB" AutoEventWireup="false" MasterPageFile="~/FANUCRoboticsMasterPageMeta.master" Title="FLEXIBLE PART FEEDING"%> in my document. I have coded this as: <xsl:text disable-output-escaping="yes"><%@ Page language="VB" AutoEventWireup="false" MasterPageFile="~/FANUCRoboticsMasterPageMeta.master" Title="FLEXIBLE PART FEEDING"%></xsl:text> in my customization. When I look at my published documents, here is what I get. <%@ Page language="VB" AutoEventWireup="false" MasterPageFile="~/FANUCRoboticsMasterPageMeta.master" Title="FLEXIBLE PART FEEDING"%> My second problem is that I need to put <asp:Content ID="cntHead" ContentPlaceHolderID="cphHeadContent" Runat="Server"> <title>Benefits of Flexible Part Feeding</title> </asp:Content> in my document. I have coded this as: <xsl:text disable-output-escaping="yes"> <asp:Content ID="cntHead" ContentPlaceHolderID="cphHeadContent" Runat="Server"> <title>Benefits of Flexible Part Feeding</title> </asp:Content> </xsl:text> Again, when I look look at my published documents, here is what I get. <asp:Content ID="cntHead" ContentPlaceHolderID="cphHeadContent" Runat="Server"> <title>Benefits of Flexible Part Feeding</title> </asp:Content> Any ideas as to what I am doing wrong? I am using V1.74 DocBook style sheets and xsltproc. I am no more ideas left on how to turn < and > into < and >. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
