RE: [docbook-apps] InputHandler error - generating PDF

-Original Message- From: Chris Borg 07-Mar-2007 17:55:45 org.apache.fop.cli.InputHandler error SEVERE: javax.xml.transform.TransformerException: org.apache.fop.layoutmgr.inline.WrapperLayoutManager Prior to the error I marked up my source XML with some index tags. I am not

Re: [docbook-apps] keycap and localized @function

Hi, On Sonntag, 4. März 2007, Thomas Schraitle wrote: [...] For the full content see: http://lists.oasis-open.org/archives/docbook-apps/200703/msg00026.html What do you think? Does it sound reasonable? :-) My question relates to empty keycaps that uses the function attribute, like this:

RE: [docbook-apps] HTML- SVG problem: How to change HTML tags?

Martin, Try setting use.embed.for.svg to 1: http://docbook.sourceforge.net/release/xsl/current/doc/html/use.embed.fo r.svg.html David Thanks a lot, I need to make my graphics visible and this problem drives me mad. Many thanks, Martin

Re: [docbook-apps] HTML- SVG problem: How to change HTML tags?

Hi Martin, I think you are very close. The part you found creates the HTML tags and saves them as a result tree fragment in the 'img' variable. Further down the big process.image template is xsl:copy-of select=$img/ which then outputs the result tree fragment created earlier. So where you

[docbook-apps] HTML Indexes

Can anybody with knowledge of the HTML autoidx.xsl code give me a quick overview of the steps the stylesheet goes through to produce the index. I'm trying to get my head around the code and I feel like the answers within reach but at the same time a long way away. I'm looking to create a

Re: [docbook-apps] HTML Indexes

Simon Kennedy wrote: Can anybody with knowledge of the HTML autoidx.xsl code give me a quick overview of the steps the stylesheet goes through to produce the index. I'm trying to get my head around the code and I feel like the answers within reach but at the same time a long way away. First

[docbook-apps] footnote numbering is suppressed

Title: footnote numbering is suppressed I find that footnotes are numbered in the body of the text, but the footnotes at the bottom of the page are not numbered. The only footnote related content in my customization layer is: xsl:param name=footnote.font.size select='85%' / xsl:param

[docbook-apps] list of figures in the TOC for an appendix

Title: list of figures in the TOC for an appendix With this in my customization layer xsl:param name=generate.toc appendix toc,title,figure article toc,title book toc,title,table,figure,example,equation chapter toc,title part toc,title preface title reference toc,title sect1 title sect2 title

Re: [docbook-apps] list of figures in the TOC for an appendix

list of figures in the TOC for an appendixHi Ron, Lists of figures, tables, etc. is only implemented for the book element. I think perhaps it was intended to be extended to other elements, but never was. I think it might be as easy as adding something like this to an appendix customization:

[docbook-apps] Modifying olink generated text

I'm having trouble making a customization to olink generated text. I want to remove the section called from olinks to sections. Can someone point out errors in my method? To troubleshoot, I have reduced my customization layer to only what I see in:

[docbook-apps] Using FOP .93 with DocBook 4

I'm trying to use DocBook 4 with FOP .93 and I get the following error: javax.xml.transform.TransformerException: org.apache.fop.apps.FOPException: file:///c:/docs/Main/xml/test/help/Test.fo:2:29513: Error(2/29513): No element mapping definition found for (Namespace URI:

Re: [docbook-apps] Using FOP .93 with DocBook 4

I believe this problem was fixed in version 1.71.1 of the DocBook XSL stylesheets. What version are you using? Bob Stayton Sagehill Enterprises DocBook Consulting [EMAIL PROTECTED] - Original Message - From: Jeff Powanda To: docbook-apps@lists.oasis-open.org Sent: Thursday,

Re: [docbook-apps] Modifying olink generated text

Hi Peter, You need to modify your en.xml to add the l:i18n wrapper element. Any gentext customization needs to include that in the local.l10n.xml parameter. Then it should work. Bob Stayton Sagehill Enterprises DocBook Consulting [EMAIL PROTECTED] - Original Message - From: Peter

RE: [docbook-apps] Modifying olink generated text

You need to modify your en.xml to add the l:i18n wrapper element. Any gentext customization needs to include that in the local.l10n.xml parameter. Then it should work. Bob Stayton Thanks, Bob. I'm still not getting the olink text to reflect the changes I make in en.xml. I had misread