ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Steffen Wolfrum <context@st.estfiles.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: linebreak NOT in section title BUT in content
Date: Wed, 31 Oct 2007 17:40:09 +0100	[thread overview]
Message-ID: <C440FC06-48EF-477B-90B5-A3CD7CCBCA55@st.estfiles.de> (raw)
In-Reply-To: <115224fb0710310450q70474e7eq4e25c20eeaf10f7c@mail.gmail.com>


Phhh! Hot stuff Wolfgang.

This one should definitely go into the wiki (maybe plus a little  
documentation?)

Very convenient option, amazing what goodies ConTeXt provides – thank  
you very, very much Hans!
And thank you Wolfgang for remembering this ... even the master  
himself forgot it ;o)

Steffen


Am 31.10.2007 um 12:50 schrieb Wolfgang Schuster:
>
>
> 2007/10/30, Taco Hoekwater <taco@elvenkind.com>: Steffen Wolfrum  
> wrote:
> >
> > But I was sure there was also a fast, direct way.
> > Well, obviously there isn't (anymore?) ...
>
> Here's a trick. It is ugly, but works reasonably well.
>
>   \starttext
>   \def\CR{\crlf}
>   \completecontent
>   \def\CR{ }
>
>   \chapter{First line\CR second line}
>
>   \stoptext
>
> Nice solution but Hans wrote a mechanism to to make two different
> titles for the text and the table of contents or whatever else you  
> want.
>
> \defineselector[title][max=2,n=2]
> \starttext
>
> \start
>   \setupselector[title][n=1]
>   \completecontent
> \stop
>
> \chapter{\select{title}{First line\crlf second line}{First line  
> second line}}
>
> \stoptext
>
> 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
> ______________________________________________________________________ 
> _____________
___________________________________________________________________________________
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:[~2007-10-31 16:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-30 16:51 Steffen Wolfrum
2007-10-30 19:43 ` Hans Hagen
2007-10-30 20:08   ` Steffen Wolfrum
2007-10-30 20:19     ` Idris Samawi Hamid
2007-10-30 20:44       ` Steffen Wolfrum
2007-10-30 21:47         ` Taco Hoekwater
2007-10-30 22:12           ` Idris Samawi Hamid
2007-10-30 22:54           ` Steffen Wolfrum
2007-10-31 11:50           ` Wolfgang Schuster
2007-10-31 16:40             ` Steffen Wolfrum [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=C440FC06-48EF-477B-90B5-A3CD7CCBCA55@st.estfiles.de \
    --to=context@st.estfiles.de \
    --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).