Re: [docbook-apps] Entity not defined

You need to define any entities you wish to use in your DOCTYPE entry. For example: ?xml version='1.0' encoding='UTF-8'? !DOCTYPE article PUBLIC '-//OASIS//DTD DocBook XML V4.5//EN' '../../DocBook/docbook-xml/docbookx.dtd' [ !-- HTML-like character entities -- !ENTITY frac12 '#189;'

Re: [docbook-apps] DocBook5: Issues in customization

For item #1, check out the DocBook XSL Handbook, chapter 8, Generated text: http://www.sagehill.net/docbookxsl/TitleFontSizes.html#ChapterTitles The gentext template you're looking to customize is the chapter template in the title context: xsl:param name=local.l10n.xml select=document('')/

Re: [docbook-apps] DocBook5: Issues in customization

(not sure why it doesn;t show up properly in my earlier post). Johnson Earls wrote: For item #1, check out the DocBook XSL Handbook, chapter 8, Generated text: http://www.sagehill.net/docbookxsl/TitleFontSizes.html#ChapterTitles The gentext template you're looking to customize

[docbook-apps] Force colophon or other element to begin on *even* page?

Hello, Resending this question in the hopes that someone has an answer. I've got a document being produced using double-sided mode, which means all the top-level elements (chapter, preface, appendix, etc.) get forced to begin on an odd page. However, the colophon is traditionally on the

[docbook-apps] How To: get HTML title when using inlinemediaobject for article title?

Hello! I have an article for which I am using a graphic for the title. To do this, I did the following: ?xml version=1.0? !DOCTYPE article PUBLIC '-//OASIS//DTD DocBook XML V4.5//EN' 'docbookx.dtd' article articleinfo title inlinemediaobject

[docbook-apps] Any way in double-sided mode to force a component to begin on an even page?

I'd like to get the colophon of my book to be on the last, even, page, rather than starting on an odd page. Is there any reasonable way to do this? - dfp Get the Yahoo! toolbar and be alerted to new

[docbook-apps] Best way to implement author-specified keep-with-next options?

Hello! In the document I'm working on, I'm finding a need to specify the keep-with-next option in several places. Since docbook-xsl 1.73.0 doesn't seem to provide this by itself, I came up with the following simplistic approach. Is this the right way to do things? !-- in

[docbook-apps] Sequential table numbering (as opposed to hierarchical) ?

Hello, I'm very much a newbie at using DocBook, and am getting lost while trying to find how to set the formatting options. I'm using DocBook v4.5, and the docbook-xsl 1.72.0 XSL stylesheets. What I'd like to do is make it so my tables (and figures, etc.) are numbered sequentially

Re: [docbook-apps] Sequential table numbering (as opposed to hierarchical) ?

Fahlgren [EMAIL PROTECTED] wrote: On 7/13/07, Johnson Earls [EMAIL PROTECTED] wrote: I'm using DocBook v4.5, and the docbook-xsl 1.72.0 XSL stylesheets. What I'd like to do is make it so my tables (and figures, etc.) are numbered sequentially through the entire Book, instead of being

[docbook-apps] New release, including fixes over the last 5.5 months?

Hello, I'm just getting started trying to use DocBook for some documentation, and I admit to being quite frustrated. I can't get it to work because of the glossary.xsl bug that fails when using xalan 2.7. I know the bug has been fixed in the svn tree, but, given that it's been 5 and a half

Re: [docbook-apps] New release, including fixes over the last 5.5 months?

Thanks; I'll eagerly await the new release. In the mean time, is it safe to simply replace the glossary.xsl file in the 1.72.0 release with the current one from the snapshot, or does it have other dependencies that would also need to be replaced? Alternatively, is there a way I could just fix my