RE: [docbook-apps] Pure JS WebHelp

[Wood Nick]

Hi Jan,

Thanks for the update.

Regards

Nick

-Original Message-
From: Jan Tosovsky [mailto:j.tosov...@email.cz] 
Sent: 05 July 2017 22:03
To: docbook-apps@lists.oasis-open.org
Subject: RE: [docbook-apps] Pure JS WebHelp 

On 2017-07-05 Wood Nick wrote:
> 
> I followed your demo on the above subject through docbook-apps and was 
> really impressed with what you have done, there were some calls for 
> you to put your customization on GitHub, I know at the time you were 
> busy, have you been able to upload the stylesheets, if so, could you 
> let me know where to find them.

I was busy with more urgent projects, but I believe in two weeks I could 
publish something.

Btw, the original link is not available any more, that beta version is now in 
production:
https://www.bilyujezd.cz/strucna-historie.html

This site is not a typical use case, but it is something I can show to the 
public.

Regards,

Jan


-
To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org


-
To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org

[docbook-apps] Pure JS WebHelp

[Wood Nick]

Hi Jan,

I followed your demo on the above subject through docbook-apps and was really 
impressed with what you have done, there were some calls for you to put your 
customization on GitHub, I know at the time you were busy, have you been able 
to upload the stylesheets, if so, could you let me know where to find them.

Regards

Nick

Nick Wood BSc(Hons) MInstLM
NATO Communications and Information Agency
AMDC2| Chief Document Engineer
Thier Mathias 1b, B-4690 Bassenge (Glons), Belgium
T: +32 42 899215  
E: nick.w...@ncia.nato.int W: www.ncia.nato.int



-
To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org

[docbook-apps] RE: Help generating custom Docbkx Maven Plugin?

[Wood Nick]

Hi Robert,

I build all my documents using the docbkx plugin, though as I have to build on 
an internal network my configuration is tailored to the environment.  I think 
your "first port of call" should be the docbkx-tools manual 
(http://docbkx-tools.sourceforge.net/docbkx-samples/manual.html) this tells you 
how to set up your POM, but also there is some excellent info on the docbkx 
forum (https://groups.google.com/forum/#!forum/docbkx-tools-users).

Cheers

Nick


From: Robert Crews [mailto:rcr...@hortonworks.com]
Sent: 27 February 2017 22:21
To: docbook-apps 
Subject: [docbook-apps] Help generating custom Docbkx Maven Plugin?


I'd like instructions for how to build a custom Docbkx maven plugin. On 
http://docbkx-tools.sourceforge.net/builder.html, the instructions seem to be:

  1.  Put a copy of docbook-xsl-[version].zip to the lib directory of your 
distribution
  2.  Configure the plugin with the version number of the Docbook XSL 
distribution
  3.  Configure a package name for the generated sources
  4.  Add some meta data for every type of output document you aim to generate 
using your plugin
  5.  If you want to know more, carefully study the sources of the Maven Docbkx 
Plugin itself

Does anyone have experience with this to fill in the gaps of my understanding? 
I am keen to get this working. Once I figure it out, I will contribute 
documentation back to the project so everyone can benefit.

Robert

RE: [docbook-apps] does not number...

[Wood Nick]

Hi,

I am by no means an expert in this area but from past experience, after 
installing saxonHE9-7-0-15J, you need to will need to place the Saxon JAR file 
on the CLASSPATH (export CLASSPATH=$CLASSPATH:/path/to/java/saxon9he.jar) and 
then you need to replace com.icl.saxon.StyleSheet with net.sf.saxon.Transform.

You should be aware that the HE edition of Saxon does have some features 
omitted, that were present in the earlier releases up to and including 9.1, and 
are now only available in the PE and EE variants of Saxon.

Regards

Nick

-Original Message-
From: Bob Stayton [mailto:b...@sagehill.net] 
Sent: 14 February 2017 04:06
To: Dave Pawson ; stim...@comcast.net
Cc: Docbook 
Subject: Re: [docbook-apps]  does not 
number...

Yes, DocBook XSL used to support syntax highlighting with xslthl, so I'll look 
into some more over the next couple of days.

Bob Stayton
Sagehill Enterprises
b...@sagehill.net

On 2/13/2017 12:14 PM, Dave Pawson wrote:
> Docbook at xslthl http://xslthl.sourceforge.net/
>
> Question for the community?
>Is this 'supported' by docbook-xsl?
>Is the author of this a part of the docbook community?
> AFAIK docbook does (used to?) support syntax hightlighting?
>
> regards
>
>
>
>
> On 13 February 2017 at 18:43,   wrote:
>> Hi,
>>
>> I thought I would summarize my progress on syntax highlighting and 
>> then ask about the sourceforge.net version of Saxon.
>>
>> My DocBook is "docbook-xsl-ns-1.79.1". My install of xslthl is 
>> "xslthl-2.1.3".
>>
>> When using the jar files which came with DocBook 5.1, and from xslthl 
>> 2.1.3, I can build without error and line numbering works, but syntax 
>> highlighting never occurs. My CLASSPATH for this case has these files 
>> in it based on various documents I found on the topic:
>> docbook-xsl-ns-1.79.1/tools/lib/saxon.jar
>> docbook-xsl-ns-1.79.1/extensions/saxon65.jar
>> xslthl-2.1.3/xslthl-2.1.3.jar
>>
>> The command to build is this after CLASSPATH export:
>> java \
>>   -Dxslthl.config=${XSLTHL}/highlighters/xslthl-config.xml \
>>   com.icl.saxon.StyleSheet \
>>   -o ${OBJ}/${TITLE}_monolithic.fo \
>>   ${OBJ}/${TITLE}_monolithic.xml \
>>   ${XSLT}/fo/docbook.xsl \
>>   use.extensions=1
>>
>> This is apparently version 6.5 of Saxon when using the jar files 
>> which come with DocBook 5.1.
>>
>> I've downloaded Saxon (saxonHE9-7-0-15J) from sourceforge.net, which 
>> provides these jar files (I assume saxon9he.jar is equivalent to the 
>> saxon.jar provided in DocBook 5.1, though DocBook 5.1 also provides a 
>> saxon9he.jar; I have no idea if saxon9-xqj.jar is involved):
>> saxon9he.jar
>> saxon9-test.jar
>> saxon9-xqj.jar
>>
>> I am unsure how I should rearrange my CLASSPATH to use XSLT 2 via 
>> saxon9he instead of XSLT 1 via the jar files included from DocBook 
>> 5.1. I've done some experimenting, but the DocBook version of 
>> saxon.jar seems to be required if com.icl.saxon.Stylesheet is to be 
>> found (I can't just substitute saxon9he.jar). Substitutions or 
>> removal of "extensions/saxon65.jar" fails
>> with:
>> No adjustColumnWidths function available.
>>
>> Is there a sample CLASSPATH or edit to the java command line to see 
>> how the XSLT 2 requirements can be filled? Related settings to enable 
>> highlighting are on, and language is correctly set (fop.xconf and 
>> fo/param.xsl are correctly configured).
>>
>> FYI, being able to syntax highlight and annotate would be a major 
>> benefit (and in some cases it is mandatory I be able to do this), so 
>> I have to keep digging in.
>>
>> Thanks!
>
>
>

-
To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org

[docbook-apps] RE: Printing the last revision number on the title page

[Wood Nick]

Hi Ekaterina,

Here is an extract of the customised version of titlepage.xsl, I use:




  
  
  
  


  
Release 

  
  





I have a number of fo:table-row entries, which I have had to omit, so you may 
have to play around with the positioning, or most probably someone has a better 
solution.

Regards

Nick

Nick Wood
NATO Communications and Information Agency
Air Command and Control Programme Office and Services | Chief Document 
Engineering and Production Section
Thier Mathias 1b, B-4690 Bassenge (Glons), Belgium
T: +32 42 899215
E: nick.w...@ncia.nato.int  W: www.ncia.nato.int





From: Shikareva, Ekaterina [mailto:eshikar...@luxoft.com] 
Sent: 24 January 2017 11:38
To: docbook-apps@lists.oasis-open.org
Subject: [docbook-apps] Printing the last revision number on the title page

Hello,

These lines in one of the recent answers in this group:

    
  Revision: 
    

made me also think about printing the last revision number on the title page in 
PDF output, but I cannot easily adapt this example to my situation.

As I understand, this example shows the .xsl title page customization. Could 
you please give me a hint how to implement the same from the very beginning: 
.xml title page customization, some corresponding element in docbook file 
itself, some customization layer modification?

Thank you very much!

-- 
Best regards,

Ekaterina Shikareva




This e-mail and any attachment(s) are intended only for the recipient(s) named 
above and others who have been specifically authorized to receive them. They 
may contain confidential information. If you are not the intended recipient, 
please do not read this email or its attachment(s). Furthermore, you are hereby 
notified that any dissemination, distribution or copying of this e-mail and any 
attachment(s) is strictly prohibited. If you have received this e-mail in 
error, please immediately notify the sender by replying to this e-mail and then 
delete this e-mail and any attachment(s) or copies thereof from your system. 
Thank you.

-
To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org

FW: [docbook-apps] Question on adjusting IDs for reused content

[Wood Nick]

Sorry, forgot to include the list in my reply to Janice.

Nick

From: Wood Nick
Sent: 05 January 2016 15:13
To: 'Janice Manwiller' <jan...@sqrrl.com>
Subject: RE: [docbook-apps] Question on adjusting IDs for reused content

Janice,

Is custom-docbook.xsl your fo customisation layer, if so, you probably have a 
customised common.xsl stylesheet above this, and that is where the object.id 
customisation should go.

Regards

Nick

From: Janice Manwiller [mailto:jan...@sqrrl.com]
Sent: 28 December 2015 21:05
To: docbook-apps@lists.oasis-open.org<mailto:docbook-apps@lists.oasis-open.org>
Subject: [docbook-apps] Question on adjusting IDs for reused content

I've been working on reusing content in the doc set I work on. The guides are 
in a single WebHelp.

- Using DocBook 5
- Output generated using the Maven docbkx plugin

As pointed out in the DocBook XSL guide, if you reuse content that has an 
identifier, then in the WebHelp output, the TOC generates the correct links. 
However, because those links all point to the same file, when you click any of 
those TOC links, the TOC selection bounces to the "first" instance. For 
example, you click a link in the Install Guide, and the TOC bounces to the 
entry in the Admin Guide.

To avoid the TOC "bouncing", the DocBook XSL reference included a suggested 
customization to have the generation process append numbers to subsequent 
instances:

http://www.sagehill.net/docbookxsl/DuplicateIDs.html#ModifyIdValues

I tried adding the template from this section to both custom-docbook.xsl (the 
main DocBook customization) and docbook-webhelp.xsl (the WebHelp 
customization), but it didn't have any affect in either place.

Am I putting the customization in the wrong place? Is there something else I'm 
missing?

Thanks,

Janice

RE: [docbook-apps] Paragraphs within list item jutting into page footer

[Wood Nick]

Janice,

I have had similar issues in the past of text bleeding into footers but since 
using FOP 1.1, I don’t recall any.  I also build with the maven-docbkx plugin 
but with a Nexus off-line repository, which means I have to occasionally update 
my Maven Central repository to get updated versions of FOP, etc.  I don’t know 
if you are in a similar position?

Regards

Nick


From: Janice Manwiller [mailto:jan...@sqrrl.com]
Sent: Wednesday, July 29, 2015 7:00 PM
To: Peter Desjardins
Cc: docbook-apps@lists.oasis-open.org
Subject: Re: [docbook-apps] Paragraphs within list item jutting into page footer

We use the maven docbkx plugin - all docs are generated using the build 
process. According to their doc, they use Apache FOP for PDF generation. They 
don't give a version.

I haven't made any customizations at all to ordered lists or list items. The 
only keep-together customization I added to was to prevent page breaks in table 
rows.

Janice

On Wed, Jul 29, 2015 at 11:28 AM, Peter Desjardins 
peter.desjardins...@gmail.commailto:peter.desjardins...@gmail.com wrote:
I'm wondering why the last listitem did not break to the next page. Have you 
applied any customization to the way orderedlists keep-together? Maybe 
temporarily turn off all your customizations and see what happens to the lists 
in the default PDF formatting?

I have very many lists with listitems that often include multiple para 
elements, programlistings, and other children. I have never seen any problem 
with listitems bleeding into page footers and have never needed to apply the 
dbfo-need processing instruction. So I would expect the correct breaking 
behavior to be fairly reliable on its own.

Maybe your FO processor could be part of the problem? I use Apache FOP 1.1. How 
is your FO processed?

Another troubleshooting technique I have used is to search the FO file produced 
by DocBook XSLT and find the corresponding elements in there. Some of the 
attributes on the list or whatever element is containing it might be giving the 
FO processor instructions that could lead to this situation. I usually open the 
FO in a text editor and search for some text strings in the content I'm looking 
for.

Good luck!

Peter



On Tue, Jul 28, 2015 at 9:25 PM, Janice Manwiller 
jan...@sqrrl.commailto:jan...@sqrrl.com wrote:
I had asked about this issue earlier, and thought I had found a solution, but 
unfortunately it's not working reliably.

On occasion, PDF pages do not break correctly within a list item. If the list 
item contains more than one paragraph, then the paragraphs can bleed into the 
page footer.

I had come across the dbfo-need option, which sometimes works, but not always.

The attached image shows an example of this happening.

Here is the source DocBook XML for the same excerpt.


listitem
paraTo use a column to add a new field to the source 
data, in the dropdown
list field, type the name of the new field, then 
press
keycapEnter/keycap./para
informalfigure
mediaobject
imageobject
imagedata scale=100

fileref=../img/ui_data_source_job_csv_new_field.png/
/imageobject
textobject
phraseEntering a new source field name 
for a CSV
column/phrase
/textobject
/mediaobject
/informalfigure
paraFor information on restrictions on field names, 
see xref

linkend=sqrrl-field-name-restrictions/./para
paraFor these new fields, Sqrrl infers the data type 
based on the values
in the file./para
?dbfo-need height=2in ?
paraThese new fields are not added to the source 
definition./para
/listitem
listitem
paraTo remove a column from the list, click its 
delete icon./para
/listitem
/orderedlist/para
So while I have the dbfo-need option set for the paragraph, it's still not 
causing the page to break.

Any ideas to get this to work reliably?

Thanks,

Janice




-
To unsubscribe, e-mail: 
docbook-apps-unsubscr...@lists.oasis-open.orgmailto:docbook-apps-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: 
docbook-apps-h...@lists.oasis-open.orgmailto:docbook-apps-h...@lists.oasis-open.org




--
Janice Manwiller
Principal Technical Writer
Sqrrl Data, Inc.
www.sqrrl.comhttp://www.sqrrl.com | @SqrrlData

[docbook-apps] RE: Docbook to IETM?

[Wood Nick]

Hi Norma,

I believe DocBook Webhelp meets the requirements for Type 1 Class 3 (and in 
some respects (e.g. search functionality) possible Class 4).

In addition to the type/class, you should also consider if other standards such 
as S1000D need to be met (most military/aerospace IETMs do), and what method of 
viewing is intended i.e. web browser or propriety viewer.

Regards

Nick

From: Emery, Norma (HGR) [mailto:nem...@whitehangar.net]
Sent: Monday, June 29, 2015 2:44 PM
To: Wood Nick; DocBook Apps Mailing List
Subject: RE: Docbook to IETM?

Hi, Nick,
This is a good question. I had done a bit of research into IETMs and it appears 
that there are multiple levels possible, each of which calls for a certain set 
of functionality. I don't yet have the specifics on which level is required. Do 
you perhaps know if Docbook - Webhelp or Docbook - Javahelp has been shown to 
meet any specific level of IETM requirements? In the meantime, I'm requesting 
more detail on the level and type required and will follow up when I have that 
information.
Kind Regards,
Norma

From: Wood Nick [mailto:nick.w...@ncia.nato.int]
Sent: Monday, June 29, 2015 3:00 AM
To: Emery, Norma (HGR); DocBook Apps Mailing List
Subject: RE: Docbook to IETM?

Hi Norma,

What specific functional requirements are you talking about i.e. what Type and 
Level of IETM do you need to produce?

Regards

Nick


From: Emery, Norma (HGR) [mailto:nem...@whitehangar.net]
Sent: 26 June 2015 21:46
To: DocBook Apps Mailing List
Subject: [docbook-apps] Docbook to IETM?

Docbook experts,

I'm looking for information on how we could render our Docbook content as IETM 
deliverables. Does anyone know of relevant tools (e.g., transform scenarios?) 
to meet specific IETM functional requirements?

Regards,

Norma Emery

[docbook-apps] RE: Docbook to IETM?

[Wood Nick]

Hi Norma,

What specific functional requirements are you talking about i.e. what Type and 
Level of IETM do you need to produce?

Regards

Nick


From: Emery, Norma (HGR) [mailto:nem...@whitehangar.net]
Sent: 26 June 2015 21:46
To: DocBook Apps Mailing List
Subject: [docbook-apps] Docbook to IETM?

Docbook experts,

I'm looking for information on how we could render our Docbook content as IETM 
deliverables. Does anyone know of relevant tools (e.g., transform scenarios?) 
to meet specific IETM functional requirements?

Regards,

Norma Emery

RE: [docbook-apps] WebHelp display issues - contents expand/collapse icons, intra-topic links

[Wood Nick]

Hi Janice,

I have similar issues not sure if  your first issue is the same, I have had 
problems with the toc as my generate.section.toc.level and chuck.section.depth 
were not in sync (I have set them both at 5 now).  Also, when creating a set, I 
include the same xml document (with an id) in different books at section level, 
as the use.id.as.filename is set at 1, this has led to  problems so I change 
use.id.as.filename  back to the default (0).

For the linking we have had exactly the same problem, it appears that JQuery is 
hampering here, we included a small piece of JS on the linkend test in 
inline.xsl as a work around, I can post separately if you want it.

Regards

Nick

From: Janice Manwiller [mailto:jan...@sqrrl.com]
Sent: Monday, March 30, 2015 6:00 PM
To: docbook-apps@lists.oasis-open.org
Subject: [docbook-apps] WebHelp display issues - contents expand/collapse 
icons, intra-topic links

I've run into a couple of minor issues with how the DocBook WebHelp is 
displayed. Has anyone else seen either of these, or have any fixes?


Expand/collapse icons in the contents become out of sync

If you display the WebHelp, expand and collapse nodes in the table of contents, 
go to another page, then return to the WebHelp, the expand/collapse icons can 
get out of sync with the expand/collapse status of the nodes. You can see the 
issue in the attached image.


Links within a topic do not jump to the target

I have a WebHelp topic that contains a link to a target ID (on a bridgehead) 
within that topic. When the topic displays, the link is visible, but the target 
is further down and so not immediately visible. When you click the link, it 
does not jump to the target. However, if you right click and open the link in a 
new tab, it opens to the correct location. I've tried using both xref and link, 
and get the same results.


Thanks,

Janice

RE: [docbook-apps] WebHelp display issues - contents expand/collapse icons, intra-topic links

[Wood Nick]

Janice, Barton,

As requested, add this fix to the linkend test in the inline.xsl, as follows:

xsl:when test=$linkend
 xsl:variable name=targets select=key('id',$linkend)/
xsl:variable name=target select=$targets[1]/

xsl:call-template name=check.id.unique
 xsl:with-param name=linkend select=$linkend/
/xsl:call-template

  a
xsl:apply-templates select=. mode=common.html.attributes/
xsl:call-template name=id.attribute/
 xsl:attribute name=href
xsl:call-template name=href.target
  xsl:with-param name=object select=$target/
 /xsl:call-template
/xsl:attribute

!--Add this fix to override JQuery--
xsl:attribute name=onclick
xsl:textdocument.location='/xsl:text
xsl:call-template name=href.target
xsl:with-param name=object select=$target/
/xsl:call-template
xsl:text';return false;/xsl:text
/xsl:attribute


xsl:apply-templates select=$target mode=html.title.attribute/
xsl:copy-of select=$content/

/a
/xsl:when

Regards

Nick

[docbook-apps] RE: Olinking for PDF generates absolute path

[Wood Nick]

Michael,

Have tried putting the document/ content in a sitemap and giving the 
directory structure for the output, see Bob's guidance at 
http://www.sagehill.net/docbookxsl/OlinkDetails.html.

Regards

Nick

From: Fritsch, Michael [mailto:michael.frit...@coremedia.com]
Sent: Thursday, December 11, 2014 3:49 PM
To: docbook-apps@lists.oasis-open.org
Subject: [docbook-apps] Olinking for PDF generates absolute path

Hello,

I try to get olinks between PDF manuals. I use XEP as the XSL-FO renderer and 
DocBook 1.78.1 stylesheets with some customizations.

I use the following olink database file:

?xml version=1.0 encoding=utf-8?
!DOCTYPE targetset [
!ENTITY importer SYSTEM importer-developer-en/target.db
!ENTITY operations SYSTEM operation-basics-en/target.db

]
targetset

document targetdoc=AImporterDeveloperManual_280878 
baseuri=importer-developer-en.pdf
  importer;
/document
document targetdoc=AOperationsBasicKnowledge-285398 
baseuri=operation-basics-en.pdf
  operations;
/document

/targetset

(Using baseuri=file:importer-developer-en.pdf does not work for me.)

In the PDF I get an absolute link as shown in the screenshot with the build 
directory as the prefix but what I want is a relative path.
Is there a setting to get it or do I something wrong?

Best regards,
Michael


Dr. Michael Fritsch
Technical Editor
tel +49.40.325587.214
fax +49.40.325587.999
michael.frit...@coremedia.commailto:michael.frit...@coremedia.com
CoreMedia AG
content | conversation | conversion
Ludwig-Erhard-Str. 18
20459 Hamburg, Germany
www.coremedia.comhttp://www.coremedia.com/
Executive Board: Gerrit Kolb (CEO), Dr. Klemens Kleiminger (CFO)
Supervisory Board: Prof. Dr. Florian Matthes (Chairman)
Trade Register: Amtsgericht Hamburg, HR B 76277

RE: [docbook-apps] Trouble formatting PDF TOC entries

[Wood Nick]

I should just like to add, in defence of the people who devote their time and 
energy to the docbkx-tools project, the issue is documented at  
https://code.google.com/p/docbkx-tools/wiki/FAQ - but sometimes you can’t see 
the wood for the trees.


From: Janice Manwiller [mailto:jan...@sqrrl.com] 
Sent: Tuesday, October 21, 2014 3:20 PM
To: docbook-apps@lists.oasis-open.org
Subject: Re: [docbook-apps] Trouble formatting PDF TOC entries

FYI, with help from Nick Wood I was finally able to figure out what was wrong 
and get this to work. Passing along in case it helps someone else.

The main problem was that I did not specify the DocBook 5 namespace. The 
namespace declaration was missing from the top of the custom stylesheet, and I 
didn't provide the namespace when specifying the items I wanted to customize.

So the when needed to be:

xsl:when test=self::d:chapter | self::d:preface | 
self::d:appendixbold/xsl:when

On Thu, Oct 16, 2014 at 1:18 PM, Barton Wright ordin...@gmail.com wrote:
Hi Janice,

Since some FO customizations do work and not others, the current issue has two 
probable causes:

• The most likely cause is that there is a docbkx parameter setting, or worse, 
an undeclared _default_ parameter setting, that is overriding your custom TOC 
template. The docbcx documentation is atrocious in general, but is worse than 
atrocious in declaring what parameters they set for you. You can get a list of 
those by running Maven in debug mode, which emits far too much information. 
Among that info is a long list of every single DocBook XSL parameter that 
docbkx sets as it prepares to build the Webhelp, with the value assigned to 
each. I saved a copy of that list somewhere and will e-mail it to you 
privately. 
• An unlikely cause is the order in which your customized templates are read in 
your FO customization file. In the XSL, one XSL file calls another, which calls 
another, and so on, and all this happens in a certain well-defined order. Your 
custom templates _should_ always overlay and replace the default templates of 
the same name, but sometimes one customized template inadvertently overrides or 
cancels another in the same layer. Thus, sometimes rearranging the order of 
templates in your customization layer makes a difference.

Best of luck,
Barton Wright

Unfortunately not anytime soon, since it was chosen for easy integration with 
the product build.

I've been able to make several customizations in the FO XSL file that do work, 
so it seems to be a bit hit or miss.

On Thu, Oct 16, 2014 at 12:43 PM, Bob Stayton b...@sagehill.net wrote:
Hi Janice,
Indeed, this behavior you see is strange.  When I copy your code into a basic 
customization layer and run it outside of Maven, it works properly.  I'm not 
sure what your reasons are for using Maven, but it seems to be getting in the 
way rather than helping.  Can you run the stylesheet outside of Maven using 
Saxon 6 or xsltproc?

Bob Stayton
Sagehill Enterprises
b...@sagehill.net

On 10/16/2014 6:29 AM, Janice Manwiller wrote:
Very strangeif the processing is ignoring toc.line.properties
completely, then why did I get the original error that xsl:choose was
required? Or is the validation of the XSL file separate from the actual
implementation?

On Thu, Oct 16, 2014 at 9:22 AM, Wood Nick nick.w...@ncia.nato.int
mailto:nick.w...@ncia.nato.int wrote:

    Hi Janice,

    __ __

    Comparing your customization to mine, there is little difference,
    other than the addition of the chapter/appendix number prefixing the
    title, and nothing here appears to be in conflict.  My observation
    remains extant regarding the processing, if maven did not complain
    about the choose element in your first run, it tells me that the
    toc.line.properties customization is being ignored.

    __ __

    Regards

    __ __

    Nick

    __ __

    *From:*Janice Manwiller [mailto:jan...@sqrrl.com
    mailto:jan...@sqrrl.com]
    *Sent:* Thursday, October 16, 2014 2:45 PM
    *To:* Fekete, Róbert
    *Cc:* Wood Nick; docbook-apps@lists.oasis-open.org
    mailto:docbook-apps@lists.oasis-open.org
    *Subject:* Re: [docbook-apps] Trouble formatting PDF TOC entries

    __ __

    It looks like the existing toc.line entry in the customization file
    does do some customization for appendices and chapters. Could that
    be interfering with the toc.line.properties attributes?

    __ __

       xsl:template name=toc.line
         xsl:param name=toc-context select=NOTANODE/

         xsl:variable name=id
           xsl:call-template name=object.id http://object.id/
         /xsl:variable

         xsl:variable name=label
           xsl:apply-templates select=. mode=label.markup/
         /xsl:variable

         fo:block xsl:use-attribute-sets=toc.line.properties

           fo:inline keep-with-next.within-line=always
             fo:basic-link internal-destination={$id}
               xsl:if test=self::appendix or self::chapter

RE: [docbook-apps] Trouble formatting PDF TOC entries

[Wood Nick]

Janice,

I build with maven docbkx; I also have the identical customization to you, and 
it works without issue.  If you like, you can send me your customized 
stylesheet (in full) and I will test it in my build environment, if you think 
that would help.

Regards

Nick


From: Barton Wright [mailto:ordin...@gmail.com]
Sent: Thursday, October 16, 2014 7:18 PM
To: Janice Manwiller
Cc: Bob Stayton; Wood Nick; Fekete, Róbert; docbook-apps@lists.oasis-open.org
Subject: Re: [docbook-apps] Trouble formatting PDF TOC entries

Hi Janice,

Since some FO customizations do work and not others, the current issue has two 
probable causes:


  *   The most likely cause is that there is a docbkx parameter setting, or 
worse, an undeclared _default_ parameter setting, that is overriding your 
custom TOC template. The docbcx documentation is atrocious in general, but is 
worse than atrocious in declaring what parameters they set for you. You can get 
a list of those by running Maven in debug mode, which emits far too much 
information. Among that info is a long list of every single DocBook XSL 
parameter that docbkx sets as it prepares to build the Webhelp, with the value 
assigned to each. I saved a copy of that list somewhere and will e-mail it to 
you privately.
  *   An unlikely cause is the order in which your customized templates are 
read in your FO customization file. In the XSL, one XSL file calls another, 
which calls another, and so on, and all this happens in a certain well-defined 
order. Your custom templates _should_ always overlay and replace the default 
templates of the same name, but sometimes one customized template inadvertently 
overrides or cancels another in the same layer. Thus, sometimes rearranging the 
order of templates in your customization layer makes a difference.

Best of luck,
Barton Wright

Unfortunately not anytime soon, since it was chosen for easy integration with 
the product build.

I've been able to make several customizations in the FO XSL file that do work, 
so it seems to be a bit hit or miss.

On Thu, Oct 16, 2014 at 12:43 PM, Bob Stayton 
b...@sagehill.netmailto:b...@sagehill.net wrote:
Hi Janice,
Indeed, this behavior you see is strange.  When I copy your code into a basic 
customization layer and run it outside of Maven, it works properly.  I'm not 
sure what your reasons are for using Maven, but it seems to be getting in the 
way rather than helping.  Can you run the stylesheet outside of Maven using 
Saxon 6 or xsltproc?

Bob Stayton
Sagehill Enterprises
b...@sagehill.netmailto:b...@sagehill.net

On 10/16/2014 6:29 AM, Janice Manwiller wrote:
Very strangeif the processing is ignoring toc.line.properties
completely, then why did I get the original error that xsl:choose was
required? Or is the validation of the XSL file separate from the actual
implementation?

On Thu, Oct 16, 2014 at 9:22 AM, Wood Nick 
nick.w...@ncia.nato.intmailto:nick.w...@ncia.nato.int
mailto:nick.w...@ncia.nato.intmailto:nick.w...@ncia.nato.int wrote:

Hi Janice,

__ __

Comparing your customization to mine, there is little difference,
other than the addition of the chapter/appendix number prefixing the
title, and nothing here appears to be in conflict.  My observation
remains extant regarding the processing, if maven did not complain
about the choose element in your first run, it tells me that the
toc.line.properties customization is being ignored.

__ __

Regards

__ __

Nick

__ __

*From:*Janice Manwiller [mailto:jan...@sqrrl.commailto:jan...@sqrrl.com
mailto:jan...@sqrrl.commailto:jan...@sqrrl.com]
*Sent:* Thursday, October 16, 2014 2:45 PM
*To:* Fekete, Róbert
*Cc:* Wood Nick; 
docbook-apps@lists.oasis-open.orgmailto:docbook-apps@lists.oasis-open.org

mailto:docbook-apps@lists.oasis-open.orgmailto:docbook-apps@lists.oasis-open.org
*Subject:* Re: [docbook-apps] Trouble formatting PDF TOC entries

__ __

It looks like the existing toc.line entry in the customization file
does do some customization for appendices and chapters. Could that
be interfering with the toc.line.properties attributes?

__ __

   xsl:template name=toc.line
 xsl:param name=toc-context select=NOTANODE/

 xsl:variable name=id
   xsl:call-template name=object.idhttp://object.id/ 
http://object.idhttp://object.id//
 /xsl:variable

 xsl:variable name=label
   xsl:apply-templates select=. mode=label.markup/
 /xsl:variable

 fo:block xsl:use-attribute-sets=toc.line.properties

   fo:inline keep-with-next.within-line=always
 fo:basic-link internal-destination={$id}
   xsl:if test=self::appendix or self::chapter
 xsl:call-template name=gentext
   xsl:with-param name=key select=local-name()/
 /xsl:call-template
 xsl:text /xsl:text

RE: [docbook-apps] Trouble formatting PDF TOC entries

[Wood Nick]

Janice,

Try xsl:choose/.

Regards

Nick

From: Janice Manwiller [mailto:jan...@sqrrl.com]
Sent: Thursday, October 16, 2014 1:45 PM
To: docbook-apps@lists.oasis-open.org
Subject: [docbook-apps] Trouble formatting PDF TOC entries

I'm trying to update the formatting of a PDF TOC. I mostly want to add 
additional space above and bold the chapter entries.

I found the following sample for toc.line.properties in the DocBook XSL 
reference, and as a test added it to my FO stylesheet.


xsl:attribute-set name=toc.line.properties

  xsl:attribute name=font-size10pt/xsl:attribute

  xsl:attribute name=font-weight

xsl:when test=self::chapter | self::preface | 
self::appendixbold/xsl:when

xsl:otherwisenormal/xsl:otherwise

  /xsl:attribute

/xsl:attribute-set
According to the guide, this should make all entries 10pt and chapter entries 
bold.

However, when I try to generate the DocBook output using our maven docbkx tool, 
it doesn't generate at all, and I get an error indicating that a when element 
must always be enclosed by a choose element.

If I add the choose element, like:

xsl:attribute-set name=toc.line.properties

  xsl:attribute name=font-size10pt/xsl:attribute

  xsl:attribute name=font-weight

   choose

xsl:when test=self::chapter | self::preface | 
self::appendixbold/xsl:when

xsl:otherwisenormal/xsl:otherwise

   /choose

  /xsl:attribute

/xsl:attribute-set
then the output generates, but there is no effect on the TOC formatting. The 
chapter entries aren't bold.

Any ideas on how to get this to work?

Thanks,

Janice

FW: [docbook-apps] Trouble formatting PDF TOC entries

[Wood Nick]

From: Wood Nick
Sent: Thursday, October 16, 2014 2:24 PM
To: 'Janice Manwiller'
Subject: RE: [docbook-apps] Trouble formatting PDF TOC entries

Janice,

If you could run maven docbkx with your original customization (i.e. choose 
instead of xsl:choose) and it did not fail, then your customization is not 
being called – I have just tested it.  Therefore, you need to look at your 
customization layer to make sure the customized stylesheets is being called.

Regards

Nick


From: Janice Manwiller [mailto:jan...@sqrrl.com]
Sent: Thursday, October 16, 2014 2:08 PM
To: Wood Nick
Cc
Subject: Re: [docbook-apps] Trouble formatting PDF TOC entries

Nope, that didn't do it. Still no bold for the chapter TOC entries.

On Thu, Oct 16, 2014 at 7:57 AM, Wood Nick 
nick.w...@ncia.nato.intmailto:nick.w...@ncia.nato.int wrote:
Janice,

Try xsl:choose/.

Regards

Nick

From: Janice Manwiller [mailto:jan...@sqrrl.commailto:jan...@sqrrl.com]
Sent: Thursday, October 16, 2014 1:45 PM
To: docbook-apps@lists.oasis-open.orgmailto:docbook-apps@lists.oasis-open.org
Subject: [docbook-apps] Trouble formatting PDF TOC entries

I'm trying to update the formatting of a PDF TOC. I mostly want to add 
additional space above and bold the chapter entries.

I found the following sample for toc.line.properties in the DocBook XSL 
reference, and as a test added it to my FO stylesheet.


xsl:attribute-set name=toc.line.properties

  xsl:attribute name=font-size10pt/xsl:attribute

  xsl:attribute name=font-weight

xsl:when test=self::chapter | self::preface | 
self::appendixbold/xsl:when

xsl:otherwisenormal/xsl:otherwise

  /xsl:attribute

/xsl:attribute-set
According to the guide, this should make all entries 10pt and chapter entries 
bold.

However, when I try to generate the DocBook output using our maven docbkx tool, 
it doesn't generate at all, and I get an error indicating that a when element 
must always be enclosed by a choose element.

If I add the choose element, like:

xsl:attribute-set name=toc.line.properties

  xsl:attribute name=font-size10pt/xsl:attribute

  xsl:attribute name=font-weight

   choose

xsl:when test=self::chapter | self::preface | 
self::appendixbold/xsl:when

xsl:otherwisenormal/xsl:otherwise

   /choose

  /xsl:attribute

/xsl:attribute-set
then the output generates, but there is no effect on the TOC formatting. The 
chapter entries aren't bold.

Any ideas on how to get this to work?

Thanks,

Janice



--
Janice Manwiller
Principal Technical Writer
Sqrrl Data, Inc.
www.sqrrl.comhttp://www.sqrrl.com | @SqrrlData

RE: [docbook-apps] Trouble formatting PDF TOC entries

[Wood Nick]

Hi Janice,

Comparing your customization to mine, there is little difference, other than 
the addition of the chapter/appendix number prefixing the title, and nothing 
here appears to be in conflict.  My observation remains extant regarding the 
processing, if maven did not complain about the choose element in your first 
run, it tells me that the toc.line.properties customization is being ignored.

Regards

Nick

From: Janice Manwiller [mailto:jan...@sqrrl.com]
Sent: Thursday, October 16, 2014 2:45 PM
To: Fekete, Róbert
Cc: Wood Nick; docbook-apps@lists.oasis-open.org
Subject: Re: [docbook-apps] Trouble formatting PDF TOC entries

It looks like the existing toc.line entry in the customization file does do 
some customization for appendices and chapters. Could that be interfering with 
the toc.line.properties attributes?

  xsl:template name=toc.line
xsl:param name=toc-context select=NOTANODE/

xsl:variable name=id
  xsl:call-template name=object.idhttp://object.id/
/xsl:variable

xsl:variable name=label
  xsl:apply-templates select=. mode=label.markup/
/xsl:variable

fo:block xsl:use-attribute-sets=toc.line.properties

  fo:inline keep-with-next.within-line=always
fo:basic-link internal-destination={$id}
  xsl:if test=self::appendix or self::chapter
xsl:call-template name=gentext
  xsl:with-param name=key select=local-name()/
/xsl:call-template
xsl:text /xsl:text
  /xsl:if
  xsl:if test=$label != ''
xsl:copy-of select=$label/
xsl:value-of select=$autotoc.label.separator/
  /xsl:if
  xsl:apply-templates select=. mode=titleabbrev.markup/
/fo:basic-link
  /fo:inline

  fo:inline keep-together.within-line=always
xsl:text /xsl:text
fo:leader leader-pattern=dots
  leader-pattern-width=3pt
  leader-alignment=reference-area
  keep-with-next.within-line=always/
xsl:text /xsl:text
fo:basic-link internal-destination={$id}
  fo:page-number-citation ref-id={$id}/
/fo:basic-link
  /fo:inline

/fo:block

 /xsl:template
  xsl:attribute-set name=toc.line.properties
xsl:attribute name=font-size10pt/xsl:attribute
xsl:attribute name=font-weight
  xsl:choose
xsl:when test=self::chapter | self::preface | 
self::appendixbold/xsl:when
xsl:otherwisenormal/xsl:otherwise
  /xsl:choose
/xsl:attribute
  /xsl:attribute-set

On Thu, Oct 16, 2014 at 8:25 AM, Fekete, Róbert 
robert.fek...@balabit.commailto:robert.fek...@balabit.com wrote:
Hi,

Your customization with Nick's correction should be working, that's what we 
also use. Do you have any other ToC-related customization that could interfere?

Robert

On Thu, Oct 16, 2014 at 2:07 PM, Janice Manwiller 
jan...@sqrrl.commailto:jan...@sqrrl.com wrote:
Nope, that didn't do it. Still no bold for the chapter TOC entries.

On Thu, Oct 16, 2014 at 7:57 AM, Wood Nick 
nick.w...@ncia.nato.intmailto:nick.w...@ncia.nato.int wrote:
Janice,

Try xsl:choose/.

Regards

Nick

From: Janice Manwiller [mailto:jan...@sqrrl.commailto:jan...@sqrrl.com]
Sent: Thursday, October 16, 2014 1:45 PM
To: docbook-apps@lists.oasis-open.orgmailto:docbook-apps@lists.oasis-open.org
Subject: [docbook-apps] Trouble formatting PDF TOC entries

I'm trying to update the formatting of a PDF TOC. I mostly want to add 
additional space above and bold the chapter entries.

I found the following sample for toc.line.properties in the DocBook XSL 
reference, and as a test added it to my FO stylesheet.


xsl:attribute-set name=toc.line.properties

  xsl:attribute name=font-size10pt/xsl:attribute

  xsl:attribute name=font-weight

xsl:when test=self::chapter | self::preface | 
self::appendixbold/xsl:when

xsl:otherwisenormal/xsl:otherwise

  /xsl:attribute

/xsl:attribute-set
According to the guide, this should make all entries 10pt and chapter entries 
bold.

However, when I try to generate the DocBook output using our maven docbkx tool, 
it doesn't generate at all, and I get an error indicating that a when element 
must always be enclosed by a choose element.

If I add the choose element, like:

xsl:attribute-set name=toc.line.properties

  xsl:attribute name=font-size10pt/xsl:attribute

  xsl:attribute name=font-weight

   choose

xsl:when test=self::chapter | self::preface | 
self::appendixbold/xsl:when

xsl:otherwisenormal/xsl:otherwise

   /choose

  /xsl:attribute

/xsl:attribute-set
then the output generates, but there is no effect on the TOC formatting. The 
chapter entries aren't bold.

Any ideas on how to get this to work?

Thanks,

Janice



--
Janice Manwiller
Principal Technical Writer
Sqrrl Data, Inc.
www.sqrrl.comhttp://www.sqrrl.com | @SqrrlData




--
Janice Manwiller
Principal Technical Writer
Sqrrl Data, Inc.
www.sqrrl.comhttp://www.sqrrl.com | @SqrrlData

RE: [docbook-apps] Coloring only internal links in FO?

[Wood Nick]

Mark,

Are you using the olink element in your source document, as I seem to recall in 
a post on the docbkx user forum that you was using link instead?

Regards

Nick


From: Mark Craig [mailto:mark.cr...@gmail.com]
Sent: Tuesday, June 03, 2014 9:41 PM
To: Bob Stayton
Cc: DocBook Apps
Subject: Re: [docbook-apps] Coloring only internal links in FO?

Hello again,

On the docbkx-tools list, Cedric suggested I try to reproduce the symptom of 
color showing up when xsl:param name=activate.external.olinks select=0 / 
without using docbkx-tools, but instead using the 1.78.1 stylesheets directly.

That's actually easier said than done.

With 
https://github.com/markcraig/DOCS-47/commit/6b5ca793474887655dcfe95d585a8e0cbf5af9e5
 I can generate PDFs that do include olinks, and the inter-book olink does turn 
out blue. But I'm not sure the olinks are getting resolved correctly.

Where could I find a simpler example to read so I can see how turning off 
activate.external.olinks does deactivate the coloring?

Regards,
Mark

On Fri, May 2, 2014 at 11:34 PM, Mark Craig 
mark.cr...@gmail.commailto:mark.cr...@gmail.com wrote:
Thanks Bob, Chris,

At least I see what the expected behavior is.

No doubt a problem somewhere in my own code.

Mark


On Fri, May 2, 2014 at 7:53 PM, Bob Stayton 
b...@sagehill.netmailto:b...@sagehill.net wrote:
Hi Mark,
Unless I'm misunderstanding what you are trying to do,
it should already work that way.  That is, if you are setting 
activate.external.olinks to zero, then the external olinks should render as 
plain text and not be formatted with the xref.properties attribute-set.  The 
xref.properties attribute-set is only applied when fo:basic-link is being 
output with @internal-destination, or if the element is an actual xref which 
also generates that output.

I just tried it with 1.78.1 and setting:

xsl:param name=activate.external.olinks select=0/
xsl:param name=current.docidshortbook/xsl:param


xsl:attribute-set name=xref.properties
  xsl:attribute name=color#47a/xsl:attribute
/xsl:attribute-set
In my PDF, the internal olinks are colored, but my external olinks are not (and 
are not active).

Bob Stayton
Sagehill Enterprises
b...@sagehill.netmailto:b...@sagehill.net


On 5/2/2014 12:07 AM, Mark Craig wrote:
Hello,

What is the right way with the 1.78.1 stylesheets to color only internal
links in FO?

I'd like to deactivate external olinks in PDF output with
activate.external.olinks, and then leave external links the same color as
surrounding text, but keep color on internal links (and URLs) because
without visual cues it can be difficult to notice that they're active.

At present I'm using the following customization, loosely based on
http://www.sagehill.net/docbookxsl/OlinkFormatting.html:

   xsl:attribute-set name=xref.properties
 xsl:attribute name=color#47a/xsl:attribute
   /xsl:attribute-set

This makes all the links blue... unfortunately including deactivated
external olinks.

I have tried setting olink.properties, too, with #000 as the color, but I
still see blue text in the PDF output for all links, including deactivated
external links.

Asking authors to add more attributes to external links is something I'd
like to avoid.

Thanks in advance for your time and your help.

Regards,
Mark

RE: [docbook-apps] Coloring only internal links in FO?

[Wood Nick]

Mark,

Then I doubt the xsl:param name=activate.external.olinks select=0 / will 
work.  Have you tried linking using olink targetdoc=”foodoc” 
targetptr=”foochap /, if you haven’t there are some additional actions 
required such as generating the target data files.

I have a sample (on an internal network) if you need it.

Regards

Nick

From: Mark Craig [mailto:mark.cr...@gmail.com]
Sent: Wednesday, June 04, 2014 10:16 AM
To: Wood Nick
Cc: Bob Stayton; DocBook Apps
Subject: Re: [docbook-apps] Coloring only internal links in FO?

Hi Nick,

The sample uses link with xlink:role set:




link xlink:href=book#chapter



  xlink:show=new



  xlink:role=http://docbook.org/xlink/role/olink;chapter/link



Regards,
Mark

On Wed, Jun 4, 2014 at 9:12 AM, Wood Nick 
nick.w...@ncia.nato.intmailto:nick.w...@ncia.nato.int wrote:
Mark,

Are you using the olink element in your source document, as I seem to recall in 
a post on the docbkx user forum that you was using link instead?

Regards

Nick


From: Mark Craig [mailto:mark.cr...@gmail.commailto:mark.cr...@gmail.com]
Sent: Tuesday, June 03, 2014 9:41 PM
To: Bob Stayton
Cc: DocBook Apps
Subject: Re: [docbook-apps] Coloring only internal links in FO?

Hello again,

On the docbkx-tools list, Cedric suggested I try to reproduce the symptom of 
color showing up when xsl:param name=activate.external.olinks select=0 / 
without using docbkx-tools, but instead using the 1.78.1 stylesheets directly.

That's actually easier said than done.

With 
https://github.com/markcraig/DOCS-47/commit/6b5ca793474887655dcfe95d585a8e0cbf5af9e5
 I can generate PDFs that do include olinks, and the inter-book olink does turn 
out blue. But I'm not sure the olinks are getting resolved correctly.

Where could I find a simpler example to read so I can see how turning off 
activate.external.olinks does deactivate the coloring?

Regards,
Mark

On Fri, May 2, 2014 at 11:34 PM, Mark Craig 
mark.cr...@gmail.commailto:mark.cr...@gmail.com wrote:
Thanks Bob, Chris,

At least I see what the expected behavior is.

No doubt a problem somewhere in my own code.

Mark


On Fri, May 2, 2014 at 7:53 PM, Bob Stayton 
b...@sagehill.netmailto:b...@sagehill.net wrote:
Hi Mark,
Unless I'm misunderstanding what you are trying to do,
it should already work that way.  That is, if you are setting 
activate.external.olinks to zero, then the external olinks should render as 
plain text and not be formatted with the xref.properties attribute-set.  The 
xref.properties attribute-set is only applied when fo:basic-link is being 
output with @internal-destination, or if the element is an actual xref which 
also generates that output.

I just tried it with 1.78.1 and setting:

xsl:param name=activate.external.olinks select=0/
xsl:param name=current.docidshortbook/xsl:param


xsl:attribute-set name=xref.properties
  xsl:attribute name=color#47a/xsl:attribute
/xsl:attribute-set
In my PDF, the internal olinks are colored, but my external olinks are not (and 
are not active).

Bob Stayton
Sagehill Enterprises
b...@sagehill.netmailto:b...@sagehill.net


On 5/2/2014 12:07 AM, Mark Craig wrote:
Hello,

What is the right way with the 1.78.1 stylesheets to color only internal
links in FO?

I'd like to deactivate external olinks in PDF output with
activate.external.olinks, and then leave external links the same color as
surrounding text, but keep color on internal links (and URLs) because
without visual cues it can be difficult to notice that they're active.

At present I'm using the following customization, loosely based on
http://www.sagehill.net/docbookxsl/OlinkFormatting.html:

   xsl:attribute-set name=xref.properties
 xsl:attribute name=color#47a/xsl:attribute
   /xsl:attribute-set

This makes all the links blue... unfortunately including deactivated
external olinks.

I have tried setting olink.properties, too, with #000 as the color, but I
still see blue text in the PDF output for all links, including deactivated
external links.

Asking authors to add more attributes to external links is something I'd
like to avoid.

Thanks in advance for your time and your help.

Regards,
Mark

[docbook-apps] RE: olink Difficulties in Maven Project

[Wood Nick]

Hi Sean,

I have had a quick look at your POM and notice that the data files 
targetsFilename and target database document targetDatabaseDocument have 
the same names.  I would expect to have a db file for each document but only 
one common target database document for the project.  Can you attach these 
documents?

Regards

Nick

From: Sean Smitz [mailto:ssm...@cssiinc.com]
Sent: Friday, December 27, 2013 2:28 PM
To: docbook-apps@lists.oasis-open.org
Subject: [docbook-apps] olink Difficulties in Maven Project

I introduced my current project at work to DocBook for creating our user's 
guide. We have now split into two separate documents and I'm trying to get 
cross-linking between the documents working. However, the xincludes seems to 
causing some kind of infinite looping? Processing for the analyst guide never 
finishes (where I have my single test olink). Processing for PDFs is still 
disabled. I've included updated src's My one and only response on StackExchange 
indicates I may have hit on a bug... Thanks in advance,

Sean

RE: [docbook-apps] Olinks in PDF missing valid destination?

[Wood Nick]

Hi Bob, List,

I don't know if this a new thread or a continuation of what has been discussed 
below.  I set up some olinks on a set of very simple documents for testing 
purposes (only transformed to pdf at this stage) and they were working fine.  

However, I have now incorporated olinks into some larger documents and the pdf 
output is not as anticipated; in that following the occurrence of an xref 
element, no heading or para text is displayed for the remainder of that chapter 
- I do get the gentext of the first and subsequent cross-references and I do 
still get heading numbers, bullets, etc.  When I remove either the olink or the 
xref the document renders as expected.  I did think that it may have been a 
problem in my customization layer but I get the same results with the standard 
1.72.0 stylesheets.  I also tested with the link element, when the link is an 
empty element I get the same problem, when the link element contains text, I do 
not.

As mentioned previously, I am using docbkx-tools 2.0.14 and FOP 1.0 with the 
1.72.0 stylesheets.  I appreciate the issue may be with my tool chain and not 
the stylesheets and I have searched the web for other instances of this 
occurrence but cannot find any,  I was wondering if you or anyone else in the 
community had observed such behavior and could provide a fix.

Regards

Nick


-Original Message-
From: Bob Stayton [mailto:b...@sagehill.net] 
Sent: Saturday, October 26, 2013 1:16 AM
To: Alexey Neyman; docbook-apps@lists.oasis-open.org
Cc: Wood Nick; Mark Craig
Subject: Re: [docbook-apps] Olinks in PDF missing valid destination?

Excellent, thanks for tracking that down and providing the fix.

Bob Stayton
Sagehill Enterprises
b...@sagehill.net

--
From: Alexey Neyman sti...@att.net
Sent: Friday, October 25, 2013 11:01 AM
To: docbook-apps@lists.oasis-open.org
Cc: Wood Nick nick.w...@ncia.nato.int; Bob Stayton 
b...@sagehill.net; Mark Craig mark.cr...@gmail.com
Subject: Re: [docbook-apps] Olinks in PDF missing valid destination?

 Hi Bob,

 Looks like the stylesheets could produce invalid link url(#dest=) if
 $fop1.extensions=1 and $insert.olink.pdf.frag=0. In that case, 
 make.olink.href template generates a string without '#something' 
 anchor. The code in olink template in fo/xref.xsl then tries to parse 
 this string as follows and
 fails:

  xsl:variable name=mybeg select=substring-before($href,'#')/
  xsl:variable name=myend select=substring-after($href,'#')/
  fo:basic-link
 external-destination=url({concat($mybeg,'#dest=',$myend)})
  xsl:use-attribute-sets=olink.properties
xsl:copy-of select=$hottext/
  /fo:basic-link

 If the $href does not contain #, both $mybeg and $myend would be 
 empty, leading to invalid URL '#dest='. Fix committed in r9825.

 Regards,
 Alexey.


 On Friday, October 25, 2013 12:37:54 am Wood Nick wrote:
 Hi Bob,

 I am using docbkx-tools 2.0.14 with the 1.72.0 stylesheets.  You are 
 correct, setting insertOlinkPdfFrag1/insertOlinkPdfFragin the POM 
 is the same as param name=insert.olink.pdf.frag select=1/ in 
 the stylesheet.  I am using FOP 1.0 (we run Nexus behind a firewall 
 and so updates are a challenge) which does not appear to support 
 fragment identifiers.  From your response below I assume FOP 1.1 does?

 Regards

 Nick



 From: Mark Craig [mailto:mark.cr...@gmail.com]
 Sent: Thursday, October 24, 2013 8:52 PM
 To: Bob Stayton
 Cc: Wood Nick; DocBook Apps
 Subject: Re: [docbook-apps] Olinks in PDF missing valid destination?

 Hi Bob,

 What I observed with insertOlinkPdfFrag left undefined -- I'm 
 assuming that means insert.olink.pdf.frag is 0 -- I was getting 
 external-destination=url(#dest=) in the .fo. No file name, no fragment.

 I think docbkx-tools 2.0.14 is picking up version 1.76.1 stylesheets. 
 What
 I didn't do is get the stylesheets and try without docbkx-tools.

 Regards,
 Mark

 On Thu, Oct 24, 2013 at 7:46 PM, Bob Stayton 
 b...@sagehill.netmailto:b...@sagehill.net wrote: Hi Mark,
 Can you clarify one point for me?   When insertOlinkPdfFrag is not set 
 to
 1, does not properly resolved mean the link can open the other PDF 
 document but not scroll to the proper location, or does it not open 
 the other PDF at all?  I would expect the former.

 I'm not a user of docbkx-tools, but I presume setting 
 insertOlinkPdfFrag is the same as setting the DocBook XSL 
 stylesheet parameter named 'insert.olink.pdf.frag', right?  That 
 parameter's default value should probably be 1, now that all XSL-FO 
 processors support the fragment identifiers.

 Bob Stayton
 Sagehill Enterprises
 b...@sagehill.netmailto:b...@sagehill.net

 From: Mark Craigmailto:mark.cr...@gmail.com
 Sent: Thursday, October 24, 2013 6:00 AM
 To: Wood Nickmailto:nick.w...@ncia.nato.int ; DocBook 
 Appsmailto:docbook-apps@lists.oasis-open.org Subject: Re:
 [docbook-apps]
 Olinks in PDF missing valid destination?

 By the way,

 When I want to resolve olinks between PDF

RE: [docbook-apps] Olinks in PDF missing valid destination?

[Wood Nick]

Hi Bob,

I am using docbkx-tools 2.0.14 with the 1.72.0 stylesheets.  You are correct, 
setting insertOlinkPdfFrag1/insertOlinkPdfFragin the POM is the same as 
param name=insert.olink.pdf.frag select=1/ in the stylesheet.  I am using 
FOP 1.0 (we run Nexus behind a firewall and so updates are a challenge) which 
does not appear to support fragment identifiers.  From your response below I 
assume FOP 1.1 does?

Regards

Nick



From: Mark Craig [mailto:mark.cr...@gmail.com]
Sent: Thursday, October 24, 2013 8:52 PM
To: Bob Stayton
Cc: Wood Nick; DocBook Apps
Subject: Re: [docbook-apps] Olinks in PDF missing valid destination?

Hi Bob,

What I observed with insertOlinkPdfFrag left undefined -- I'm assuming that 
means insert.olink.pdf.frag is 0 -- I was getting 
external-destination=url(#dest=) in the .fo. No file name, no fragment.

I think docbkx-tools 2.0.14 is picking up version 1.76.1 stylesheets. What I 
didn't do is get the stylesheets and try without docbkx-tools.

Regards,
Mark

On Thu, Oct 24, 2013 at 7:46 PM, Bob Stayton 
b...@sagehill.netmailto:b...@sagehill.net wrote:
Hi Mark,
Can you clarify one point for me?   When insertOlinkPdfFrag is not set to 1, 
does not properly resolved mean the link can open the other PDF document but 
not scroll to the proper location, or does it not open the other PDF at all?  I 
would expect the former.

I'm not a user of docbkx-tools, but I presume setting insertOlinkPdfFrag is 
the same as setting the DocBook XSL stylesheet parameter named 
'insert.olink.pdf.frag', right?  That parameter's default value should probably 
be 1, now that all XSL-FO processors support the fragment identifiers.

Bob Stayton
Sagehill Enterprises
b...@sagehill.netmailto:b...@sagehill.net

From: Mark Craigmailto:mark.cr...@gmail.com
Sent: Thursday, October 24, 2013 6:00 AM
To: Wood Nickmailto:nick.w...@ncia.nato.int ; DocBook 
Appsmailto:docbook-apps@lists.oasis-open.org
Subject: Re: [docbook-apps] Olinks in PDF missing valid destination?

By the way,

When I want to resolve olinks between PDF documents, it looks like I also need 
insertOlinkPdfFrag1/insertOlinkPdfFrag.

Otherwise external-destinations are not properly resolved (though according to 
Olink debug messages they are resolved).

Again, I'm seeing this behavior with 1.76.1.

Regards,
Mark

On Oct 23, 2013, at 3:38 PM, Mark Craig wrote:


Hi Nick,

Thanks very much for your help.

Following your suggestion does the trick:

currentDocidbook/currentDocid

As a result, the link gets resolved as an internal-destination in the .fo, and 
this works fine in the PDF.

fo:basic-link internal-destination=chapterfo:inlinelink to the next 
chapter/fo:inline/fo:basic-link.

Regards,
Mark

On Oct 23, 2013, at 2:35 PM, Wood Nick wrote:


Mark,

I do not pretend to be an expert on this - I setup my pdf olinks using Bob's 
excellent book plus some guidance you have posted in the past.  However, have 
you tried adding currentDocid/ in the configuration/ of your POM and then 
using the sitemap in your olinkdb.xml (as I believe this provide the location 
of the documents).

Regards

Nick


From: Mark Craig [mailto:mark.cr...@gmail.commailto:mark.cr...@gmail.com]
Sent: Wednesday, October 23, 2013 10:11 AM
To: DocBook Apps
Subject: [docbook-apps] Olinks in PDF missing valid destination?

Hello,

In the past I have successfully set up Olink resolution for HTML.

I have read and tried to implement
http://www.sagehill.net/docbookxsl/OlinkPrintOutput.html#PdfLinkingSetup
But I'm not managing to do the same for PDF.

A clickable link of the Olink is there in the PDF, but with no valid 
destination.

This is with docbkx-tools 2.0.14, so DocBook XSL 1.76.1 and FOP 1 (I think 1.1).

My little test is at https://github.com/markcraig/DOCS-47.
(There's only one Olink, in the para at line 20 of 
book.xmlhttps://github.com/markcraig/DOCS-47/blob/master/src/docbkx/book.xml#L20.)

The main part of the target database 
documenthttps://github.com/markcraig/DOCS-47/blob/master/src/docbkx/olinkdb.xml
 for the test is minimal:

?xml version='1.0' encoding='utf-8'?
!DOCTYPE targetset[
...
!ENTITY book SYSTEM '../../target/target.db'
]
targetset
 document targetdoc=book baseuri=book.pdfbook;/document
/targetset

Although Olink debug messages make it look like the stylesheets are finding a 
match for the link, the .fo is missing information.

In the build output, I see:

Olink debug: cases for targetdoc='book' and targetptr='chapter' in language ''.
Olink debug: CaseA matched.
Olink debug: CaseA key is the final selection: book/chapter/

But the .fo has an external-destination with no actual destination:

fo:basic-link show-destination=replace external-destination=url(#dest=)
fo:inlinelink to the next chapter/fo:inline/fo:basic-link

If I remove the baseuri value from the document element in the target 
database document, then the external-destination attribute changes a little:

fo:basic-link show-destination=replace 
external-destination=url(#dest=chapter

RE: [docbook-apps] Olinks in PDF missing valid destination?

[Wood Nick]

Mark,

I do not pretend to be an expert on this - I setup my pdf olinks using Bob's 
excellent book plus some guidance you have posted in the past.  However, have 
you tried adding currentDocid/ in the configuration/ of your POM and then 
using the sitemap in your olinkdb.xml (as I believe this provide the location 
of the documents).

Regards

Nick


From: Mark Craig [mailto:mark.cr...@gmail.com]
Sent: Wednesday, October 23, 2013 10:11 AM
To: DocBook Apps
Subject: [docbook-apps] Olinks in PDF missing valid destination?

Hello,

In the past I have successfully set up Olink resolution for HTML.

I have read and tried to implement
http://www.sagehill.net/docbookxsl/OlinkPrintOutput.html#PdfLinkingSetup
But I'm not managing to do the same for PDF.

A clickable link of the Olink is there in the PDF, but with no valid 
destination.

This is with docbkx-tools 2.0.14, so DocBook XSL 1.76.1 and FOP 1 (I think 1.1).

My little test is at https://github.com/markcraig/DOCS-47.
(There's only one Olink, in the para at line 20 of 
book.xmlhttps://github.com/markcraig/DOCS-47/blob/master/src/docbkx/book.xml#L20.)

The main part of the target database 
documenthttps://github.com/markcraig/DOCS-47/blob/master/src/docbkx/olinkdb.xml
 for the test is minimal:

?xml version='1.0' encoding='utf-8'?
!DOCTYPE targetset[
...
!ENTITY book SYSTEM '../../target/target.db'
]
targetset
 document targetdoc=book baseuri=book.pdfbook;/document
/targetset

Although Olink debug messages make it look like the stylesheets are finding a 
match for the link, the .fo is missing information.

In the build output, I see:

Olink debug: cases for targetdoc='book' and targetptr='chapter' in language ''.
Olink debug: CaseA matched.
Olink debug: CaseA key is the final selection: book/chapter/

But the .fo has an external-destination with no actual destination:

fo:basic-link show-destination=replace external-destination=url(#dest=)
fo:inlinelink to the next chapter/fo:inline/fo:basic-link

If I remove the baseuri value from the document element in the target 
database document, then the external-destination attribute changes a little:

fo:basic-link show-destination=replace 
external-destination=url(#dest=chapter)
fo:inlinelink to the next chapter/fo:inline/fo:basic-link

What should I do differently for a valid destination to be generated?

Thanks for your advice.
Regards,
Mark

RE: [docbook-apps] initial pdf view with index side pane

[Wood Nick]

Richard,

Have you set the param fop1.extensions to 1, this works for me.

Nick
[Description: cid:image001.png@01CD4491.87A64560]

Nick Wood BSc(Hons) MInstLM
NATO Communications and Information Agency
Chief Document Engineering and Production Section
Thier Mathias 1b, B-4690 Bassenge (Glons), Belgium
T: +32 42 899215  F: +32 2 707 8770
E: nick.w...@ncia.nato.intmailto:  W: www.ncia.nato.int





From: Bob Stayton [mailto:b...@sagehill.net]
Sent: Wednesday, September 18, 2013 11:40 PM
To: Richard Henwood; docbook-apps@lists.oasis-open.org
Subject: Re: [docbook-apps] initial pdf view with index side pane

This would be a feature of your XSL-FO processor that generates the PDF.   If 
you are using FOP, you need to look at FOP's PDF output configuration, and see  
if FOP has such a setting.  There is no way to do it in DocBook XSL.

Bob Stayton
Sagehill Enterprises
b...@sagehill.netmailto:b...@sagehill.net

From: Richard Henwoodmailto:rjhenw...@yahoo.co.uk
Sent: Wednesday, September 18, 2013 2:02 PM
To: Bob Staytonmailto:b...@sagehill.net ; 
docbook-apps@lists.oasis-open.orgmailto:docbook-apps@lists.oasis-open.org
Subject: Re: [docbook-apps] initial pdf view with index side pane

Hi Bob,

What I want is when my viewer opens the PDF (I generated from Docbook) for the 
first time, it presents the user with the table of contents (the 'index' 
according to evince) in a panel on the left hand side.

This gives the user an overview of the document; without this appearing on 
initial view, a user may not know it exists.

Something like this: http://blog.rockymountaintraining.com/?p=383

r,



From: Bob Stayton b...@sagehill.netmailto:b...@sagehill.net
To: Richard Henwood rjhenw...@yahoo.co.ukmailto:rjhenw...@yahoo.co.uk; 
docbook-apps@lists.oasis-open.orgmailto:docbook-apps@lists.oasis-open.org
Sent: Wednesday, 18 September 2013, 15:00
Subject: Re: [docbook-apps] initial pdf view with index side pane

Hi Richard,
Do you mean you want to replace the PDF bookmarks with a back-of-the-book index 
in the left pane?

Bob Stayton
Sagehill Enterprises
b...@sagehill.netmailto:b...@sagehill.net

From: Richard Henwoodmailto:rjhenw...@yahoo.co.uk
Sent: Wednesday, September 18, 2013 12:16 PM
To: docbook-apps@lists.oasis-open.orgmailto:docbook-apps@lists.oasis-open.org
Subject: [docbook-apps] initial pdf view with index side pane

Hi All,

Is there a switch I can throw to force the PDF that is generated to default to 
displaying the index as a (left-hand) side bar?

The best I could find from my searching was: 
http://wiki.apache.org/xmlgraphics-fop/ExtensionsForPdf but I am unsure how to 
interpret this page. Any help would be gratefully appreciated!

cheers,
Richard

inline: image001.png

RE: [docbook-apps] FW: PROBELMS WITH BIBLIOGRAPHY

[Wood Nick]

Hi Bob,

Yes the outputted xref should be an active link to a biblioentry.  

My inintial customisation (matching biliolist) aimed at rendering my 
biblionetries in a table within a chapter.  In further chapters I have xrefs 
with linkend ids with the value of the biblioentry ids.  My table renders as 
expected and the xrefs also render as expected, with the exception that the 
generated text is not an active link to an entry in the table. On inspecting 
the fo output I noticed there was no id in the first fo:block for each 
biblioentry.

I suspected this had something to do with calling template object.id. as in the 
original biblio stylesheet, so I tried the following:

xsl:template match=bibliolist
xsl:variable name=id
xsl:call-template name=object.id/
/xsl:variable

On inspecting the fo output I noticed that the id in the first fo:block for 
each biblioentry was still empty.  So to test, I tried the same customisation 
but this time matching bibliography (as in the original stylesheet).  This did 
put a value in the id in the fo ouput (and my links were active) but the 
entries did not rendered in a table.

Regards

Nick Wood
NATO Communications and Information Agency
Chief Document Engineering and Production Section, NPC
Thier Mathias 1b
4690 Bassenge (Glons), Belgium
T: +32 4 289 9211  F: +32 4 289 9329
E: nick.w...@ncia.nato.int  W: www.ncia.nato.int

From: Bob Stayton [b...@sagehill.net]
Sent: Wednesday, February 20, 2013 5:59 PM
To: Wood Nick; DocBook Apps
Subject: Re: [docbook-apps] FW: PROBELMS WITH BIBLIOGRAPHY

Hi Nick,
I'm not quite following the customizations you made.  I'm not clear what the
xrefs are supposed to connect to.  The first template matched on
bibliolist, but the change you made for id matches on bibliography.  Are
you trying to link to biblioentrys?

Bob Stayton
Sagehill Enterprises
b...@sagehill.net

--
From: Wood Nick nick.w...@ncia.nato.int
Sent: Tuesday, February 19, 2013 1:44 AM
To: DocBook Apps docbook-apps@lists.oasis-open.org
Subject: [docbook-apps] FW: PROBELMS WITH BIBLIOGRAPHY

 Hi,

 I posted the mail below last week but it didn't get through (probably as a
 result of an organsiational change here last year and the concomiatnt
 change in e-mail addresses).So here goes again.

 Regards

 Nick Wood
 NATO Communications and Information Agency
 Chief Document Engineering and Production Section, NPC
 Thier Mathias 1b
 4690 Bassenge (Glons), Belgium
 T: +32 4 289 9211  F: +32 4 289 9329
 E: nick.w...@ncia.nato.int  W: www.ncia.nato.int
 
 From: Wood Nick
 Sent: Tuesday, February 12, 2013 3:11 PM
 To: DocBook Apps
 Subject: PROBELMS WITH BIBLIOGRAPHY

 Hi,

 I am currently working with the Docbook 1.72.0 styleshhets.
 I am having a real problem getting my References (bibliography) to output
 as I want in pdf.  As I work with military-style references I need the
 output in a table as follows:


 Reference Document NameIssueTitle

 A  FOO-SIP  1.0   FOO System
 Installation Plan

 An excerpt of my xml is as follows:

 bibliolist
  biblioentry id=foosip
  productnumberFOO-SIP/productnumber
 !--pubdate misused for realease number --
  pubdate1.0/pubdate
  titleFOO System Installation Plan/title
/biblioentry
--
  /bibliolist


 I have developed the following customisation layer:

 ?xml version='1.0'?
 xsl:stylesheet
 xmlns:xsl=http://www.w3.org/1999/XSL/Transform;
 xmlns:fo=http://www.w3.org/1999/XSL/Format;
 version='1.0'
 xsl:template match=bibliolist
 fo:table width=16cm table-layout=fixed
 border=1.0pt solid black
 text-align=left space-before=1cm 
 fo:table-column column-width=1cm /
 fo:table-column column-width=4cm/
 fo:table-column column-width=2cm /
 fo:table-column column-width=8cm/
 fo:table-header background-color=rgb(102,122,187)
 fo:table-row
  fo:table-cell border=solid padding=4pt 
   fo:block color=white font-weight=boldRef/fo:block
  /fo:table-cell
  fo:table-cell border=solid padding=4pt
   fo:block color=white font-weight=boldDocument/fo:block
  /fo:table-cell
  fo:table-cell border=solid padding=4pt
   fo:block color=white font-weight=boldIssue/fo:block
  /fo:table-cell
  fo:table-cell border=solid padding=4pt
   fo:block color=white font-weight=boldTitle/fo:block
  /fo:table-cell
 /fo:table-row
 /fo:table-header
 fo:table-body
 xsl:for-each select=biblioentry 
 fo:table-row
 fo:table-cell border=solid padding=4pt
 fo:block
xsl:number from=bibliography count=biblioentry|bibliomixed
  level=any format=A/
 /fo:block
 /fo:table-cell
 fo:table-cell border=solid padding=4pt
 fo:block
 xsl:value-of select=productnumber /
 /fo:block
 /fo:table-cell
 fo:table-cell border=solid padding=4pt
 fo:block
 xsl:value-of select=pubdate /
 /fo:block
 /fo:table-cell
 fo:table-cell border=solid padding=4pt
 fo:block
 xsl:value

[docbook-apps] FW: PROBELMS WITH BIBLIOGRAPHY

[Wood Nick]

Hi,

I posted the mail below last week but it didn't get through (probably as a 
result of an organsiational change here last year and the concomiatnt change in 
e-mail addresses).So here goes again.

Regards 

Nick Wood
NATO Communications and Information Agency
Chief Document Engineering and Production Section, NPC
Thier Mathias 1b
4690 Bassenge (Glons), Belgium
T: +32 4 289 9211  F: +32 4 289 9329
E: nick.w...@ncia.nato.int  W: www.ncia.nato.int

From: Wood Nick
Sent: Tuesday, February 12, 2013 3:11 PM
To: DocBook Apps
Subject: PROBELMS WITH BIBLIOGRAPHY

Hi,

I am currently working with the Docbook 1.72.0 styleshhets.
I am having a real problem getting my References (bibliography) to output as I 
want in pdf.  As I work with military-style references I need the output in a 
table as follows:


Reference Document NameIssueTitle

A  FOO-SIP  1.0   FOO System 
Installation Plan

An excerpt of my xml is as follows:

bibliolist
  biblioentry id=foosip
  productnumberFOO-SIP/productnumber
 !--pubdate misused for realease number --
  pubdate1.0/pubdate
  titleFOO System Installation Plan/title
/biblioentry
--
  /bibliolist


I have developed the following customisation layer:

?xml version='1.0'?
xsl:stylesheet
 xmlns:xsl=http://www.w3.org/1999/XSL/Transform;
 xmlns:fo=http://www.w3.org/1999/XSL/Format;
 version='1.0'
xsl:template match=bibliolist
fo:table width=16cm table-layout=fixed
border=1.0pt solid black
text-align=left space-before=1cm 
fo:table-column column-width=1cm /
fo:table-column column-width=4cm/
fo:table-column column-width=2cm /
fo:table-column column-width=8cm/
fo:table-header background-color=rgb(102,122,187)
 fo:table-row
  fo:table-cell border=solid padding=4pt 
   fo:block color=white font-weight=boldRef/fo:block
  /fo:table-cell
  fo:table-cell border=solid padding=4pt
   fo:block color=white font-weight=boldDocument/fo:block
  /fo:table-cell
  fo:table-cell border=solid padding=4pt
   fo:block color=white font-weight=boldIssue/fo:block
  /fo:table-cell
  fo:table-cell border=solid padding=4pt
   fo:block color=white font-weight=boldTitle/fo:block
  /fo:table-cell
 /fo:table-row
/fo:table-header
fo:table-body
xsl:for-each select=biblioentry 
fo:table-row
fo:table-cell border=solid padding=4pt
fo:block
xsl:number from=bibliography count=biblioentry|bibliomixed
  level=any format=A/
/fo:block
/fo:table-cell
fo:table-cell border=solid padding=4pt
fo:block
xsl:value-of select=productnumber /
/fo:block
/fo:table-cell
fo:table-cell border=solid padding=4pt
fo:block
xsl:value-of select=pubdate /
/fo:block
/fo:table-cell
fo:table-cell border=solid padding=4pt
fo:block
xsl:value-of select=title /
/fo:block
/fo:table-cell
/fo:table-row 
/xsl:for-each
/fo:table-body
/fo:table
/xsl:template
/xsl:stylesheet

This works fine but the xerf links in the document are not active as the ID is 
missing.  Having looked through the biblio stylesheet I changed/added the 
following

xsl:template match=bibliography
xsl:variable name=id
xsl:call-template name=object.id/
/xsl:variable

and added id={id} to the first fo:block.  Now my links are active but the 
output is longer displayed in a table?

Any ideas would be appreacited.

Thanks


Nick Wood
NATO Communications and Information Agency
Chief Document Engineering and Production Section, NPC
Thier Mathias 1b
4690 Bassenge (Glons), Belgium
T: +32 4 289 9211  F: +32 4 289 9329
E: nick.w...@ncia.nato.int
-
To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org

RE: [docbook-apps] PAGE NUMBER APPEARS ON TITLEPAGE

[Wood, Nick]

Bob,

You are correct, it now works fine.

Thanks alot.

Nick


From: Bob Stayton [b...@sagehill.net]
Sent: Thursday, February 09, 2012 5:47 PM
To: Wood, Nick; DocBook Apps
Subject: Re: [docbook-apps] PAGE NUMBER APPEARS ON TITLEPAGE

Hi Nick,
I think your footer.content template needs to take into account your new 
page-master
name:

xsl:choose
xsl:when test=$pageclass = 'coversequence'
!-- nop --
/xsl:when
etc.

Bob Stayton
Sagehill Enterprises
b...@sagehill.net


- Original Message -
From: Wood, Nick nick.w...@npc.nato.int
To: DocBook Apps docbook-apps@lists.oasis-open.org
Sent: Thursday, February 09, 2012 8:27 AM
Subject: RE: [docbook-apps] PAGE NUMBER APPEARS ON TITLEPAGE


Paul,

Thanks for your response, of course your observation is correct, but 
unfortunately it
it had no effect either.  I  previously had the following:

xsl:when test=$position='centertop'
xsl:if test=$pageclass != 'titlepage'  
fo:page-number/
/xsl:if
/xsl:when

But this has no effect, by adding further parameters to the test I get different
results but never the right the one!

Regards

Nick



From: Paul Tremblay [paulhtremb...@gmail.com]
Sent: Thursday, February 09, 2012 2:14 PM
To: Wood, Nick
Cc: DocBook Apps
Subject: Re: [docbook-apps] PAGE NUMBER APPEARS ON TITLEPAGE


Nick, your code puts a number on the title page:

xsl:when test=$pageclass = 'titlepage'and $sequence = 'first'
fo:page-number!-- nop --/fo:page-number
/xsl:when

I see you have a comment of !--nop--. But the empty element fo:pagenumber/ 
inserts
a page number. I think you want:

xsl:when test=$pageclass = 'titlepage'and $sequence = 'first'/

Paul




On Thu, Feb 9, 2012 at 2:49 AM, Wood, Nick nick.w...@npc.nato.int wrote:

Paul,

I have already customised the footer.content template, see the extract for 
numbering
below.  My problem is that everything works fine until I call the
select.user.pagemaster template.  I assume it has something to do with the
page-sequence-master but I don't what.

xsl:when test=$position='centertop'
fo:block
xsl:choose
xsl:when test=$pageclass = 'titlepage'and $sequence = 'first'
fo:page-number!-- nop --/fo:page-number
/xsl:when
xsl:otherwise
fo:page-number/
/xsl:otherwise
/xsl:choose
/fo:block
/xsl:when


Regards

Nick




From: Paul Tremblay [paulhtremb...@gmail.com]
Sent: Wednesday, February 08, 2012 6:25 PM
To: Wood, Nick
Cc: DocBook Apps
Subject: Re: [docbook-apps] PAGE NUMBER APPEARS ON TITLEPAGE



I think you have to customize the footer.template:

xsl:template name=footer.content ...

Check out the same documentation (Docbook XSL The Complete Guide).


On Wed, Feb 8, 2012 at 8:49 AM, Wood, Nick nick.w...@npc.nato.int wrote:

Hi,

I recently had to further customise my setup-pagemasters.xsl  (taken from
fo/pagemaster.xsl) as Parts have been introduced to some of our books, and I was
getting the background image on both the Title page and the Part page.  
Following the
guidelines from Docbook XSL (The Complete Guide) and various postings on 
docbook-apps,
I renamed the page-sequence master and added the select.user.pagemaster 
template; the
customisation works fine, with the excpetion that now I get a page number on my
titlepage and legal notice page.

I have tried several customisations to remove the page number but whenever I 
call the
select.user.pagemaster template I get the same result.  Any help would be 
grarefully
recieved.

Regards

Nick Wood

xsl:template name=user.pagemasters
xsl:variable name=npclogo
select='../installed/logos/documentation_front_09e.jpg'/
xsl:variable name=npclogodraft
select='../installed/logos/documentation_front_09e-draft.jpg'/
 !-- setup for title page(s) --
  fo:page-sequence-master master-name=coversequence
fo:repeatable-page-master-alternatives
  fo:conditional-page-master-reference master-reference=blank
blank-or-not-blank=blank/
  fo:conditional-page-master-reference 
master-reference=titlepage-first-npc
page-position=first/
  fo:conditional-page-master-reference master-reference=titlepage-odd-npc
odd-or-even=odd/
  fo:conditional-page-master-reference
odd-or-even=even
xsl:attribute name=master-reference
  xsl:choose
xsl:when test=$double.sided != 0titlepage-even/xsl:when
xsl:otherwisetitlepage-odd/xsl:otherwise
  /xsl:choose
/xsl:attribute
  /fo:conditional-page-master-reference
/fo:repeatable-page-master-alternatives
  /fo:page-sequence-master
  fo:simple-page-master master-name=titlepage-first-npc
 page-width={$page.width}
 page-height={$page.height}
 margin-top=5mm
 margin-bottom=5mm
 margin-left=5mm
 margin-right=5mm

RE: [docbook-apps] PAGE NUMBER APPEARS ON TITLEPAGE

[Wood, Nick]

Paul,  

Thanks for your response, of course your observation is correct, but 
unfortunately it it had no effect either.  I  previously had the following:

xsl:when test=$position='centertop'
xsl:if test=$pageclass != 'titlepage'  
fo:page-number/
/xsl:if
/xsl:when

But this has no effect, by adding further parameters to the test I get 
different results but never the right the one!

Regards

Nick



From: Paul Tremblay [paulhtremb...@gmail.com]
Sent: Thursday, February 09, 2012 2:14 PM
To: Wood, Nick
Cc: DocBook Apps
Subject: Re: [docbook-apps] PAGE NUMBER APPEARS ON TITLEPAGE


Nick, your code puts a number on the title page:

xsl:when test=$pageclass = 'titlepage'and $sequence = 'first'
fo:page-number!-- nop --/fo:page-number
/xsl:when

I see you have a comment of !--nop--. But the empty element fo:pagenumber/ 
inserts a page number. I think you want:

xsl:when test=$pageclass = 'titlepage'and $sequence = 'first'/

Paul




On Thu, Feb 9, 2012 at 2:49 AM, Wood, Nick nick.w...@npc.nato.int wrote:

Paul,

I have already customised the footer.content template, see the extract for 
numbering below.  My problem is that everything works fine until I call the 
select.user.pagemaster template.  I assume it has something to do with the 
page-sequence-master but I don't what.

xsl:when test=$position='centertop'
fo:block
xsl:choose
xsl:when test=$pageclass = 'titlepage'and $sequence = 'first'
fo:page-number!-- nop --/fo:page-number
/xsl:when
xsl:otherwise
fo:page-number/
/xsl:otherwise
/xsl:choose
/fo:block
/xsl:when


Regards

Nick




From: Paul Tremblay [paulhtremb...@gmail.com]
Sent: Wednesday, February 08, 2012 6:25 PM
To: Wood, Nick
Cc: DocBook Apps
Subject: Re: [docbook-apps] PAGE NUMBER APPEARS ON TITLEPAGE



I think you have to customize the footer.template:

xsl:template name=footer.content ...

Check out the same documentation (Docbook XSL The Complete Guide).


On Wed, Feb 8, 2012 at 8:49 AM, Wood, Nick nick.w...@npc.nato.int wrote:

Hi,

I recently had to further customise my setup-pagemasters.xsl  (taken from 
fo/pagemaster.xsl) as Parts have been introduced to some of our books, and I 
was getting the background image on both the Title page and the Part page.  
Following the guidelines from Docbook XSL (The Complete Guide) and various 
postings on docbook-apps, I renamed the page-sequence master and added the 
select.user.pagemaster template; the customisation works fine, with the 
excpetion that now I get a page number on my titlepage and legal notice page.

I have tried several customisations to remove the page number but whenever I 
call the select.user.pagemaster template I get the same result.  Any help would 
be grarefully recieved.

Regards

Nick Wood

xsl:template name=user.pagemasters
xsl:variable name=npclogo 
select='../installed/logos/documentation_front_09e.jpg'/
xsl:variable name=npclogodraft 
select='../installed/logos/documentation_front_09e-draft.jpg'/
 !-- setup for title page(s) --
  fo:page-sequence-master master-name=coversequence
fo:repeatable-page-master-alternatives
  fo:conditional-page-master-reference master-reference=blank
blank-or-not-blank=blank/
  fo:conditional-page-master-reference 
master-reference=titlepage-first-npc
page-position=first/
  fo:conditional-page-master-reference master-reference=titlepage-odd-npc
odd-or-even=odd/
  fo:conditional-page-master-reference
odd-or-even=even
xsl:attribute name=master-reference
  xsl:choose
xsl:when test=$double.sided != 0titlepage-even/xsl:when
xsl:otherwisetitlepage-odd/xsl:otherwise
  /xsl:choose
/xsl:attribute
  /fo:conditional-page-master-reference
/fo:repeatable-page-master-alternatives
  /fo:page-sequence-master
  fo:simple-page-master master-name=titlepage-first-npc
 page-width={$page.width}
 page-height={$page.height}
 margin-top=5mm
 margin-bottom=5mm
 margin-left=5mm
 margin-right=5mm
xsl:if test=$axf.extensions != 0
  xsl:call-template name=axf-page-master-properties
xsl:with-param name=page.masterblank/xsl:with-param
  /xsl:call-template
/xsl:if

 fo:region-body margin-bottom=0mm
  margin-top=0mm
  column-gap={$column.gap.titlepage}
  column-count={$column.count.titlepage}
 xsl:attribute name=background-image
xsl:call-template name=fo-external-image
  xsl:with-param name=filename select=$npclogo/
/xsl:call-template
  /xsl:attribute
  xsl:attribute name=background-attachmentfixed/xsl:attribute
  xsl:attribute 
name=background-position-horizontalcenter

[docbook-apps] PAGE NUMBER APPEARS ON TITLEPAGE

[Wood, Nick]

Hi, 

I recently had to further customise my setup-pagemasters.xsl  (taken from 
fo/pagemaster.xsl) as Parts have been introduced to some of our books, and I 
was getting the background image on both the Title page and the Part page.  
Following the guidelines from Docbook XSL (The Complete Guide) and various 
postings on docbook-apps, I renamed the page-sequence master and added the 
select.user.pagemaster template; the customisation works fine, with the 
excpetion that now I get a page number on my titlepage and legal notice page.

I have tried several customisations to remove the page number but whenever I 
call the select.user.pagemaster template I get the same result.  Any help would 
be grarefully recieved.

Regards

Nick Wood

xsl:template name=user.pagemasters
xsl:variable name=npclogo 
select='../installed/logos/documentation_front_09e.jpg'/
xsl:variable name=npclogodraft 
select='../installed/logos/documentation_front_09e-draft.jpg'/
 !-- setup for title page(s) --
fo:page-sequence-master master-name=coversequence
  fo:repeatable-page-master-alternatives
fo:conditional-page-master-reference master-reference=blank
  blank-or-not-blank=blank/
fo:conditional-page-master-reference 
master-reference=titlepage-first-npc
  page-position=first/
fo:conditional-page-master-reference 
master-reference=titlepage-odd-npc
  odd-or-even=odd/
fo:conditional-page-master-reference 
  odd-or-even=even
  xsl:attribute name=master-reference
xsl:choose
  xsl:when test=$double.sided != 0titlepage-even/xsl:when
  xsl:otherwisetitlepage-odd/xsl:otherwise
/xsl:choose
  /xsl:attribute
/fo:conditional-page-master-reference
  /fo:repeatable-page-master-alternatives
/fo:page-sequence-master
fo:simple-page-master master-name=titlepage-first-npc
   page-width={$page.width}
   page-height={$page.height}
   margin-top=5mm
   margin-bottom=5mm
   margin-left=5mm
   margin-right=5mm
  xsl:if test=$axf.extensions != 0
xsl:call-template name=axf-page-master-properties
  xsl:with-param name=page.masterblank/xsl:with-param
/xsl:call-template
  /xsl:if
  
   fo:region-body margin-bottom=0mm
margin-top=0mm
column-gap={$column.gap.titlepage}
column-count={$column.count.titlepage}
   xsl:attribute name=background-image
  xsl:call-template name=fo-external-image
xsl:with-param name=filename select=$npclogo/
  /xsl:call-template
/xsl:attribute
xsl:attribute name=background-attachmentfixed/xsl:attribute
xsl:attribute 
name=background-position-horizontalcenter/xsl:attribute
   xsl:attribute name=background-repeatno-repeat/xsl:attribute
xsl:attribute 
name=background-position-verticalcenter/xsl:attribute
  /fo:region-body
  fo:region-before region-name=xsl-region-before-first
extent={$region.before.extent}
display-align=before/
  fo:region-after region-name=xsl-region-after-first
   extent={$region.after.extent}
display-align=after/
/fo:simple-page-master
fo:simple-page-master master-name=titlepage-odd-npc
   page-width={$page.width}
   page-height={$page.height}
   margin-top={$page.margin.top}
   margin-bottom={$page.margin.bottom}
   margin-left={$margin.left.inner}
   margin-right={$page.margin.outer}
  xsl:if test=$axf.extensions != 0
xsl:call-template name=axf-page-master-properties
  xsl:with-param name=page.masterblank/xsl:with-param
/xsl:call-template
  /xsl:if
  fo:region-body margin-bottom={$body.margin.bottom}
  margin-top={$body.margin.top}
  column-gap={$column.gap.titlepage}
  column-count={$column.count.titlepage}
  /fo:region-body
  fo:region-before region-name=xsl-region-before-odd
extent={$region.before.extent}
display-align=before/
  fo:region-after region-name=xsl-region-after-odd
   extent={$region.after.extent}
display-align=after/
/fo:simple-page-master
fo:simple-page-master master-name=titlepage-even-npc
   page-width={$page.width}
   page-height={$page.height}
 

RE: [docbook-apps] PAGE NUMBER APPEARS ON TITLEPAGE

[Wood, Nick]

Paul, 

I have already customised the footer.content template, see the extract for 
numbering below.  My problem is that everything works fine until I call the 
select.user.pagemaster template.  I assume it has something to do with the 
page-sequence-master but I don't what.

xsl:when test=$position='centertop'
fo:block
xsl:choose
xsl:when test=$pageclass = 'titlepage'and $sequence = 'first'
fo:page-number!-- nop --/fo:page-number
/xsl:when
xsl:otherwise
fo:page-number/
/xsl:otherwise
/xsl:choose
/fo:block
/xsl:when


Regards

Nick




From: Paul Tremblay [paulhtremb...@gmail.com]
Sent: Wednesday, February 08, 2012 6:25 PM
To: Wood, Nick
Cc: DocBook Apps
Subject: Re: [docbook-apps] PAGE NUMBER APPEARS ON TITLEPAGE


I think you have to customize the footer.template:

xsl:template name=footer.content ...

Check out the same documentation (Docbook XSL The Complete Guide).


On Wed, Feb 8, 2012 at 8:49 AM, Wood, Nick nick.w...@npc.nato.int wrote:

Hi,

I recently had to further customise my setup-pagemasters.xsl  (taken from 
fo/pagemaster.xsl) as Parts have been introduced to some of our books, and I 
was getting the background image on both the Title page and the Part page.  
Following the guidelines from Docbook XSL (The Complete Guide) and various 
postings on docbook-apps, I renamed the page-sequence master and added the 
select.user.pagemaster template; the customisation works fine, with the 
excpetion that now I get a page number on my titlepage and legal notice page.

I have tried several customisations to remove the page number but whenever I 
call the select.user.pagemaster template I get the same result.  Any help would 
be grarefully recieved.

Regards

Nick Wood

xsl:template name=user.pagemasters
xsl:variable name=npclogo 
select='../installed/logos/documentation_front_09e.jpg'/
xsl:variable name=npclogodraft 
select='../installed/logos/documentation_front_09e-draft.jpg'/
 !-- setup for title page(s) --
   fo:page-sequence-master master-name=coversequence
 fo:repeatable-page-master-alternatives
   fo:conditional-page-master-reference master-reference=blank
 blank-or-not-blank=blank/
   fo:conditional-page-master-reference 
master-reference=titlepage-first-npc
 page-position=first/
   fo:conditional-page-master-reference 
master-reference=titlepage-odd-npc
 odd-or-even=odd/
   fo:conditional-page-master-reference
 odd-or-even=even
 xsl:attribute name=master-reference
   xsl:choose
 xsl:when test=$double.sided != 0titlepage-even/xsl:when
 xsl:otherwisetitlepage-odd/xsl:otherwise
   /xsl:choose
 /xsl:attribute
   /fo:conditional-page-master-reference
 /fo:repeatable-page-master-alternatives
   /fo:page-sequence-master
   fo:simple-page-master master-name=titlepage-first-npc
  page-width={$page.width}
  page-height={$page.height}
  margin-top=5mm
  margin-bottom=5mm
  margin-left=5mm
  margin-right=5mm
 xsl:if test=$axf.extensions != 0
   xsl:call-template name=axf-page-master-properties
 xsl:with-param name=page.masterblank/xsl:with-param
   /xsl:call-template
 /xsl:if

  fo:region-body margin-bottom=0mm
   margin-top=0mm
   column-gap={$column.gap.titlepage}
   column-count={$column.count.titlepage}
  xsl:attribute name=background-image
 xsl:call-template name=fo-external-image
   xsl:with-param name=filename select=$npclogo/
 /xsl:call-template
   /xsl:attribute
   xsl:attribute name=background-attachmentfixed/xsl:attribute
   xsl:attribute 
name=background-position-horizontalcenter/xsl:attribute
  xsl:attribute name=background-repeatno-repeat/xsl:attribute
   xsl:attribute 
name=background-position-verticalcenter/xsl:attribute
 /fo:region-body
 fo:region-before region-name=xsl-region-before-first
   extent={$region.before.extent}
   display-align=before/
 fo:region-after region-name=xsl-region-after-first
  extent={$region.after.extent}
   display-align=after/
   /fo:simple-page-master
   fo:simple-page-master master-name=titlepage-odd-npc
  page-width={$page.width}
  page-height={$page.height}
  margin-top={$page.margin.top}
  margin-bottom={$page.margin.bottom}
  margin-left={$margin.left.inner}
  margin-right={$page.margin.outer}
 xsl:if test=$axf.extensions != 0
   xsl:call-template name=axf