ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Wolfgang Schuster" <schuster.wolfgang@googlemail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: Adding custom key/value pairs
Date: Tue, 15 Apr 2008 12:56:11 +0200	[thread overview]
Message-ID: <115224fb0804150356o3df708bm29be96b33364cb2c@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0804141206410.8826@nqv-yncgbc>

On Mon, Apr 14, 2008 at 6:11 PM, Aditya Mahajan <adityam@umich.edu> wrote:
> On Mon, 14 Apr 2008, Taco Hoekwater wrote:
>
> > Wolfgang Schuster wrote:
> >>
> >> Why not, I have nothing against a few predefined title pages layouts.
> >
> > Somewhat related: it would be nice if there was some common code for
> > titles (books as well as articles).
> >
> > [snip]
> >
> > Anyway, the maps module contains all the code to do everything. And
> > the same is true for the TUG module. And for quite a few others I have
> > laying around. Lots of duplicate code all over, so a common framework
> > would be great. I've been meaning to write one for a long time, but
> > somehow I never quite get around to actually doing it.
> >
> > Just saying this to let you know that I would really welcome a module
> > with commands like \setuptitle, \definetitle, and \placetitle.
>
> I agree with that. It will be really nice to have a module that does a few
> "simple" titles (alternate=(a|b|c), etc.) For one of my personal modules,
> I was following something along the lines of the maps module. But I find
> Wolfgang's solution on the wiki to be more ConTeXtish than what all other
> modules use.

Hi Aditya,

could you use a few lines what do you expect from a placetitle/placetitlepage
command or a titlepage environment.

What should we do with the abstract, did it depend on the document title ...

Wolfgang
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2008-04-15 10:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-12 19:44 Rory Molinari
2008-04-13 10:08 ` Taco Hoekwater
2008-04-13 17:37   ` Rory Molinari
2008-04-14  9:56     ` Olivier Guéry
2008-04-14 10:18       ` Wolfgang Schuster
2008-04-14 10:34         ` Olivier Guéry
2008-04-14 10:58           ` Wolfgang Schuster
2008-04-14 11:20             ` Taco Hoekwater
2008-04-14 11:53               ` Wolfgang Schuster
2008-04-14 16:11               ` Aditya Mahajan
2008-04-15 10:56                 ` Wolfgang Schuster [this message]
2008-04-15 15:34                   ` Aditya Mahajan
2008-04-17  8:24                     ` Wolfgang Schuster
2008-04-17  8:42                       ` Taco Hoekwater

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=115224fb0804150356o3df708bm29be96b33364cb2c@mail.gmail.com \
    --to=schuster.wolfgang@googlemail.com \
    --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).