[OpenJade-devel] openjade branches (Re: Implied SGML declaration)

[Karl E. <ke...@gm...>]

Ian Castle <ian...@op...> writes:

> I didn't remove it from CVS because it wasn't necessary. The makefiles
> don't mention refer to it and I was trying to touch as little as
> possible...
>
> Really, we want to switch to HEAD - or create a new branch for 1.4 and
> start from there....

Okay, I'll not touch the openjade RELEASE-1_3 branch for cosmetical
changes.  Unfortunately I don't know how much HEAD differs from the
RELEASE branch.  The new flow objects will coming soon and I'd like to
see them release ASAP.  This would probably mean it's better to
continue with the current RELEASE branch -- an in case it's necessary
to release another 1.3.x version we can make this a branch of
RELEASE-1_3:

    RELEASE-1_3 -> 1.3.2 --|new flow objects|--> 1.4.0
                     |
                  branch
                     |
                     +--> 1.3.3

Or as you like; you are more familiar with the CVS.

> Cleaning up configure.in is probably worthwhile.

Okay, I'll apply this simple "fix".

> Are we doing a 1.3.3?
>
> I've put in a small fix for the RTF backend.. not sure if it cures the
> problem that the Alabama people were having with wordperfect though.

Good.  I cannot judge about RTF.  If someone is able to track down the
table problem, a new 1.3.x release would be a good thing.

Otherwise, parts of SP are broken, some AF features don't work:

    #MAPTOKEN is announced as "new".

    Deriving attribute content work with nsgmls.jc but not with
    onsgmls, and that's very bad -- we lost a feature.

-- 
ke...@su... (work) / ke...@gm... (home):              |
http://www.gnu.franken.de/ke/                            |      ,__o
Free Translation Project:                                |    _-\_<,
http://www.iro.umontreal.ca/contrib/po/HTML/             |   (*)/'(*)