headers
Kerry, Richard | 20 May 2013 15:22
Favicon

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

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

Permalink | Reply | 0 comments |
headers
Kerry, Richard | 14 May 2013 18:12
Favicon

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 :

 


but I'm getting :
 


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

Permalink | Reply | 4 comments |
headers
Lars Vogel | 14 May 2013 16:13
Picon
Gravatar

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
Permalink | Reply | 5 comments |
headers
Claudio Tubertini | 12 May 2013 12:52
Picon
Gravatar

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
Permalink | Reply | 1 comment |
headers
honyk | 11 May 2013 15:38
Picon

XSL-FO to PPTX

Dear All,

I generate slides from db via XSL-FO into PDF. 

While this solution fullfills our internal needs, there is a request from
sales guys to enable editing capabilities for small customizations. They
prefer PowerPoint format.

This conversion is needed for approx. 10 presentations (each with ca 20
slides) per year. It is just a fraction of our outputs.

I've tried a new Adobe Acrobat XI PDF to PPTX conversion feature, but it
isn't mature yet and it requires further tweaking. I've tried several other
tools, but to be honest, all of them fall behind new Acrobat...

OOXML is too complex for creating a simple DocBook to PPTX conversion.
Additionaly I enjoy an automatic slide content overflowing to the next slide
during the XSL-FO to PDF conversion step which cannot be simulated in the
pure XSLT (to split the content into several PPTX slides).

I was hoping this PPTX output is already offered by some XSL-FO processor,
but I haven't found any.

Has anybody any experience with any slide-like editable format which could
be offered to them? Is there something better for PDF to PPTX conversion
than Acrobat?

Any hints are highly appreciated.

Thanks, Jan
Permalink | Reply | 0 comments |
headers
Alexey Neyman | 11 May 2013 01:23
Picon
Favicon
Gravatar

<menuchoice> FOP quirk

Hi all, and especially Bob (since you introduced the code below),

 

I am seeing a weird formatting artifact with FOP, where the arrow introduced between the parts of <menuchoice> sequence results in an increase of line height. It is especially visible where that line is a part of list item, as the list marker ends up being near the top of the line rather than in a middle. A screenshot is attached, and another one shows (with thin colored boxes) the height of the elements inside a <menuchoice>)

 

I traced this to the the following XSL code in fo/inline.xsl:

 

<xsl:variable name="mm.separator">

<xsl:choose>

<xsl:when test="($fop.extensions != 0 or $fop1.extensions != 0 ) and

contains($menuchoice.menu.separator, '&#x2192;')">

<fo:inline font-family="Symbol">

<xsl:copy-of select="$menuchoice.menu.separator"/>

</fo:inline>

</xsl:when>

<xsl:otherwise>

<xsl:copy-of select="$menuchoice.menu.separator"/>

</xsl:otherwise>

</xsl:choose>

</xsl:variable>

 

If I remove that fo:inline, <menuchoice> is formatted correctly. We don't use Symbol font, and we don't have it in fop.cfg. For that reason, we have $symbol.font.family set to empty value in our customization. Yet, this template bypasses the $symbol.font.family and attempts to use Symbol font directly. It maybe a font issue (having a glyph which exceeds the font size?), but the core issue is why DocBook XSL is attempting to use a font it wasn't configured to use?

 

I tried to dig the history what this workaround was trying to solve, but the commit message is not very descriptive:

 

Author: bobstayton

Date: Fri Apr 22 07:27:58 2005 UTC (8 years ago)

Changed paths: 1

Log Message:

Fix menuchoice.menu.separator for FOP.

 

Can you shed some light as to what issue this code tries to fix? Removing this <xsl:choice> and using $menuchoice.menu.separator seems to work fine for me (using FOP 1.1). If it is kept, is it possible to: add "and $symbol.font.family != ''" to <xsl:when/>, and set font-family to "{$symbol.font.family}"?

 

Regards,

Alexey.

 

 

 

If removal


---------------------------------------------------------------------
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
Permalink | Reply | 4 comments |
headers
Jirka Kosek | 10 May 2013 18:01
Picon
Favicon
Gravatar

Re: Fw: Namespace issues with titlepage templates in slides

On 8.5.2013 7:19, Bob Stayton wrote:

> Would have time to take a look at this?  It seems Alexey spent a
> great deal of time sorting out the namespace issues for the DocBook
> titlepage template system, and has proposed many improvements.  As
> far as I can tell, they make sense, but I think you should look at
> it.

Sure, I originally skipped message as from subject line I got impression
it's related to slides only.

> This issue, however, shows that the titlepage.xsl is not not fully
> namespace aware. First, it shouldn't "autoguess" the namespace for
> t:wrapper - instead, it should just discover the namespace referred
> to by the t:wrapper attribute.

Autoguessing is here just for backward compatibility. Ideally namespace
should be passed by ns parameter. Problems you have seen in slides
titlepages are caused by missing ns parameter in the build script.

> Attached patches deal with these issues:

Thanks for the patches. There are many good ideas in your code, but I'm
little bit worried about backward compatibility -- in past we have tried
very hard to keep old titlepage templates to work with newer versions of
stylesheets. I'm not sure whether this is still true with all your
proposed changes.

Also what's not clear to me is whether your patch will work with non-ns
version of stylesheets which is primarily targeted for DocBook V4.x.
Your code has several tests for DocBook namespace which suggests that
you target only ns version of stylesheets.

For example how titlepage will look like for for HTML (not XHTML, so no
namespace) for non-ns stylesheets (DocBook V4.x, again no namespace)?

Thanks,

				Jirka

--

-- 
------------------------------------------------------------------
  Jirka Kosek      e-mail: jirka <at> kosek.cz      http://xmlguru.cz
------------------------------------------------------------------
       Professional XML consulting and training services
  DocBook customization, custom XSLT/XSL-FO document processing
------------------------------------------------------------------
 OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep.
------------------------------------------------------------------
    Bringing you XML Prague conference    http://xmlprague.cz
------------------------------------------------------------------
Permalink | Reply | 2 comments |
headers
Robert Fekete | 10 May 2013 14:23
Favicon

How to create draft from an assembly?

Hi,

I have an assembly that is rendered as a book, and I'd like to create a draft 
version from it. However, it seems that the status="draft" attribute gets lost 
somewhere.

I assume that I should add the status attribute to the <structure> tag, but I 
haven't find it mentioned in the DocBook 5.1: The Definitive Guide.

Do the assembly stylesheets handle the status attribute or pass it to the 
underlying templates?

My assembly.xsl says it's version <!-- $Id: assemble.xsl,v 1.10 2012-04-10 
07:56:58 bobs Exp $ -->

Kind Regards,

Robert
Permalink | Reply | 1 comment |
headers
Ron Catterall | 9 May 2013 22:14

Fwd: hide files

My apologies to all, I sent this to the wrong list. Please forgive.

-------- Original Message --------
Subject: [docbook-apps] hide files
Date: Wed, 08 May 2013 15:34:05 -0500
From: Ron Catterall <ron <at> catterall.net>
Reply-To: ron <at> catterall.net
To: docbook-apps <at> lists.oasis-open.org

Probably a trivial query, but I can't find the answer:

I want to set BBedit so that when I open a file the files sidebar is
hidden, so I don't have to do View:Hide Files.
--

-- 
ron <at> catterall.net

---------------------------------------------------------------------
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
Permalink | Reply | 0 comments |
headers
Ron Catterall | 8 May 2013 22:34

hide files

Probably a trivial query, but I can't find the answer:

I want to set BBedit so that when I open a file the files sidebar is 
hidden, so I don't have to do View:Hide Files.
--

-- 
ron <at> catterall.net
Permalink | Reply | 0 comments |
headers
Bob Stayton | 7 May 2013 21:23

DocBook XSL snapshots are back

The DocBook XSL snapshot builds are working and available again:

   http://snapshots.docbook.org/

Thanks to David Cramer for fixing the filesystem problem on the snapshot 
build machine.

Bob Stayton
Sagehill Enterprises
bobs <at> sagehill.net
Permalink | Reply | 2 comments |

Gmane