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: bug? gap appears in columnset
Date: Thu, 19 Sep 2013 01:22:58 +0200	[thread overview]
Message-ID: <523A35D2.20009@wxs.nl> (raw)
In-Reply-To: <523A1F7C.8020002@sil.org>

On 9/18/2013 11:47 PM, Lars Huttar wrote:
> Regarding "sane" interlinespace,
> Hans wrote,
>> ok, but then, an interlinespace is normally around 1.2 times the
>> bodyfontsize
>
> OK. That's helpful.
>
> But notice that in the following example, the interline space that
> causes the problem is in the *first* section (where htdp is 12pt and
> baselineskip is also 12pt!), while the gap shows up in the *second*
> section, whose interlinespace is 2.8ex:

Columnsets are rather special and mostly meant for magazine like 
documents, where content can span columns, images are explicitly placed 
on the grid, etc. For that reason columnset soperate on a rather strict 
grid that gets setup based in the lineheight and although content can be 
larger, the grid dictates what happens. Balancing is semi automatic and 
nearly always demands some tweaks.

Using columnsets for a large document that has to flow automatically is 
therefore debatable. Regular multi columns or in mkiv mixed-columns are 
a better choice then.

You need to keep in mind that tex has no concept of columns so it is 
faked by using a virtual page nofcolumns * text height.

Anyway, as columnsets are supposed to cooperate with grid mode, any 
messing with the lineheight will interfere. Normally a document has a 
consistent lineheight everywhere.

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
___________________________________________________________________________________


  reply	other threads:[~2013-09-18 23:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-13 20:07 Lars Huttar
2013-09-13 20:20 ` Lars Huttar
2013-09-16 18:29   ` Lars Huttar
2013-09-16 21:29     ` Lars Huttar
2013-09-16 22:32       ` Aditya Mahajan
2013-09-17 14:47       ` Hans Hagen
2013-09-17 15:02       ` Lars Huttar
2013-09-17 15:31         ` Hans Hagen
2013-09-17 18:57         ` Lars Huttar
2013-09-17 20:02           ` Hans Hagen
2013-09-18 21:47           ` Lars Huttar
2013-09-18 23:22             ` Hans Hagen [this message]
2013-09-19 14:25             ` Lars Huttar
2013-09-19 15:19               ` 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=523A35D2.20009@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).