Re: FW: [docbook-apps] Can't get olink to generate a working link between books in a set

[Bob Stayton <bobs@sagehill.net>]

Hi Bob,

I suggest you capture and examine the FO output, which will tell us more than the PDF reader's tooltips. In Oxygen, create a duplicate Transformation but turn off the FO Processor step and save the output as a .fo file, which you can open in Oxygen. And then find how the olink is expressed in the .fo file.

Bob Stayton
Sagehill Enterprises
bobs@sagehill.net

On 12/14/2018 10:34 AM, Bob McIlvride wrote:

Hi Bob,

Â

I apologize for the delay, was working on other aspects of the project, but in doing so I might have made some forward progress in this area, too.Â

Â

Iâm now using a smaller number of source test files (2 test books in my test set), and am now able to get the olink output to point to the correct part of the test-set.pdf file. However, the links donât actually work. For example, when I hover the mouse over a link, this link shows in the tooltip:

Â

file:///C/Activity/Cogent/Docs/DocsOx/Source/TestSet/out/pdf/test-set.pdf#dest=test1-introduction

Â

Please see the attached image for more examples. I know this isnât correct because we want the output to be independent of my file system.

Â

My olink-fo.db file looks like this:

Â

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

<!DOCTYPE targetset [

<!ENTITY testsettargets SYSTEM "target-fo.db">

<!ENTITY test1targets SYSTEM "../TestBook1/target-fo.db">

<!ENTITY test2targets SYSTEM "../TestBook2/target-fo.db">

]>

<targetset>

ÂÂÂ <targetsetinfo>Description</targetsetinfo>

ÂÂÂ <document targetdoc="test-set"> &testsettargets; </document>

ÂÂÂ <document targetdoc="test1-book"> &test1targets; </document>

ÂÂÂ <document targetdoc="test2-book"> &test2targets; </document>

</targetset>

Â

The resulting target-fo.db output looks like this:

Â

<div element="set" href="" number="" targetptr="test-set">
ÂÂÂ <ttl>Test Set</ttl>
ÂÂÂ <xreftext>Test Set</xreftext>
ÂÂÂ <div element="book" href="" number="" targetptr="test1-book">
ÂÂÂÂÂÂÂ <ttl>Test Book 1</ttl>
ÂÂÂÂÂÂÂ <xreftext>Test Book 1</xreftext>
ÂÂÂÂÂÂÂ <div element="chapter" href="" number="" targetptr="test1-introduction">
ÂÂÂÂÂÂÂÂÂÂÂ <ttl>Introduction</ttl>
ÂÂÂÂÂÂÂÂÂÂÂ <xreftext>
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ <fo:inline xmlns:fo="http://www.w3.org/1999/XSL/Format" font-style="italic"
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ >Introduction</fo:inline>
ÂÂÂÂÂÂÂÂÂÂÂ </xreftext>
ÂÂÂÂÂÂÂ </div>
ÂÂÂ </div>

. . .

Â

</div>

Â

Iâm using Oxygen XML editor, and the debug output (from setting the olink.debug parameter to 1) includes this kind of output for each olink:

Â

[Saxon6.5.5] Olink debug: cases for targetdoc='test1-book' and targetptr='test1-introduction' in language ''.

[Saxon6.5.5] Olink debug: CaseA matched.

Â

This suggests to me that the olinks are being resolved correctly. What do I need to change to get them to work in the actual output?

Â

Thanks for your attention and help on this.

Â

Best wishes,

Â

Bob

Â

Bob McIlvride ÂÂ Director, Communications Skkynet Cloud Systems, Inc. T Â 1 905 702 7851 ext 103 skkynet.com

Â

From: Bob McIlvride <bob.mcilvride@cogent.ca>
Sent: Tuesday, August 14, 2018 5:16 PM
To: 'Bob Stayton' <bobs@sagehill.net>; docbook-apps@lists.oasis-open.org
Subject: RE: [docbook-apps] Can't get olink to generate a working link between books in a set

Â

Hi Bob,

Â

Thank you for your guidance on this. We are making good progress, but not completely there yet. Implementing your suggestions we are now getting output for individual books and the set. The regular links in the individual books all work, but the olinks in the set still don't. Oddly enough, the links created look different in two different PDF Readers, Acrobat and Foxit.

Â

To double-check the portability of the output, I moved the output file to a different directory on my system (C:/Activity/Cogent/). Here's what we are seeing:

Â

Acrobat - mouse hover

Â

Acrobat - mouse click

Â

Acrobat - mouse click "Allow"

Â

When I click âOKâ here, the dialog goes away but nothing else happens.Â

Â

Foxit - mouse hover

Â

Foxit - mouse click

Â

Â

Foxit - mouse click "Allow"

Â

Â

This index opens in another window.

Â

Any suggestions?

Â

All the best,

Â

Bob

Â

Â

Bob McIlvride ÂÂ Communications Manager Cogent Real-Time Systems Inc., a Skkynet company T Â 1 905 702 7851 ext 103 cogent.ca

Â

From: Bob Stayton <bobs@sagehill.net>
Sent: Saturday, August 11, 2018 12:27 PM
To: docbook-apps@lists.oasis-open.org
Subject: Re: [docbook-apps] Can't get olink to generate a working link between books in a set

Â

Hi Bob,

Sorry this is so complicated.

If I understand, in the Oxygen transformation scenario, you have set the stylesheet parameter 'targets.filename' to 'target-fo.db'. When you process it, it seems that Oxygen is trying to write the target-fo.db file into the Oxygen location of the stylesheets, for which you are denied access.

The template that writes out that file is 'write.chunk', which is borrowed from the HTML side (in fo/docbook.xsl, you can see <xsl:include href=""/>). However, that template expects the filename it is passed to already be processed to include $base.dir if it is set. Unfortunately, that works in HTML output but the FO stylesheet does not use base.dir. So it does not work with base.dir in the fo context, and that's a bug that should be fixed.

In your case, you'll need to set the full path in the 'targets.filename' parameter in your scenario, to something like:

${cfd}/target-fo.db

or whatever the location specified by the path in your olinkdb-fo.xml file.

Now back to your olinkdb-fo.xml file. The targetdoc attribute must match the value of the targetdoc attributes that are written into your olinks, not the name of the pdf output file. The targetdoc attribute is just an identifier, used on both the olinks to identify the book and in the database to find the right set of target data. So they must match to work.Â

When you process your set, you will need a set of target data for each book in the set, and the olinkdb-fo.xml file pulling in each file into a <document> element with the correct targetdoc attribute for that book.

And if you are generating a single PDF output, you should omit the baseuri attribute, which is only needed when linking between PDF files. Internally linking within a single PDF file does not need a baseuri.

Bob Stayton

Sagehill Enterprises

bobs@sagehill.net

Â

On 8/10/2018 1:54 PM, Bob McIlvride wrote:

Hi Bob,

Â

Thank you for the suggestion. This is unfamiliar territory for me, and I seem to have run into an obstacle implementing this suggestion: "So you need to use your PDF stylesheet to generate separate data files for PDF output."

Â

Starting with a single book, I have created a separate target database document (olinkdb-fo.xml) that is supposed to generate a separate targets database (target-fo.db)Â However, I get an error message:

E [Saxon6.5.5] target-fo.db (Access is denied)

Â

And the target-fo.db file does not get generated. A search on this list suggested that to avoid this error I need to change my base.dir to the location where the output files will be generated. So I have specified that as:

Â

C:/Activity/Cogent/Docs/DocsOx/Source/${cfn}/out/pdf/

Â

(Where ${cfn} is a variable for the file name and directory name of the current book, in this case it's 'DHScripting'.)

Â

However, I still get the error. Here is the complete error message:

Â

System ID: C:\Activity\Cogent\Docs\DocsOx\Source\DHScripting\dhs-book.xml

Scenario: Skkynet-PDF - TargetDB

XML file: C:\Activity\Cogent\Docs\DocsOx\Source\DHScripting\dhs-book.xml

XSL file: C:\Activity\Cogent\Docs\DocsOx\FO-SS-Book.xsl

Engine name: Saxon6.5.5

Severity: error

Description: target-fo.db (Access is denied)

Â

My olinkdb-fo.xml file for the book contains this:

Â

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

<!DOCTYPE targetset [

<!ENTITY dhstargets SYSTEM "./target-fo.db">]>

<targetset>

ÂÂÂ <targetsetinfo> Description</targetsetinfo>

ÂÂÂ <document targetdoc="./out/pdf/dhs-book.pdf"

ÂÂÂÂÂÂÂ baseuri="./out/pdf/dhs-book.pdf">

ÂÂÂÂÂÂÂ &dhstargets; </document>

</targetset>

Â

The HTML version, olinkdb.xml, generates the target.db database as expected. What am I doing wrong that is preventing me from generating a PDF version?

Â

As always, I greatly appreciate your help.

Â

Best wishes,

Â

Bob

Â

Â

Bob McIlvride ÂÂ Communications Manager Cogent Real-Time Systems Inc., a Skkynet company T Â 1 905 702 7851 ext 103 cogent.ca

Â

From: Bob Stayton <bobs@sagehill.net>
Sent: Tuesday, August 07, 2018 6:06 PM
To: Bob McIlvride <bob.mcilvride@skkynet.com>; docbook-apps@lists.oasis-open.org
Subject: Re: [docbook-apps] Can't get olink to generate a working link between books in a set

Â

Ah, you need to keep your generated data files for HTML and PDF outputs separate. That is, you need to generate target data with the stylesheet you are using to generate output. When you use your HTML stylesheet, it generates target data with .html references. So you need to use your PDF stylesheet to generate separate data files for PDF output. Those files with different names would be referenced by the PDF version of the target database document.Â

Bob Stayton

Sagehill Enterprises

bobs@sagehill.net

On 8/7/2018 12:07 PM, Bob McIlvride wrote:

Hi Bob,

Â

That would make sense. Iâve tried it, and although it now seems to recognize the correct ID, it still comes up within a pointer to an html file:

Â

Â

Iâve used the sample xml code that you suggested for my olinkdb.xml file, as well as a number of other combinations. But they all seem to yield essentially the same results.Â

Â

Do you have any further thoughts?

Â

All the best,

Â

Bob

Â

Â

Bob McIlvride ÂÂ Communications Manager Cogent Real-Time Systems Inc., a Skkynet company T Â 1 905 702 7851 ext 103 cogent.ca

Â

From: Bob Stayton <bobs@sagehill.net>
Sent: Monday, August 06, 2018 11:46 AM
To: docbook-apps@lists.oasis-open.org
Subject: Re: [docbook-apps] Can't get olink to generate a working link between books in a set

Â

Hi Bob,

The problem is the setup of the target database document, with a sitemap and separate baseuri attributes for each book. That setup is for separate book PDF files trying to link to each other.

If you are processing the books as a single set element, you should instead set it up as a sequence of document elements without a sitemap and without @baseuri's, which should then form relative links.

<targetset>
ÂÂÂÂÂÂÂÂÂÂ <document targetdoc="test-set">
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ &testsettargets;
ÂÂÂÂÂÂÂÂÂÂÂ </document>

ÂÂÂÂÂÂÂÂÂÂÂ <document targetdoc="dhs-book"
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ &dhstargets;
ÂÂÂÂÂÂÂÂÂÂÂ </document>
Âetc.

I haven't tested this, but I think it will work. Let me know if it doesn't.

Bob

Â

Bob Stayton

Sagehill Enterprises

bobs@sagehill.net

On 8/2/2018 2:07 PM, Bob McIlvride wrote:

Hi Bob,

Â

Thank you for the quick reply.

> Do you use targetdoc attributes in your olink elements, and are they different for each book?Â

Yes, for example, this olink is located in the text of the book whose xml:id="dos-bookâ:

â (see <olink targetdoc="dhs-book" targetptr="dhs-book">DataHub Scripting</olink>), which â

The link renders like this in the PDF document output:

When I took the above screenshot (OlinkOutput.png, attached) the mouse was hovering over the text âDataHub Scriptingâ, as highlighted in yellow. You can see how the link seems to be looking for an external file.

> Is your target database document for PDF output set up as a single document, and do you generate a single target.db file for the set?

I believe so, but I could be mistaken. Below is a copy of the olinkdb.xml file. It references the target.db of each of the three books in the set (as I think it is supposed to) and creates a single target.db file for the set. The id of the output file is âtest-setâ, and the filename is test-set.pdf. It is located in the directory shown in the screenshot above. I donât know why the string âoxygen-main.htmlâ has been appended to the filename.

Â

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

<!DOCTYPE targetset [

<!ENTITY testsettargets SYSTEM "target.db">

<!ENTITY dhstargets SYSTEM "../DHScripting/target.db">

<!ENTITY dostargets SYSTEM "../DHODBCScripting/target.db">

<!ENTITY dwstargets SYSTEM "../DHWinScripting/target.db">]

>Â

Â

<targetset>

ÂÂÂ <targetsetinfo>Description</targetsetinfo>

ÂÂÂ <sitemap>

ÂÂÂÂÂÂÂ <dir name="./">

ÂÂÂÂÂÂÂÂÂÂÂ <document targetdoc="test-set"

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ baseuri="test-set.pdf">

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ &testsettargets;

ÂÂÂÂÂÂÂÂÂÂÂ </document>

ÂÂÂÂÂÂÂÂÂÂÂ <document targetdoc="dhs-book"

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ baseuri="test-set.pdf">

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ &dhstargets;

ÂÂÂÂÂÂÂÂÂÂÂ </document>

ÂÂÂÂÂÂÂÂÂÂÂ <document targetdoc="dos-book"

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ baseuri="test-set.pdf">

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ &dhstargets;

ÂÂÂÂÂÂÂÂÂÂÂ </document>

ÂÂÂÂÂÂÂÂÂÂÂ <document targetdoc="dws-book"

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ baseuri="test-set.pdf">

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ &dhstargets;

ÂÂÂÂÂÂÂÂÂÂÂ </document>

ÂÂÂÂÂÂÂ </dir>

ÂÂÂ </sitemap>

</targetset>

Â

I hope this helps clarify the situation a bit. If you need any additional information or files, please let me know.

Â

Best wishes,

Â

Bob

Â

Bob McIlvride ÂÂ Communications Manager Cogent Real-Time Systems Inc., a Skkynet company T Â 1 905 702 7851 ext 103 cogent.ca

Â

From: Bob Stayton <bobs@sagehill.net>
Sent: Wednesday, August 01, 2018 6:29 PM
To: docbook-apps@lists.oasis-open.org
Subject: Re: [docbook-apps] Can't get olink to generate a working link between books in a set

Â

Hi Bob,

I would need a little more clarity on your set up. Do you use targetdoc attributes in your olink elements, and are they different for each book?Â

Is your target database document for PDF output set up as a single document, and do you generate a single target.db file for the set?

Bob Stayton

Sagehill Enterprises

bobs@sagehill.net

On 8/1/2018 12:25 PM, Bob McIlvride wrote:

Dear friends,

Â

After almost two years being moved to other tasks, I now have an opportunity

to complete this project. The HTML output is working fine, but the issue

now is PDF (FO) output. Here's a summary of what we would like to do:

Â

We have several books that we can publish individually in HTML (actually

'webhelp' in oXygen) and in PDF outputs. Using the same source files, we

are publishing those same books in sets--HTML and PDF output.

Â

The challenge is that we would like to have active links between the books

when they are in a set, which become plain text references when the books

are published separately. We are using olinks to achieve this goal, and

they work fine for HTML output. 

Â

However, when we generate PDF output, it seems that the olinks are looking

for external documents, not for books within the set. Is there any way to

point the olinks back into the set document and have them work in the PDF

output as well?

Â

Any suggestions would be much appreciated.

Â

Best regards,

Â

Bob

Â

Bob McIlvrideÂÂÂ Communications Manager

Cogent Real-Time Systems Inc., a Skkynet company

TÂ 1 905 702 7851 ext 103

cogent.ca

Â

-----Original Message-----

From: Bob McIlvride <bob.mcilvride@cogent.ca> 

Sent: Monday, September 26, 2016 12:44 PM

To: 'Bob Stayton' <bobs@sagehill.net>; docbook-apps@lists.oasis-open.org

Subject: RE: [docbook-apps] Can't get olink to generate a working link

between books in a set

Â

Hi Bob,

Â

Thank you for pointing this out. It is working now, and I'm very grateful

for your help!

Â

Best wishes,

Â

Bob

Bob McIlvrideÂÂÂ Communications Manager

Cogent Real-Time Systems Inc., a Skkynet company TÂ 1 905 702 7851 ext 103

cogent.ca

Â

-----Original Message-----

From: Bob Stayton [mailto:bobs@sagehill.net]

Sent: Saturday, September 24, 2016 5:37 PM

To: Bob McIlvride <bob.mcilvride@skkynet.com>;

docbook-apps@lists.oasis-open.org

Subject: Re: [docbook-apps] Can't get olink to generate a working link

between books in a set

Â

Hi Bob,

I think the problem is in the targetdoc attributes in your olinkdb.xml file.

The targetdoc value in both a document's olink element and in the database

document element is just an identifier name, not a filename. 

Those identifiers must match, and they will when you remove the ".xml" 

from the targetdoc value in the database file.

Â

There is a good reason why targetdoc is not a filename, and that is because

filenames can be changed without having to rewrite dozens of olinks embedded

in files.

Â

Bob Stayton

Sagehill Enterprises

bobs@sagehill.net

Â

On 9/23/2016 11:36 AM, Bob McIlvride wrote:

Dear friends,

Â

Â

Â

I am having problems getting olinks to correctly generate links 

between books in a set in HTML output. I want to be able to output 

independent books that contain references to content in other books, 

and when the books are produced as part of a set, these references 

should become links in HTML output.

Â

Â

Â

I am using oXygen XML Editor 18.0 that uses Saxon to generate HTML 

output. I've set up project files for two books (srr-book.xml and

dos-book.xml) and one set (test-set.xml) as a test. I have inserted 

one olink in the srr-book that points to a section in the dos-book.

Â

Â

Â

The test-set.xml document looks like this:

Â

Â

Â

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

Â

<!DOCTYPE set [

Â

<!ENTITY % commonentities SYSTEM

"../../Source/Common/commonentities.ent" >

Â

%commonentities;

Â

]>

Â

<set xmlns="http://docbook.org/ns/docbook" version="5.0"

xmlns:xi="http://www.w3.org/2001/XInclude"

Â

ÂÂÂ xmlns:xlink="http://www.w3.org/1999/xlink"</a" xml:id="test-set">

Â

ÂÂÂ <info>

Â

ÂÂÂÂÂÂÂ <title>Test Set</title>

Â

ÂÂÂ </info>

Â

ÂÂÂ <xi:include href=""/>

Â

ÂÂÂ <xi:include href=""/>

Â

</set>

Â

Â

Â

The olink markup in the srr-book.xml document looks like this:

Â

Â

Â

<para>Not to be confused with <olink targetdoc="dos-book"

targetptr="dos-overview">Overview Link</olink>,which is something 

altogether different.</para>

Â

Â

Â

When the test-set.xml document is processed, oXygen gives this error

message:

Â

Â

Â

[xslt] Error: unresolved olink: targetdoc/targetptr = 

'dos-book/dos-overview'.

Â

Â

Â

And the HTML output where the link should be looks like this:

Â

Â

Â

<p>Not to be confused with <span class="olink">Overview Link</span>, 

which is something altogether different.</p>

Â

Â

Â

The olinkdb.xml files for the books and the set are as follows:

Â

Â

Â

- srr-book.xml:

Â

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

Â

<targetset>

Â

ÂÂÂ <targetsetinfo> Description</targetsetinfo>

Â

ÂÂÂ <document targetdoc="srr-book.xml">

Â

ÂÂÂÂÂÂÂ <xi:include href=""

xmlns:xi="http://www.w3.org/2001/XInclude"/>

Â

ÂÂÂ </document>

Â

</targetset>

Â

Â

Â

- dos-book.xml:

Â

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

Â

<targetset>

Â

ÂÂÂ <targetsetinfo> Description</targetsetinfo>

Â

ÂÂÂ <document targetdoc="dos-book.xml">

Â

ÂÂÂÂÂÂÂ <xi:include href=""

xmlns:xi="http://www.w3.org/2001/XInclude"/>

Â

ÂÂÂ </document>

Â

</targetset>

Â

Â

Â

- test-set.xml:

Â

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

Â

<targetset>

Â

ÂÂÂ <targetsetinfo>A test of olink target sets.</targetsetinfo>

Â

ÂÂÂ <document targetdoc="../SRRModule/srr-book.xml">

Â

ÂÂÂÂÂÂÂ <xi:include href=""

xmlns:xi="http://www.w3.org/2001/XInclude"/>

Â

ÂÂÂ </document>

Â

ÂÂÂ <document targetdoc="../DHODBCScripting/dos-book.xml">

Â

ÂÂÂÂÂÂÂ <xi:include href=""

xmlns:xi="http://www.w3.org/2001/XInclude"/>

Â

ÂÂÂ </document>

Â

ÂÂÂ <document targetdoc="test-set.xml">

Â

ÂÂÂÂÂÂÂ <xi:include href=""

xmlns:xi="http://www.w3.org/2001/XInclude"/>

Â

ÂÂÂ </document>

Â

</targetset>

Â

Â

Â

The target.db content that results from these olinkdb.xml files looks 

correct. For example, here is the part that corresponds to the 

dos-book that refers to the Overview section to which the olink points:

Â

Â

Â

<div element="book" href="" number="" 

targetptr="dos-book">

Â

ÂÂÂÂÂÂÂÂÂÂÂ <ttl>DataHub<sup

xmlns="http://www.w3.org/1999/xhtml">Â</sup> ODBC Scripting</ttl>

Â

ÂÂÂÂÂÂÂÂÂÂÂ <xreftext>DataHub<sup

xmlns="http://www.w3.org/1999/xhtml">Â</sup> ODBC Scripting</xreftext>

Â

ÂÂÂÂÂ ÂÂÂÂÂÂ<div element="chapter" href=""

number="1" targetptr="dos-introduction">

Â

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ <ttl>Introduction</ttl>

Â

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ <xreftext>Chapter 1, <em 

xmlns="http://www.w3.org/1999/xhtml"

Â

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ >Introduction</em></xreftext>

Â

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ <div element="section"

href="" number="1.1"

Â

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ targetptr="dos-overview">

Â

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ ÂÂ<ttl>Overview</ttl>

Â

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ <xreftext>Section 1.1, âOverviewâ</xreftext>

Â

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ </div>

Â

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ ...

Â

Â

Â

I think I am doing everything correctly and according to Bob Stayton's 

clear and well-written documentation, but apparently I have missed 

something. Can anyone see what I may be doing wrong?

Â

Â

Â

Appreciatively yours,

Â

Â

Â

Bob

Â

Â

Â

Â

Â

COGENT <http://cogent.ca/>

Â

ÂÂ 

Â

*Bob McIlvride **ÂÂ Communications Manager*

Â

Cogent Real-Time Systems Inc., a Skkynet company

Â

TÂÂ 1 905 702 7851 ext 103

Â

cogent.ca <http://cogent.ca/>

Â

Â

Â

Â

Â

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

To unsubscribe, e-mail: docbook-apps-unsubscribe@lists.oasis-open.org

For additional commands, e-mail: docbook-apps-help@lists.oasis-open.org

Â

Â

Â

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

To unsubscribe, e-mail: docbook-apps-unsubscribe@lists.oasis-open.org

For additional commands, e-mail: docbook-apps-help@lists.oasis-open.org

Â

Â

Â

Â

Â

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

To unsubscribe, e-mail: docbook-apps-unsubscribe@lists.oasis-open.org

For additional commands, e-mail: docbook-apps-help@lists.oasis-open.org

Â

Â

Â