ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: Linespacing in TOC
Date: Sat, 23 Nov 2013 13:54:05 +0100	[thread overview]
Message-ID: <5290A56D.9010109@wxs.nl> (raw)
In-Reply-To: <002101cee849$b1e90c60$15bb2520$@tosovsky@email.cz>

On 11/23/2013 1:44 PM, Jan Tosovsky wrote:
> On 2013-11-23 Hans Hagen wrote:
>> On 11/23/2013 12:16 PM, Jan Tosovsky wrote:
>>> On 2013-11-23 Jan Tosovsky wrote:
>>>> On 2013-11-22 Hans Hagen wrote:
>>>>> On 11/22/2013 9:44 PM, Jan Tosovsky wrote:
>>>>>> On 2013-11-20 Hans Hagen wrote:
>>>>>>> On 11/19/2013 11:48 PM, Jan Tosovsky wrote:
>>>>>>>>
>>>>>>>> I'd like to tweak a default TOC linespacing...
>>>>>>>>
>>>>>>> \title{Table of Contents}
>>>>>>>
>>>>>>> \start
>>>>>>>         \setupinterlinespace[line=0.8ex]
>>>>>>>         \placecontent
>>>>>>> \stop
>>>>>>
>>>>>> But as I found, any value below 2.8ex causes interline
>>>>>> inconsistencies when
>>>>>> special cases appears, see the extreme below:
>>>>>>
>>>>>> \starttext
>>>>>> \start
>>>>>> \setupinterlinespace[line=1.0ex]
>>>>>> \placecontent
>>>>>> \stop
>>>>>> \chapter{aaaaaaaa}. % line without descenders
>>>>>> \chapter{pppppppp}. % line with descenders
>>>>>> \chapter{ŠŠŠŠŠŠŠŠ}. % the result is an inconsistent baseline
>>>>>> \stoptext
>>>>>>
>>>>>> Is there any remedy for this? Can I fix the baseline distance
>>>>>> somehow?
>>>>>>
>>>>>
>>>>> \definegridsnapping[crap] [fit,0.2]
>>>>> \setuplayout[grid=crap]
>>>>
>>>> This helps! But... it breaks something else :-(
>>>
>>> I've finally found an acceptable solution.
>>>
>>> During my tests I found a crucial difference between:
>>>
>>> \setupinterlinespace[line=2.0ex]
>>>
>>> and
>>>
>>> \setupinterlinespace[0.25]
>>>
>>> The latter sets the baseline distance correctly even without that
>>> problematic snapping to the grid!
>>>
>>>> All lines in my book have a certain (default) linespacing.
>>>> TOC entries are rendered (by default) using bigger linespacing.
>>>
>>> Btw, is there any option to override a default (huge) TOC
>> linespacing? I
>>> still consider my solution rather a hack.
>>
>> just set 'before' and 'after'
>
> Ok. I haven't realize that.
>
>> normally linespacing in the toc is the same as in the rest of the
>> document unless one has assigned to before/after
>
> This example shows different behaviour:
>
> \showgrid
> \starttext
> \start
> \placecontent
> \stop
> \chapter{aaaaaaaa}Foo
>
> Bar
> \chapter{pppppppp}.
> \chapter{ŠŠŠŠŠŠŠŠ}.
> \stoptext
>
> On my computer the TOC linespacing is almost twice as big as that in the
> paragraph.

if the grid is on that can indeed be the case but only if there are 
lines with > lineheight so that's why you can use less strict options 
(older mails)

Hans



-- 

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________


  parent reply	other threads:[~2013-11-23 12:54 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <013a01cee579$6a0c5640$3e2502c0$@tosovsky@email.cz>
2013-11-19 23:00 ` Hans Hagen
2013-11-22 20:44   ` Jan Tosovsky
     [not found]   ` <011201cee7c3$b3b1dc60$1b159520$@tosovsky@email.cz>
2013-11-22 21:45     ` Hans Hagen
2013-11-22 23:11       ` Jan Tosovsky
     [not found]       ` <013501cee7d8$1fefbb40$5fcf31c0$@tosovsky@email.cz>
2013-11-23 11:16         ` Jan Tosovsky
     [not found]         ` <001701cee83d$77460650$65d212f0$@tosovsky@email.cz>
2013-11-23 11:51           ` Hans Hagen
2013-11-23 12:44             ` Jan Tosovsky
     [not found]             ` <002101cee849$b1e90c60$15bb2520$@tosovsky@email.cz>
2013-11-23 12:54               ` Hans Hagen [this message]
2013-11-23 13:32                 ` Jan Tosovsky
     [not found]                 ` <002601cee850$6c3196e0$4494c4a0$@tosovsky@email.cz>
2013-11-23 13:35                   ` Hans Hagen
2014-02-10 21:49                     ` Jan Tosovsky
     [not found]                     ` <52f9499c.826f0e0a.58db.ffffbb09SMTPIN_ADDED_BROKEN@mx.google.com>
2014-02-10 22:25                       ` Wolfgang Schuster
2014-02-11 16:32                         ` Jan Tosovsky
     [not found]                         ` <52fa509d.826f0e0a.5656.ffff8d0bSMTPIN_ADDED_BROKEN@mx.google.com>
2014-02-11 17:58                           ` Wolfgang Schuster
2014-02-12 16:02                             ` Jan Tosovsky
     [not found]                         ` <00d901cf2746$d2b9ce20$782d6a60$@tosovsky@email.cz>
2014-02-11 18:45                           ` Hans Hagen
2013-11-19 22:48 Jan Tosovsky

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=5290A56D.9010109@wxs.nl \
    --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).