gmane.text.docbook.apps

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

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

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

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

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

XSL-FO to PPTX

honyk — 2013-05-11T13:38:40

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

FOP quirk

Alexey Neyman — 2013-05-10T23:23:04

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

How to create draft from an assembly?

Robert Fekete — 2013-05-10T12:23:44

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

Fwd: hide files

Ron Catterall — 2013-05-09T20:14:37

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.

hide files

Ron Catterall — 2013-05-08T20:34:05

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.

DocBook XSL snapshots are back

Bob Stayton — 2013-05-07T19:23:24

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

HTML Output viewed with Firefox and IE mutated vowel looks like " Ãœberblick" instead of "Überblick"

Petra Funke — 2013-05-07T11:52:50

How can I fix that. I use docbook 5 and the command 

 

xsltproc  --output  dmDOC_BH.html  /usr/share/xml/docbook/stylesheet/nwalsh5/1.76.1/epub/docbook.xsl  dmDOC_BH.xml

 

to convert to HTML.

 

PDF looks OK German!

The  header of my document looks like this: 

 

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE book SYSTEM "/home/petra/docbook/docbookpetra.dtd">

<book  lang="DE_DE">

 

 

Petra Funke

Dokumentation und Qualitätsicherung

DocuMatrix Output- und Informationstechnologie Consulting Gmbh

A-3441 Abstetten

 

 <mailto:markus.andreas< at >documatrix.com> petra.funke< at >documatrix.com

 <http://www.documatrix.com> www.documatrix.com

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

Shlomi Fish — 2013-05-06T17:23:52

Hi all,

dbtoepub appears to be broken on the latest docbook-xsl-ns-snapshot. How can
it be fixed? I'm on Mageia Linux 3 Cauldron and the xhtml-1_1 stylesheets
appear to be missing. I'm attaching the offending DocBook 5/XML file inside
a .zip file.

Regards,

Shlomi Fish

shlomif[The-Enemy]:$trunk/The-Enemy/the-enemy$ 
shlomif[The-Enemy]:$trunk/The-Enemy/the-enemy$ 
shlomif[The-Enemy]:$trunk/The-Enemy/the-enemy$ 
shlomif[The-Enemy]:$trunk/The-Enemy/the-enemy$
ruby /home/shlomif/Download/unpack/file/docbook/docbook-xsl-ns-snapshot/epub/bin/dbtoepub
-o English-Docbook/The-Enemy-English.epub
English-Docbook/PROCESSED_The-Enemy-English.db5.xml warning: failed to load
external entity
"/home/shlomif/Download/unpack/file/docbook/docbook-xsl-ns-snapshot/xhtml-1_1/docbook.xsl"
compilation error:
file /home/shlomif/Download/unpack/file/docbook/docbook-xsl-ns-snapshot/epub/docbook.xsl
line 21 element import xsl:import : unable to
load /home/shlomif/Download/unpack/file/docbook/docbook-xsl-ns-snapshot/xhtml-1_1/docbook.xsl
warning: failed to load external entity
"/home/shlomif/Download/unpack/file/docbook/docbook-xsl-ns-snapshot/xhtml-1_1/chunk-common.xsl"
compilation error:
file /home/shlomif/Download/unpack/file/docbook/docbook-xsl-ns-snapshot/epub/docbook.xsl
line 22 element import xsl:import : unable to
load /home/shlomif/Download/unpack/file/docbook/docbook-xsl-ns-snapshot/xhtml-1_1/chunk-common.xsl
warning: failed to load external entity
"/home/shlomif/Download/unpack/file/docbook/docbook-xsl-ns-snapshot/xhtml-1_1/chunk-code.xsl"
compilation error:
file /home/shlomif/Download/unpack/file/docbook/docbook-xsl-ns-snapshot/epub/docbook.xsl
line 23 element include xsl:include : unable to
load /home/shlomif/Download/unpack/file/docbook/docbook-xsl-ns-snapshot/xhtml-1_1/chunk-code.xsl /home/shlomif/Download/unpack/file/docbook/docbook-xsl-ns-snapshot/epub/bin/lib/docbook.rb:91:in
`render_to_epub': Could not render as .epub to
English-Docbook/The-Enemy-English.epub (cd
"/home/shlomif/tmp/.epubtmp1367860699.0057495" && xsltproc --stringparam
chunk.quietly 1 --stringparam callout.graphics.path images/callouts/
--stringparam callout.graphics.number.limit 15 --stringparam
callout.graphics.extension .png --stringparam base.dir OEBPS/  --stringparam
epub.metainf.dir META-INF/ --stringparam epub.oebps.dir OEBPS/
"/home/shlomif/Download/unpack/file/docbook/docbook-xsl-ns-snapshot/epub/docbook.xsl"
"/home/shlomif/Docs/Humour/The-Enemy/hg/The-Enemy/the-enemy/English-Docbook/.collapsed.PROCESSED_The-Enemy-English.db5.xml")
(RuntimeError)
from /home/shlomif/Download/unpack/file/docbook/docbook-xsl-ns-snapshot/epub/bin/lib/docbook.rb:43:in
`render_to_file'
from /home/shlomif/Download/unpack/file/docbook/docbook-xsl-ns-snapshot/epub/bin/dbtoepub:75:in
`block in <main>'
from /home/shlomif/Download/unpack/file/docbook/docbook-xsl-ns-snapshot/epub/bin/dbtoepub:64:in
`each'
from /home/shlomif/Download/unpack/file/docbook/docbook-xsl-ns-snapshot/epub/bin/dbtoepub:64:in
`<main>' shlomif[The-Enemy]:$trunk/The-Enemy/the-enemy$

Merging the stylesheet modules

Joshua Wulf — 2013-05-04T04:00:06

Webkit has an ugly and long-standing bug where it can't load xsl:imports via http. 

I've been working around this by doing server-side rendering, but I'm running into scalability limits. 

How theoretically possible/feasible is it for me to merge the modular Docbook xsl (I'm currently using DB4.5) down to a single megalithic file?

Am I dreaming?

- Josh

~ Kirtan is Life! ~
Sent from my Mobile Device

DocBook snapshot SVN problem

Bob Stayton — 2013-05-03T16:25:43

I'm investigating the problem with the DocBook XSL snapshot builds, and it 
seems SVN is having a
problem that I don't understand.

$ svn cleanup
svn: Write-lock stolen in 'contrib/tools/pawson'

$ svn update
svn: Working copy '.' locked
svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details)

And running "svn cleanup" does not remove the lock.

I get this error only on the snapshot machine, not my home machine.  So I 
think it is a problem with the snapshot machine's working copy.

Anyone know how to fix this?  I could probably check out a new working copy, 
but that takes awhile and I would rather fix it with some kind of unlock 
command.

Bob Stayton
Sagehill Enterprises
bobs< at >sagehill.net

EPUB2-Bugfixing

Thomas Schraitle — 2013-04-30T06:56:16

Hi,

if I'm not mistaken, the EPUB2 stylesheet isn't really maintained
anymore. Although there is EPUB3 available, I think there is still a
place for a good and stable EPUB2 solution. Especially if some
publishers still require the older version.

To cut a long story short: I would be happy to add/submit some bugfixes
and implement some missing features (like support for admonitions).  

However, I don't want to create any conflicts or problems so I hope
nobody objects if I do so. :)

Can I link directly to a WebHelp page?

Xmplar — 2013-04-29T14:19:47

I'd like to link into a specific WebHelp page that is formatted in 
frames. I've created SVG graphics with <a href> links, and want to go 
straight to a frameset page created with DocBook WebHelp in oXygen. I 
can link to the home page easily enough (index_frames.html) - is there a 
HTML "target" specification to then navigate to a page in that frameset? 
Or is it possible with Javascript?

converting DocBook to Confluence

robert — 2013-04-29T13:38:04

Dear all,

My technical documentation is developed using DocBook and then published
to many different formats using the DocBook XSL library, everything works
smoothly.

Now, I would like to publish some content developed in DocBook to a
Confluence-based portal. Confluence accepts its own XML format so I can of
course write XSL transformations by myself, but before I start I would like
to ask you if you have ever tried to convert DocBook to the one of
supported Confluence format. Are you aware of any existing tools that would
do the job?

Thanks,
Robert

JFYI: Observations on snapshots.docbook.org and SVN Commits

Thomas Schraitle — 2013-04-29T06:58:21

Hi,

not sure if the project owners know this already (or are fully aware),
but I've noticed that the archives on snapshots.docbook.org don't
contain the latest version (again). :)

Another issue: In former times, the latest change were printed below
the list of archive. This isn't shown anymore.

It seems, any commit doesn't create a new snapshot (or is running
late). Furthermore, I've observed that each commit prints a warning
message from the SVN post-commit hook. I can't remember its message,
but if I remember correctly, it has something to do with the migration
to SourceForge's new Allura system.

Just to let you know. Thanks!

Namespace issues with titlepage templates in slides

Alexey Neyman — 2013-04-29T06:44:37

Hi all,

I've tried using the stylesheets in slides directory; it seems that they are improperly 
declaring the namespaces for wrapping elements. Hence, in the output the 
respective elements (fo:block and div) are declared without a namespace, which 
leads to empty title pages in both XHTML and PDF outputs. 

Adding a namespace is possible either by passing a parameter to the stylesheet 
(<xsl:param name="ns"/>). The titlepage.xsl stylesheet tries to guess the namespace 
for wrapping elements by looking if any elements in the input are declared in the XSL-
FO or XHTML namespace. The templates for slides do not contain any elements in 
the target namespace, though.

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. Same with t:element - 
this is especially important, as that element may be in a non-DocBook namespace; for 
example, "DocBook slides" format declares elements in a separate namespace 
(dbs:slides, dbs:foil, etc.). Current titlepage.xsl cannot deal with template XML where 
DocBook elements are in non-default namespace - it outputs XPath expressions such 
as "d:d:title".

Also, it looks like some of the templates for the titlepages abuse the namespaces: for 
example, xhtml/titlepage.templates.xml declares default namespace as XHTML 
(xmlns="http://www.w3.org/1999/xhtml") but contains both DocBook elements 
(<title/>, <corpauthor/>, ...) as well as XHTML elements (<hr/>) in the default 
namespace.

Attached patches deal with these issues:

- titlepage.xsl.diff (patch for titlepage generation stylesheet):
  * New attribute on t:templates: t:copy-namespaces; contains the list of
    namespace prefixes to copy from the template to the resulting stylesheet
    (currently, titlepage.xsl just copies exsl: and d: prefixes from the
    titlepage.xsl itself); this results in appropriate namespace prefix being
    defined at the top of the resulting stylesheet rather than on every
    element.
  * New template, output.wrapper, outputs the wrapper element with the
    namespace as defined in the template - no "guessing" needed. The 'ns'
    parameter is no longer needed and is thus removed. Also, template for
    attributes in "copy.literal.atts" mode is no longer needed - also 
    removed.
  * Move common code for "document.order" and "stylesheet.order" templates
    into common templates, t.element.info and t.element.altinfo. Make these
    new templates also namespace-aware (e.g., if the element is in non-DocBook
    namespace, it does not make sense to check for DocBook-specific 'altinfo'
    names such as <artheader/>
  * New template, t.element.name, to be used in place of references to
    < at >t:element where this name is used to generate mode and attribute set
    names (strips namespace from < at >t:element)
  * Use local-name(.) instead of name(.) where d: prefix is output to the
    resulting stylesheet (otherwise, if DocBook elements are in non-default
    namespace in the template, stylesheet contains XPaths such as "d:d:title")
  * Generalize param:node template to support other XPath axes (but still,
    only at the beginning of an expression) and recognize elements in a
    namespace following axis specifier, if any. By default, only param:node
    is handled - but new attribute, < at >t:xpath-fixup, allows to apply this
    behavior to other param:* attributes (e.g., HTML templates also contain
    param:object which expects to be run through the same fixup).
  * Output a message and fail if t:titlepage-content contains any elements in
    non-DocBook namespace. This will indicate when customizations would need
    to be updated with proper namespace specifications.

- templates-namespace.diff (patch for templates in the DocBook XSL outputs):
  * epub3, html, xhtml, webhelp: add DocBook namespace with d: prefix, to
    separate from output namespace; declare XPath fixup to apply to
    param:object
  * fo: define default namespace to be DocBook; copy fo: namespace prefix
    definition to output; declare XPath fixup to apply to param:title
    (previously, this hack was hardcoded in the titlepage.xsl - but this
    template is the only one which uses param:title)
  * slides/fo: declare namespaces for DocBook, DocBook slides, copy namespaces
    for DocBook slides and XSL-FO; specify which (DocBook/DocBook slides)
    namespace applies to which element.
  * slides/xhtml: declare namespaces for DocBook, DocBook slides, copy
    namespace for DocBook slides; specify DocBook namespace on elements.

- generated.diff (diff for stylesheets generated with the above changes)
  * except for slides/fo and slides/xhtml; the changes are movement of the
    namespace declarations from individual elements to the stylesheet. The
    addition of the d:docinfo appears even if I regenerate stylesheets from
    templates in the unmodified sources. What is this <docinfo/>, by the way?
    It is not declared in the DocBook 4.x or 5.x schemas.

Regards,
Alexey.

---------------------------------------------------------------------
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

Combining legalnotice tags

Eric Nordlund — 2013-04-26T19:14:40

Hello. The source files for my company's books all have 4 legalnotice tags on them. This is fine in the PDF output, but in the HTML output I get 4 legal notice links on the front page.

Is there a way to funnel all of the legalnotice content into one legalnotice page and corresponding link in the final HTML output without changing all of my source files?

Thanks!

Eric Nordlund
Customer Documentation and Training
Cray Inc.
901 5th Ave
Seattle, WA 98164
(206)701-2232