OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

docbook-apps message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Inline customization problem


I have the book "DocBook XSL", and it's been most useful, but
there's still one minor problem I can't clear up.  I'm using
the 1.65.1 stylesheets and XEP.

I often use constructs like this:

     <userinput>function(<replaceable>parameter</replaceable>)</userinput>

where I want "function" to appear in monospaced font and
"parameter" to appear in monospaced italic, so the reader
gets a clue that the "parameter" is a replaceable.

This works fine in two contexts:

1.  All HTML contexts.

2.  On the FO side, it looks great inside a <programlisting>.

However, inside a "para", or within "varlistentry/term", the
replaceables are not italicized.  They use the same bold
monospaced font as the <userinput> element not inside
<replaceable>.

Here is one template I tried that didn't affect the font of a
"userinput/replaceable" element:

     <xsl:template match="userinput/replaceable">
       <xsl:call-template name="inline.italicmonoseq"/>
     </xsl:template>

I also tried matching "varlistentry/term/userinput/replaceable".
No help.

I'd appreciate any suggestions you might have for other things
to try.

Best regards,
John Shipman (john@nmt.edu), Applications Specialist, NM Tech Computer Center,
Speare 128, Socorro, NM 87801, (505) 835-5950, http://www.nmt.edu/~john
   ``Let's go outside and commiserate with nature.''  --Dave Farber



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]