Re[2]: the "xdesc" module

[Giuseppe Bilotta <bourbaki@bigfoot.com>]

Wednesday, July 18, 2001 Hans Hagen wrote:

>>Since the "objects" code could be used as a base for lots of
>>things, among which epigraphs and bibliographies, in a
>>"consistent" and highly customizable way (see the template
>>feature), I think that core support for it can be taken in
>>consideration :-)

HH> sure, but then more xml based; this is something i'm working on

I thought that XML was just a "wrapper" around TeX code? That is,
TeX code is defined first, and then a XML wrapper to turn XML code
to TeX code?

>>Now, what am I exactly thinking about? The .tui file would contain
>>entries of this kind:
>>
>>o d {objname} {keyname} {keyname} ... {keyname}
>>
>>[o d = object define]
>>
>>which would inform TeXUtil of the order of the keys of the object
>>{objname}. Then we would have entries in the form
>>
>>o e {objname} {tag} {keyval} {keyval} ... {keyval} {pagenumber}
>>{realpage}

HH> since we want predicatibility:

HH> {keyval,keyval,keyval}

Ok.

HH> and not pagenumber/realpagenumber, but the full location stamp [including 
HH> chapter and so, so that we can select!

Ok.

HH> also, this may be combined with indexes -)

I thought about using indexes, initially, but I could not find a
way to sort on different, possibly multiple, keys.

>>produced by the \get<object>[objref] commands, (I still have to
>>think of a "nice" way to allow sanitized keyvals) and finally
>>entries in the form
>>
>>o s {objname} {keyname} {keyname} {keyname} ... {keyname}
>>
>>[o s = object sort]

HH> there is already sort key support

Uh? I missed that! How do you do it?

>>Can we discuss the implementation of this feature?

HH> sure, but keep in mind that i have to work to finish, machines to install, 
HH> etc -)

Oops :-) I guess I'm the only one here with nothing to do in my
hands ... (well, unless I gather enough will to start to study for
the doctorate ...) ;-)

--
Giuseppe "Oblomov" Bilotta