From: Henning Hraban Ramm <texml@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: columnsets messed up
Date: Sun, 4 Jul 2021 10:40:46 +0200 [thread overview]
Message-ID: <CC8357B9-AC09-4317-9B63-10D2DDBC452B@fiee.net> (raw)
In-Reply-To: <D4BFFC4F-27CC-4E55-BB84-272A1991811E@fiee.net>
> Am 02.07.2021 um 14:49 schrieb Henning Hraban Ramm <texml@fiee.net>:
> 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?
Even curioser:
If there isn’t a \page after \stopcolumnset, the second-to-last section (subject) disappears and the last one is typeset completely.
(Later:)
Ok, found it:
\def\stopArticle{%
\par\signArticle
\doif{\getvariable{CG-Journal}{NOFColumns}}{>1}
{\stopcolumnset}
\page
}
--> \stopcolumnset is never executed, since \doif can’t handle ">1". – Did it ever or is this a regression?
Hraban
___________________________________________________________________________________
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 prev parent reply other threads:[~2021-07-04 8:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
2021-07-01 18:04 Henning Hraban Ramm
2021-07-02 6:51 ` Hans Hagen
2021-07-02 9:03 ` Henning Hraban Ramm
2021-07-02 9:25 ` 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=CC8357B9-AC09-4317-9B63-10D2DDBC452B@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).