OpenJade and TeTeX (was: Re: Building the FTP tree (was Re: en_US/books/handbook/book.pd* b0rken))

[Murray Stokely]

On Tue, Apr 08, 2003 at 10:01:32AM -0700, Bruce A. Mah wrote:
> >   1.  Remove the hack in the Handbook's PDF build process to use
> >       tex, since the new port can handle the size of the Handbook.
> > 
> >   2.  Switch to OpenJade for the build to get bookmarks in the PDF
> >       files.
> > 
> > Thoughts?  We should probably shift this discussion over to doc at .
> 
> The only problem I see with #2 is that it'll probably take a flag day
> to do this.  If we switch the doc infrastructure to use OpenJade (with
> or without an override), then existing Jade-based toolchains will
> break.  I think the benefits outweigh the costs but I am uncertain how
> best to proceed.  Do we give lots of advance warning via multiple
> HEADSUP messages and just go for it?

As long as we continue to support Jade via 'USE_JADE' or something
similar then this sounds like a good idea to me.

> PS.  For newcomers: The issue is whether to switch to using OpenJade
> (rather than Jade) for all doc builds.  OpenJade is under active
> development, and we are forced to use OpenJade on the 64-bit platforms
> anyways.  At one point, there were concerns about OpenJade's ability
> to handle non-English languages, but my impression is that those have
> been resolved.

It seems many people are generally under the assumption that OpenJade
is under "active" development, but the last I checked that really
wasn't the case.  I had some patches to commit and they even gave me
commit access on sourceforge ISTR but there was hardly anyone actually
doing any work.  When I've worked with it I have indeed found some
cool new stuff, but I also have found other parts broken that "just
worked" with regular jade.  Have they started doing regular releases?

I don't mean to be negative, because I have not evaluated OpenJade in
over a year.  I just want us to keep this in mind and move forward
cautiously and not just because of misconceptions.

So, do not break my jade setup (which may have special hacks for my
print-output activities) to do this.  You can switch the default to
OpenJade, but regular jade must still be supported.

	- Murray
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 155 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20030408/ab6fc251/attachment.sig>