ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Giuseppe Bilotta <bourbaki@bigfoot.com>
Subject: A proposal for the sectioning commangs
Date: Fri, 21 Jun 2002 15:46:16 +0200	[thread overview]
Message-ID: <1809370081.20020621154616@bigfoot.com> (raw)

Hello,

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?).

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)

Content

\stopchapter

Some pluses that would come from this approach, apart from
intrinsic structure:

* easy way to know where a section starts and ends (so as to be
able to put both starting and ending page in the ToC, for example).

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

title listtitle markingtitle bmtitle

Setting one of them would also set the subsequent ones (e.g.
setting the title would set all forms, setting the listtitle would
set the list, marking and bm title, but not the title). This is at
times needed because running heads usually need shorter texts, and
one cannot put special stuff (e.g. math) in bookmarks.
\title would also actually typeset the title. Note that none of
the commands \title, \listtitle, \markingtitle, \bmtitle should
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.

* 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.

* in editors that allow folding: proper folding of whole sections.

Hans, do you think you can implement this easily?

-- 
Giuseppe "Oblomov" Bilotta


             reply	other threads:[~2002-06-21 13:46 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-21 13:46 Giuseppe Bilotta [this message]
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 ` A proposal for the sectioning commangs 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=1809370081.20020621154616@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).