This is the mail archive of the docbook@lists.oasis-open.org mailing list for the DocBook project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [docbook] DocBook colwidth Problems

Hi Ray,

Yes that should work as well.

I just gave it a try using the DocBook XSL 1.66.1 that comes with oXygen 5.0, configuring Saxon6.5.3 as XSLT processor and having the saxon651.jar in the oXygen lib folder and it works without problems. See below the output I got.
The parameters for the transformation were:
Name/Value
draft.mode/no
admon.graphics/1
tablecolumns.extension/1
use.extensions/1


<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>Article Title</title><meta name="generator" content="DocBook XSL Stylesheets V1.66.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="article" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="d0e1"></a>Article Title</h2></div></div><hr></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#d0e4">Section1 Title</a></span></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="d0e4"></a>Section1 Title</h2></div></div></div><p>Text
</p><div class="table"><a name="d0e9"></a><p class="title"><b>Table&nbsp;1.&nbsp;Test table</b></p><table summary="Test table" border="1"><colgroup><col width="796"><col width="74"><col width="354"></colgroup><tbody><tr valign="top"><td colspan="2" valign="top"><p>cols 1 and 2</p></td><td valign="top"><p>col 3</p></td></tr></tbody></table></div><p>
</p></div></div></body></html>

HTH,
George
---------------------------------------------------------------------
George Cristian Bina
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com


Ray Miller wrote: 
After the parameter is set, Java classes and jars from the extension
paths are dinamically loaded and can be used by the transformer
processors with no extra setting.


But, does not copying the extension jars to the oXygen lib directory place the the aforementioned within the classpath?

Ray

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]