I have no idea if anyone on this forum will be familiar enough with Docbook and
the XSL-FO stylesheets for creating PDFs but I need to figure out how to
customize my stylesheet template so that I can do pagebreaks differently for
each chapter.
There is a standard param element to set page break
Hello,
I'm working with a customization layer based on a dated version of DocBook XSL
(HTML 1.41?) and using the 1.74 release HTML style sheets for everything else.
This is for a home-grown WebHelp solution that I'm in the process of
internationalizing (mostly complete, except for the Lu
We're using 'imageobjectco's in our manuals (we must have sinned greatly in our previous lives), and I'm wondering if there is a better way to render them.Currently they're a bit of a no-op - the default rendering in FO is identical to an imageobject. For HTML the default rendering is also of an im
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This [1] message provides an alternative approach that will change the
color of text based on an attributes on any element. An advantage to
this approach is that it only requires the addition of a few templates
rather than the modifications of many exi
Good try, but not quite. 8^)
You will lose some features if you do it that way. To customize, a better practice
is to find the base template for that element that already exists in the DocBook
stylesheets, copy it to your customization layer, and modify the match attribute and
anything you w
Hi,
That blank page is actually the verso titlepage, but just has nothing on it. There are
two ways to customize the part verso titlepage.
1. Customize the titlepage specs and regnerate the titlepage templates.That
process is described here:
http://www.sagehill.net/docbookxsl/TitlePageP
I want to find all paras marked as role="high" and render them as red text in
FO output.
http://www.sagehill.net/docbookxsl/CustomInlines.html shows how to do this
sort of thing when matching on inline text. Is it possible at block level?
Here is my first attempt:
--
View this message
Hello all.
Is there a (more or less simple) way to customise the blank page that is
inserted after the titlepage when generating FO output? In my customisation
layer I have tried with different template names: page.titlepage.before.blank,
lot.titlepage.before.recto etc. But nothing makes it int
Correction. I tried this on my work computer and it is now working as
expected.
mike 675 wrote:
>
> I never got this to work for chapter-level TOCs. The section TOCs fix
> worked well, intro text was rendered before the section TOC.
> Here are the changes I made to the chapter template:
>
>
>
Hi Mark,
FOP's error message says 0x107, which is the correct Unicode value for "Latin
Small Letter C with acute", which suggests that the FO output is correct.
I think you will need to consult the FOP list on this one.
Bob Stayton
Sagehill Enterprises
b...@sagehill.net
- Original Messa
Thanks, Bob, for your help.
I've set my project up to use DejaVu, which as seen in the font viewer does
include ć in all the families, styles, and weights available.
Looking at your instructions on missing characters:
If the entity were entered wrong, I'd expect it to be a problem in all output
On 6.10.2011 5:08, Larry Garfield wrote:
> If you do, I'd recommend making them an option. The lion's share of my
> userbase, for instance, is Firefox and Chrome users. I think IE is 4th
> overall, and I have more Android users than IE 6 and 7 combined. I'd be
> inclined to just "go modern and
I never got this to work for chapter-level TOCs. The section TOCs fix worked
well, intro text was rendered before the section TOC.
Here are the changes I made to the chapter template:
I never got this to work for chapter-level TOCs. The section TOCs fix worked
well, intro text was rendered before the section TOC.
Here are the changes I made to the chapter template:
14 matches
Mail list logo
