ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Lars Huttar <lars_huttar@sil.org>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: bug? gap appears in columnset
Date: Wed, 18 Sep 2013 17:47:40 -0400	[thread overview]
Message-ID: <523A1F7C.8020002@sil.org> (raw)
In-Reply-To: <5238A635.6040103@sil.org>

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:

\def\printHtdp{\setbox0\hbox{()} \the\htdp0,\the\baselineskip}


\definecolumnset[columnset1][n=2]

\setupcolumnset[columnset1][distance=5mm,balance=yes]


\starttext


\section{Introduction}


\setupinterlinespace[line=12pt]

\startcolumnset[columnset1]

\printHtdp

\dorecurse {7} { \input knuth }

\stopcolumnset


\section{Bibliography}


\tfxx

\setupinterlinespace[line=2.8ex] %or use 11pt

\startcolumnset[columnset1]

\printHtdp

\dorecurse {10} { \input knuth }

\stopcolumnset


\stoptext


Since the problem can appear a ways after the cause, that makes it an
especially hard problem to track down, especially for someone who is
unaware of the nature of the problem. But even now that we're aware of
what the problem (hopefully) is, we've not been able to fix it in our
real-life document.


We sprinkled in many places the code to show htdp and baselineskip
(\printHtdp). E.g. in the early sections that would putatively cause the
problem, our htdp/baselineskip in 8.60252pt,10.5pt. That's a ratio of
more than 1.2. We have eliminated all the places we could find where the
htdp/baselineskip ratio was less than 1.2, even where there was no text.
But the gap persists.

We have a large and complex document, so there might conceivably be
places where a larger htdp than expected is hiding. Are there any tools
for automatically going through a document and reporting places where
not-sane interlinespace occurs?

Thanks,
Lars

___________________________________________________________________________________
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-09-18 21:47 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 [this message]
2013-09-18 23:22             ` Hans Hagen
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=523A1F7C.8020002@sil.org \
    --to=lars_huttar@sil.org \
    --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).