ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: A proposal for the sectioning commangs
Date: Sun, 23 Jun 2002 12:43:33 +0200	[thread overview]
Message-ID: <5.1.0.14.1.20020623123326.02d205f0@server-1> (raw)
In-Reply-To: <1809370081.20020621154616@bigfoot.com>

At 03:46 PM 6/21/2002 +0200, Giuseppe Bilotta wrote:

>one of the main features of both ConTeXt and LaTeX over plain TeX
>is their heavily "object-oriented" approach to source writing,
>giving a large set of useful tools to build well-structured
>documents.
>
>There is though one aspect which has not been addressed in either:
>structuring of the sections. One still uses \chapter, \section,
>\subsection etc to denote the start of any of these, while
>structured writing would call for \startchapter ... \stopchapter,
>\startsection ... \stopsection etc.
>
>My proposal is to switch to such a method, while still retaining
>compatibility with the old-style sectioning (maybe we can use some
>flag like the one used to left left/right alignment use the
>_correct_ term --what was the switch name?).

actually, this is on my to do list, for most of the project that we run 
currently we use this approach since it gives you the options

(1) to skip a chapter / section
(2) to attach hooks to the end-of-some-section

>How should it work:
>
>\startchapter[optional reference name]
>
>Possible stuff before the title (e.g. an epigraph)
>
>\title{Title of the chapter}
>Optional commands to set alternative forms of the title (see
>below)

no, just \startchapter[ref]{title} is ok, since i don't want to pick up the 
title separately (imagine that you want \startchapter to trigger a complex 
title page

also, we currently test (play with) some mechanism to have section (or 
whatever) dependent variables, thereby introducing more convenient ways to 
tune typo behaviour.

* easy way to set different titles for ToCs, running heads, (PDF)
>bookmarks etc. Consider the following hierarchy of titles:
>
>title listtitle markingtitle bmtitle

that's for variables (since here we also have things like several graphics 
to be used in typesetting the chapter page)

>write anything to the .tuo file; this ought to be done by the
>\stop<section-name> command, which would save all of them together
>with the appropriate counter values and beginning/ending page.

hm, i'm not sure if i like that

>* easy way to put things before the title (e.g. an epigraph) while
>still within the structure of the section.
>
>* also comes from the above: currently, when using the /XYZ method
>for PDF references, link targets end out-of-the-window because the
>TeX cohordinate used is that of the baseline. This means that the
>visible part of the page does not include the target reference
>(which is rather uncomfortable). Instead, with the new approach
>the mark could be set "right before everything else, but still
>within the correct structure", with optimal PDF navigation.

that is a whole different matter, (1) output format/driver dependent and 
(2) can handled now by moving things around and (3) we don't want those 
funny nodes to screw up the spacing [actually, since i never use that xyz 
way of viewing docs [too inconstent auto scaling in viewers] i never felt 
the need to look into it; maybe something for a cold winter night]

>Hans, do you think you can implement this easily?

the \start-\stop thing will certainly be there

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
-------------------------------------------------------------------------
                        information: http://www.pragma-ade.com/roadmap.pdf
                     documentation: http://www.pragma-ade.com/showcase.pdf
-------------------------------------------------------------------------


      parent reply	other threads:[~2002-06-23 10:43 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-21 13:46 Giuseppe Bilotta
2002-06-21 15:27 ` John Culleton
2002-06-21 21:15   ` Re[2]: " Giuseppe Bilotta
2002-06-21 22:37     ` Duncan Hothersall
2002-06-22  2:24       ` John Culleton
2002-06-23 21:47     ` Re[2]: " Hans Hagen
2002-06-23 10:45   ` Hans Hagen
2002-06-21 16:01 ` A proposal for the sectioning commands--addendum John Culleton
2002-06-21 21:17   ` Re[2]: " Giuseppe Bilotta
2002-06-23 19:39   ` Hans Hagen
2002-06-23 21:42     ` Re[2]: " Giuseppe Bilotta
2002-06-24  8:40       ` Hans Hagen
2002-06-24  8:55         ` Re[3]: " Giuseppe Bilotta
2002-06-24 18:06           ` texedit (was: something else) Henning Hraban Ramm
2002-06-25 15:47             ` Hans Hagen
2002-06-26 18:43               ` Henning Hraban Ramm
2002-06-27 16:54                 ` Hans Hagen
2002-06-28 21:48                   ` Henning Hraban Ramm
2002-06-23 10:43 ` Hans Hagen [this message]

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.20020623123326.02d205f0@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).