RE: Olinking for PDF generates absolute path

[Wood Nick <Nick.Wood@ncia.nato.int>]

 

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.fritsch@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.fritsch@coremedia.com

CoreMedia AG

content | conversation | conversion

Ludwig-Erhard-Str. 18
20459 Hamburg, Germany
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