David:

That's good to know... I always thought that elements without a closing match 
were to be reported as errors by XSL parsers. 

Carlos

On Jun 5, 2012, at 12:11 PM, David Cramer wrote:

> Hi Carlos,
> Actually, it ends up working out ok since I've escaped the < signs as
> &lt; inside the <xsl:text>. Those come out as < in the generated html.
> This is in the customization layer that produces the books posted
> here, so I know it works :-)
> 
> http://docs.rackspace.com/api/
> 
> I'm adding this to webhelp-common.xsl (~ line 220) and will commit
> once I've tested it.
> 
> David
> 
> On 06/05/2012 12:04 PM, Carlos Araya wrote:
> > David:
> > 
> > I think you need to close the xsl:text element on the first line of
> > your comment.  I think it should be
> > 
> > <xsl:comment><xsl:text>[if IE]</xsl:text>
> > 
> > Carlos On Jun 5, 2012, at 9:57 AM, David Cramer wrote:
> > 
> >> Ok, guess that's a bug in webhelp. This is how I have that in my 
> >> customization layer:
> >> 
> >> <xsl:comment><xsl:text>[if IE]> &lt;link rel="stylesheet"
> >> type="text/css" href="../common/css/ie.css"/> 
> >> &lt;![endif]</xsl:text></xsl:comment>
> >> 
> >> David
> >> 

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

Reply via email to