From: Giuseppe Bilotta <bourbaki@bigfoot.com>
Subject: Extended description -- complete with sorts and selection
Date: Mon, 12 Nov 2001 11:16:10 +0100 [thread overview]
Message-ID: <145178722.20011112111610@bigfoot.com> (raw)
Hello ConTeXt users!
I'm proud to announce the first "real" release of my xdesc
(extended descriptions) module, with selection and multisorting
capabilities. Please find attached the xdesc.zip file, containing:
* a patched texutil.pl; waiting for Hans to provide external
module support for texutil, I had to patch
support for xdesc right in the main file;
rename the texutil.pl you already have as
something like texutil.original and
replace it with this one.
The patch consists only in three routines
(look for "patch" in the file to find them)
and a couple of lines to trigger them. It
doesn't touch any other code. I will
discuss with Hans the details for the
plug-in interface of TeXUtil, so the next
version will probably come in a Perl
module rather than a patch ...
* t-xdesc.tex; the module; for those using the previous version
(that is nobody :->): the interface has slightly
changed --you don't use angle brackets (<>) to call
slot values within a template, but the command
\getslot. Also, the list placement commands have
changed (see module and example file for further
details). Put this in the "user" directory in the
ConTeXt tree and refresh the filename database.
* desc-tst.tex; example test file. (Snippet from the document that
originally called for the need of extended
descriptions). Put it anywhere and test it.
Known bugs/limitations/todos:
* does not integrate with the ConTeXt multilingual interface
(yet).
* is not the most robust or fast or otherwise optimized code; I
will optimize/make it robust as the need arises *if* I know how to
fix/optimize it.
* object selection in list placement does not (yet) support
by"section" and such.
* I suspect it consumes string space very fast.
* no \start .. \stop pairs are defined (yet). Will probably come
with the multilingual interface.
* not thoroughly tested.
Other comments:
The next version of the epigraph module will very probably be
based on this xdesc module. (I wonder if it's worth writing it,
though: it's not too hard and much more customizable to just say
\defineextendeddescription[epigraph][epigraphs]
[author=,year=,source=,
whateverotherattributeyouwantforyourepigraphs=,]
and then use it as
\epigraph[author={Donald Arsenau},
title={post on {\tt comp.text.tex}},
note={May the 15th, 2001}]
{\quotation{Acrobat} is so named because of the contortions one
must do to get around its bugs.}
Any comments/suggestions/critics/enhancement requests are welcome.
For Hans: I'm pretty sure the code (especially the Perl code) is
independent (or "indipendentable") enough from the particular
structure of the xdescs, so an XML interface (maybe even an
interface to BibTeX databases) is feasible.
--
Giuseppe "Oblomov" Bilotta
next reply other threads:[~2001-11-12 10:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-12 10:16 Giuseppe Bilotta [this message]
2001-11-12 12:46 ` 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=145178722.20011112111610@bigfoot.com \
--to=bourbaki@bigfoot.com \
/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).