public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Alan W. Irwin" <irwin@beluga.phys.uvic.ca>
To: docbook-tools-discuss@sources.redhat.com
Subject: Re: .pdf generation error using the "newer" tools
Date: Wed, 27 Dec 2000 06:36:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.21.0012081908280.6874-100000@localhost> (raw)
In-Reply-To: <Pine.LNX.4.10.10012081812470.4428-100000@lug.calpoly.edu>

Both the Cygnus DocBook packages and vanilla RedHat DocBook run on RedHat.
But you have to clearly choose Cygnus or vanilla.  If you try both on RedHat
they will interfere with each other. 

I don't want to get into a DocBook distribution war here, but my impression is the
Cygnus tools are generally better than the vanilla RedHat ones.  For example,
Cygnus is recommended to build the KDE documentation, and I have had more
troubles with the vanilla version than the Cygnus version for my documentation
project.

But to take advantage of Cygnus you have to get the latest version.  For
example, there was an upgraded package today at
ftp://sourceware.cygnus.com/pub/docbook-tools/new-trials/RPMS that Eric
kindly prepared to fix another bug that I found.

The major problem with pdfjadetex hasn't been fixed yet, but Eric said on
this list that it is on his ToDo list.  He will have to delay looking at it
until another higher priority project was completed, but I am willing to
settle for that.

Debian has a reliable DocBook system where pdfjadetex (and everything else
for my documentation project) works reliably for me, but if you don't have
access to Debian, I think you are going to have to wait to build your pdf
documents on Cygnus (or else give the vanilla Redhat DocBook system a try to
see if you can work around other problems there.) While waiting for pdf on
Cygnus you can certainly validate your input by looking at html or
postscript output.

Alan

email: irwin@beluga.phys.uvic.ca
phone: 250-727-2902	FAX: 250-721-7715
snail-mail:
Dr. Alan W. Irwin
Department of Physics and Astronomy,
University of Victoria, P.O. Box 3055,
Victoria, British Columbia, Canada, V8W 3P6 
__________________________

Linux-powered astrophysics
__________________________

On Fri, 8 Dec 2000, Bill Brooks wrote:

> On Sat, 2 Dec 2000, Alan W. Irwin wrote:
> 
> > Sorry for bringing this up again from the recent archives, but I am a newbie
> > on this list. 
> > 
> > I have exactly the same problem as Bill Brooks, and the suggested fix
> > doesn't work.
> 
> Sorry for the late follow-up. Yes, the suggested fix didn't work for me
> either. 
> 
> I really wonder what the developers of the Cygnus docbook tool chain are
> using...if it doesn't work on RedHat, what will it work on? 
> 
> I filed a bug report about this with RedHat and their support person
> mailed me back saying that the ones that ship with 6.2 work...the new
> RPM's on the old cygnus site aren't supported. 
> 
> Bill
> 
> 
> 

WARNING: multiple messages have this Message-ID
From: "Alan W. Irwin" <irwin@beluga.phys.uvic.ca>
To: docbook-tools-discuss@sources.redhat.com
Subject: Re: .pdf generation error using the "newer" tools
Date: Fri, 08 Dec 2000 19:39:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.21.0012081908280.6874-100000@localhost> (raw)
Message-ID: <20001208193900.6xioYkBXFCGwopIhoYZDIokWq17grY0NXjqWIIk42Dg@z> (raw)
In-Reply-To: <Pine.LNX.4.10.10012081812470.4428-100000@lug.calpoly.edu>

Both the Cygnus DocBook packages and vanilla RedHat DocBook run on RedHat.
But you have to clearly choose Cygnus or vanilla.  If you try both on RedHat
they will interfere with each other. 

I don't want to get into a DocBook distribution war here, but my impression is the
Cygnus tools are generally better than the vanilla RedHat ones.  For example,
Cygnus is recommended to build the KDE documentation, and I have had more
troubles with the vanilla version than the Cygnus version for my documentation
project.

But to take advantage of Cygnus you have to get the latest version.  For
example, there was an upgraded package today at
ftp://sourceware.cygnus.com/pub/docbook-tools/new-trials/RPMS that Eric
kindly prepared to fix another bug that I found.

The major problem with pdfjadetex hasn't been fixed yet, but Eric said on
this list that it is on his ToDo list.  He will have to delay looking at it
until another higher priority project was completed, but I am willing to
settle for that.

Debian has a reliable DocBook system where pdfjadetex (and everything else
for my documentation project) works reliably for me, but if you don't have
access to Debian, I think you are going to have to wait to build your pdf
documents on Cygnus (or else give the vanilla Redhat DocBook system a try to
see if you can work around other problems there.) While waiting for pdf on
Cygnus you can certainly validate your input by looking at html or
postscript output.

Alan

email: irwin@beluga.phys.uvic.ca
phone: 250-727-2902	FAX: 250-721-7715
snail-mail:
Dr. Alan W. Irwin
Department of Physics and Astronomy,
University of Victoria, P.O. Box 3055,
Victoria, British Columbia, Canada, V8W 3P6 
__________________________

Linux-powered astrophysics
__________________________

On Fri, 8 Dec 2000, Bill Brooks wrote:

> On Sat, 2 Dec 2000, Alan W. Irwin wrote:
> 
> > Sorry for bringing this up again from the recent archives, but I am a newbie
> > on this list. 
> > 
> > I have exactly the same problem as Bill Brooks, and the suggested fix
> > doesn't work.
> 
> Sorry for the late follow-up. Yes, the suggested fix didn't work for me
> either. 
> 
> I really wonder what the developers of the Cygnus docbook tool chain are
> using...if it doesn't work on RedHat, what will it work on? 
> 
> I filed a bug report about this with RedHat and their support person
> mailed me back saying that the ones that ship with 6.2 work...the new
> RPM's on the old cygnus site aren't supported. 
> 
> Bill
> 
> 
> 

  parent reply	other threads:[~2000-12-27  6:36 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-27  6:36 Alan W. Irwin
2000-12-02 19:17 ` Alan W. Irwin
2000-12-27  6:36 ` Bill Brooks
2000-12-08 18:16   ` Bill Brooks
2000-12-27  6:36   ` Alan W. Irwin [this message]
2000-12-08 19:39     ` Alan W. Irwin
2000-12-27  6:36     ` Eric Bischoff
2000-12-09  4:05       ` Eric Bischoff
2000-12-27  6:36   ` Eric Bischoff
2000-12-09  3:49     ` Eric Bischoff
2000-12-27  6:36     ` Tim Waugh
2000-12-09  3:56       ` Tim Waugh
2000-12-27  6:36       ` Mirko Streckenbach
2000-12-13  1:32         ` Mirko Streckenbach
2000-12-27  6:36         ` Eric Bischoff
2000-12-13  2:45           ` Eric Bischoff
2000-12-27  6:36 ` Alan W. Irwin
2000-12-02 22:58   ` Alan W. Irwin
2000-12-27  6:36   ` pdfjadetex does not work! (was .pdf generation error using the"newer" tools) Alan W. Irwin
2000-12-04  9:46     ` Alan W. Irwin
2000-12-27  6:36     ` jade catalog problems for Cygnus DocBook 4.1 XML Alan W. Irwin
2000-12-06 14:27       ` Alan W. Irwin
2000-12-27  6:36       ` Eric Bischoff
2000-12-07  2:41         ` Eric Bischoff
  -- strict thread matches above, loose matches on Subject: below --
2000-12-27  6:36 .pdf generation error using the "newer" tools Bill Brooks
2000-10-10 21:52 ` Bill Brooks
2000-12-27  6:36 ` Eric Bischoff
2000-10-11  4:53   ` Eric Bischoff
2000-12-27  6:36   ` Bill Brooks
2000-10-11 15:28     ` Bill Brooks
2000-12-27  6:36     ` Eric Bischoff
2000-10-12  4:54       ` Eric Bischoff

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.21.0012081908280.6874-100000@localhost \
    --to=irwin@beluga.phys.uvic.ca \
    --cc=docbook-tools-discuss@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).