Markus Innerebner wrote:
Hello to everyone,
I am trying to decrease the font size of the examples.
para
example
titleMy First Example/title
programlisting
![CDATA[
root
child id=123/
/root
]]
/programlisting
/example
Hi
Use CSS (assuming html output).
The output is pdf.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Markus,
What you need is to change the values in your xsl stylesheets.
Information on how to do that within the docbook-xsl package can be found at
http://docbook.sourceforge.net/release/xsl/current/doc/fo/index.html
Hope this is helpfull,
Tom Van de Putte.
On 5/16/07, Markus Innerebner
Hi Bob
The attribute-set named 'monospace.verbatim.properties' lets you set
properties on all programlisting elements. See this reference:
http://www.sagehill.net/docbookxsl/ProgramListings.html#ReduceFontSize
If you only want to change the size when a programlisting is within an
Sorry for the bad code format.
now I correct it.
programlisting
![CDATA[
root?db-font-weight=bold?
child id=123/
/root
]]
/programlisting
xsl:attribute-set name=monospace.verbatim.properties
xsl:attribute name=font-weight
xsl:choose
xsl:when
Bob Stayton wrote:
Well, no. The processing instruction would be applied to the whole
programlisting, because that is the level at which the attribute-set
is applied. In any case, I believe any markup inside CDATA would not
be recognized in an XPath select statement.
If you want to
Miller, Ray (Centech) wrote:
docbook-rnc-5.0CR3, xsl-1.72, oxygen-8.2.0 (eclipse-3.2.2 plugin)
How would one implement html imagemaps in DocBook?
Inaccessibly.
No way to make an imagemap accessible.
Docbook does a good job of making XML into accessible HTML.
Let's keep it that way
I have a docbook book that has been translated into Japanese. FOP will
not produce a PDF. Seems like encoding=Shift_JIS would do the trick
but no. I've fiddled with a lot of other changes without success.
Has anyone made docbook files in Japanese go through FOP? If so, can you
please send me
To whom may be concerned/interested by getting simple and semantically
correct XHTML output from the DocBook XSLT project.
A long time ago (in a galaxy far, far away), Rene Hache wrote:
PROPOSED GUIDING PRINCIPLES FOR SIMPLER, ACCESSIBLE AND
SEMANTICALLY CORRECT XHTML OUTPUT
* Version 1.1
PROPOSED ROADMAP TO IMPLEMENT R.H.' GUIDELINES
FOR SIMPLER AND SEMANTICALLY CORRECT XHTML OUTPUT
* Version 1.0 1.1 *
1. Produce a set of desired XHTML outputs corresponding to all
possible DocBook structures, according to Rene Hache's guidelines.
[COMMENT BY N.R.] This is probably the
-Original Message-
From: Markus Innerebner
Use CSS (assuming html output).
The output is pdf.
[moved to the docbook-apps list, which is more appropriate in this case]
There is an attribute-set for example properties:
I've done it with XSL Formatter from Antenna House, three years ago. Back
then, FOP was too immature, so XSL Formatter was the only viable choice.
Antenna House is a Japanese company, so Japanese handling is not a problem
with XSL Formatter.
Taro
Eckel, George [EMAIL PROTECTED]
I notice that simplesects are not chunks and so can be a way to let the
writer put subsections in an individual chunk/topic. Before we start
using them like this, I want to make sure I'm not relying on a bug. Is
it intentional that simplesects are not chunks?
One other thing I've noticed:
El Miércoles, 16 de Mayo de 2007 11:48, Nicolas RAINARD escribió:
[COMMENT FROM N.R.] Somebody (I don't remember who and when) said:
Be flexible in what you accept as input, be strict in what you
output (or something the like). Strict 1.0 (or maybe even 1.1) XHTML
is much easier and simpler
El Miércoles, 16 de Mayo de 2007 11:59, Nicolas RAINARD escribió:
3. Completely rewrite the XHTML XSL from scratch, since the current
one is based on the HTML one (even in the XSLT2 snapshot, this is
still the case - correct me if I am wrong). Strict XHTML is
definitively not Transitional
The content on my Part titlepages isn't indented correctly. Instead,
everything in the partintro tag has an indent of 0 (like the title).
So I added the following to my customization layer to try to set the
start-indent to 1.25in:
xsl:template match=partintro mode=part.titlepage.recto.mode
16 matches
Mail list logo
