Re: DOCBOOK-APPS: docbook2txt and mediaobjects

[Tim Waugh]

--7+7T3ZdO12I8zLgo
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Thu, Mar 13, 2003 at 12:31:07PM -0800, Ben Hratshorne wrote:

> I find that when I run docbook2txt, it first uses the HTML
> conversion, then uses lynx or something to make the conversion from
> HTML to text.  All in all, that seems like a fine idea., except that
> none of my figures and pictures come out.  The pictures there's no
> getting around, but I figured I could add a  to the
>  and then draw some ascii art to replace my .pdf or
> .png.

Support for that kind of thing isn't implemented yet.  Ideas for ways
to do so or even better, patches, are welcome.

Tim.
*/

--7+7T3ZdO12I8zLgo
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+cQcatO8Ac4jnUq4RAgJSAJ9sHMop05ydMAtJPmdja6vsd2MN1gCgpXeK
XGJMT5onGMZk1z27x8vKA0k=
=1iyu
-END PGP SIGNATURE-

--7+7T3ZdO12I8zLgo--

Re: DOCBOOK-APPS: how to upgrade docbook XSL stylesheets?

[Tim Waugh]

--pEAjBjStGYT6H+Py
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Thu, Mar 06, 2003 at 01:49:01PM -0500, Robert P. J. Day wrote:

> p.s.  i went looking for an RPM of the new stuff, but found a
> "docbook-xsl-129-1" at www.rpmfind.net.  not sure what that's all
> about, but i'm pretty sure i don't want it.

You can just 'rpmbuild --rebuild' this:

ftp://people.redhat.com/twaugh/tmp/docbook-style-xsl-1.60.1-1.src.rpm

Tim.
*/

--pEAjBjStGYT6H+Py
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+Z8W0tO8Ac4jnUq4RAuOrAJ49D59hQZn2+T2iJdrSOEwmyuM2agCguAgj
Jv6i5nFYnKrPD+uwoPv7CxA=
=Qg+8
-END PGP SIGNATURE-

--pEAjBjStGYT6H+Py--

Re: DOCBOOK-APPS: trying to use "xmlto" in red hat to customize PDFoutput

[Tim Waugh]

On Tue, Mar 04, 2003 at 10:42:12AM -0500, Robert P. J. Day wrote:

> the temporary stylesheet looks fine -- an xsl:import and some
> xsl:includes.  what's baffling me is that docbook markup that
> rendered beautifully in HTML renders untelligibly or causes the
> rendering to fail when trying to generate PDF.

Well, there is an extra step for PDF relative to HTML of course:
XSL-FO.  With current Red Hat Linux distributions you'll get
passivetex when using xmlto.

You could generate XSL-FO with 'xmlto fo -m ...' and try a different
XSL-FO processor than passivetex, to eliminate that and see if that's
the cause.

Tim.
*/


pgp0.pgp
Description: PGP signature

Re: DOCBOOK-APPS: trying to use "xmlto" in red hat to customize PDFoutput

[Tim Waugh]

--SLDf9lqlvOQaIe6s
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Tue, Mar 04, 2003 at 05:48:11AM -0500, Robert P. J. Day wrote:

> and add it to the xmlto command with "-m", it has no effect.
> is this because it's not an xsl:param, but an xsl:attribute-set?

The xmlto program doesn't interpret the fragments at all, just builds
a temporary stylesheet file which includes all the fragments.

If you comment out the 'trap' line in /usr/bin/xmlto and run it with
-v it will tell you the names of the temporary files it creates, and
won't remove them at exit.

Tim.
*/

--SLDf9lqlvOQaIe6s
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+ZK10tO8Ac4jnUq4RAp4cAJ49v4r2QCE0oQIQU+XqIezE+cFNYQCeLuz5
6zc394aForMO6Jigm6vS/bA=
=S2/N
-END PGP SIGNATURE-

--SLDf9lqlvOQaIe6s--

Re: DOCBOOK-APPS: [patch] fo:marker fix

[Tim Waugh]

--KXBzRT9YWDEmI8VQ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Oct 18, 2002 at 10:31:11AM -0500, Dennis Grace wrote:

> Hmmm, since you're messing with section.title.properties, I wonder if you
> aren't having the same problem I had with section title markup with
> PassiveTeX 1.21. If your section titles contain any markup or entities,
> PassiveTeX spits up.=20

Yes, that's the problem I'm seeing.

> I found that this is actually two problems. The
> fotex:bookmark apparently cannot process text entities (it even chokes on
> "). I'm not sure why PassiveTeX won't process text markup in titles,
> but even with the fotex:bookmark commented out, PassiveTeX won't process
> section title markup.

It was fo:markers with fo:inline children that it wouldn't like, for
me (not using extensions).

> The simplest fix, of course, is to disallow markup or text entities in my
> section titles.

Hm. :-/

> I suppose your fix is the only way to get markup in the section
> titles short of fixing PassiveTeX.

Obviously fixing PassiveTeX would be preferable to the patch I'm using
with docbook-xsl.

Tim.
*/

--KXBzRT9YWDEmI8VQ
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9sCoytO8Ac4jnUq4RAugNAJ94YVCBegt6btL1D5d8wdMTN2dkqgCcDQYv
SY35r8xonAQpMTdPVdIpmE0=
=rs6/
-END PGP SIGNATURE-

--KXBzRT9YWDEmI8VQ--

Re: DOCBOOK-APPS: Re: conditionalization of XML

[Tim Waugh]

On Thu, Oct 10, 2002 at 05:43:38PM -0400, Daniel Veillard wrote:

> > (1) You add support for ?if? and friends to xsltproc.  Probably the
> > fastest route to a complete solution.
> > 
> > (2) You tell me you'll take a patch from me to implement them.  I'd
> > have to learn the xsltproc code, so it would take longer, but I 
> > can do that.
> 
>   Honnestly 1/ and 2/ are not acceptable. Now if someone decides
> to standardize something like  then it's a big mess.
> Moreover if this can be done by a small and fast external preprocessing,
> why try to put everything in the same tool ? 

Eric has written a tool, xmlif, to do this, and it's available in
xmlto-0.0.11pre6.  What's a 'big mess', incidentally?  Do 'if' et al
need to be namespaced, you mean?

Tim.
*/



msg06122/pgp0.pgp
Description: PGP signature

Re: DOCBOOK-APPS: Manually Chunking with PIs

[Tim Waugh]

--DNbkntcEGyiBe7B+
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Oct 10, 2002 at 11:45:26AM -0400, Daniel Veillard wrote:

> There is also a couple of new options:
>  --nowrite : refuse to write to any file or resource
>  --nomkdir : refuse to create directories
>=20
>   To be able to protect the environment when the stylesheets are not cons=
idered
> trusted enough.

It would be useful if you could limit creation of files to within a
particular directory, but I realise that's non-trivial.

Tim.
*/

--DNbkntcEGyiBe7B+
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9paVmtO8Ac4jnUq4RAvUsAJwNlBKBKP8dm1r6KJGl5m6tKHzo1ACfeAAg
npLqGq7m/uAygIFY5mPVgmQ=
=7ggP
-END PGP SIGNATURE-

--DNbkntcEGyiBe7B+--

DOCBOOK-APPS: docbook-xsl 1.55.0: xhtml/chunk.xsl outputs HTML

[Tim Waugh]

--GTGEtWEe6jD60dxL
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Is it intentional that xhtml/chunk.xsl spits out HTML not XHTML?
(xhtml/docbook.xsl outputs XHTML as expected.)

Tim.
*/

--GTGEtWEe6jD60dxL
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9ovvmtO8Ac4jnUq4RAgn+AJ9x9w5Gesjsc5avcjVbi41mW+LOJgCgjYdE
kWkITjtRyLpg4plAl95Tz1w=
=wq7D
-END PGP SIGNATURE-

--GTGEtWEe6jD60dxL--

Re: DOCBOOK-APPS: The Best Linux Distribution to work with DocBoo k

[Tim Waugh]

--3BL0Ng5d1iPP6beU
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Mon, Apr 29, 2002 at 05:53:22PM +0200, Peter Ring wrote:

> For a while, Mandrake appeared to me to be most up-to-date. But I don't
> think there's much difference now. Anyway, most of the DocBook and jade or
> xslt specific packages can be installed from source without too much hassle.
> I'd pick the distribution based on some other criteria (like how easy is it
> to get passivetex working).

There are several RPM-based distributions (I don't know about
non-RPM-based ones) that have PassiveTeX RPM packages.  PLD, for
instance.  For Red Hat Linux: .

So, for RPM-based distributions at least, setting up PassiveTeX isn't
hard any more. [In theory..]

So, to agree with Peter: pick some other criteria..

Tim.
*/

--3BL0Ng5d1iPP6beU
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8zW3lyaXy9qA00+cRAnHFAJ4+bsEqx28iGMwKQdm5Uv8pI97oaQCfQo8e
3xybFaRk/DvXmk81NdKSU1c=
=m4nX
-END PGP SIGNATURE-

--3BL0Ng5d1iPP6beU--

Re: DOCBOOK-APPS: Passivetex Step by step installation

[Tim Waugh]

(Oops, replied in private mail by accident; for the list, in summary:)

On Fri, Apr 26, 2002 at 11:44:06AM -0500, Dennis Grace wrote:

> Does the PassiveTeX rpm include the upgrades to pdfTeX/teTeX (from
> http://www.redhat.com/support/errata/RHEA-2001-166.html) and the
> JadeTeX upgrade (from
> http://www.redhat.com/support/errata/RHEA-2001-167.html)? I
> installed from Sebastian's site but couldn't make PassiveTeX work on
> Red Hat 7.2 without the teTeX upgrades, and they broke JadeTeX,
> requiring the latter.

No.  Apply the updates, then install the passivetex RPM.

Tim.
*/

Re: DOCBOOK-APPS: Re: DOCBOOK: Manpages in Linux

[Tim Waugh]

On Fri, Apr 26, 2002 at 09:25:25AM -0500, Dennis Grace wrote:

> Trying to build man pages with docbook2man was (pace Steve Cheng)
> something of a nightmare for us. It's incomplete. If you want to
> build man pages from XML, I recommend processing with XSLTPROC via
> Martin van Beers' db2man.xsl (available from Sourceforge). Works
> like a champ.

I have made a substantial number of improvements to db2man, and (as I
said earlier) have distributed this improved version as part of xmlto.

I would love to incorporate the improvements into CVS.  I spoke to
Martin about it some months ago, but the few patches I had sent him at
the time have never shown up. :-(

You can get xmlto from here: http://cyberelk.net/tim/xmlto

For a demonstration of the output quality, take a look at the xmlto
man page, or the man pages distributed with patchutils
(http://cyberelk.net/tim/patchutils).

Martin, any chance of getting these improvements into CVS yet?

Tim.
*/

Re: DOCBOOK-APPS: Passivetex Step by step installation

[Tim Waugh]

--JVTRtevMO87SusWP
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Thu, Apr 25, 2002 at 01:25:00PM -0700, Carlos wrote:

> Does anyone have step by step install instructions for PassiveTex. I've
> tried following the instructions on the website but got confused by the
> locations and instructions.

http://cyberelk.net/tim/docbook has information about which RPM
packages you need to install for Red Hat Linux.

Tim.
*/

--JVTRtevMO87SusWP
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD4DBQE8yQG+yaXy9qA00+cRAso8AJiOwwJrnOU0MqCriwThKglHFPEsAJ4lS1M3
zD4MWV5ayIZJRlZmSc27vQ==
=URTS
-END PGP SIGNATURE-

--JVTRtevMO87SusWP--

Re: DOCBOOK-APPS: pdfTeX upgrade kills jw

[Tim Waugh]

--cWoXeonUoKmBZSoM
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Fri, Apr 05, 2002 at 10:24:37AM -0600, Dennis Grace wrote:

> I am running Red Hat 7.2 on my IBM T21 ThinkPad. I installed Red Hat's
> upgrades at http://www.w3.org/TR/2001/WD-xhtml1-20011004/

At _where_? ;-)

> in order to allow PassiveTeX to function properly on my computer. It
> worked. Unfortunately, the upgrade seems to have somehow disabled
> the OpenJade/jadeTeX/jw toolchain. Now, when I attempt to use those
> portions of jw (docbook2pdf) that rely upon pdfTeX (docbook2pdf or
> docbook2txt) I get the following error message:

You should also have seen a jadetex upgrade: did you apply that too?

Tim.
*/

--cWoXeonUoKmBZSoM
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8rdISyaXy9qA00+cRAutZAJ40Iw8UF0EAjAS/7oWUnDEMRDiS0QCeKVGh
tQe/Plw5FIiBSWbP/rbt1fM=
=LAkF
-END PGP SIGNATURE-

--cWoXeonUoKmBZSoM--

Re: DOCBOOK-APPS: free DocBook tools that handle Japanese

[Tim Waugh]

--lQcP9vuZCkvmDKre
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Mon, Jan 28, 2002 at 05:44:51AM -0600, Michael Smith wrote:

>  * XSLT engine: xsltproc (outputs ISO-8859-1 with character references
>for the Japanese characters)

How about for FO processing?

Tim.
*/

--lQcP9vuZCkvmDKre
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8VTosyaXy9qA00+cRAsQzAJ9Qg3bCA6RLi6n6+LBPa8z1eMnyBwCfU64l
CZR0IubQsTtWxKkFjpBpCXI=
=KSZ0
-END PGP SIGNATURE-

--lQcP9vuZCkvmDKre--

DOCBOOK-APPS: free DocBook tools that handle Japanese

[Tim Waugh]

Is anyone on this list using free software DocBook tools that handle
Japanese?

Thanks,
Tim.
*/

Re: DOCBOOK-APPS: Encoding for French?

[Tim Waugh]

--HNePlKHf6vuaTOUD
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Thu, Jan 17, 2002 at 09:08:54AM -0500, Daniel Veillard wrote:

>   Usually you will need Iso Latin 1, but people start to switch to
> Iso Latin 15 to get the Euro symbol support. Make sure you have
> 

(Of course, in DocBook the euro symbol should be obtained via
'€'.)

Tim.
*/

--HNePlKHf6vuaTOUD
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8Rt7oyaXy9qA00+cRApN+AKC5YvdHto/L/myNQtmV6nG/3mvn9wCfaiSq
tcsJEi0pL7dUs0+lcvos1SA=
=UvIS
-END PGP SIGNATURE-

--HNePlKHf6vuaTOUD--

Re: DOCBOOK-APPS: Re: DocBook with AbiWord?

[Tim Waugh]

--gV1yUYniiDLxW66s
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Sun, Jan 13, 2002 at 09:11:01PM -0800, Carlos Araya wrote:

> A couple days ago I asked about an RPM for Passivetex and even then
> I'm having a hell of time trying to find if I have the correct
> versions of required software,

You can take a look at http://cyberelk.net/tim/docbook/ for pointers
to the required RPM packages for XSL with PassiveTeX; it's also
mentioned in the Selfdocbook (XML edition).

Tim.
*/

--gV1yUYniiDLxW66s
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8QpRyyaXy9qA00+cRAiTmAJ9OgDM+moeX9vGaK87XSyJJJKic/gCgjyYM
n204uMYhMB+IhshXaQYxK/M=
=nM8n
-END PGP SIGNATURE-

--gV1yUYniiDLxW66s--

Re: DOCBOOK-APPS: Re: Conceptual model for processing DocBook SGML andXML

[Tim Waugh]

--tZCmRiovzb4sxAVa
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Jan 09, 2002 at 03:40:14AM -0500, Daniel Veillard wrote:

>   Hum, one of the thing which strikes me is that there is no
> direct=20
> DocBook XML -> TeX
> transformations. Basically they require going through FO where the
> semantic is lost and only content/formatting is left, where then TeX
> is generated.

If you mean via PassiveTeX, it doesn't really produce any actual TeX.

Tim.
*/

--tZCmRiovzb4sxAVa
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8PA1ByaXy9qA00+cRAkScAJ4mgOLXd+G8Ptg0YULpGb9xKi3f6wCeJDJG
dnknS4LvCdroZ0lWWBY8ewI=
=kfLz
-END PGP SIGNATURE-

--tZCmRiovzb4sxAVa--

DOCBOOK-APPS: Re: simplelist within entry

[Tim Waugh]

I think there are two bugs here: I found a smaller test case (
in place of your entry) that one part of this patch fixed, but the
full test case needed the other part as well to complete a run.

Unfortunately, the output is very bad, since I don't really know any
TeX.  But hopefully it helps someone who does..

Tim.
*/

--- /usr/share/texmf/tex/xmltex/passivetex/fotex.styFri Dec  7 15:06:37 2001
+++ fotex.sty   Fri Dec 14 10:36:02 2001
@@ -281,6 +281,7 @@
 \global\NCols\FOcolumnnumber
\fi
\ifx\prop@width\FOcolumnwidth\def\FOcolumnwidth{1in}\fi
+   \ifx\FOcolumnwidth\@empty\def\FOcolumnwidth{1in}\fi
\TablePercentToDimen{\FOcolumnwidth}%
\addToArray{fotable\the\AbsoluteTableCount:}{\the\@tempdima}%
\DEBUG{Table Column \the\NCols, in Table \the\AbsoluteTableCount, 
@@ -321,7 +322,7 @@
  \else
 \global\advance\CellCount by 1
  \fi
- \ifnum\NCols<1
+ \ifnum\NCols<2
   \CurrentCellWidth\z@
   \setbox0=\hbox{#1}%
   \CurrentCellWidth=\wd0

Re: DOCBOOK-APPS: Undefined control sequence

[Tim Waugh]

--qp4W5+cUSnZs0RIF
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Difficult to tell from the output, but perhaps it's because "Absolute
dimensions always work, but proportional ones are often not
recognized" (from the PassiveTeX page).

(Your informaltable example used proportional dimensions.)

Tim.
*/

--qp4W5+cUSnZs0RIF
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8GOyPyaXy9qA00+cRAq3SAJ916j2gq165vVmP3/2OhT/J1hEhsgCeJLdW
Q151bipRrT8SRVx2Vi1/aBU=
=xtc2
-END PGP SIGNATURE-

--qp4W5+cUSnZs0RIF--

Re: DOCBOOK-APPS: Undefined control sequence

[Tim Waugh]

On Thu, Dec 13, 2001 at 10:28:33AM -0700, Rankine, Alastair J (Alastair) wrote:

> ! Undefined control sequence.
> \NoTableCell ...1}\CurrentCellWidth =\wd 0 \DEBUg 
>   {report \the

Try this obviously-correct patch:

--- fotex.sty.orig  Thu Dec 13 17:42:11 2001
+++ fotex.sty   Thu Dec 13 17:42:42 2001
@@ -325,7 +325,7 @@
   \CurrentCellWidth\z@
   \setbox0=\hbox{#1}%
   \CurrentCellWidth=\wd0
-\DEBUg{report \the\CurrentCellWidth}%
+\DEBUG{report \the\CurrentCellWidth}%
  \else
   \CurrentCellWidth=\csname fotable\the\AbsoluteTableCount:\the\CellCount\endcsname
  \fi

Tim.
*/

Re: DOCBOOK-APPS: db2html

[Tim Waugh]

--dUqh8vgUBVXHzm9w
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Tue, Dec 11, 2001 at 06:24:13PM -0600, G.L. Grobe wrote:

> I've heard how to w/ docbook2html (newer version) which I havn't
> found yet (really havn't look, as it took alot of work to install
> docbook from scratch and I don't want to mess this up), but I was
> wondering if there was another way w/ the db2html script I have. If
> not, can I just download the docbook2html script by itself and only
> replace that piece?

Not sure (I haven't tried).  But the 'newer version' I was referring
to is the docbook-utils package.

Tim.
*/

--dUqh8vgUBVXHzm9w
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8FxiOyaXy9qA00+cRAsIcAJ9hnj4uhQcS7+EGP2eXSj2pH94mYACeL2MC
BcpTUSJ2aIGC0QenE2ve450=
=gN2+
-END PGP SIGNATURE-

--dUqh8vgUBVXHzm9w--

Re: DOCBOOK-APPS: "link annotations can't be nested" from Passivetex(pdfxmltex)

[Tim Waugh]

What version of pdfTeX do you have?  I think this might be due to a
bug in an old version of pdfTeX (I'm using 0.14h here).

Tim.
*/



msg03402/pgp0.pgp
Description: PGP signature

Re: tetex and PassiveTeX in Red Hat (was Re: DOCBOOK-APPS: htmlcosmetics)

[Tim Waugh]

--OZkY3AIuv2LYvjdk
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Dec 11, 2001 at 01:03:11AM -0800, Alex Lancaster wrote:

> On this very subject, I'm working through getting a working
> XSL/FO/PassiveTex setup working on my Red Hat 7.2 system, and
> following the instructions above in "Chapter 2. Tools", it lists the
> following dependencies available in Raw Hide:
>=20
>   libxml2 (at least 2.4.6-1)
>   libxslt
>   sgml-common and xml-common (at least 0.6.3-3)
>   tetex (at least 1.0.7-35)
>   xmltex
>   passivetex (at least 1.11-1)
>   docbook-style-xsl (at least 1.47-1)
>   docbook-dtd412-xml
>=20
> All well and good, and I'm used to getting packages from Raw Hide, and
> it's not normally a problem, but unfortunately tetex-1.0.7-35 is now
> gone! (all of the other packages install fine).  Again, not normally a
> problem (after all it says "at least 1.0.7-35"), so it's been replaced
> with 1.0.7-38, which again would be all fine and good, except that
> it's been compiled with the new GCC (as noted in the changelog of Dec
> 06).

Yes, I know.  I am looking at getting a newer teTeX package released
as an enhancement/bugfix advisory soon.  In the mean time I'll see if
I can rebuild the rawhide teTeX against a 7.2 build tree.

> So is there any way to smoothly install the necessary tools to use the
> XSL/FO/PassiveTex toolchain short of wholesale committing to the
> entire (unstable) distro of Raw Hide? =20

I have put everything except for teTeX here:
.  It should work
against 7.2 (I'm using those packages here on a 7.2 machine).  If
there are dependencies I've missed, please let me know.

> It would also be nice to be able to upgrade the binary without
> having to fiddle around manually with the ".cnf" files in tetex,
> which are just completely opaque to me [not being a great
> TeX-pert].)

You shouldn't need to.  If you have modified the texmf.cnf file then
you will find a texmf.cnf.rpmnew file after upgrade; just move the
=2Erpmnew file over the .cnf file.

Tim.
*/

--OZkY3AIuv2LYvjdk
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8Fc2gyaXy9qA00+cRAmH9AJ4ovHY/gXnaqzS4qd0tsx6T4HGa2gCeLMpT
SuQ1JLCJEhkcIk4k5VjRY0A=
=/aht
-END PGP SIGNATURE-

--OZkY3AIuv2LYvjdk--

Re: DOCBOOK-APPS: "link annotations can't be nested" from Passivetex(pdfxmltex)

[Tim Waugh]

--mfP1iJBimQeSOP+4
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Dec 10, 2001 at 06:33:10PM +1300, Dave Brooks, BCS Systems wrote:

> I'm using the latest version of Passivetex to try to produce PDF from=20

Version 1.11, posted a few days ago?

> Docbook. Processing the FO file produced from the following test document=
=20
> results in a "link annotations can't be nested" error from pdfxmltex the=
=20
> second time it is run - the first time I am warned (as expected) that the=
re=20
> are undefined cross references.

Works fine for me.

Tim.
*/

--mfP1iJBimQeSOP+4
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8FHCayaXy9qA00+cRAjZIAJ9Rp9IAmwZ1f6yYanaJlb+rPZKvAQCgsmZi
KJZ2BIVmhGuOFiJ/V56Z5MI=
=3pQk
-END PGP SIGNATURE-

--mfP1iJBimQeSOP+4--

Re: DOCBOOK-APPS: html cosmetics

[Tim Waugh]

--FWV58dOTQOM6W93I
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Sun, Dec 09, 2001 at 06:10:54PM -0600, G.L. Grobe wrote:

> Is there a simple example that does this posted anywhere's.

I just added this to the Selfdocbook:


 (XML edition)

> Also, I'm using db2html on my Redhat system and havn't yet figured out how
> to process these *driver files* w/ my own *.sgml files as show here.
> http://www.dpawson.co.uk/docbook/dsssl/dssslgeneral.html#custom

For newer versions of db2html (actually docbook2html) there is a -d
option for this.

Tim.
*/

--FWV58dOTQOM6W93I
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8FG+1yaXy9qA00+cRAs/dAJ9IJGXn3hvXQxrwd/LKV5udRJDYxACfRP8R
o5Uno4mAg+zIbGTQodFKKMY=
=GWX7
-END PGP SIGNATURE-

--FWV58dOTQOM6W93I--

Re: DOCBOOK-APPS: XSL for docbook.xml --> FOT ?

[Tim Waugh]

--s9YZkuRHoz8CjAJx
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Thu, Dec 06, 2001 at 11:39:54AM +0100, Norbert Pfistner wrote:

> Or are there other recomandations for processing docbook.xml with a XSL
> into PDF/PS (maybe even without using a java engine)?

I'm using PassiveTeX with quite good results.

Tim.
*/

--s9YZkuRHoz8CjAJx
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8D00nyaXy9qA00+cRAmyMAJ9gCsF54N9xjQuQl4DG5+vwXi2uiACfYuQv
0d5F/hXuYIFJToOeTkMhKYY=
=fZTW
-END PGP SIGNATURE-

--s9YZkuRHoz8CjAJx--

Re: DOCBOOK-APPS: Re: DOCBOOK: Docbook XML tools

[Tim Waugh]

--hiUvK+R7oewjwcXw
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Wed, Dec 05, 2001 at 05:54:33PM +0100, Yann Dirson wrote:

> You may want to have a look at sgml2x, which aims at simplifying
> SGML/XML processing with jade (this is a beta release, I know of some
> small bugs, but if you're just processing an "article" it should be OK).
> Install it, and just run "docbook2pdf" on your xml file.  Then play
> with the options :)

(Of course, you can do this with the docbook-utils package too.)

Tim.
*/

--hiUvK+R7oewjwcXw
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8DlYvyaXy9qA00+cRAlCWAJ9GDfSp5mlx43h61qOegr/x+60AMgCeM/nf
xR4OyrG1ELiU9Aw3AhW3A6A=
=o4Pc
-END PGP SIGNATURE-

--hiUvK+R7oewjwcXw--

Re: DOCBOOK-APPS: Strange fonts in new PassiveTeX

[Tim Waugh]

--BNK5cO+49IguOVQa
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Wed, Dec 05, 2001 at 05:16:47PM +0100, Jirka Kosek wrote:

> does anyone of you tried new version of PassiveTeX and xmltex? I
> grabbed them just now, and all fonts in formatted result are quite
> large and in Helvetica (instead of decent size Times Roman). To sum
> it, results from PassiveTeX are now totaly useless. ;(

Sebastian has a fixed PassiveTeX in testing at the moment I think.

Tim.
*/

--BNK5cO+49IguOVQa
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8DkouyaXy9qA00+cRAmZcAJ9qwUZ6n7hsHadbXMJC6nn2/Km0iwCglXtB
JEsZc174XW+lJaJi5EuUBmk=
=owJU
-END PGP SIGNATURE-

--BNK5cO+49IguOVQa--

Re: DOCBOOK-APPS: legalnotice id

[Tim Waugh]

On Thu, Nov 15, 2001 at 12:29:13PM -0500, Tammy Fox wrote:

> I have my stylesheet set to generate a link to a separate
> HTML page for the legalnotice. My legalnotice has
> an id set for it: ,
> but the HTML filename for it is still randomly generated.
> Am I doing something wrong or is this a bug?

I think this is intentional.  Take a look at html/dbparam.dsl:300
where there is this comment:

  ;; Name of the output file for legal notices if
  ;; '%generate-legalnotice-link%' is true.  Since several legal
  ;; notices may occur (in a Set of Books, for example), this is no
  ;; longer a fixed filename.

How about this?:

(define ($legalnotice-link-file$ legalnotice)
  (if (and %use-id-as-filename%
   (attribute-string (normalize "id") legalnotice))
  (string-append (case-fold-down (attribute-string (normalize "id")
   legalnotice))
 %html-ext%)
  (string-append "ln"
 (number->string (all-element-number legalnotice))
 %html-ext%)))

Tim.
*/



msg02967/pgp0.pgp
Description: PGP signature

Re: DOCBOOK-APPS: Mandrake DSSSL and jadetex customizations

[Tim Waugh]

--NSWmqrgMASeejWAY
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Nov 13, 2001 at 04:57:55PM +0100, Michael Wiedmann wrote:

> Has anyone successfully tested the use of the 'url' package as suggested=
=20
> by the Mandrake 'jadetex.cfg' and DSSSL customization?

Yes, it works fine here.  xpdf doesn't handle the PDF output, but
ghostscript does.  I haven't tried Acrobat Reader myself.

Tim.
*/

--NSWmqrgMASeejWAY
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE78UNQyaXy9qA00+cRAiuBAJ9EVgVK7kWzdomznXpLhVhZr+4/YQCfZ571
ylnYYNC6LgNQToyRBOxY1HE=
=gxIE
-END PGP SIGNATURE-

--NSWmqrgMASeejWAY--

Re: DOCBOOK-APPS: Mandrake DSSSL and jadetex customizations

[Tim Waugh]

--MxYQAzdbOWKZB282
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Mon, Nov 12, 2001 at 02:55:59PM +0100, camille wrote:

> I have followed coding only from far, but URLs appear in black in both
> PDF and PS and the links work in PDF.

Huh.  The PostScript output looks great, but when trying to view PDF
output with xpdf I get this:

Error: This document uses Type 3 fonts - some text may not be
correctly displayed.  I guess it's an xpdf problem..

Thanks,
Tim.
*/

--MxYQAzdbOWKZB282
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE779l7yaXy9qA00+cRAlxGAJ4hV4BsAW8P0R5+kw1RnUDSwn9szACfRpJH
hVwcCyTEupDXecC08ObMMgI=
=9yIy
-END PGP SIGNATURE-

--MxYQAzdbOWKZB282--

Re: DOCBOOK-APPS: Mandrake DSSSL and jadetex customizations

[Tim Waugh]

--i6jgfrJswdyoXnQp
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Mon, Nov 12, 2001 at 01:46:35PM +, Tim Waugh wrote:

> I notice this particular customization is based on the '\url{...}'
> LaTeX stuff.  Have you found a way around the magenta-URL-text problem
> in PS output?  Also, do you get any URL output for PDF?

Oh, wait, it's in jadetex.cfg by the looks of it:

% URLs color is black
\hypersetup{colorlinks=false}

Great stuff.

Thanks,
Tim.
*/

--i6jgfrJswdyoXnQp
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE779NYyaXy9qA00+cRAqJ+AJ9BQOJrAOIbDs8lZZbAqzhHO8nIlACdH8I2
/YiGpy4GYgJrIL+9mHohF34=
=y/lz
-END PGP SIGNATURE-

--i6jgfrJswdyoXnQp--

Re: DOCBOOK-APPS: Mandrake DSSSL and jadetex customizations

[Tim Waugh]

--Y+QtaVjtxOtr8cXH
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Mon, Nov 12, 2001 at 02:39:50PM +0100, camille wrote:

> - hyphenation problems on URLs and menu entries

I notice this particular customization is based on the '\url{...}'
LaTeX stuff.  Have you found a way around the magenta-URL-text problem
in PS output?  Also, do you get any URL output for PDF?

Tim.
*/

--Y+QtaVjtxOtr8cXH
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE779K6yaXy9qA00+cRAt6YAJ47kLfswwzRGvPBcMrit3rnDqSVKgCgi7W8
D+iA+xWayB49k7jcc6RIQ1o=
=4DxD
-END PGP SIGNATURE-

--Y+QtaVjtxOtr8cXH--

Re: DOCBOOK-APPS: Mac OS X and OpenJade

[Tim Waugh]

--8jcWiON1L7A8HfS7
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Mon, Nov 12, 2001 at 11:22:02AM +0100, Ali Saffari wrote:

> checking whether the C++ compiler (c++ -O2 ) is a cross-compiler... yes

This looks wrong for a start.  You might want to take a look at what's
in config.log to see why it comes to the conclusion that your C++
compiler is a cross-compiler.

I'll send you the patches that are used for building the Red Hat Linux
openjade RPM under separate cover.

Tim.
*/

--8jcWiON1L7A8HfS7
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE776c8yaXy9qA00+cRAtu6AKCnLhEV4XJnjkC5aqXfB5EMLxkNHgCgrG9L
mAZ9dGCfTmJB1LySB/Oo07M=
=9V//
-END PGP SIGNATURE-

--8jcWiON1L7A8HfS7--

Re: DOCBOOK-APPS: URLs as system identifiers

[Tim Waugh]

--wuUGvGHayROCMC3J
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Nov 02, 2001 at 03:33:11PM -0500, Adam Di Carlo wrote:

> > (The Red Hat Linux openjade RPMs build without http support; should I
> > change this?)
>=20
> Yes, I think so.

Okay.

> > The real solution would be for openjade to support XML Catalogs.  On
> > my system, a document that starts:
>=20
> Uh, what's an XML Catalog?  *blink* Do you mean SGML Open Catalogs?
> Or is there really a perverse new standard, and if so, god help us?

I mean XML Catalogs.

http://www.oasis-open.org/committees/entity/spec.html

"Abstract

The requirement that all external identifiers in XML documents must
provide a system identifier has unquestionably been of tremendous
short-term benefit to the XML community. It has allowed a whole
generation of tools to be developed without the added complexity of
explicit entity management.

However, the interoperability of XML documents has been impeded in
several ways by the lack of entity management facilities:

1. External identifiers may require resources that are not always
   available. For example, a system identifier that points to a
   resource on another machine may be inaccessible if a network
   connection is not available.

2. External identifiers may require protocols that are not accessible
   to all of the vendors' tools on a single computer system. An
   external identifier that is addressed with the ftp: protocol, for
   example, is not accessible to a tool that does not support that
   protocol.

3. It is often convenient to access resources using system identifiers
   that point to local resources. Exchanging documents that refer to
   local resources with other systems is problematic at best and
   impossible at worst.

The problems involved with sharing documents, or packages of
documents, across multiple systems are large and complex. While there
are many important issues involved and a complete solution is beyond
the current scope, the OASIS membership agrees upon the enclosed set
of conventions to address a useful subset of the complete problem. To
address these issues, this Standard defines an entity catalog that
maps both external identifiers and arbitrary URI references to URI
references."

Tim.
*/

--wuUGvGHayROCMC3J
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE74yd8yaXy9qA00+cRAuxqAJ97oiwc2QNtbq90KQIm8HdUfuNa7gCeIK9E
PYUruvm1luqR5IcPIQozg8s=
=k+tl
-END PGP SIGNATURE-

--wuUGvGHayROCMC3J--

Re: DOCBOOK-APPS: Linux file layout

[Tim Waugh]

--ESr4fftwSwE2Rzwi
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Oct 30, 2001 at 11:35:21AM -0500, Gregory Leblanc wrote:

> There's a section on this in the FHS (Filesystem Heirarchy Standard).=20
> Basically it says that things belong under /usr/share/sgml.  Take a look
> at a modern debian or redhat (7.1 or newer) system, as those are pretty
> close to where things "ought" to go.

Indeed.  Still up for grabs is where the XML stuff (DTD, stylesheets)
should go.  But that's not really for this list.

Tim.
*/

--ESr4fftwSwE2Rzwi
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD4DBQE73wPbyaXy9qA00+cRAl+PAJYlMzDzkBSAldLMIv7kTj0JpoQrAJwLPFUd
Ht9J1514z4s8abWDNzaQZw==
=GE1e
-END PGP SIGNATURE-

--ESr4fftwSwE2Rzwi--

Re: DOCBOOK-APPS: URLs as system identifiers

[Tim Waugh]

--RyB1I56Pcq42iZjE
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Thu, Oct 25, 2001 at 12:43:28PM -0400, Adam Di Carlo wrote:

> This isn't true.  You probably just have a version which was built
> with http support.
  ^out

(The Red Hat Linux openjade RPMs build without http support; should I
change this?)

> Probably the real thing you wanna do is use the PUBLIC identifier (and
> the local copy of the DTD) rather than the system identifier (using
> the DTD off the network).  You should put "OVERRIDE YES" in the
> catalog file that contains the entry for the docbook entry you
> reference in your DOCTYPE declaration.

DocBook XML documents have both a public identifier and a system
identifer though, don't they?

The real solution would be for openjade to support XML Catalogs.  On
my system, a document that starts:

http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd";[
...
]>

is processed by xsltproc without any network access needed.  The DTD
is fetched from the local disk, and associated with the URL by an XML
Catalog.

Tim.
*/

--RyB1I56Pcq42iZjE
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE73u5WyaXy9qA00+cRAhYQAJ9LwD8o9RHjyGUvceHV0vByiTlWVACgjc7t
uHZC3i+jtOMM4bdwKIAnFAo=
=VsYz
-END PGP SIGNATURE-

--RyB1I56Pcq42iZjE--

Re: DOCBOOK-APPS: "--" again; this time via passivetex

[Tim Waugh]

--GEn4szYucjS2InE7
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Oct 12, 2001 at 06:02:20PM +0200, Jirka Kosek wrote:

> PassiveTeX reads directly XML source so there is no preprocessing stage
> as in JadeTeX which can turn -- into -\/-\/. Standard TeX ligature
> processing cann't be turned off AFAIK. Maybe Sebastian could talk more
> on this topic.
>=20
> > Any ideas on how to fix it, or even whereabouts the bug is?
>=20
> If you want quick workaround, you can insert zero-width joining space
> character (?) between two -:
>=20
> Two dashes or not two dashes: -​-?

We already have a preprocessing stage of course: XSL-T.  Here is some
XSL that works around the problem in a better way, by translating '--'
in the XML source into '-​-' in the XSL-FO.

Tim.
*/


http://www.w3.org/1999/XSL/Transform";
xmlns:fo=3D"http://www.w3.org/1999/XSL/Format";
version=3D'1.0'>




 
 
  
   

 
 -​-
 

   
  
  
   
  
 



 
  
 





--GEn4szYucjS2InE7
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE73o9hyaXy9qA00+cRAjeeAJ9YX2t3AsBR3Gs78zD5PLMJfHr3RACeIL31
/0pB0goPwZbXWh1/pMQXaJA=
=Sro3
-END PGP SIGNATURE-

--GEn4szYucjS2InE7--

Re: DOCBOOK-APPS: pdfTeX and PNG images

[Tim Waugh]

--5scqBHJkaHHnMcIt
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Sun, Oct 28, 2001 at 08:14:22PM +0100, Peter Eisentraut wrote:

> Looks like a botched installation.  I have tetex-1.0.7-7 as contained in
> Red Hat 7.0.

The libpng ABI changed but the soname didn't, and the teTeX RPM didn't
get rebuilt.  Unfortunately it didn't get caught in time.

In theory, you should just be able to rebuild the package using 'rpm
--rebuild tetex*.src.rpm' to get a working set-up; in practice, the
LaTeX included in that package will complain that it is too old.

I think that the teTeX package from Red Hat Linux 7.2 should work on
Red Hat Linux 7.0, so you might want to give that a go.

Tim.
*/

--5scqBHJkaHHnMcIt
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE73F9WyaXy9qA00+cRApUzAJ4jgmd7Gehd+71mYKaeNePVUlPoawCfVSrw
pMCcwj1El2Dtxh1VBfpUa2U=
=zwE8
-END PGP SIGNATURE-

--5scqBHJkaHHnMcIt--

Re: DOCBOOK-APPS: Best Linux toolchain for SGML->PDF

[Tim Waugh]

--ET435nAiv4vKWmQH
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Oct 27, 2001 at 07:29:29PM -0400, Tammy Fox wrote:

> > I've also encountered various TeX-related problems, such as pdfTeX not
> > accepting png images with some weird error message (and I haven't found=
 a
> > way to make pdf images, so I'm running "imageless"), "font substitution=
s"
> > that I have no clue about, and formatting reference pages into TeX mess=
es
> > up the linking completely.
> >=20
>=20
> Try used EPS images. I convert my PNGs into EPSs, convert SGML to
> TeX, TeX to DVI, DVI to PS, and finally using ghostscript to convert
> PS to PDF.

On the subject of getting images to work for PDF and for PS from the
same source:

For DocBook SGML and the jade/openjade toolchain, see the solution I
am using for the Selfdocbook:

   

 


 

   

The trick is to miss off the extension for 'format=3D"eps"', and use
this DSSSL:

;; TeX backend can go to PS (where EPS is needed)
;; or to PDF (where PNG is needed).  So, just
;; omit the file extension altogether and let
;; tex/pdfjadetex sort it out on its own.
(define (graphic-file filename)
 (let ((ext (file-extension filename)))
  (if (or (equal? 'backend 'tex) ;; Leave off the extension for TeX
  (not filename)
  (not %graphic-default-extension%)
  (member ext %graphic-extensions%))
  filename
  (string-append filename "." %graphic-default-extension%

For DocBook XML with PassiveTeX, I am using this although I don't
think it's strictly to the DTD:

   

 


 

   

I use fig2dev to create formats from .fig source.

Tim.
*/

--ET435nAiv4vKWmQH
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD4DBQE73CN9yaXy9qA00+cRAmzxAJ40dbahZaeXnPZP0tk7CqIpfBWiYwCXeJV7
jYnQtK43cuhfKclBeIzqzA==
=I8mm
-END PGP SIGNATURE-

--ET435nAiv4vKWmQH--

Re: DOCBOOK-APPS: "--" again; this time via passivetex

[Tim Waugh]

--3pZQ0wszfDg7ZRO+
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Oct 12, 2001 at 06:02:20PM +0200, Jirka Kosek wrote:

> If you want quick workaround, you can insert zero-width joining space
> character (?) between two -:
>=20
> Two dashes or not two dashes: -​-?

Thanks, that work-around works fine until a real fix can be found.

Tim.
*/

--3pZQ0wszfDg7ZRO+
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE7ypMOyaXy9qA00+cRApVDAKCE8imhP+277zVWmNcTh6gLUdlJUgCfYqdA
+wlu1tgVqSKwBF/aMTWmmNE=
=sWMA
-END PGP SIGNATURE-

--3pZQ0wszfDg7ZRO+--

Re: DOCBOOK-APPS: Problem

[Tim Waugh]

On Fri, Oct 12, 2001 at 07:55:23PM +0200, Juan R. Migoya wrote:

> It seems that the "pdfjadetex" macro has been missed in db2pdf
> when calling pdftex. I don't know anything about db2tex
> but this is the message I get when I run pdftex without the
> "&pdfjadetex" option or when the "pdfjadetex.fmt" is not
> valid for some reason.

This is probably another instance of the Red Hat Linux jadetex
packaging bug: there is a missing trigger (now fixed), so you need to
run this by hand:

fmtutil --cnffile /usr/share/texmf/tex/jadetex/jadefmtutil.cnf --all

Tim.
*/



msg03230/pgp0.pgp
Description: PGP signature

DOCBOOK-APPS: "--" again; this time via passivetex

[Tim Waugh]

--924gEkU1VlJlwnwX
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

This troublesome document:


Two dashes or not two dashes: --?

gets converted using openjade to TeX correctly, so long as you use the
right patch from CVS. (The two dashes come out as '-\/-\/', and so
don't get interpreted together as a long dash.)

But xmltex/passivetex gives incorrect output, that reads:

"Two dashes or not two dashes: -?" (the single dash is long)

Any ideas on how to fix it, or even whereabouts the bug is?

Thanks,
Tim.
*/

--924gEkU1VlJlwnwX
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE7xwDpyaXy9qA00+cRAsN9AKCL/nDYFK9uwAVtDzFdYDKGes6TCwCgh2UQ
bFBCoRjsvaTBwf2RT6xkkkY=
=/Hhk
-END PGP SIGNATURE-

--924gEkU1VlJlwnwX--

Re: DOCBOOK-APPS: Fatal format error; I'm stymied ...

[Tim Waugh]

On Tue, Oct 02, 2001 at 09:37:59AM +0930, Richard Sharpe wrote:

> pdfjadetex on a clean machine gives me:
> (Fatal format file error; I'm stymied)

Can't reproduce this.  On a clean install of Red Hat Linux 7.1, 'make
selfdocbook.pdf' works fine for me when I unpack
http://cyberelk.net/tim/docbook/selfdocbook.tar.gz>.

tetex-1.0.7-15
jadetex-3.3-1

(It also works after I rebuild the format files, of course.)

What are you doing different to me?

Tim.
*/

 PGP signature

Re: DOCBOOK-APPS: Fatal format error; I'm stymied ...

[Tim Waugh]

On Tue, Oct 02, 2001 at 12:39:12AM +0930, Richard Sharpe wrote:

> Even though I have run 'fmtutil --all', I am still getting the above.

Try:

fmtutil --cnffile /usr/share/texmf/tex/jadetex/jadefmtutil.cnf --all

If you are using Red Hat based packages, the relevant bug report is
here:

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=51921>

Tim.
*/

 PGP signature

Re: DOCBOOK-APPS: Re: DOCBOOK: Including a DocBook document in aDocBook document

[Tim Waugh]

On Sun, Apr 22, 2001 at 06:25:32PM -0500, David Cramer wrote:

> Is there a way around this? For example, is there a way to let emacs or
> XMetaL know that a document gets its document type declaration from
> another document?

Put this at the end of the file:





Tim.
*/

 PGP signature

Re: DOCBOOK-APPS: Getting started on Linux?

[Tim Waugh]

On Mon, Feb 05, 2001 at 10:17:21PM -0330, Michael D. Crawford wrote:

> Is there any kind of a quick start or howto guide for formatting DocBook
> documents using tools for Linux?

I don't know if this helps you, but it might:

http://people.redhat.com/twaugh/docbook/selfdocbook/>

Tim.
*/

 PGP signature

Re: DOCBOOK-APPS: PSGML 1.2.* and DTD compilation...

[Tim Waugh]

On Sun, Jan 14, 2001 at 07:20:51PM -0500, Norman Walsh wrote:

> Anyone else encountered this and constructed a workaround?

I've encountered this but haven't found a fix yet.  It apparently
broke somewhere between psgml-1.0.3 and psgml-1.1.4.

Tim.
*/

 PGP signature