Hi Dick,
It sounds like what would happen if you have a keep-together on a fo:block
around the code listing. I'd check for that.
I also did a quick test with a document that has long code listings: Using XEP
and our customization layer which is based on the 1.72.0 xsls, everything is
fine.
Indeed, that's on the list for WebHelp: Add an option to use Lucene for
server-side searches with table of contents state persisted on the server.
http://wiki.docbook.org/topic/WebHelpGsoc2011
It would be good for situations where running Eclipse as a war is too heavy and
presumably simpler to
Hi Sanjaya,
Also, please don’t feel limited to the ideas posted. As you explore the DocBook
tools and the features it has and doesn’t you may come up with your own idea
for a project. According to Google, those are often the most successful.
David
From: Sanjaya Liyanage
Hi there,
Towards the end of last year's Google Summer of Code, I started a wiki page [1]
with some possible projects for 2011 in case we decide to participate again and
are accepted as a mentoring org. I've recently gotten a couple of questions
from students who are thinking ahead and doing
Perhaps you could programmatically process the input file somewhere along the
way (e.g. the fo file before rendering the pdf) to change the space(s) after
le, la, and les to #160; (a non-breaking space).
David
-Original Message-
From: Faehndrich Philippe
I haven't gotten around to trying out svgweb [1] with DocBook content yet, but
it looks to me like the most promising solution to the problem.
David
[1] http://code.google.com/p/svgweb/
-Original Message-
From: Steve Johnson [mailto:ste...@caringo.com]
Sent: Thursday, December 16,
This is probably a hack, but have you tried using negative margin values on the
region-body? Here’s what I do (works with xep):
fo:region-body
margin-bottom=-.02in
margin-top=-.02in
margin-left=-.02in
margin-right=-.02in
background-repeat=no-repeat
Hi Christian,
I'm posting this to the docbook-apps mailing list so we can continue the thread
there since your questions pertain to DocBook generally. Also, other members of
the community might have things to contribute.
Yes, you can produce WebHelp from simplified DocBook. WebHelp is based on
On Tue, 16 Nov 2010 19:38:51 +
Rowland, Larry larry.rowl...@hp.com wrote:
Actually, if you read the entire message, I was not suggesting that
the rendered document have the content in a different location, I was
suggesting that there was already markup available to represent the
But this isn't a glossary entry Larry? It's semantically wrong
IMHO.
DaveP
Really? You come across
glosstermacronymTLA/acronym/glossterm in a document and
don't know what TLA means...
OK, I'll play dumb.
I want to use acronym, with an expansion, in a para David.
The fact that
Hi David,
What version of ant are you using? I've just discovered that the webhelp
build.xml fails with ant 1.8.1 (and I know it works with 1.6.5 to 1.8.0),
however it fails at a different point and with a different error than you're
seeing.
David
-Original Message-
From: David
-
From: Cramer, David W (David)
Sent: Wednesday, November 17, 2010 3:28 PM
To: 'David Priest'; docbook-apps@lists.oasis-open.org
Subject: RE: [docbook-apps] Docbook Webhelp: saxparser problem
Hi David,
What version of ant are you using? I've just discovered that the
webhelp build.xml fails
[mailto:ji...@kosek.cz]
Sent: Saturday, November 13, 2010 10:50 AM
To: Cramer, David W (David)
Cc: DocBook Apps ML
Subject: Re: [docbook-apps] svgweb and DocBook
Cramer, David W (David) wrote:
Hi there,
Has anybody incorporated svgweb into their DocBook-produced html? As
I understand
Hi there,
Has anybody incorporated svgweb into their DocBook-produced html? As I
understand it, it's some JavaScript goo that uses Flash to render the SVG in
primitive browsers that don't support SVG or in cases where you want more
consistent rendering of the SVG.
://ant-contrib.sourceforge.net/tasks/tasks/trycatch.html
[2] http://sourceforge.net/projects/ant-contrib/files/
-Original Message-
From: Peter Desjardins [mailto:peter.desjardins...@gmail.com]
Sent: Tuesday, November 09, 2010 11:06 PM
To: Cramer, David W (David)
Cc: DocBook Apps
Hi Nathalie,
I once started to implement an acronym expanding xslt with the idea that I
could write acronymTLA/acronym and have the first occurrence automatically
be expanded to TLA (Three Letter Acronym). Things were going fine till I hit
GNU and ended up with GNU (GNU (GNU (...) is not Unix)
Hi Mike,
Interesting idea about removing xml:id from titles. Try the following:
include href=docbookxi.rng
define name=db.title.attlist
interleave
optional
ref
Hi Peter,
You could have a build.xml for each top-level/buildable source file that:
1. Declares properties like current.docid etc.
2. Imports your main build.xml that contains your build logic import
file=path/to/main-build.xml/
Optionally, you could store the key/value pairs in a properties
-Original Message-
From: Tom Browder [mailto:tom.brow...@gmail.com]
Sent: Thursday, October 28, 2010 1:59 PM
To: Bob Stayton
Cc: Docbook Apps Help list
Subject: Re: [docbook-apps] Re: qanda listings in html output
On Thu, Oct 28, 2010 at 13:07, Bob Stayton b...@sagehill.net wrote:
On Tue, Oct 5, 2010 at 2:08 AM, Mimil Mimil mimilo...@gmail.com
wrote:
The java code is now extracted has a library (as saxon and xalan
extensions)
named xsl-webhelpindexer, we now have something near to work, the
only thing
missing is concerning the VERSION file which seems to be a
]
Sent: Saturday, September 25, 2010 10:02 AM
To: DocBook Apps
Subject: Re: [docbook-apps] translated indexes
On 25 sept. 10, at 12:49, Cramer, David W (David) wrote:
Typically you just translate the indexterms in place in the document and let
the xslts generate a new index. For Japanese, you add
Hi Sam and Jim,
You might be interested in Jirka's proposal for transclusions in DocBook. It
notes the problems with xincludes for the very use case you bring up:
http://lists.oasis-open.org/archives/docbook-tc/201007/msg00041.html
David
-Original Message-
From: Sam Fischmann
Typically you just translate the indexterms in place in the document and let
the xslts generate a new index. For Japanese, you add sortas attributes to your
primary, secondary, and tertiary elements with the term transliterated into a
phonetic script (katakana or hiragana).
Another problem is
which
seems to generate announcement(s) for freshmeat and sourceforge.
Sorry I haven't had time to look into all this yet.
Thanks,
David
From: Mimil Mimil [mailto:mimilo...@gmail.com]
Sent: Tuesday, September 21, 2010 7:47 AM
To: Cramer, David W (David); Keith Fahlgren; Docbook Apps; docbook
I also agree that draft mode as currently implemented should have a default of
no.
The problem I have with the current, image-based draft watermark mechanism is
that if the image is dark enough to appear when printed (on all
printers...different printers yield different results), then it's so
This thread makes me wonder if we should all update and add details to
http://wiki.docbook.org/topic/WhoUsesDocBook
David
-Original Message-
From: Ruediger Landmann [mailto:r.landm...@redhat.com]
Sent: Tuesday, September 07, 2010 6:25 PM
To: docbook-apps@lists.oasis-open.org
Subject:
Hi Sam,
Maybe try building it using an hhk file instead of the activex goo put in place
of each indexterm by default. See:
http://docbook.sourceforge.net/release/xsl/current/doc/html/htmlhelp.use.hhk.html
and
http://www.sagehill.net/docbookxsl/HtmlHelp.html#HHGenIndex
David
From: Sam
Thanks Bob,
I got it working in my customization layer and have added a feature request:
https://sourceforge.net/tracker/?func=detailaid=3059394group_id=21935atid=373750
David
From: Bob Stayton [mailto:b...@sagehill.net]
Sent: Friday, September 03, 2010 11:52 AM
To: Cramer, David W (David
Hi there,
I would like to set up olinking so that when I generate certain output formats
(pdf, webhelp) olinks to the same document are hyperlinks (just as if they were
xrefs) but olinks to other documents only show the title of the section and
document name, but are not hyperlinks. For these
Thanks for posting the details Jan. I've added a feature request linking back
to this post. I think it would be a nice addition to the base xsls:
https://sourceforge.net/tracker/index.php?func=detailaid=3057673group_id=21935atid=373750
David
-Original Message-
From: honyk
Hi Keith,
Please also mention the addition of webhelp as a newly supported output format
in the release notes :-)
Thanks,
David
-Original Message-
From: Keith Fahlgren [mailto:abdela...@gmail.com]
Sent: Tuesday, August 31, 2010 2:56 AM
To: docbook-developers
Cc: Docbook Apps
Subject:
...@gmail.com]
Sent: Tuesday, August 31, 2010 10:39 AM
To: Cramer, David W (David)
Cc: docbook-developers; Docbook Apps
Subject: Re: [docbook-dev] DocBook-XSL 1.76.0-RC1 for preliminary testing
Ok. I'll ad something to look for that in the notes. Would you please
provide the text?
--
Typed with thumbs
the ideal way to
achieve that would actually be.
Thanks,
David
From: Bob Stayton [mailto:b...@sagehill.net]
Sent: Monday, August 30, 2010 10:28 PM
To: Cramer, David W (David); DocBook Apps
Subject: Re: [docbook-apps] Changing default olink behavior
Hi,
There is no parameter option to do that. You
Hi there,
I would like to change the behavior of olinks so that by default the default
olink text from the olink database is used instead of the link text (the
contents of the olink element). However, I would like the writer to be able to
specify individual cases that the link text should be
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
Message-
From: Keith Fahlgren [mailto:abdela...@gmail.com]
Sent: Monday, August 23, 2010 12:33 AM
To: Cramer, David W (David)
Cc: Bob Stayton; Docbook Apps
Subject: Re: [docbook-apps] The next formal DocBook-XSL release
Hi,
On Sun, Aug 1, 2010 at 6:43 PM, Cramer, David W (David)
dcra...@motive.com
Hi Sharon,
I had the very same problem long ago and was helped by Bob Stayton on the
docbook-apps mailing list:
This is one of the gotchas of XSL import precedence. This template in
fo/footnote.xsl:
xsl:template match=footnote/para[1]
|footnote/simpara[1]
to the list.
Regards,
Kasun Gajasinghe
On Thu, Aug 12, 2010 at 10:56 AM, Cramer, David W (David)
dcra...@motive.commailto:dcra...@motive.com wrote:
Hi Robert,
Kasun knows more about the details of the stemmer, but I can point you to the
documentation for the porter stemmer we used:
http
-Original Message-
From: Fekete Róbert [mailto:frob...@balabit.com]
Sent: Friday, August 13, 2010 2:01 AM
To: Kasun Gajasinghe
Cc: =?utf-8?q?cra...@mail.balabit.hu; Cramer, David W (David);
docbook-apps@lists.oasis-open.org
Subject: Re: [docbook-apps] Help needed testing CJK search support in webhelp
a great work for this summer, and best of luck for your
project! :)
David, if you can find some docbook files which doesn't have any confidential
issues, please send them to the list.
Regards,
Kasun Gajasinghe
On Thu, Aug 12, 2010 at 10:56 AM, Cramer, David W (David)
dcra
Hi Robert,
Kasun knows more about the details of the stemmer, but I can point you to the
documentation for the porter stemmer we used:
http://snowball.tartarus.org/algorithms/porter/stemmer.html
Currently, English, French, and German are supported.
You are correct search does not support
We should also plan for a post-GSOC release that incorporates the work of our
students this summer.
David
-Original Message-
From: Bob Stayton [mailto:b...@sagehill.net]
Sent: Sunday, August 01, 2010 5:33 PM
To: Keith Fahlgren; Docbook Apps
Subject: Re: [docbook-apps] The next formal
-Original Message-
From: Keith Fahlgren [mailto:abdela...@gmail.com]
Sent: Sunday, August 01, 2010 8:12 PM
To: Cramer, David W (David)
Cc: Bob Stayton; Docbook Apps
Subject: Re: [docbook-apps] The next formal DocBook-XSL release
What do you think would be the best time for that release
Hi there,
I've notice some odd behavior in the DocBook xsls: If you import your titlepage
xsl after importing the main docbook.xsl file, then all the headings for any
section level are h1. However if you import the titlepage xsl first, then the
headings are h1, h2, etc as you expect. I've put a
44 matches
Mail list logo
