From: Tobias Burnus <tobias.burnus@physik.fu-berlin.de>
Cc: ntg-context@ntg.nl
Subject: Re: epigraphs and subtitles?
Date: Wed, 7 Aug 2002 19:28:18 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.44.0208071927330.4852-100000@warp9.physik.fu-berlin.de> (raw)
In-Reply-To: <2893740.1028739316653.JavaMail.cpadmin@nassol01.mcs.muohio.edu>
Hi,
> Epigraphs. Peter Wilson's epigraph LaTeX style is a good model, but it
> would work something like \epigraph[attribution]{epigraph text}.
I think http://digilander.libero.it/bilotta/giuseppe/xdesc.zip
does such a thing (search for xdesc or epigraph at the list archive).
Tobias
next prev parent reply other threads:[~2002-08-07 17:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-07 16:55 Bruce D'Arcus
2002-08-07 17:28 ` Tobias Burnus [this message]
2002-08-11 17:16 ` Re[2]: " Giuseppe Bilotta
2003-01-13 16:36 ` Long section headings in footertexts Adam Lindsay
2003-01-13 16:56 ` Duncan Hothersall
2003-01-13 17:06 ` Adam Lindsay
2003-01-14 17:07 ` Hans Hagen
[not found] <2893740.1028739316653.JavaMail.cpadmin@nassol01.mcs.muohio .edu>
2002-08-08 6:54 ` epigraphs and subtitles? Hans Hagen
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=Pine.LNX.4.44.0208071927330.4852-100000@warp9.physik.fu-berlin.de \
--to=tobias.burnus@physik.fu-berlin.de \
--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).