From: Hans Hagen <j.hagen@xs4all.nl>
To: ntg-context@ntg.nl
Subject: Re: columns unexpected (odd) results
Date: Thu, 2 Aug 2018 19:43:01 +0200 [thread overview]
Message-ID: <5616922a-d71b-1e1a-7a60-437bf39be19b@xs4all.nl> (raw)
In-Reply-To: <7067615f-b152-e555-99b5-869051d1cec2@gmx.es>
On 8/1/2018 12:37 PM, Pablo Rodriguez wrote:
> On 08/01/2018 11:48 AM, Henri Menke wrote:
>> Cannot reproduce with TL2018 or latest beta.
>
> Hi Henri,
>
> I’m afraid that Floris is right. With latest beta and a simple
> improvement to your file, I get wrong output:
>
> \starttext
> \startlines
> Testing 1971-04-26
> \startcolumns[n=3]
> \dorecurse{200}{+ 17271 \rightarrow\ 2018-08-08
> }
> \stopcolumns
> \stoplines
> \stoptext
>
> If the closing parenthesis is on the same line, the plus sign is
> misplaced in the last item.
>
> With the previous sample, the second page gets a wrong interline space
> (between the third and the fourth item from the first column).
quick hack:
\unprotect
\unexpanded\def\page_otr_synchronize_page_indeed
{\ifx\currentoutputroutine\s!multicolumn\else\clf_synchronizepage\fi
\glet\page_otr_synchronize_page\page_otr_synchronize_page_yes}
\protect
Actually I don't see it here because i have
\definemixedcolumns
[\v!columns]
[\c!balance=\v!yes,
\c!blank={\v!line,\v!fixed}]
\unexpanded\def\setupcolumns
{\setupmixedcolumns[\v!columns]}
in a local test file (already for years so maybe it's time time to make
that default)
(btw, pagecolumns are an other alternative)
Hans
-----------------------------------------------------------------
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
___________________________________________________________________________________
prev parent reply other threads:[~2018-08-02 17:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-01 9:34 Floris van Manen
2018-08-01 9:48 ` Henri Menke
2018-08-01 10:37 ` Pablo Rodriguez
2018-08-01 11:04 ` Taco Hoekwater
2018-08-01 13:39 ` Floris van Manen
2018-08-01 19:28 ` Wolfgang Schuster
2018-08-01 20:16 ` Floris van Manen
2018-08-02 7:42 ` Pablo Rodriguez
2018-08-02 16:35 ` Wolfgang Schuster
2018-08-02 17:01 ` Wolfgang Schuster
2018-08-02 17:43 ` Hans Hagen [this message]
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=5616922a-d71b-1e1a-7a60-437bf39be19b@xs4all.nl \
--to=j.hagen@xs4all.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).