I've been unable to implement 1.78.1 webhelp because fragment hrefs
(generated from local links and olinks) don't seem to work. For example,
clicking this link does nothing when the target is in the same chunk:
a class=link href=ch01.html#testtargetTest local link/a
Local links like this
In docbook-xsl-ns-1.78.1 (and going back to 1.77.1, I think), I've found
a possible bug in the sample webhelp/build.xml Ant file.
In the chunk target, the first xslt task, which generates a profiled
version of the document, specifies the Xerces XML parser:
sysproperty
Hi Devine,
afaik, copying the template to your customization is the right way to
go, as described in http://sagehill.net/docbookxsl/CustomizingPart.html.
It's certainly better than directly editing the stock templates.
If it's a bug and the template gets fixed in a future release, you can
Hi Jeff,
I gave up trying to get catalogs to work with the ANT xslt task,
probably because I don't know ANT well enough. But it did get things to
work after ditching the xslt task and just using the java task. Attached
are my current build and properties files (note, i haven't upgraded it
, you could modify your ant
script to use xsltproc for the xslt portion.
David
On 06/17/2012 08:44 AM, Denis Bradford wrote:
The problem seems to be the doctype generation in the generated
targetdb
Sorry, I meant The problem seems to be the doctype line in the
generated target.db
On 06/17
docbook-xsl-ns-1.77.1 appears to break Webhelp olinks. My build hangs
while processing the target database. The problem seems to be the
doctype generation in the generated targetdb, which was not there in 1.76.1:
!DOCTYPE div
PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN
The problem seems to be the doctype generation in the generated targetdb
Sorry, I meant
The problem seems to be the doctype line in the generated target.db
On 06/17/2012 09:36 AM, Denis Bradford wrote:
docbook-xsl-ns-1.77.1 appears to break Webhelp olinks. My build hangs
while processing
Version 1.77.0 adds support for xlink:show=new, so you can open an
HTML link in a new window instead of replacing the current window. It
works for various inline elements, but not for link itself. Is this a
bug? For example this link
paralink xlink:href=my.mp3 xlink:show=newAudio/link/para
I didn't realize the jquery css file was intended for overrides, either.
So my solution was to add a link to my custom CSS style sheet at the end
of the user.head.content template, after all the stock css and js files.
That way, my CSS rules take precedence.
- Denis
On 01/28/2012 10:35 AM,
:
| -Original Message-
| From: Denis Bradford
|
| I've been trying to preprocess xincludes in my DocBook 5
| build with xom,
| using the incantation in Bob Stayton's Complete Guide:
|
| $ java -cp xom-1.2.1.jar:xom-samples.jar
| nu.xom.samples.XIncludeDriver source.xml serialized.xml
I've been trying to preprocess xincludes in my DocBook 5 build with xom,
using the incantation in Bob Stayton's Complete Guide:
$ java -cp xom-1.2.1.jar:xom-samples.jar
nu.xom.samples.XIncludeDriver source.xml serialized.xml
The xincludes resolve just fine, but the serialized doc's encoding
I second the motion, but maybe there's not a huge hurry. My 2₵:
Help 3 (official name: Microsoft Help Viewer) is currently used only in
Visual Studio (and MSDN, in some form) -- MS does not yet consider it a
general purpose replacement for HTML Help.
Help 3 design is still a moving target.
Also see Bob Stayton's summary of using xincludes in
http://www.sagehill.net/docbookxsl/DuplicateIDs.html.
I've successfully implemented xincludes in place of entity refs, but it
was tricky, along the lines that Sam describes.
That's why I sat up when David mentioned Jirka's transclusion
Hi Jochen
According to 'DocBook 5: The Definitive Guide'
(http://www.docbook.org/tdg51/en/html/info.html), article/info is not
designed to appear in output:
==
Description
The info element contains meta-information about the element that
contains it.
Processing
Hi Jochen,
In your layout.xml, you can add titles to tocentries, like this:
tocentry filename=am-paris.html page=am-paris.xml
titleShort title/title
/tocentry
If you add the optional title element a tocentry, it is displayed in the
TOC instead of the title that's in
You can create a file with a collection of text entities, similar to
the examples in docbook/schema/dtd/4.5/dbgenent.mod, and then reference
the ones you want in your document.
But I believe XIncludes are intended to replace entities for this
purpose, and DocBook 5 supports them. An XInclude
all this very cool development. Thanks to all for your thoughtful responses!
Dave Pawson wrote:
On Thu, 27 May 2010 01:00:47 +1000
Ruediger Landmann r.landm...@redhat.com wrote:
On 05/20/2010 11:33 AM, Denis Bradford wrote:
Neat! That ought to prove my point -- both of us can't be wrong
Hi David,
Sorry I missed the WebHelp project -- you're right, the features I had
in mind do suggest user assistance.
I'm not sure what should be in the Index tab, but I'll see if I can help.
Thanks,
Denis
David Cramer wrote:
-Original Message-
From: Denis Bradford
Dave Pawson wrote:
On Wed, 19 May 2010 17:31:59 -0400
Denis Bradford denis.bradf...@verizon.net wrote:
Another example, on the Website side: why should only books and help
systems have an index? It's a great navigation tool for an
informational web site, too. So, I hacked the Website
Hi Sina, please see my response at the bottom.
Sina K. Heshmati wrote:
Denis Bradford denis.bradf...@verizon.net said:
Hello Denis,
Not sure if this the best place to post this, but here goes:
Where better than here?
Sina, I'm so glad to see active development on Website, it's
Not sure if this the best place to post this, but here goes:
Sina, I'm so glad to see active development on Website, it's such a
terrific product. As long as you're thinking about its next stage of
development, has anyone suggested folding Website into DocBook? I use
both all the time, and I
Neat! That ought to prove my point -- both of us can't be wrong.
Doug wrote:
On Thu, 20 May 2010, Denis Bradford wrote:
Not sure if this the best place to post this, but here goes:
Sina, I'm so glad to see active development on Website, it's such a
terrific product. As long as you're thinking
As usual, I should have dug a little more before asking for help. Found
the source of my problem:
In db4-upgrade.xsl, the * mode=AddNS template adds a version
attribute to the root element, like this:
xsl:if test=not(parent::*)
xsl:attribute name=version5.0/xsl:attribute
I'm working on an XSL 1.0 stylesheet that processes a DocBook Website
autolayout file, transforming its Website pages into DocBook 5 articles.
My stylesheet imports Norm's db4-upgrade.xsl, which does most of the
work. My output is valid, and looks fine except for one nagging detail:
some
Sorry, posted to wrong list:
Original Message
To: docb...@lists.oasis-open.org
... the DocBook model (so far)
has been a top-down approach, with documents typically being authored
as entire publications that contain chapters and sections.
Introducing a topic into DocBook
In terms of the cost of customization, I have found customizing the
DocBook 4 DTD to be easier than customizing the DITA DTDs.
Talk about complex transforms: I've been using DITA recently, and the OT
stylesheets look pretty intimidating to me - and no 'DITA XSL The
Complete Guide' to help
If you're interested in a tree-view TOC *without* frames, there's
DocBook Website.
http://docbook.sourceforge.net/release/website/example/
Website has a whole chapter in Bob Stayton's Complete Guide,
and the XSL is part of the basic DocBook distribution.
You'll enjoy customizing the
I'm including an offsite document in my Website 2.6.0 layout. However,
some -generated tocs do not link to it when I specify its location with
a relative path.
For example, in this layout the second tocentry specifies an offsite
document that is to be found in the output-root directory.
give me a clue, I installed it and
generated a website.database.xml there. Learned nothing new: the file
has the same structure.
Denis Bradford wrote:
Sorry, I should have indicated that the first bit was a fragment - I do
have a sitemap element.
I'm confused about your second point: I
I maintain a web site as a collection of DocBook websites, each with its
own layout and its own TOC. I want to replace the old ulinks with
olinks. The olinks are working fine within each website, but olinks
across websites fail to resolve. Here's how TDG says to do it:
Once you have the
FWIW, here's the docbook2.pdf that I generate using docbook-xsl-1.73.2
and FO 0.20. I don't think the mail list likes attachments, but the PDF
is small, so I'll just cat the contents below:
a%PDF-1.3
%ª«¬
4 0 obj
/Type /Info
/Producer (FOP 0.20.5)
endobj
5 0 obj
/Length 122 /Filter [
Two possible starting points using the base DocBook stylesheets:
* Olink databases, if you use olinks. To quote 'Target database
additional uses' in Chapter 24 of Stayton's book:
You may find additional uses for the target database that keeps track
of potential olink targets. The database
to tables which makes
the layout difficult. Using DIV allows mcuh more control through the
use of CSS.
Russell
Denis Bradford wrote:
Where do you want to generate divs?
I haven't noticed a one-to-one mapping in the docbook HTML
stylesheets: divs seem to be generated to put structure around all
I think you're dealing with apples and oranges.
A reference is (I think) designed to be used for reference information,
often presented in a dictionary-style for easy lookup. A reference is a
collection of refentries, similar to a book comprising a bunch of
chapters or articles. In addition
Sorry, I meant to say, the analog of a section is a refsection.
Also, I think a reference can be a good choice for an API, for the
reason that you guessed: it's designed to give you a regular structure
that makes information easy to up. I think that's what most people do
with API docs.
35 matches
Mail list logo
