ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: Alan BRASLAU <alan.braslau@cea.fr>
Cc: ntg-context@ntg.nl, Hans Hagen <pragma@wxs.nl>
Subject: Re: "\setuplabeltext [appendix=Appendix ]" broken mkiv
Date: Wed, 17 Feb 2010 22:30:57 +0100	[thread overview]
Message-ID: <6faad9f01002171330o2376ac5ds9857880578e52864@mail.gmail.com> (raw)
In-Reply-To: <201002171844.12493.alan.braslau@cea.fr>

On Wed, Feb 17, 2010 at 18:44, Alan BRASLAU wrote:
>
> Why \definehead[appendix][chapter]?
> Why not use \chapter{} and \section{}
> within \startappendices\stopappendices?

I don't remember exactly (and it was bug anyway even if my code could
have been optimized), but I wanted to have different font size,
different position, different placement in TOC ("Appendix A - Title"
instea of just "A Title"), different page breaking, ... Though I still
didn't figure out how to have "Appendix A -" also printed out in TOC
(instead of plain "A").

So I simply defined another type of section (faster solution than
figuring out how to change appearance of chapter in appendices only).

> \chapter{} and \section{} get put into the TOC.
>  (However, there is a bug and they do not get the proper label:
>  \setlabeltext [appendix=Appendix ] in the head;
>  \setlabeltext [chapter=Chapter ] in the list.)
>
> \appendix{} does not get put into the TOC
> so it works like \title{} rather than \chapter{}

I defined the second list for that purpose (really ugly, but the
fastest way to get it done). But there was a tiny problem with that as
well (mkii more problematic) - I didn't manage to get the spacing
between two consecutive lists right. For example (compare mkii and
mkiv):

\definecombinedlist
	[contenta]
	[chapter,section]
	[level=section,
	 criterium=all,alternative=c,aligntitle=yes,width=2.5em]

\setuplist
	[chapter]
	[style=bold]

\setupwhitespace[big]

\starttext

\placecontenta [alternative=c,aligntitle=yes,width=2.5em]
\placecontenta [alternative=c,aligntitle=yes,width=2.5em]

\blank % no effect in mkii at all - remains too narrow

\placecontenta [alternative=c,aligntitle=yes,width=2.5em]

\blank\blank[big]

\placecontenta [alternative=c,aligntitle=yes,width=2.5em]

\crlf % too big

\placecontenta [alternative=c,aligntitle=yes,width=2.5em]

\chapter{a}
\section{a.1}
\section{a.2}
\chapter{b}
\section{b.1}
\section{b.2}

\stoptext

Mojca
___________________________________________________________________________________
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  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2010-02-17 21:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-15 15:31 Alan BRASLAU
2010-02-16 21:39 ` Mojca Miklavec
2010-02-16 22:03   ` Hans Hagen
2010-02-16 22:21   ` Hans Hagen
2010-02-17 17:44     ` Alan BRASLAU
2010-02-17 21:30       ` Mojca Miklavec [this message]
2010-02-17 21:36         ` Hans Hagen
2010-05-23 12:02           ` Alan BRASLAU

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=6faad9f01002171330o2376ac5ds9857880578e52864@mail.gmail.com \
    --to=mojca.miklavec.lists@gmail.com \
    --cc=alan.braslau@cea.fr \
    --cc=ntg-context@ntg.nl \
    --cc=pragma@wxs.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).