public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Eric Bischoff <e.bischoff@noos.fr>
To: Bill Brooks <wbrooks@lug.ee.calpoly.edu>
Cc: DocBook List <docbook-tools-discuss@sources.redhat.com>
Subject: Re: .pdf generation error using the "newer" tools
Date: Sat, 09 Dec 2000 03:49:00 -0000	[thread overview]
Message-ID: <3A321E35.14DCE2BD@noos.fr> (raw)
Message-ID: <20001209034900.mDEi6FEyMkze7Cn4RTYK6G5-TFApIf1D8u3jSd_Q0qs@z> (raw)
In-Reply-To: <Pine.LNX.4.10.10012081812470.4428-100000@lug.calpoly.edu>

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

Bill Brooks wrote:
> 
> 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.

... which means they provide outdated DTDs and style sheets then, if I
understand correctly. If this is true, then it's not good. At cygnus you
can find:
- The 4.1 DTD in SGML and XML versions
- The 1.59 style sheets
- Jadetex version 2.20
Which versions does RedHat provide currently?

Basically, it's a TeX problem, not a DocBook one. If RedHat fixes it in
the DocBook package, then they are wrong, because it breaks the
principle of packages independancy that they themselves edicted. The
right thing is to fix it in TeX package. This way, it will both work for
old and new Cygnus packages.

BTW, Cygnus is owned by RedHat - I'm criticizing them here, but I must
also thank them for helping the DocBook-tools project by hosting it :-).

Having said that, I must recognize that I also have my part of
responsability. I took their old patch to texmf.cnf and found it too
violent, so I removed from it everything that I found not indispensable.
This was wrong, JadeTeX really needs *lots* of TeX ressources. But I
must also say that I never considered this patch as something official,
I was just sending it to people to help them.

Here is how we can fix it. Someone, please send me RedHat's texmf.cnf.
Then I will put the changes they did as a patch file somewhere on
Cygnus' site. And promised, I won't remove anything from it this time.
It will eat all your memory, folks, get prepared ;-).

-- 
+----------------------------------------------------------------------+
| Éric Bischoff                              mailto:e.bischoff@noos.fr |
| (Old address, in case of problems:  mailto:ebisch@cybercable.tm.fr )  |
+----------------------------------------------------------------------+

  parent reply	other threads:[~2000-12-09  3:49 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 ` 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
2000-12-27  6:36 ` .pdf generation error using the "newer" tools Bill Brooks
2000-12-08 18:16   ` Bill Brooks
2000-12-27  6:36   ` Eric Bischoff [this message]
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-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 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=3A321E35.14DCE2BD@noos.fr \
    --to=e.bischoff@noos.fr \
    --cc=docbook-tools-discuss@sources.redhat.com \
    --cc=wbrooks@lug.ee.calpoly.edu \
    /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).