RE: Unregistered flow objects

["Didier PH Martin" <martind@xxxxxxxxxxxxx>]

Hi Carlos,

Like Matthias, I discovered later that it is part of the spec. In fact, the
spec only contains two small paragraphs about this topic.

regards
Didier PH Martin
mailto:martind@xxxxxxxxxxxxx
http://www.netfolder.com
-----Original Message-----
From: owner-dssslist@xxxxxxxxxxxxxxxx
[mailto:owner-dssslist@xxxxxxxxxxxxxxxx]On Behalf Of Carlos Villegas
Sent: Monday, July 05, 1999 11:21 PM
To: dssslist@xxxxxxxxxxxxxxxx
Subject: Re: Unregistered flow objects



Didier Martin wrote:
> Actually, with this kind of expansion mechanism (the
> declare-flow-object-class ) you can add new flow objects to the core set
and
> have them switched on or off by a declaration. This mechanism, as you now,
> is not part of the spec and is specific to OpenJade/Jade.
>
As Matthias found out, the mechanism for adding extension flow objects
IS part
of the standard, see section 12.4.3 for the definition of the
application-
flow-object-class-declaration as the standard calls it. What it is not
standard, of course, is the particular extension flow objects added by
Jade,
and how that is actually done in the implementation. The declaration is
standard, but of course, the backend that implements those extensions
needs
to know about the new objects and so they need to be defined in some
internal structure inside jade. The same applies for additional
characteristics,
see section 12.4.6 declare-characteristic, as are the ones added to the
simple-page-sequence by the RTF and TeX backends (page-n-columns, etc.).

Cheers,


Carlos Villegas
Uniscope, Inc.


 DSSSList info and archive:  http://www.mulberrytech.com/dsssl/dssslist


 DSSSList info and archive:  http://www.mulberrytech.com/dsssl/dssslist