Have you looked at the process.empty.source.toc parameter? You will
Probably want to add a role attribute to control depth.
Regards,
Larry Rowland
-Original Message-
From: Glen Mazza [mailto:glen.ma...@gmail.com]
Sent: Tuesday, February 15, 2011 10:46 AM
To:
I think that's a great idea. It would also be helpful to extend it to
work as a component in a TomCat environment where Lucene could replace
the search engine (for larger help environments).
Larry Rowland
-Original Message-
From: Jirka Kosek [mailto:ji...@kosek.cz]
Sent: Thursday,
through a
document. Centrally locating the associated expansion reduces redundant
coding.
Regards,
Larry
-Original Message-
From: Dave Pawson [mailto:da...@dpawson.co.uk]
Sent: Thursday, November 11, 2010 12:37 AM
To: Rowland, Larry
Cc: Cramer, David W (David); n...@n-faktor.net;
docbook
We used make for a while before adopting Ant. It was much more difficult to
explain to writers than Ant proved to be, and customizing the builds was more
difficult for them, since they had XML tools for editing DocBook, anyway, but
were not familiar with pure text editors. Ant was also
Hello Nathalie,
A couple of things:
1) You don't have to have a single glossary database for all your documents.
It is quite reasonable to break it up into glossaries that are
topic-appropriate.
2) Title was what the W3C consortium recommend at one time for the expansion.
I have
The glossentry element includes acronym and abbrev as valid children. This is
where it might be best to link the expansion of the acronym or abbreviation to
the acronym or abbreviation (the expansion is in the glossterm). A fairly
simple extension of the transforms allowed us to have the
We use an XSLT script to add the sortas attribute to the documents before we
turn it over to the Japanese localizers, since some of the translation memory
tools they use do not allow them to modify the structure of the document (and
the attributes attached to an element is considered part of
, Rowland, Larry wrote:
We use an XSLT script to add the sortas attribute to the documents before we
turn it over to the Japanese localizers, since some of the translation memory
tools they use do not allow them to modify the structure of the document (and
the attributes attached to an element
on the attribute.
Regards,
Larry Rowland
-Original Message-
From: Jean-Christophe Helary [mailto:jean.christophe.hel...@gmail.com]
Sent: Monday, September 27, 2010 8:32 AM
To: DocBook Apps
Subject: Re: [docbook-apps] translated indexes
On 27 sept. 10, at 23:21, Rowland, Larry wrote:
We use an XSLT
I believe it was set to maybe so that the status attribute on things like
chapters and sections can be used to indicate that part of a document is draft
(in documents that may take months to complete, being able to indicate that
part of a document is draft is important, since significant
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
Did you look at Bob Stayton's write-up on consecutive page numbers (it includes
a bit on page x of y):
http://www.sagehill.net/docbookxsl/PrintHeaders.html#ConsecutivePageNumbers
If you are going to do much with DocBook, Bob's reference is pretty much
essential.
Regards,
Larry Rowland
There is a parameter in the FO transforms that might be helpful. We use empty
toc elements to indicate where to generate a ToC and set this parameter
accordingly:
http://docbook.sourceforge.net/release/xsl/current/doc/fo/process.empty.source.toc.html
Our transforms have considerable
Did you try providing a titleabbrev element with the alternate, shorter title.
That is normally what is used for providing a title that is shorter than the
full title. I am not that familiar with the Website grammar, but I know that
is how it works in other contexts.
Regards,
Larry Rowland
: [docbook-apps] Re: Website: is there any additional *short* title for
use in the TOC / left column?
Rowland, Larry larry.rowl...@hp.com writes:
Did you try providing a titleabbrev element with the alternate, shorter
title.
Many thanks for the hint, Larry!
Tried it, but to no success.
Well
I would suggest looking at the following sections in Bob Stayton's excellent
reference on DocBook XSL.
On using external code files:
http://www.sagehill.net/docbookxsl/ExternalCode.html
On syntax highlighting:
http://www.sagehill.net/docbookxsl/SyntaxHighlighting.html
Regards,
Larry Rowland
You might want to read Bob Stayton's write-up on using CSS:
http://www.sagehill.net/docbookxsl/UsingCSS.html
From: PC Thoms [mailto:pcth...@gmail.com]
Sent: Wednesday, June 23, 2010 1:11 PM
To: docbook-apps@lists.oasis-open.org
Subject: [docbook-apps] aligning text
I'm converting some older
There actually is a mechanism for preserving directives for publishing in a
specific output format: processing instructions. If they become very dense,
they make the markup hard to read, but the mechanism is there. Processing
instructions are ignored if they are not recognized by a processing
The reference section contains refentry elements, which were originally
developed to produce man pages for UNIX-like systems. In general references
contain descriptions of things like commands, code-libraries, functions, and
configuration file formats (in general, the things that users and
Jan,
I know of a couple of things that might lead an organization to adopting
Wiki technology for their help systems.
1) User annotation. One of the things lost when paper went away was the
ability of users to add their own information to a document. This is
important, particularly
You might consider using a simplelist instead:
simplelist type=vert
memberulink url=xxx//member !-- uses the URL for anchor text --
memberulink url=yyymy anchor text/ulink/member
simplelist
It does not generate a ul, but does not require the para elements. If you want
a symbol preceding
This is controlled by the generated text mechanism, which is described in Bob
Stayton's excellent reference:
http://www.sagehill.net/docbookxsl/CustomGentext.html
You need to redefine the templates with the name chapter (there are a number of
them for different purposes).
The section in
You might want to check the parameter:
process.empty.source.toc
in the parameter reference for FO or HTML. Do a search for
docbook parameters to find an online version, although you
should check the copy of the parameter reference that came
with the specific version of the transforms that
Another thing to keep in mind is that DocBook already has a large
assortment (some people say too many, but others of us disagree) of
semantic elements available that describe many features of computers.
Before investing in time to create a new class of things by using a
role on emphasis, make
It sounds like the xincludes are being passed through to the DocBook transforms
rather than being resolved before the processing is taking place. Take a look
at Bob Stayton's write-up:
http://www.sagehill.net/docbookxsl/Xinclude.html
His reference on DocBook XSL is excellent.
Regards,
Larry
Marty,
Bob Statyton has a good discussion of program listings:
http://www.sagehill.net/docbookxsl/ProgramListings.html
There is a section on syntax highlighting (which differentiates among things
like keywords, constants, and parameters) at the bottom of the ToC on this page.
Regards,
Larry
: [docbook-apps] RE: Test condition to check if the current node is
the first child
Larry,
Thanks for the suggestion. But it does not work if white spaces exist
between note and para such
As
note
para
...
/para/note
Sherwood
-Original Message-
From: Rowland, Larry
You might try testing for there being no preceding sibling:
preceding-sibling::node() = ''
Regards,
Larry Rowland
From: Sherwood Hu [mailto:sherw...@morovia.com]
Sent: Wednesday, February 24, 2010 1:26 PM
To: docbook-apps@lists.oasis-open.org
Subject:
A DOCTYPE declaration in XML requires a system value, and yours does not appear
to have one.
The declaration should look more like this:
!DOCTYPE book PUBLIC -//OASIS//DTD DocBook XML V4.4//EN
http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd;[
!ENTITY cereals productnameFrobozz
While I agree that embedding the CSS in the header is not the best solution,
particularly for chunked output, we are sometimes required to deliver files
into existing delivery environments that require file-per-file replacement of
HTML files that were originally produced using output from
That's interesting. I tried it on Ubuntu Linux with OpenOffice 2.4.1 and
it worked, opening my sample DocBook file as a word-processing document.
When I tried on my Windows XP system, with OO 2.3.1 (what was installed
there -- I don't use Windows very much and haven't kept it up to date),
I
Jennifer,
Word does support internal links.
I am not sure which versions of DocBook and OpenOffice you are using
or the platform you are working on, but OpenOffice can import some
DocBook versions. You set the document type to DocBook in the Open
dialog box and then open the XML file. Your
Dave,
Figures are formal objects, that is, they have titles. Mediaobjects are not,
and thus do not have titles. In general, only formal objects show up in lists
of things that are auto generated. If you want a mediaobject to show up in a
list, the general practice is to wrap it in a figure.
-
From: Dave Pawson [mailto:da...@dpawson.co.uk]
Sent: Friday, August 21, 2009 11:13 AM
To: Rowland, Larry
Cc: docbook-apps@lists.oasis-open.org
Subject: Re: [docbook-apps] mediaobject in lots tocs
On 21/08/09 17:10, Rowland, Larry wrote:
Dave,
Figures are formal objects, that is, they have
The keywordset is generally a child of an information block of some sort. In
4.x, that would be refentryinfo, in 5.x, it is an info element.
Larry Rowland
From: Kathleen Mattson [mailto:kathl...@millermattson.com]
Sent: Thursday, August 06, 2009 1:43 PM
To:
Daniele,
Moreover I don't understand why the FO processor stretch the images
instead using their original size!
Part of this is because the size of a PNG has much to do with the way
the image is viewed. Another is that not all PNG creation tools store
an accurate resolution in pixels per inch
We use Apache Ant to control builds. It is possible to use it directly to
invoke a transform (using the XSLT task). By default, Xalan is bound as the
XSLT transform engine, but it can be replaced with Saxon fairly easily. A big
advantage it has is working cross-platform, which is important
are just PNG and photos are JPEG, unless they have
callouts, which we do by overlaying them on the image using SVG).
LRR
Rowland, Larry wrote:
We have over 15000 books in multiple languages on docs.hp.com, so we
share the assets.
You're just a big show-off Larry :-)
We use a versioned
I put a copy of our style assets directory at the root of my hard drive. We
always use the /styles/... type of path on our production pages that are aimed
at the Web. That way if I open the file on my Windows system the styles are
available, too.
Larry Rowland
-Original Message-
, 2009 11:41 AM
To: Rowland, Larry
Cc: docbook-apps
Subject: Re: [docbook-apps] Docbook images/graphics. Where do you keep them?
Rowland, Larry wrote:
Actually, I was just trying to set the context -- I don't even work on that
part of the production process any longer.
The smaller your
by the user in the Ant property. The style
assets are delivered in a different directory.
LRR
-Original Message-
From: DavePawson [mailto:da...@dpawson.co.uk]
Sent: Thursday, May 14, 2009 11:45 AM
To: Rowland, Larry
Cc: docbook-apps
Subject: Re: [docbook-apps] Docbook images/graphics. Where do
The xinclude syntax includes a parse attribute that indicates whether to treat
as XML or text. A programlisting is designed for displaying files such as
configuration files. Not sure if that is exactly what you were looking for.
Larry Rowland
-Original Message-
From: DavePawson
As nearly as I can tell, you are attempting to include a chapter inside a
chapter (StaffServices.xml, which is a chapter includes Cataloging.xml, which
is also a chapter). You also have a para following the inclusion of
Cataloging.xml, which would be a para following a chapter (or section, if
Karen,
The XML is what needs to be preserved in your source tree. If some of your
documentation is shipped with a product, the result files are likely to be
checked into the product build tree (we check in ZIP files of the help system
for most of our products along with some PDF documents).
Most of control of specific output characteristics is done with processing
instructions in DocBook. This allows specifics for different outputs to be
specified (using dbfo and dbhtml type identifiers within the processing
instructions). I guess this is part of the philosophy of trying to
+--
| Another problem I have, a long command line, e.g. calling
| java, saxon for a transform,
| docbook has no
|
| linejava -cp .
| linebreak/main.class
| linebreak/param1
| etc
|
| To enable XSLT to re-build a single line from one
| split, for the sake of convenience?
+--
We face this
The pound character is a reserved character in the URL syntax and should not be
used in file names. Since the value you are specifying is a URL, you need to
observer the syntax of URLs.
From the spec:
Hash for Fragment Identifiers
The hash (#, ASCII 23 hex) character is reserved as a
47 matches
Mail list logo
