Hi there
When generating HTML from DocBook XML, structures (such as tables or
appendices) with ids generate HTML like this:
div class=appendix lang=en
h2 class=title style=clear: botha name=appendix_a
id=appendix_a/aA.nbsp;Databases to be backed up/h2
div class=glosslist
That's
Jean Jordaan wrote:
Consider putting the id in a place that actually identifies the entire
named section?
The problem is that some older HTML browsers do not suppot ID attributes
and it is thus necessary to emit a name=.../. You can't have ID
attribute with the same value on different
On 14/04/2008, Alan Oehler [EMAIL PROTECTED] wrote:
snip/
Hope that helps...
It did, yes. My eventual solution was to add the following to my
customization layer:
xsl:template name=book.titlepage.separator
/xsl:template
Andrew
--
You did not read the manual
Our tech writer is sad
Locked in
Hi Jirka
But to accommodate your needs you can easily put ID into class attribute.
Just add the following into your customization layer:
Excellent! Thank you very much. Perhaps this can be considered for
inclusion in the standard stylesheets ..
--
jean . .. //\\\oo///\\
Jirka Kosek wrote:
which you can easily access in CSS by
.appendix._foo
I forgot about CSS escaping rules, so you should write this down as
.appendix.\_foo
You might try to use different character then underscore to prefix ID
values.
--
Jirka Kosek [mailto:[EMAIL PROTECTED] wrote:
The problem is that some older HTML browsers do not suppot ID
attributes
and it is thus necessary to emit a name=.../. You can't have ID
attribute with the same value on different element.
I wonder, is support for such old browsers really
Hello folks,
In my custom stylesheet I defined my own template for guilabel,
guimenu, etc.
Sometimes I use those tags inside section title and I would like to a
font-size proportional to the title font size.
I tried with font-size=0.9em (in the fo:inline statement). It's ok
for the
Hi,
Multiple columns are specified in the page-master, so your index content
must be removed from the main article page-sequence that uses the body
page-master and put into a new page-sequence using the index page-master.
You would have to customize the template with match=article from
Andrew McFarland wrote:
On 14/04/2008, Alan Oehler [EMAIL PROTECTED] wrote:
snip/
Hope that helps...
It did, yes. My eventual solution was to add the following to my
customization layer:
xsl:template name=book.titlepage.separator
/xsl:template
You might want to know that this problem
Hi Harry,
I can’t reproduce your problem. The FO file rendered fine with both
FOP 0.94 and FOP 0.95beta.
Since your issue is FOP-specific, I suggest you to post another sample
XSL-FO file and a PNG image to the fop-users mailing list [1], if you
still have troubles. People will also better be
-Original Message-
From: Xuan Ngo
table.cell.border.color doesn't applied in HTML output.
However, it is displaying the expected
color in FO. The parameter exists in HTML as it is showing here
http://docbook.sourceforge.net/release/xsl/current/doc/html/ta
Hi,
I had the same problem as Rasmus and up to now I was using another
suggestion Bob gave me on November 1, 2006 (Subject: generating an index
with 2 columns) which also consisted of a modification of the
fo/component.xsl plus the setting of the column.count.body stylesheet
parameter to 2.
Oh, right, the page numbering starts over because the context node is article
when the page.sequence template is called by name. Instead, that template can
be called using appy-templates in a mode:
xsl:apply-templates select=index mode=page.sequence
xsl:with-param name=content
I had a similar problem resizing a font in different contexts. You can use
xsl:attribute to set font-size and put an xsl:choose inside it like this:
fo:inline xmlns:fo=http://www.w3.org/1999/XSL/Format;
font-family=LucidaGrande font-weight=normal
xsl:attribute name=font-size
xsl:choose
14 matches
Mail list logo
