Hi,
I have been using ant for publishing for some time. Typical usage scenarios in
my company are these:
- publish documentation to webhelp and pdf as part of the application build
- publish documentation as an eclipse infocenter plugin (this involves updating
working copy from svn, stopping
On Wed, 25 Aug 2010 22:55:36 -0400
Peter Desjardins peter.desjardins...@gmail.com wrote:
Here are some of the questions I have. Any input will be very helpful.
* What are some advantages an Ant-based publishing system has over a
shell script system? Clearly Ant is cross-platform, what else?
I'm reading a text which is very localized. It's odd words, rather than
boilerplate which I believe is the basis for docbook I18N.
Anyone any references please for best practice in this area?
I like the docbook principles, to keep all 'foreign' text out of the
main body and reference it [via
Hi Peter,
I also use Ant for our build process and would add a couple of points to those
others have made:
The xslt task [1] allows you to pass in parameters if they have been
specified. This is very convenient since you want to use the default values
from the xslts unless you pass in a
Dean:
For what it is worth, I have also seen very similar errors - but definately not
using a segmented list,
Using DocBook XSL 1.75.2, FOP 0.95
same warning, and error message about proportional column width, and though not
a segmented list it was in some other sort of list and/or a table.
We have a fairly complex Ant based system that uses an individual build file
for each document that includes a set of build files that have the actual
targets for building; this allows us to customize things like file names and
destination paths easily. Each document can be processed into a
Thanks, but that type doesn't do anything in the code. Also using the PIs
does not help either.
After looking closer in the 1.75.2 stylesheets, the segmentedlist template in
fo/lists.xsl has a problem when used in FOP. It specifies the table as an
auto table and it needs to be a fixed table
Hi,
Actually, this was a bug in DocBook XSL. The stylesheets sometimes use
fo:table to layout certain elements. For segmentedlist, a layout table is
used if the stylesheet parameter 'segmentedlist.as.table' is changed from the
default 0 to 1. In this case, because the fo:table-columns use
| -Original Message-
| From: deannelson
|
| After looking closer in the 1.75.2 stylesheets, the
| segmentedlist template in fo/lists.xsl has a problem when
| used in FOP. It specifies the table as an auto table and
| it needs to be a fixed table since FOP doesn't support
|
Hi Dave,
I guess I need some clarification of your terminology here. When you say odd words,
I presume that means the text is mixed language text, with foreign words mixed with
English text, rather than foreign content isolated in elements? And when you say
boilerplate, are you referring to
BTW, my direct email responses to Mauritz are bouncing. I wonder if he is
aware of that problem? I don't have an alternate channel to inform him.
Bob Stayton
Sagehill Enterprises
b...@sagehill.net
- Original Message -
From: deannelson
To: Mauritz Jeanson ; 'reflexing' ;
Thanks Mauritz Bob!
In a message dated 08/26/10 09:37:07 Pacific Daylight Time,
m...@johanneberg.com writes:
| -Original Message-
| From: deannelson
|
| After looking closer in the 1.75.2 stylesheets, the
| segmentedlist template in fo/lists.xsl has a problem when
| used
12 matches
Mail list logo
