To: Jeff Hooker; docbook-apps@lists.oasis-open.org
Subject: Re: [docbook-apps] PDF Output: calling a different page master for a
specific element
Hi Jeff,
If you are using XEP for your XSL-FO processor, you can use the rx:flow-section
extension element provided by RenderX that is like a block
be writing some layout-intensive
publishing scripts from scratch later this year and that looks very well suited
to the task.
Cheers,
Jeff.
-Original Message-
From: Bob Stayton [mailto:b...@sagehill.net]
Sent: September-05-13 9:27 AM
To: Jeff Hooker; docbook-apps@lists.oasis-open.org
Subject: Re
Hi all,
I'd like to call a specific page master for an element that contains a specific
attribute value. Essentially, if for long, narrow tables I want to be able to
call a three-column page master that prevents it from flowing over a 100 pages
when 33 would do. I'm having issues figuring out
Hi all,
I'm using docbook-xsl-1.73.2 and Saxon 9 HE to generate PDFs via XEP.
I'm attempting to strip any remark elements that authors have embedded
in title elements from the content reproduced in the TOC. As far as I
can tell, simply adding
xsl:template match=remark
as blank values, the global values are used.
I'm going to keep picking at this, but any further suggestions would be
welcome.
Thanks,
Jeff.
-Original Message-
From: Jeff Hooker [mailto:jeff_hoo...@pmc-sierra.com]
Sent: Thursday, March 18, 2010 12:12 PM
To: Keith Fahlgren; David Cramer
Cc
And once again I am left wishing that I had simply asked for help
sooner. Removed the default values from docbook.xsl and things started
behaving.
Thanks Bob.
Jeff.
-Original Message-
From: Bob Stayton [mailto:b...@sagehill.net]
Sent: Friday, March 19, 2010 1:48 PM
To: Jeff Hooker
That addressed the problem quite nicely, thank you very much. I would
have been groping for that for quite a while.
-Original Message-
From: Keith Fahlgren [mailto:abdela...@gmail.com]
Sent: Thursday, March 18, 2010 7:15 AM
To: David Cramer
Cc: Jeff Hooker; DocBook Apps
Subject: Re
Hi all,
I'm trying to generate eclipse help, and am running into an odd problem.
I can define either chunker.output.doctype-public OR
chunker.output.doctype-system as seen below, and everything works with
the exception of a malformed doctype statement.
xsl:param
Hi all,
I'm trying to change the processing of table columns whose corresponding
colspec element have an align=center value (in particular, I want to
add a grey background to the entry elements). I've tried to unwind how
the DocbookXSL 1.73 stylesheets process these things and it's an
absolute
The *slightest* of tweaks (preface/section to preface//section) and it's all
lovely.
Thanks,
Jeff.
-Original Message-
From: Bob Stayton [mailto:b...@sagehill.net]
Sent: Thursday, December 10, 2009 11:26 PM
To: David Cramer; Jeff Hooker; docbook-apps@lists.oasis-open.org
Subject: Re
Hi all,
Is there already a parameter established for suppressing section labels within
prefaces? I've looked, to no avail.
Barring that, anybody know of a quick way of doing it? I'm inches away from
just tranforming the section/titles into bridgeheads and moving on.
Cheers,
Jeff.
a simplified processing model.
Just thought I'd check to see if anyone had already done this and what the best
approach turned out to be.
Thanks,
Jeff.
Jeff Hooker, XDocs Admin, Technical Communications
PMC-Sierra, Inc., 100-2700 Production Way, Burnaby BC V5A 4X1
(Tel) 604.415.6000 x 2625
(Cell) 778-855
Hi Jan,
In order to get AIR Help from my docbook files, I first convert them into DITA
files and then I use the DITA Open Toolkit with Scott Prentice's AIR Help
plugin (www.leximation.com).
I'm sure there's an easier way. There usually is. This is just the way I
figured out.
Cheers,
Jeff.
While the DITA DTDs are messy and complex, I do find the way that the DITAOT
XSLs process data (i.e. refering to @class attributes rather than element
names) to be a lovely, elegant way of allowing fall-through generalization. To
me, it makes just as much sense to abstract the XSL from the XML
We use XMLMind 4.2. You do not need to have any reference to the DTD or schema
in the document itself as long as your xxe config file is set up to detect the
document type correctly and contains a reference to the DTD or schema itself.
-Original Message-
From: Eric Johnson
9:22 AM
To: Jeff Hooker; docbook-apps@lists.oasis-open.org
Subject: RE: Setting the draft.watermark.image parameter value
Parameters can contain all kinds of interesting things. For example, you
might do something like this:
xsl:parameter name=draft.watermark.image
xsl:choose
xsl:when test
[mailto:johnbrown...@hotmail.com]
Sent: Tuesday, March 10, 2009 9:37 AM
To: docbook-apps@lists.oasis-open.org
Subject: RE: [docbook-apps] Setting the draft.watermark.image parameter
value
Jeff Hooker wrote:
Hi all,
I'm trying to allow my users to set their own watermark simply
by defining an image
at
the root of the document:
?dbfo draft.watermark.image=/docbook-xsl-1.73.2/fo/mods/watermarks.png?
and it's all good.
Cheers,
Jeff.
-Original Message-
From: Jeff Hooker [mailto:jeff_hoo...@pmc-sierra.com]
Sent: Tuesday, March 10, 2009 9:40 AM
To: docbook-apps@lists.oasis-open.org
tried the precise path to the watermark's
doorstep, but when all else fails, going global usually works.
I'll go back and revisit...
-Original Message-
From: Bob Stayton [mailto:b...@sagehill.net]
Sent: Tuesday, March 10, 2009 10:21 AM
To: Jeff Hooker; docbook-apps@lists.oasis-open.org
Speaking as a guy who chewed through a lot of hours trying to get DiffMk
operating at an acceptable level, just buy the DeltaXML license and figure out
a way of scripting access to it.
DiffMk was an hobby/experiment for Norm. The DeltaXML people are specialists
and have built a tonne of
Hi all,
I'm extracting data from a great swack of .c files dropping the data into
programlisting elements and then separating the different kinds of data with
Bridgehead titles. Overall, it's working swimmingly, but I've run into an issue
with the bridgehead creating unnatural breaks in the
Hi all,
Just wondering if anyone is developing anything for Adobe Air?
I currently administer both Docbook and DITA projects, and have been following
the development of a DITA plugin for creating AIR Help with great interest.
Adapting the DITA project to provide online, cross-platform help
Hi folks,
This one is embarrassing, but I've pored over the scripts for hours and I still
can't figure out how to dump the trailing period used in label numbers.
Basically, the Docbook scripts give me 1.2.3.4. Title and I need 1.2.3.4
Title.
I know. This should be simple, and likely is. I
.
-Original Message-
From: Bob Stayton [mailto:b...@sagehill.net]
Sent: Wednesday, January 21, 2009 1:06 PM
To: Jeff Hooker; DocBook Apps Mailing List
Subject: Re: [docbook-apps] Removing the trailing period in
chapter/section labels
The last period comes from the generated text templates in common
Hi all,
I'm using Docbook 5, Docbook XSL 1.73.2, and RenderX XEP. I've got the main
hypenate parameter for my style sheets set to true and I've also hardcoded
the hypenate=true property into the inline element containing the output of
the XREF element, and yet...not hypenating, not even
Hi all,
My employer is rolling out an XML CMS that has issues resolving xincludes. The
workaround that I need to perform is writing a short XSL to preprocess my files
and resolve Xincludes manually.
My script worked fine on a couple of test docbook 4 test files that used the id
attribute to
be most interested.
Cheers,
Jeff.
-Original Message-
From: Jeff Hooker [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 09, 2008 1:56 PM
To: docbook-apps@lists.oasis-open.org
Subject: [docbook-apps] Processing Xincludes using document() and xml:id
(docbook 5)
Hi all,
My employer
I'd suggest *defining* the parsing of the xinclude element rather than just
going with the default. I'd start by parsing the xinclude as text
(parse=text) and seeing if that prevents the parser from messing with the
content. See 4.2 Included Items when parse=xml and 4.3 Included Items
when
Hi all,
Google and the Adobe PDF specification have let me down; let's see if
anyone here has the answer.
I'd like to be able to insert Acobat comment markers into the PDFs
that I generate using the DocbookXSL stylesheets so that reviewers can
simply use the view next comment feature in Acrobat
Hi all,
I'm trying to define my custom profiling attributes from the command line
rather than from within a customization layer and having problems.
I've defined my custom attributes according to
http://www.sagehill.net/docbookxsl/AddProfileAtt.html and they function fine
when called via a
. If there are
more than one siblings following the affected element, they are untouched.
Does this look familar to anyone?
Thanks,
Jeff.
-Original Message-
From: Camille Bégnis [mailto:[EMAIL PROTECTED]
Sent: Friday, May 30, 2008 2:15 AM
To: Jeff Hooker
Cc: apps docbook
Subject: Re: [docbook-apps
Hi,
I've got an issue where field names (e.g. PIF_TXO_PN[7:0]) are overrunning
table cell boundries rather than wrapping. From the reading that I've done, it
looks as if the only solution when dealing with long words that have no natural
hyphenation break (e.g. REFCLKBPN) is to insert soft
a few page masters and tweaking
some parameters. Am I mistaken here? Any suggestions for a good approach to
this would be appreciated.
Jeff Hooker, Technical Writer, Technical Communications
PMC-Sierra, Inc., 100-2700 Production Way, Burnaby BC V5A 4X1
(Tel) 604.415.6000 x 2255
(Cell) 778-855
33 matches
Mail list logo
