public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Joe Cooper <joe@swelltech.com>
To: "Alan W. Irwin" <irwin@beluga.phys.uvic.ca>
Cc: docbook-tools-discuss@sourceware.cygnus.com
Subject: Re: pdf output.
Date: Tue, 27 Feb 2001 15:25:00 -0000	[thread overview]
Message-ID: <3A9C3837.7030806@swelltech.com> (raw)
Message-ID: <20010227152500.uzPDVaalzGnHX_0ievv_Z1RmQvlslrlqngctJuIU7Jg@z> (raw)
In-Reply-To: <Pine.LNX.4.21.0102271302390.21013-100000@localhost>

Thanks so much, Alan, for your quick and detailed fix it instructions.

I'll try following them to the letter and see what happens (I learned a 
few things...like rerunning the pdftex and pdfjadetex scripts...never 
heard of that one before--but I figured their must be something going on 
with all the stuff flying by during the RPM install!).

Hopefully, I'll have some printable output tonight.

Alan W. Irwin wrote:

> Hello Joe:
> 
> All I will say about your postscript problem is I suspect an unclean upgrade
> (see rpm comments below about how to insure a clean upgrade).  The rest of
> this post will concentrate on your pdf problems.
  >--Snipped for brevity--<

                                   --
                      Joe Cooper <joe@swelltech.com>
                  Affordable Web Caching Proxy Appliances
                         http://www.swelltech.com

  reply	other threads:[~2001-02-27 15:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-27 10:25 Joe Cooper
2001-02-27 14:58 ` Alan W. Irwin
2001-12-19 22:49   ` Joe Cooper [this message]
2001-02-27 15:25     ` Joe Cooper

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=3A9C3837.7030806@swelltech.com \
    --to=joe@swelltech.com \
    --cc=docbook-tools-discuss@sourceware.cygnus.com \
    --cc=irwin@beluga.phys.uvic.ca \
    /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).