From erich.steinboeck at gmail.com Sun Nov 15 13:48:29 2015 From: erich.steinboeck at gmail.com (=?UTF-8?Q?Erich_Steinb=C3=B6ck?=) Date: Sun, 15 Nov 2015 14:48:29 +0100 Subject: [publican-list] Publican on Windows: cannot build offline Message-ID: When working offline or during Sourceforge outages like the one yesterday evening I'm receiving the following Publican error: xsl:include : unable to load http://docbook.sourceforge.net/release/xsl/current/ fo/footnote.xsl I uninstalled and re-installed Publican (Windows installer) with Docbook selected, all other brands deselected, but wasn't offered any "local install" option. Windows Registry keys seem to be set correctly: WriteRegStr HKLM "Software\Publican" "" C:\Program Files (x86)\Publican WriteRegStr HKLM "Software\Publican" "dtd_path" "C:\Program Files (x86)\Publican\DocBook_DTD" WriteRegStr HKLM "Software\Publican" "xsl_path" "C:\Program Files (x86)\Publican\docbook-xsl-1.76.1" -------------- next part -------------- An HTML attachment was scrubbed... URL: From erich.steinboeck at gmail.com Sun Nov 15 14:02:50 2015 From: erich.steinboeck at gmail.com (=?UTF-8?Q?Erich_Steinb=C3=B6ck?=) Date: Sun, 15 Nov 2015 15:02:50 +0100 Subject: [publican-list] How to write Message-ID: I'm working on existing documentation, where hundreds of examples are defined like this: ~~~~ Xxxx class ~~~~ When building as PDF, this show up with two blank lines at the top, and another one at the bottom. ~~~~ +--------------- | | | instance = .Xxxx~new | instance~method | +--------------- ~~~~ By changing the markup to below, I can get rid of one blank line at the the top, and the one at the bottom. ~~~~ ~~~~ But to get rid of the remaining blank line at the top, I'd have to code as below, which I really don't like, as it makes the example XML difficult to read and maintain (code doesn't line up nicely any more) ~~~~ ~~~~ So I'm wondering whether Publican could be instructed to accept the initial markup, but without any surplus blank lines. -------------- next part -------------- An HTML attachment was scrubbed... URL: From erich.steinboeck at gmail.com Sun Nov 15 14:31:24 2015 From: erich.steinboeck at gmail.com (=?UTF-8?Q?Erich_Steinb=C3=B6ck?=) Date: Sun, 15 Nov 2015 15:31:24 +0100 Subject: [publican-list] How to avoid unwanted whitespace with Message-ID: I'm working on existing documentation with heavy indexing. The way that is coded will very often lead to unwanted whitespace (blank lines). I've read a lot about how to correctly index with Docbook/Publican, but I'm still unable to find an acceptable solution. Existing XML, which typically looks like this, will show up with an additional blank line between the section header and the included diagram. ~~~~
method method of Class method method of Class Returns .. ~~~~ Moving the into the (as shown below) will remove the blank line, but any <xref> links to this id will show up with a glaring trailing blank, even if I carefully orchestrate <indexterm> and <indexterm>. ~~~~ <section id="mthXxxx"><title>method<indexterm> <primary>method</primary> <secondary>of Class</secondary> </indexterm><indexterm> <primary>method</primary> <secondary>method</secondary> <tertiary>of Class</tertiary> </indexterm> ~~~~ Moving the into the following paragraph isn't a nice option either, as any links should really point to the heading, not (depending on the diagram size) maybe much further down. As I'm having the same issue with indexed examples without titles, where I cannot see *any *possibility to move the to, I'm wondering if Publican could be instructed to simply ignore whitespace that gets introduced with -------------- next part -------------- An HTML attachment was scrubbed... URL: