ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
	Henning Hraban Ramm <texml@fiee.net>
Subject: Re: columnsets messed up
Date: Fri, 2 Jul 2021 08:51:37 +0200	[thread overview]
Message-ID: <81204697-216f-8195-209f-dd93ede5a2e2@xs4all.nl> (raw)
In-Reply-To: <A5E83FB5-CE93-41F1-BE04-8136E2F99415@fiee.net>

On 7/1/2021 8:04 PM, Henning Hraban Ramm wrote:
> Hi,
> I’m working at the current CG journal whose layout uses columnsets. They aren’t usable any more. Same in current LMTX and MkIV.
> 
> - the first line can start one or more lines lower
> - then the same number of lines is printed over each other at the bottom
> - it gets worse with footnotes (looks like their space isn’t considered at all)
> - if the column set doesn’t start at the top of the page, the second column does
> 
> 
> Hraban
> 
> 
> \definecolumnset[cgjcolset][n=2]
> 
> \starttext
> 
> \chapter{This is a chapter about column sets}
> 
> \startcolumnset[cgjcolset]
> 
> \dorecurse{20}{
> \samplefile{sapolsky}\par
> }
> 
> \stopcolumnset
> 
> \stoptext
Personally I'd never use columnsets for anything else than very 
controlled situations because that's what they were made for. Not to be 
mixed with the normal pagebuilder. So, first of all you need to operate 
on the grid (i can probably get rid of some side effects and maigt even 
force that but not now). Then, \chapter itself flushes pages so that 
should be disabled.

Here is a simple example:

\setuplayout[lines=40,grid=yes]

\definecolumnset[cgjcolset][n=2]

\starttext

\definecolumnsetspan
  [chapter]
  [background=color,
   backgroundcolor=red]

\setuphead[chapter][page=no,after=,before=]

\startcolumnset[cgjcolset]

     \startcolumnsetspan[chapter]
         \chapter{This is a chapter about column sets}
     \stopcolumnsetspan

     \dorecurse{20}{
         \samplefile{sapolsky}\par
     }

\stopcolumnset

\stoptext



-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2021-07-02  6:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-01 18:04 Henning Hraban Ramm
2021-07-02  6:51 ` Hans Hagen [this message]
2021-07-02  9:03   ` Henning Hraban Ramm
2021-07-02  9:25     ` Hans Hagen
     [not found] <233FE0DA-C7E2-4629-A764-3B23B5A9D859@fiee.net>
2021-07-02 12:49 ` Fwd: " Henning Hraban Ramm
2021-07-04  8:40   ` Henning Hraban Ramm

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=81204697-216f-8195-209f-dd93ede5a2e2@xs4all.nl \
    --to=j.hagen@xs4all.nl \
    --cc=ntg-context@ntg.nl \
    --cc=texml@fiee.net \
    /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).