public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Eric Bischoff <ebisch@cybercable.tm.fr>
To: Thomas Porter <txporter@mindspring.com>
Cc: docbook-tools-discuss@sourceware.cygnus.com
Subject: Re: Jadetex and pdftex problems, sgml file included
Date: Wed, 27 Dec 2000 06:36:00 -0000	[thread overview]
Message-ID: <3993FD77.872875E1@cybercable.tm.fr> (raw)
In-Reply-To: <3993F809.CC375EED@mindspring.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1451 bytes --]

Thomas Porter wrote:
> 
> Eric,
> 
> Thanks for the work on this, but I determined that my problem was that
> pdfjadetex in the rpm was generated with pdftex version 13, not version
> 14 like I am using.

If I understand well,

	- I've corrected a problem that you had not and that I had
	- I haven't corrected the problem that you had and that I had not

with the very same file. Funny ;-).

> I ended up downloading the jadetex src.rpm in order to get the
> jadetex.ini and pdfjadetex.ini files out of it, then rebuilt the format
> files using pdfinitex.
> 
> Just a suggestion to the jadetex rpm maintainer:  they might want to
> include the .ini files in the binary rpm to allow people to more easily
> rebuild their .fmt files if needed.

Please send me a corrected SPEC file, and I'll rebuild the package and
I'll put it online.

You'll probably only need to add the ini files you want to the %Files
section at the end of the SPEC file.

-- 
 Éric Bischoff   -   mailto:ebisch@cybercable.tm.fr
 __________________________________________________
                                           \^o~_.
     .~.                           ______  /( __ )
     /V\         Toys story         \__  \/  (  V
   //   \\                            \__| (__=v
  /(     )\                        |\___/     )
    ^^-^^                           \_____(  )
     Tux                        Konqui     \__=v
 __________________________________________________

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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.10.10008101321530.9281-100000@traveller.rlf.org>
     [not found] ` <3992EA24.A888C4D4@cybercable.tm.fr>
     [not found]   ` <3992F924.FDA54CF4@mindspring.com>
2000-12-27  6:36     ` Eric Bischoff
2000-12-27  6:36       ` Thomas Porter
2000-12-27  6:36         ` Eric Bischoff [this message]

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=3993FD77.872875E1@cybercable.tm.fr \
    --to=ebisch@cybercable.tm.fr \
    --cc=docbook-tools-discuss@sourceware.cygnus.com \
    --cc=txporter@mindspring.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).