Re: About DSSSL 2 Specifications

[Matthias Clasen <clasen@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>]

> Actually the DSSSL-1 specifications allows a feature not implemented in
> OpenJade. This is part of the declaration element and named The
> literal-described-char. In a certain way, this could show a very limited
> template based processing in DSSSSL. For DSSSL-2, a more elaborate template
> based construct could be proposed.

[...]

> 
> B) expand from this construct for template based processing
> ------------------------------------------------------------
> The above construct allows to substitute a string by an other. So each time
> the parser encounters a "logoSGML" it is substituted to "SGML User?s Group
> logo" in the source document grove elements. This is a kind of find and
> replace feature.
> 

No, this is a severe misunderstanding of the SGML/DSSSL character model.
A literal described char is a coded character (`bit combination' in ISO speak)
in the document which can not be described by reference to a coded character
in a standard charset. Thus it is described by a literal. DSSSL identifies
characters by their names and describes them by references to coded characters
in the `universal character set' ISO10646 (this is what standard-chars does)
or by simply naming them (in other-chars). The baseset-encoding and
literal-described-char forms define the map from coded characters in the
doc to DSSSL character names (via the description of the coded characters
in the SGML declaration).  

There is no string search and replace happening here at all.


-- 
Matthias Clasen, 
Tel. 0761/203-5606
Email: clasen@xxxxxxxxxxxxxxxxxxxxxxxxxx
Mathematisches Institut, Albert-Ludwigs-Universitaet Freiburg


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