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: Re: [docbook-apps] Inline customization problem

Hi John,
I'm not sure what you are seeing.  When I cut and pasted your example into a
para, and then processed it using docbook-xsl-1.66.1, xsltproc and XEP 3.83,
I get the word "function" in bold monospace, and the word "parameter" in
bold italic monospace.  Based on the way the templates are written, that is
what I would expect.  The userinput template wraps the content in a
fo:inline and sets the font-weight="bold".  The replaceable template wraps
the content in a fo:inline and set the font-style="italic".  Since those are
separate properties, they don't affect each other.  Can you send me a short
FO file that illustrates the problem?

Bob Stayton
Sagehill Enterprises
DocBook Consulting

----- Original Message ----- 
From: "John W. Shipman" <john@nmt.edu>
To: "docbook-apps mailing list" <docbook-apps@lists.oasis-open.org>
Sent: Wednesday, November 03, 2004 5:39 PM
Subject: [docbook-apps] 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
> 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]