Next in thread → Next in month →

Re: [docbook-apps] Should ie.css be included by default in the generated webhelp files?

From
Carlos Araya <>
Date
2012-06-06T18:24:35+00:00
ID
CANL4y-oiu=jo1duOHz=XpcEiVB4txi=-k1Em=USRo=+qDc=
Thread
Re: [docbook-apps] Should ie.css be included by default in the generated webhelp files?
David:

thank you for the observation. I missed the closing xsl:text until you pointed it out. 

Carlos

On Tue, Jun 5, 2012 at 2:10 PM, David Cramer <> wrote:

-----BEGIN PGP SIGNED MESSAGE-----

Hash: SHA1

In this case, the closing xsl:text tag is in the third line, just

before the closing xsl:comment tag:

<xsl:comment><xsl:text>[if IE]>

&lt;link rel="stylesheet" type="text/css" href="">
&lt;![endif]</xsl:text></xsl:comment>

So all the contents of the comment is inside the xsl:text.

David

On 06/05/2012 04:02 PM, Carlos Araya wrote:

> 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="">
>>>> &lt;![endif]</xsl:text></xsl:comment>

>>>>

>>>> David

>>>>

>

-----BEGIN PGP SIGNATURE-----

Version: GnuPG v1.4.11 (GNU/Linux)

Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPznW7AAoJEMHeSXG7afUhrukH/jiKGfnWl4mIKOh6GhtP2IHv

pIik1+uZlFb3PT9cNaahLce81QiOTgyfVWsD1nxCHpKiun3jfYmQzBWA2aDI7cH1

qQglZUIqS5iZX57zgWhNbNF4w6mxRizOXkvvNHSF91WAkF99bxLUXnJWtW+lPzAj

Yxy4EiXwSk2LYBzgJgF1JkH1qMz6xNHTitF0PgOTiPgzLpXkUlom4H5eQTdosxao

lO6XDt8eyfPZUI9XhObCdTFGcxgdguBbNN4Cy5/Nq8PXrMUW1BGrqraF3DhJEwaN

fF9bfpSkcJofuX11Tm2O08qdyNdAb7esNvf5XYt4NBKSwM8s9+3f4lEXptgXbts=

=j6h5

-----END PGP SIGNATURE-----

---------------------------------------------------------------------

To unsubscribe, e-mail: 

For additional commands, e-mail: 
Next in thread → Next in month →