From: Henning Hraban Ramm <texml@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Fwd: columnsets messed up
Date: Fri, 2 Jul 2021 14:49:25 +0200 [thread overview]
Message-ID: <D4BFFC4F-27CC-4E55-BB84-272A1991811E@fiee.net> (raw)
In-Reply-To: <233FE0DA-C7E2-4629-A764-3B23B5A9D859@fiee.net>
[-- Attachment #1.1: Type: text/plain, Size: 1678 bytes --]
> Am 02.07.2021 um 11:03 schrieb Henning Hraban Ramm <texml@fiee.net <mailto:texml@fiee.net>>:
>
>>
>> Am 02.07.2021 um 08:51 schrieb Hans Hagen <j.hagen@xs4all.nl <mailto:j.hagen@xs4all.nl>>:
>>
>> 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.
>
> Thank you, I got it mostly working now.
In several articles I get a problem, and I can’t (yet) reproduce it in a MWE:
The text in a two-column columnset suddenly breaks at the end of a left column, the end is missing.
Here’s an example PDF:
https://sedna.fiee.net/f/24d54a952b0243a98775/?dl=1
What could case that?
Hraban
[-- Attachment #1.2: Type: text/html, Size: 7152 bytes --]
[-- Attachment #2: Type: text/plain, Size: 493 bytes --]
___________________________________________________________________________________
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
___________________________________________________________________________________
next parent reply other threads:[~2021-07-02 12:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <233FE0DA-C7E2-4629-A764-3B23B5A9D859@fiee.net>
2021-07-02 12:49 ` Henning Hraban Ramm [this message]
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=D4BFFC4F-27CC-4E55-BB84-272A1991811E@fiee.net \
--to=texml@fiee.net \
--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).