From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: the "xdesc" module
Date: Wed, 18 Jul 2001 12:52:33 +0200 [thread overview]
Message-ID: <5.1.0.14.1.20010718124207.03e7b9e8@server-1> (raw)
In-Reply-To: <19911277763.20010717221948@bigfoot.com>
At 10:19 PM 7/17/2001 +0200, Giuseppe Bilotta wrote:
>Hi,
>
>I'm going quite deep in this xdesc module, as posted in the
>mailing list --maybe I'll change its name again to "objects",
>since it's all about objects and properties.
i will look into it later and see in what extend we can merge the ideas ; i
have both a simple database handler and sorted things available [use them
for adresses base and previous sorted biblio module] so there are some
frameworks already.
>But, to implement the object listing and sorting capabilities I
>need some extended TeXUtil support. The reason for this is that I
>plan to support listing of objects with multiple sorting keys. If
>it was going to be a single sort key, it could have been achieved
>hacking (overloading) the register feature, but that's too
>limiting.
there is something in texutil, but undocumented, had to to with abusing
sorted lists
>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 :-)
sure, but then more xml based; this is something i'm working on
>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}
since we want predicatibility:
{keyval,keyval,keyval}
and not pagenumber/realpagenumber, but the full location stamp [including
chapter and so, so that we can select!
also, this may be combined with indexes -)
>[o e = object entry]
>
>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]
there is already sort key support
>Can we discuss the implementation of this feature?
sure, but keep in mind that i have to work to finish, machines to install,
etc -)
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
next parent reply other threads:[~2001-07-18 10:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <19911277763.20010717221948@bigfoot.com>
2001-07-18 10:52 ` Hans Hagen [this message]
2001-07-19 10:10 ` Re[2]: " Giuseppe Bilotta
2001-07-19 11:16 ` Hans Hagen
2001-07-20 10:33 ` Re[3]: " Giuseppe Bilotta
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5.1.0.14.1.20010718124207.03e7b9e8@server-1 \
--to=pragma@wxs.nl \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).