gmane.text.docbook.apps

RE: HtmlHelp/CHM - Revision History+generate.revhistory.link - not visible in output

Kerry, Richard — 2013-05-24T09:33:28


So I may be the only person using HtmlHelp and the generate.revhistory.link and seeking to customize the resulting revhistory html page .....



And leaving aside the issue of exactly what the (very old and badly documented) MS Help Compiler is doing, and why it sort of works even if its input appears not to be correct .....



There would appear to be a fault in the default stylesheets for html-help generation.  If generate.revhistory.link is set, although the rh-prefixed html file is generated, no reference to the generated revhistory html file is generated in the [FILES] section in the hhp file.



Looking in htmlhelp-common.xsl I can see the code that generates the [FILES] section.  Though I can't follow how it works in full.

I would appreciate it if someone familiar with this process could explain how it works, and preferably provide a fix.



Once the process is fixed I can resume customizing the html.





Regards,

Richard.








[Blue line]
Richard Kerry
BNCS Engineer
T: +44 (0)20 82259063[X]<thismessage:/Body.htm#>
M: +44 (0)7812 325518[X]<thismessage:/Body.htm#>
Room EBX 301, BBC Television Centre, Wood Lane, London, W12 7RJ
richard.kerry< at >atos.net<https://webmail.siemens-it-solutions.com/owa/redir.aspx?C=9fb20d019e3e4cb99344d708709a3177&URL=mailto%3arichard.kerry%40atos.net>
uk.atos.net<https://webmail.siemens-it-solutions.com/owa/redir.aspx?C=9fb20d019e3e4cb99344d708709a3177&URL=http%3a%2f%2fuk.atos.net%2fen-uk%2f>
[Atos logo]
This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable
________________________________
From: Kerry, Richard [richard.kerry< at >atos.net]
Sent: 20 May 2013 14:22
To: DocBook Apps Mailing List ‎[docbook-apps< at >lists.oasis-open.org]‎
Subject: [docbook-apps] HtmlHelp/CHM - Revision History+generate.revhistory.link - not visible in output




I'm looking at the CHM/HtmlHelp output from my project.  (Using Saxon-6, Microsoft Html Help Compiler, and Ant to call them both)

I want to customize how the Revision History is displayed.  I would like to be able to show it linked from the title-page, using generate.revhistory.link.



If I copy the d:revhistory and d:revhistory/d:revision templates from html/block.xsl I can customize them with no problem.  However, that is relevant to "in-line" revision histories, ie within a <section>.  I would like to have the Revision History available linked from the title page, but in another page, which should be achievable using generate.revhistory.link.



However, if I copy the d:revhistory and d:revhistory/d:revision templates for mode="titlepage.mode" from html/titlepage.xsl I start getting problems.  (Note that at this stage I've made no changes to those templates so that can't be what's causing the problem)



The first problem I noticed was that merely copying the relevant templates out of the default stylesheet file and into my customization stylesheet file would break the result.  The Revision History link is available on the title page, but clicking it gives me a page "This program cannot display the webpage".  By looking at the html produced by the DocBook-Xsl transformation I know that a page with the Revision History has been generated, named rh-something.html.  However, it is not referenced by the .hhp file, which should list all the html files, shouldn't it ?   (It does list all the other html files)

That was where I'd got to last week.  Today I sat down to look at it again and I am now even more puzzled.

The .hhp file never contains a reference to the rh file !

Whether or not the resulting chm works there is no rh-something.html file listed in the .hhp file that has been produced by the DocBook stylesheets.

If I manually add the rh file, as generated by the transform, to the list in the hhp file, it then works.

Unfortunately I can't find any reference documentation for the Html Help Compiler (which is very old, and twice superseded.....) so I can't see whether it should contain some built-in rules for finding pages which aren't listed.



So, does anyone know :



1.  Why it works when not customized, despite the rh file not being listed in the hhp ?

2.  How the DocBook-XSL system is supposed to work for HtmlHelp; specifically the generation of the .hhp file and the writing of the reference for the rh-something file into the hhp.





Puzzledly,

Richard.







Richard Kerry
BNCS Engineer
T: +44 (0)20 82259063[X]<thismessage:/Body.htm#>
M: +44 (0)7812 325518[X]<thismessage:/Body.htm#>
Room EBX 301, BBC Television Centre, Wood Lane, London, W12 7RJ
richard.kerry< at >atos.net<mailto:richard.kerry< at >atos.net>
uk.atos.net<http://uk.atos.net/en-uk/>
This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable

Re: Assemblies in DocBook 5.1: generating multiple structure outputs using assemble.xml

2013-05-22T14:23:47

Hi Thomas,
Thanks for your help - that works as you suggest.

I'd still like to know if it's possible to produce assembled DocBook
versions of _all_ the structures in my assembly, just by invoking the
XSL file. Is that feasible?

I was under the impression that XSL processors could create multiple
files where necessary (like topic-maker-chunk.xsl is supposed to).
Ideally, I'd like it to create the assembled DocBook files named after
their structure IDs.

Graeme

On Wed, May 22, 2013, at 15:13, Thomas Schraitle wrote:

Re: Assemblies in DocBook 5.1: generating multiple structure outputs using assemble.xml

Thomas Schraitle — 2013-05-22T14:13:17

Hi Graeme,

On Wed, 22 May 2013 14:45:44 +0100
graeme< at >heliocentrik.net wrote:


Have you tried the parameter structure.id? The assemble.xsl stylesheet
contains the following comment:

  May be used to select one structure among several to  process

Perhaps you should try the structure.id parameter like this:

 xsltproc --stringparam structure.id  book1 \
   ~/docbook-xsl/assembly/assemble.xsl assembly-file.xml


Hope that helps.

Assemblies in DocBook 5.1: generating multiple structure outputs using assemble.xml

2013-05-22T13:45:44

Hi there,
My use case is that I want to maintain a single assembly file
per-project, containing all the <structure> elements which define my
document output. The problem I'm having is that XSLTproc (and the other
XSLT processors I've tried) only seem to generate assembled DocBook
files for the first <structure> element encountered, and the rest are
ignored.

My assembly file looks like:

<structure xml:id="article1">
<output renderas="article" />
<module resourceref="thing1"/>
    <module resourceref="thing2"/>
</structure>

<structure xml:id="book1">
    <output renderas="book" />
    <module resourceref="thing3"/>
    <module resourceref="thing4"/>    
</structure>

<structure xml:id="book2">
    <output renderas="book" />
    <module resourceref="thing3"/>
    <module resourceref="thing4"/>    
</structure>

When I run assemble.xml (version v 1.10 2012-04-10 07:56:58 from the
latest stylesheets), I'm invoking it like this:

xsltproc ~/docbook-xsl/assembly/assemble.xsl assembly-file.xml

In the output, I get the <article> element for 'article1', but 'book1'
and 'book2' are ignored.

Here are the details of the xsltproc tool I'm using:

Using libxml 20703, libxslt 10124 and libexslt 813
xsltproc was compiled against libxml 20703, libxslt 10124 and libexslt
813
libxslt 10124 was compiled against libxml 20703
libexslt 813 was compiled against libxml 20703

Thanks in advance for any guidance.

Graeme

HtmlHelp/CHM - Revision History+generate.revhistory.link - not visible in output

Kerry, Richard — 2013-05-20T13:22:06

I'm looking at the CHM/HtmlHelp output from my project. (Using Saxon-6, Microsoft Html Help Compiler, and Ant to call them both)

I want to customize how the Revision History is displayed. I would like to be able to show it linked from the title-page, using generate.revhistory.link.

If I copy the d:revhistory and d:revhistory/d:revision templates from html/block.xsl I can customize them with no problem. However, that is relevant to "in-line" revision histories, ie within a <section>. I would like to have the Revision History available linked from the title page, but in another page, which should be achievable using generate.revhistory.link.

However, if I copy the d:revhistory and d:revhistory/d:revision templates for mode="titlepage.mode" from html/titlepage.xsl I start getting problems. (Note that at this stage I've made no changes to those templates so that can't be what's causing the problem)

The first problem I noticed was that merely copying the relevant templates out of the default stylesheet file and into my customization stylesheet file would break the result. The Revision History link is available on the title page, but clicking it gives me a page "This program cannot display the webpage". By looking at the html produced by the DocBook-Xsl transformation I know that a page with the Revision History has been generated, named rh-something.html. However, it is not referenced by the .hhp file, which should list all the html files, shouldn't it ? (It does list all the other html files)

That was where I'd got to last week. Today I sat down to look at it again and I am now even more puzzled.

The .hhp file never contains a reference to the rh file !

Whether or not the resulting chm works there is no rh-something.html file listed in the .hhp file that has been produced by the DocBook stylesheets.

If I manually add the rh file, as generated by the transform, to the list in the hhp file, it then works.

Unfortunately I can't find any reference documentation for the Html Help Compiler (which is very old, and twice superseded.....) so I can't see whether it should contain some built-in rules for finding pages which aren't listed.

So, does anyone know :

1. Why it works when not customized, despite the rh file not being listed in the hhp ?

2. How the DocBook-XSL system is supposed to work for HtmlHelp; specifically the generation of the .hhp file and the writing of the reference for the rh-something file into the hhp.

Puzzledly,

Richard.

Richard Kerry
BNCS Engineer
T: +44 (0)20 82259063
M: +44 (0)7812 325518
Room EBX 301, BBC Television Centre, Wood Lane, London, W12 7RJ
richard.kerry< at >atos.net<mailto:richard.kerry< at >atos.net>
uk.atos.net<http://uk.atos.net/en-uk/>
This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable

Re: Page numbers in body.margin.outer

Bob Stayton — 2013-05-15T21:55:11

Hi Claudio,
This should get you started, with some comments:

<!-- Shift some of the page side margin to the body side margin to make room -->
<xsl:param name="page.margin.outer">.5in</xsl:param>
<xsl:param name="body.margin.outer">.25in</xsl:param>
<xsl:param name="region.outer.extent">12pt</xsl:param>
<!-- extend the side region over the header/footer regions -->
<xsl:param name="side.region.precedence">true</xsl:param>

<xsl:attribute-set name="region.outer.properties">
  <!-- By default, the side region reference-orientation is 90 so text is rotated to fit,
     so this sets it back to zero for upright numbers -->
  <xsl:attribute name="reference-orientation">0</xsl:attribute>
 <!-- But I don't think FOP supports "outside" yet -->
  <xsl:attribute name="text-align">outside</xsl:attribute>
  <xsl:attribute name="width">0.25in</xsl:attribute>
</xsl:attribute-set>

<xsl:attribute-set name="outer.region.content.properties">
  <!-- Put any text formatting attributes here --></xsl:attribute-set>

<xsl:template name="outer.region.content">
  <xsl:param name="pageclass" select="''"/>
  <xsl:param name="sequence" select="''"/>
  <xsl:param name="position" select="''"/>
  <xsl:param name="gentext-key" select="''"/>

  <!-- pageclass can be front, body, back -->
  <!-- sequence can be odd, even, first, blank -->
  <!-- position can be left, center, right -->

  <!-- Play with these settings to get them right.  I added the border just for visualization of the location -->
  <fo:block-container border="0.1pt solid blue" 
         height="3in" display-align="after" text-align="outside" width=".25in">
    <fo:block xsl:use-attribute-sets="outer.region.content.properties">
      <!-- this bit compensates for FOP's lack of text-align="outside" -->
       <xsl:attribute name="text-align">
        <xsl:choose>
          <xsl:when test="$sequence='odd' or $sequence='first'">end</xsl:when>
          <xsl:otherwise>start</xsl:otherwise>
        </xsl:choose>
      </xsl:attribute>
    <!-- and here is where the page number is specified -->
      <fo:page-number/>
    </fo:block>
  </fo:block-container>
</xsl:template>

Let me know if you have any questions.

Bob Stayton
Sagehill Enterprises
bobs< at >sagehill.net


From: Claudio Tubertini 
Sent: Sunday, May 12, 2013 3:52 AM
To: docbook-apps< at >lists.oasis-open.org 
Subject: [docbook-apps] Page numbers in body.margin.outer


I would like to put the page number (in chapters or articles) in the body.margin.outer (I believe this is the correct parameter, but I'm not sure), in the middle of the page, instead of usual place in footer or header. Can someone suggest me where to look for? I'm using FOP processor with Oxygen. 
Regards
Claudio Tubertini

Re: Box around the footer (re-post with images attached)

Bob Stayton — 2013-05-15T18:19:01

Hi Richard,
The 'foot.sep.rule' template can apply attributes to the fo:table that displays the footer content.  You probably used that to add the border around the whole footer.

To get the spacing you want, I recommend using margin properties in the fo:block element in the footer.content template.  That fo:block is used in each of the three table cells in the footer.   Something like:

<fo:template name="footer.content">
  ...
  <fo:block>
      <xsl:attribute name="border">0.1pt solid red</xsl:attribute>
      <xsl:attribute name="margin-left">6pt</xsl:attribute>
      <xsl:attribute name="margin-right">6pt</xsl:attribute>
      <xsl:attribute name="margin-top">3pt</xsl:attribute>
      <xsl:attribute name="margin-bottom">12pt</xsl:attribute>

      <xsl:choose>
          ...

You might define and use an attribute-set instead.  I added a border attribute just so you can see where the boundaries are, so you will want to remove that after testing.  

With the border turned on, you can experiment with padding too, but you will find that the FO space-resolution rules sometimes alter the margin to compensate for the padding. 

Bob Stayton
Sagehill Enterprises
bobs< at >sagehill.net


From: Kerry, Richard 
Sent: Wednesday, May 15, 2013 5:41 AM
To: DocBook Apps Mailing List ‎[docbook-apps< at >lists.oasis-open.org]‎ 
Subject: [docbook-apps] Box around the footer (re-post with images attached)




Ok - retrying this.  The images may appear in-line but I've attached the files in case they don't.

And I've added descriptions in case they still don't appear.



I've managed to get a border around my document's footer, using foot.sep.rule.

However, it isn't spaced how I want it and I can't get it to change in the way I want.





I'm trying to get (word footer.png):











The image shows a number of text items in the footer.  There is a box around all of them.
There is a space of a few millimetres/pixels (Looks like about 1mm) between the top of the text and the top line.
There is a slightly wider space between the right and left edges of the text and their respective border lines.
There is a gap between the bottom of the text and the bottom border line of roughly the height of one line of text.


but I'm getting (pdf footer.png):


 


There is a space of a few millimetres/pixels (Looks like about 2mm this time) between the top of the text and the top border line.
There is no significant space between the right and left edges of the text and their respective border lines (less than 1mm).
There is a space of a few millimetres/pixels (Looks like about 2mm this time) between the bottom of the text and the bottom border line.

(don't they say a picture is worth a thousand words - I reckon I've written about 150 here)


Note the lack of spacing at both left and right edges. Also the requirement for roughly one text line below the text showing here (some documents will have some text there).

I seem to get some effect by customizing footer.content.properties - that's how I've got the text to be grey.
However I don't seem to get any useful effect from the padding attributes, which are the ones I'd expect to need to use for this.
If I set "padding" I seem to get some padding added at the left edge, but not the other three. Even if I set all four of padding-left/right/top/bottom I only get space added at the left.

Can anyone advise what I need to do to get padding at right, left and bottom ?

I'm doing DocBook -> FO and then to PDF using FOP 1.1.

Regards,
Richard.


















Richard Kerry

BNCS Engineer


T: +44 (0)20 82259063 

M: +44 (0)7812 325518

Room EBX 301, BBC Television Centre, Wood Lane, London, W12 7RJ

richard.kerry< at >atos.net

uk.atos.net








This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable



--------------------------------------------------------------------------------



---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-apps-unsubscribe< at >lists.oasis-open.org
For additional commands, e-mail: docbook-apps-help< at >lists.oasis-open.org

Box around the footer (re-post with images attached)

Kerry, Richard — 2013-05-15T12:41:12

Ok - retrying this. The images may appear in-line but I've attached the files in case they don't.

And I've added descriptions in case they still don't appear.

I've managed to get a border around my document's footer, using foot.sep.rule.

However, it isn't spaced how I want it and I can't get it to change in the way I want.

I'm trying to get (word footer.png):

[X]

The image shows a number of text items in the footer. There is a box around all of them.
There is a space of a few millimetres/pixels (Looks like about 1mm) between the top of the text and the top line.
There is a slightly wider space between the right and left edges of the text and their respective border lines.
There is a gap between the bottom of the text and the bottom border line of roughly the height of one line of text.

but I'm getting (pdf footer.png):

[X]

There is a space of a few millimetres/pixels (Looks like about 2mm this time) between the top of the text and the top border line.
There is no significant space between the right and left edges of the text and their respective border lines (less than 1mm).
There is a space of a few millimetres/pixels (Looks like about 2mm this time) between the bottom of the text and the bottom border line.

(don't they say a picture is worth a thousand words - I reckon I've written about 150 here)

Note the lack of spacing at both left and right edges. Also the requirement for roughly one text line below the text showing here (some documents will have some text there).

I seem to get some effect by customizing footer.content.properties - that's how I've got the text to be grey.
However I don't seem to get any useful effect from the padding attributes, which are the ones I'd expect to need to use for this.
If I set "padding" I seem to get some padding added at the left edge, but not the other three. Even if I set all four of padding-left/right/top/bottom I only get space added at the left.

Can anyone advise what I need to do to get padding at right, left and bottom ?

I'm doing DocBook -> FO and then to PDF using FOP 1.1.

Regards,
Richard.

[Blue line]
Richard Kerry
BNCS Engineer
T: +44 (0)20 82259063
M: +44 (0)7812 325518
Room EBX 301, BBC Television Centre, Wood Lane, London, W12 7RJ
richard.kerry< at >atos.net<mailto:richard.kerry< at >atos.net>
uk.atos.net<http://uk.atos.net/en-uk/>
[Atos logo]
This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-apps-unsubscribe< at >lists.oasis-open.org
For additional commands, e-mail: docbook-apps-help< at >lists.oasis-open.org

Re: WARNING: cannot add < at >xml:base to node set root element. Relative paths may not work.

Lars Vogel — 2013-05-15T09:47:23

Thanks everyone for the reply. I'm not using Docbook 5 nor do I use
profile-docbook.xsl.
I'm also using saxon6.5.5 and the Docbook I'm processing is one big file
which I preprocessed with an XInclude Ant tasks.

I will try to investigate further and if I find out more, I post this to
the this group.

Thanks again everyone, Lars




2013/5/14 Alexey Neyman <stilor< at >att.net>

Re: WARNING: cannot add < at >xml:base to node set root element. Relative paths may not work.

Alexey Neyman — 2013-05-14T19:55:05

Indeed, I've just checked and Xerxes seems to have the same issue.

So, this is one caveat to keep in mind when processing modular DocBook 
documents with Saxon/Xerxes.

Regards,
Alexey.

On Tuesday, May 14, 2013 12:00:50 pm Bob Stayton wrote:

Re: WARNING: cannot add < at >xml:base to node set root element. Relative paths may not work.

Bob Stayton — 2013-05-14T19:00:50

I don't think Saxon itself supports XIncludes.  Saxon uses the Xerces parser 
with the XInclude function turned on:

http://www.saxonica.com/documentation/sourcedocs/controlling-parsing.html

The XInclude spec says that xml:base attributes must be relative to the 
closest ancestor xml:base. I'm pretty sure that is how Saxon 6 behaves.  If 
Saxon9 is generating xml:base attributes always relative to the top level, 
then that is not what the XInclude spec says, nor what the DocBook 
stylesheet expects.

Bob Stayton
Sagehill Enterprises
bobs< at >sagehill.net

--------------------------------------------------
From: "Alexey Neyman" <stilor< at >att.net>
Sent: Tuesday, May 14, 2013 10:25 AM
To: <docbook-apps< at >lists.oasis-open.org>
Cc: "Bob Stayton" <bobs< at >sagehill.net>; "Lars Vogel" <lars.vogel< at >gmail.com>
Subject: Re: [docbook-apps] WARNING: cannot add < at >xml:base to node set root 
element. Relative paths may not work.

Re: RE: Box around the footer

Stefan Knorr — 2013-05-14T17:28:14

Hi Richard,

On Di, 2013-05-14 at 16:46 +0000, Kerry, Richard wrote:

I see an Outlook Web Access login screen. So, no they don't seem to have
come through.

Hth, Stefan.

Re: WARNING: cannot add < at >xml:base to node set root element. Relative paths may not work.

Alexey Neyman — 2013-05-14T17:25:47

Hi Lars, Bob,

Just one point: xsltproc does xml:base fixup on nodesets included through 
XInclude, so inside the document there are xml:base elements added properly. 
However, Bob's point still stands: if the top-level document is in non-current 
directory, it will break the external references.

Speaking of Saxon, I am not sure if it does xml:base fixup properly on 
XIncluded modular documents from different directories. Originally, I was 
investigating a bug in libxml2 regarding xml:base fixup (pushed to master, 
will be in the next release), but I also tried Saxon. Here is a link to the 
thread on libxml2 mailing list (which has a small test case attached):

  https://mail.gnome.org/archives/xml/2013-April/msg00024.html

In brief, Saxon seems to emit xml:base relative to top-level document rather 
than to the most recent point of inclusion. DocBook stylesheets (at least, 
1.78.0 that I used) assume the location relative to the base of the including 
nodeset. xsltproc conforms to the expectations of DocBook stylesheets, and as 
far as I understand, to the XInclude specification.

Regards,
Alexey.

On Tuesday, May 14, 2013 09:01:37 am Bob Stayton wrote:

RE: Box around the footer

Kerry, Richard — 2013-05-14T16:46:17


I don't know what everyone else is seeing in this message ....

One one client (Outlook) I'm getting little red Xs telling me the image is not available.

On the other (webmail, using IE 9) I can see the images as I thought I was sending them.



If they haven't come through please let me know and I'll find some other way of sending them.





Uncertainly,

Richard.





Richard Kerry
BNCS Engineer
T: +44 (0)20 82259063
M: +44 (0)7812 325518
Room EBX 301, BBC Television Centre, Wood Lane, London, W12 7RJ
richard.kerry< at >atos.net<mailto:richard.kerry< at >atos.net>
uk.atos.net<http://uk.atos.net/en-uk/>
This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable
________________________________
From: Kerry, Richard [richard.kerry< at >atos.net]
Sent: 14 May 2013 17:12
To: DocBook Apps Mailing List ‎[docbook-apps< at >lists.oasis-open.org]‎
Subject: [docbook-apps] Box around the footer




I've managed to get a border around my document's footer, using foot.sep.rule.

However, it isn't spaced how I want it and I can't get it to change in the way I want.



I'm trying to get :



[X]


but I'm getting :


[X]

Note the lack of spacing at both left and right edges. Also the requirement for roughly one text line below the text showing here (some documents will have some text there).

I seem to get some effect by customizing footer.content.properties - that's how I've got the text to be grey.
However I don't seem to get any useful effect from the padding attributes, which are the ones I'd expect to need to use for this.
If I set "padding" I seem to get some padding added at the left edge, but not the other three. Even if I set all four of padding-left/right/top/bottom I only get space added at the left.

Can anyone advise what I need to do to get padding at right, left and bottom ?

I'm doing DocBook -> FO and then to PDF using FOP 1.1.

Regards,
Richard.






Richard Kerry
BNCS Engineer
T: +44 (0)20 82259063
M: +44 (0)7812 325518
Room EBX 301, BBC Television Centre, Wood Lane, London, W12 7RJ
richard.kerry< at >atos.net<mailto:richard.kerry< at >atos.net>
uk.atos.net<http://uk.atos.net/en-uk/>
This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable

Box around the footer

Kerry, Richard — 2013-05-14T16:12:44


I've managed to get a border around my document's footer, using foot.sep.rule.

However, it isn't spaced how I want it and I can't get it to change in the way I want.



I'm trying to get :



[https://webmail.siemens-it-solutions.com/OWA/attachment.ashx?id=RgAAAADuafvq2wn5ToY5TFygcdi1BwAxjteD9W0ARqkWij6loXgaAAAAAQlZAABhxn3HMwi9SbLUtlBySA26AAAVOvmVAAAJ&attcnt=1&attid0=EACLf%2bZZePPtSaIp6eKC8ubY&attcid0=7716d0a4-6acd-4cd0-af75-6cdb428b6975]


but I'm getting :


[https://webmail.siemens-it-solutions.com/OWA/attachment.ashx?id=RgAAAADuafvq2wn5ToY5TFygcdi1BwAxjteD9W0ARqkWij6loXgaAAAAAQlZAABhxn3HMwi9SbLUtlBySA26AAAVOvmVAAAJ&attcnt=1&attid0=EAAuTDbeBlA9QYoLDLUMY1bp&attcid0=a154a93e-4a37-4e49-b724-a60be5177ece]

Note the lack of spacing at both left and right edges. Also the requirement for roughly one text line below the text showing here (some documents will have some text there).

I seem to get some effect by customizing footer.content.properties - that's how I've got the text to be grey.
However I don't seem to get any useful effect from the padding attributes, which are the ones I'd expect to need to use for this.
If I set "padding" I seem to get some padding added at the left edge, but not the other three. Even if I set all four of padding-left/right/top/bottom I only get space added at the left.

Can anyone advise what I need to do to get padding at right, left and bottom ?

I'm doing DocBook -> FO and then to PDF using FOP 1.1.

Regards,
Richard.





[Blue line]
Richard Kerry
BNCS Engineer
T: +44 (0)20 82259063
M: +44 (0)7812 325518
Room EBX 301, BBC Television Centre, Wood Lane, London, W12 7RJ
richard.kerry< at >atos.net<mailto:richard.kerry< at >atos.net>
uk.atos.net<http://uk.atos.net/en-uk/>
[Atos logo]
This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable

Re: WARNING: cannot add < at >xml:base to node set root element. Relative paths may not work.

Bob Stayton — 2013-05-14T16:01:37

Hi Lars,
You should get that message only when two conditions are met:

1.  You are processing a DocBook 5 document with the non-namespaced stylesheets.
         or
    You are single-step profiling by using profile-docbook.xsl (probably your case).

and

2.  You are using xsltproc (which lacks an extension function to get the name of the current directory).

With either condition in (1), the document is preprocessed into an internal nodeset (a nodeset held in memory) before being processed by the stylesheets.  The internal nodeset loses all contact with the filesystem where the files originated, so the preprocessing template tries to add relative directory references into the internal nodeset by adding xml:base attributes to preserve the relative locations.  It uses an extension function to get the original base directory of the document, but xsltproc does not have a function to fetch that information, while Saxon and Xalan do.

So if you use modular doc and the modules are in various directories, that directory structure  information gets lost in the internal subset.  If your documents don't need such xml:base attributes, then it has no effect on your output.

You can avoid it by either using Saxon, or by using two-step profiling.

Bob Stayton
Sagehill Enterprises
bobs< at >sagehill.net


From: Lars Vogel 
Sent: Tuesday, May 14, 2013 7:13 AM
To: DocBook Apps 
Subject: [docbook-apps] WARNING: cannot add < at >xml:base to node set root element. Relative paths may not work.


Hello, 


since a while I get the following warning during the transformation with the docbook distribution:


WARNING: cannot add < at >xml:base to node set root element.  Relative paths may not work.



I'm not sure what triggers this warning, a Google search resulted in hints about Docbook V5.0 but I'm still using Docbook 4.5.


I'm currently using the docbook-xsl-1.77.1 distribution and I think (but I'm not sure) that I have this warning since I upgraded from 1.76. The output looks ok to me, but this warning does not create a warm fussy feeling. ;-)


Any hint how to get rid of this warning? 



Best regards, Lars

WARNING: cannot add < at >xml:base to node set root element. Relative paths may not work.

Lars Vogel — 2013-05-14T14:13:29

Hello,

since a while I get the following warning during the transformation with
the docbook distribution:

WARNING: cannot add < at >xml:base to node set root element.  Relative paths may
not work.

I'm not sure what triggers this warning, a Google search resulted in hints
about Docbook V5.0 but I'm still using Docbook 4.5.

I'm currently using the docbook-xsl-1.77.1 distribution and I think (but
I'm not sure) that I have this warning since I upgraded from 1.76. The
output looks ok to me, but this warning does not create a warm fussy
feeling. ;-)

Any hint how to get rid of this warning?

Best regards, Lars

Re: Fw: Namespace issues with titlepage templates in slides

Jirka Kosek — 2013-05-14T11:36:08


Indeed


But might be your code might be extended to handle this case as well and
emit warning message?


No, they are generated from the single source which currently is
docbook-xsl. During the build process correct namespace declarations and
d: prefixes are added into all XPath expressions and docbook-xsl-ns is
created.


Currently master one is non-ns version, but there is plan to reverse the
process in a due future.

Conversion is done by xslns-build Perl script in releasetools directory.

Jirka

Re: dbtoepub is broken on latest docbook-xsl-ns-snapshot

Shlomi Fish — 2013-05-12T11:09:16

Hi Bob and all,

On Sun, 12 May 2013 00:06:57 +0300
Shlomi Fish <shlomif< at >shlomifish.org> wrote:


Thanks! Using the 1.78.1 distribution appears to have made it work again.

Regards,

Shlomi Fish

Page numbers in body.margin.outer

Claudio Tubertini — 2013-05-12T10:52:32

I would like to put the page number (in chapters or articles) in the
body.margin.outer (I believe this is the correct parameter, but I'm not
sure), in the middle of the page, instead of usual place in footer or
header. Can someone suggest me where to look for? I'm using FOP processor
with Oxygen.
Regards
Claudio Tubertini

Re: dbtoepub is broken on latest docbook-xsl-ns-snapshot

Shlomi Fish — 2013-05-11T21:06:57

Hi Bob,

On Sat, 11 May 2013 13:02:29 -0700
"Bob Stayton" <bobs< at >sagehill.net> wrote:


Thanks for letting me know and for the advice about the workaround. I'm going
to try it.

Regards,

Shlomi Fish