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>
Cc: Steffen Wolfrum <context@st.estfiles.de>
Subject: Re: another surprising change (line break in TOC)
Date: Tue, 17 Jan 2012 23:41:59 +0100	[thread overview]
Message-ID: <FD644821-E712-4C51-8737-C00640BA200A@googlemail.com> (raw)
In-Reply-To: <CF8966C9-85F8-4825-9FA5-FCCE1BB7F424@st.estfiles.de>


Am 17.01.2012 um 13:14 schrieb Steffen Wolfrum:

> 
> Am 17.01.2012 um 12:19 schrieb luigi scarso:
> 
>> Probably a bug, but this is ok
>> \definelistplacement[MyListItemIT][none]#1#2#3%
>> {\hfill\kern-1em\it#1%
>> \hfill\strut\crlf\strut\hfill\hphantom{\tf#3}%
>> \framedtext[frame=off,offset=overlay,align=middle,style=bold]%
>> {#2}%
>> \hfill\tf#3
>> }
> 
> 
> Not really ok. That's a pitfall with minimal examples ... "the devil is in the details" ;o)
> For getting it minimal I wrote \bf, but in the original file it is used as a bold style with a certain size and a certain interlineskip: \TOCstyleBF
> 
> And this interlineskip is ignored in your solution, test the following please:
> 
> 
> \def\TOCstyleBF{\switchtobodyfont[9pt]\bf\setupinterlinespace[line={40pt}]}
> 
> \definelistplacement[MyListItemIT][none]#1#2#3%
>   {\hfill\kern-1em\it#1\hfill\strut\crlf\strut\hfill\hphantom{\tf#3}\framedtext[frame=off,offset=overlay,align=middle,style=TOCstyleBF]{#2}\hfill\tf#3} % here the interlinespace is ignored
> %   {\hfill\kern-1em\it#1\hfill\strut\crlf\strut\hfill\hphantom{\tf#3}\framedtext[frame=off,offset=overlay]{\TOCstyleBF\midaligned{#2}}\hfill\tf#3} % here the interlinespace worked


You should try to make your code more readable.

\definelistplacement[MyListItemIT][none]#1#2#3%
   {\maxaligned\bgroup
      \rlap{\it#1}%
      \framed[frame=off,align=middle,location=bottom,width=broad,foregroundstyle=\TOCstyleBF]{#2}%
      \llap{\tf#3}%
    \egroup}

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


  reply	other threads:[~2012-01-17 22:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-16 14:21 Steffen Wolfrum
2012-01-16 14:29 ` Wolfgang Schuster
2012-01-16 14:39   ` Steffen Wolfrum
2012-01-16 16:18     ` Hans Hagen
2012-01-17 10:37       ` Steffen Wolfrum
2012-01-17 11:19         ` luigi scarso
2012-01-17 12:14           ` Steffen Wolfrum
2012-01-17 22:41             ` Wolfgang Schuster [this message]
2012-01-18  6:25               ` Steffen Wolfrum
2012-01-18  7:30                 ` luigi scarso
2012-01-18  7:39                   ` luigi scarso
2012-01-18  7:45                   ` Wolfgang Schuster
2012-01-18  8:37                   ` Hans Hagen
2012-01-18  8:56             ` luigi scarso

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=FD644821-E712-4C51-8737-C00640BA200A@googlemail.com \
    --to=schuster.wolfgang@googlemail.com \
    --cc=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).