On Tue, January 31, 2012 10:39 pm, Boris Schäling wrote:
...
1. My book is about C++. Unfortunately C++ is not a word - so e-readers
seem to break C++ wherever they like. A line could end with C+ or C,
and the plus sign(s) is on the next line. I turned C++ into
C#xfeff;+#xfeff;+ (which is
Hi David,
It is possible to checkout the source for the DocBook distribution
from svn [1], but you would then have to build it [2], so typically
working with the snapshot builds is much easier if you need features
that haven't made it into a release yet.
Thanks for the info! I'll set things
Paul Tremblay-2 wrote:
I'm at work right now, so I can't give you a detailed answer just yet.
I've
done the same thing. Basically, you can do this two ways:
1. include a page break in your block
fo:block break-after=page ...
2. Probably better for your purposes, call on your own
Thanks for responding. I feel like I must be missing some basic concept
here. I've looked at the documentation, most of which I think I understand,
but when I use my custom titlepage xml spec file to generate the xsl for the
title page, and then import that into my main style sheet, I still
Hi Dan,
I am actually using a custom styesheet:
xsl:stylesheet
xmlns:xsl=http://www.w3.org/1999/XSL/Transform;
xmlns:doc=http://docbook.org/ns/docbook;
xmlns:fo=http://www.w3.org/1999/XSL/Format;
xmlns:d=http://docbook.org/ns/docbook;
version=1.1
xsl:import
Hi Dan,
The spec file has an error. This empty element should not be in there:
t:titlepage-content t:side=recto
/t:titlepage-content
Bob Stayton
Sagehill Enterprises
b...@sagehill.net
- Original Message -
From: danmauer dan.ma...@gmail.com
To:
OK, so the body_text thing was a separate issue relating to a missing XSL
template in your customization, so I presume you fixed that.
Regarding the CSS, the Oxygen editor has its own CSS for displaying editable
DocBook XML in the editor. That CSS has selectors that match docbook element
Has anyone had success with using callout icons and the calloutlist
using xsltproc and fop?
If so, did you have to do anything special not noted in DocBook XSL
(the book)?
I'm trying to use callouts with a programlisting of literal xml code
(and using lt; and gt; in the usual places). I
Is there a possibility to emulate with 'olink' the behavior of the
attributes 'linkend' and 'endterm' used together in the 'xref' element?
I would like that a couple of my olinks (necessarily used instead of 'xref'
in modular documents with XInclude) receive a dedicated cross reference
text
On Wed, Feb 1, 2012 at 15:40, Bob Stayton b...@sagehill.net wrote:
If you are getting callouts in the HTML, then you probably have it correct
on the XML side. You can check in on the PDF side by setting the stylesheet
param 'callout.graphics' to zero, which will cause it to insert text numbers
-Original Message-
From: Tony Graham [mailto:tgra...@mentea.net]
Sent: Mittwoch, 1. Februar 2012 14:21
To: docbook-apps@lists.oasis-open.org
Subject: Re: [docbook-apps] Unicode characters in epub
[...]
The Unicode Standard says that you are supposed to use #x2060; in new
text,
11 matches
Mail list logo
