public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Eric Bischoff <e.bischoff@noos.fr>
To: Mirko Streckenbach <strecken@infosun.fmi.uni-passau.de>,
	DocBook Tools Mailing List
	<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: <00121311454901.01268@boson.caldera.de> (raw)
In-Reply-To: <d8fg0jsk6o1.fsf@cuba.fmi.uni-passau.de>

Le Mercredi 13 Décembre 2000 10:32, vous avez écrit :
> Tim Waugh <twaugh@redhat.com> writes:
> > On Sat, Dec 09, 2000 at 12:57:41PM +0100, Eric Bischoff wrote:
> > > - The 4.1 DTD in SGML and XML versions
> > > - The 1.59 style sheets
> > > - Jadetex version 2.20
> > > Which versions does RedHat provide currently?
> >
> > 3.1(!) DTD, 1.57 stylesheets, openjade 1.3.
>
> BTW: Is it planned for the "new-trials" packages to move from
> jade-1.2.1 to openjade-1.3?

I haven't the time for this right now. If someone wants to do it, then fine, 
he can send me the resulting source package, and I will integrate it to the 
others (we will need a Provide: virtual capability to be able to use 
indifferently one or the other package) but I won't do it.

> The compiler in RedHat 7 does not compile jade-1.2.1 out of the box
> and I double the official gcc-3 will, when it is
> realeased. Historcially newer versions of gcc have always broken the
> out of the box compilation for jade.

It compiles out of the box on my LinuxPPC. For Caldera, I had to do a patch 
against gcc, that's true, but now it works. Another solution would be to test 
this patch on a vanilla RedHat. Volunteers please mail in private.

-- 
Éric Bischoff  -  Documentation and Localization
Caldera (Deutschland) GmbH - Linux for eBusiness
Tel: +49 9131 7192 300 -  Fax: +49 9131 7192 399
http://www.caldera.de/

WARNING: multiple messages have this Message-ID
From: Eric Bischoff <e.bischoff@noos.fr>
To: Mirko Streckenbach <strecken@infosun.fmi.uni-passau.de>,
	DocBook Tools Mailing List
	<docbook-tools-discuss@sources.redhat.com>
Subject: Re: .pdf generation error using the "newer" tools
Date: Wed, 13 Dec 2000 02:45:00 -0000	[thread overview]
Message-ID: <00121311454901.01268@boson.caldera.de> (raw)
Message-ID: <20001213024500.QzlhHpwsvfkgMaloNOH0rksN-vzYjLuf09BNoQ2g3jU@z> (raw)
In-Reply-To: <d8fg0jsk6o1.fsf@cuba.fmi.uni-passau.de>

Le Mercredi 13 Décembre 2000 10:32, vous avez écrit :
> Tim Waugh <twaugh@redhat.com> writes:
> > On Sat, Dec 09, 2000 at 12:57:41PM +0100, Eric Bischoff wrote:
> > > - The 4.1 DTD in SGML and XML versions
> > > - The 1.59 style sheets
> > > - Jadetex version 2.20
> > > Which versions does RedHat provide currently?
> >
> > 3.1(!) DTD, 1.57 stylesheets, openjade 1.3.
>
> BTW: Is it planned for the "new-trials" packages to move from
> jade-1.2.1 to openjade-1.3?

I haven't the time for this right now. If someone wants to do it, then fine, 
he can send me the resulting source package, and I will integrate it to the 
others (we will need a Provide: virtual capability to be able to use 
indifferently one or the other package) but I won't do it.

> The compiler in RedHat 7 does not compile jade-1.2.1 out of the box
> and I double the official gcc-3 will, when it is
> realeased. Historcially newer versions of gcc have always broken the
> out of the box compilation for jade.

It compiles out of the box on my LinuxPPC. For Caldera, I had to do a patch 
against gcc, that's true, but now it works. Another solution would be to test 
this patch on a vanilla RedHat. Volunteers please mail in private.

-- 
Éric Bischoff  -  Documentation and Localization
Caldera (Deutschland) GmbH - Linux for eBusiness
Tel: +49 9131 7192 300 -  Fax: +49 9131 7192 399
http://www.caldera.de/

  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 ` 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   ` 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   ` 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 [this message]
2000-12-13  2:45           ` Eric Bischoff
  -- strict thread matches above, loose matches on Subject: below --
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=00121311454901.01268@boson.caldera.de \
    --to=e.bischoff@noos.fr \
    --cc=docbook-tools-discuss@sources.redhat.com \
    --cc=strecken@infosun.fmi.uni-passau.de \
    /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).