ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Giuseppe Bilotta <gip.bilotta@iol.it>
Cc: ntg-context@ntg.nl
Subject: Re[4]: epigraph
Date: Fri, 29 Nov 2002 17:16:23 +0100	[thread overview]
Message-ID: <531035368.20021129171623@iol.it> (raw)
In-Reply-To: <0BC4F9AC-039C-11D7-B62F-0050E4258255@fastmail.fm>


Friday, November 29, 2002 Bruce D'Arcus wrote:

>> You can use the xdesc module I developed to define a very
>> flexible epigraph environment (i.e. one which also allows you to
>> have a "list of epigraphs" etc).

BDA> "You" in this context is me, as an individual?

Yes.

BDA>   The issue I have here 
BDA> (and it may well not be an issue, since I'm not sure I grasp every 
BDA> detail) is the one I mentioned last week:

BDA> If we are going to be able to have elegant and flexible typesetting of 
BDA> DocBook files, shouldn't DocBook structures like epigraph be in the 
BDA> core?  Simon shouldn't have to generate lower-level code for these sort 
BDA> of things (the meta info stuff as well) with his project, because it 
BDA> then becomes more difficult for the user to customize output (and for 
BDA> him to maintain the code?).

BDA> Or am I missing something?

You're not. IMO the whole xdesc module should get into the core
--it can work as a base for bibliographies, too, for example.

-- 
Giuseppe "Oblomov" Bilotta

  reply	other threads:[~2002-11-29 16:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-28 19:47 epigraph Simon Pepping
2002-11-28 20:04 ` epigraph Bruce D'Arcus
2002-11-29 11:23   ` Re[2]: epigraph Giuseppe Bilotta
2002-11-29 11:30   ` Giuseppe Bilotta
2002-11-29 13:11     ` Bruce D'Arcus
2002-11-29 16:16       ` Giuseppe Bilotta [this message]
2002-11-29 19:12       ` Simon Pepping
2002-11-29 22:41         ` Re[4]: epigraph 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=531035368.20021129171623@iol.it \
    --to=gip.bilotta@iol.it \
    --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).