Bug#535828: Jade changed

[Neil Roeth <neil@debian.org>]

On Nov 11, Joachim Breitner (nomeata@debian.org) wrote:
 > Hi Neil, Hi Paul,
 > 
 > Am Dienstag, den 10.11.2009, 20:21 -0500 schrieb Neil Roeth:
 > > Thanks for bringing me into this.  The original Jade package was forked and
 > > made into two separate packages, OpenJade and OpenSP.  This was done outside
 > > of Debian, but both are also in Debian and also maintained by me.  So, we
 > > should use OpenSP.  I am planning to remove Jade from Debian when I get around
 > > to it, AFAIK, there is nothing it does that OpenJade and OpenSP cannot do.
 > 
 > thanks. Do you have any estimate as to when this will happen? E.g.,
 > should I look into packaging Serna against the current Jade in Debian
 > (possibly with a patched Jade inside), once the other issues with Serna
 > are resolved, or do you think youâ??ll get around to do with within the
 > next weeks, and Serna should concentrate on being buildable against
 > OpenSP?
 > 
 > @Paul: I guess your modifications best go to this list
 > https://lists.sourceforge.net/lists/listinfo/openjade-devel
 > (which is discouraging inactive, according to the archive). Have you
 > tried contacting them before?

I am not that clear on what the modifications in Serna are, but if they have
to do with using a different character set, one of the differences between SP
and OpenSP is that the latter uses 32 bit characters.  So, first thing to do
is just try using libosp instead of libsp and see what happens in Serna.
Perhaps the local modifications will not be needed.

You are correct, that mailing list is where the modifications should go.  I am
on that mailing list.  OpenJade and OpenSP are not being actively developed.
The SGML/DTD/DSSSL paradigm that they support has faded in popularity while
the XML/Schema/XSL paradigm has grown. That's why it's quiet.

-- 
Neil Roeth