From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: Xan <dxpublica@telefonica.net>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Hans Hagen <pragma@wxs.nl>
Subject: Re: Bug in \column
Date: Wed, 20 Mar 2013 10:28:59 +0100 [thread overview]
Message-ID: <6AB5D979-057E-4EDB-8F52-26A56EE229EA@gmail.com> (raw)
In-Reply-To: <5148C16A.3070909@telefonica.net>
Am 19.03.2013 um 20:50 schrieb Xan <dxpublica@telefonica.net>:
> Can you modify it for working? By the user perspective it's an annoying bug. A clean command should not produce that, isn't it?
I have to agree that the current situation with the \column command isn’t perfect but each solution has it’s own problems.
The example below uses three different definitions for the \column command, the first and third result in a empty column when there is to much text in the first column while the second definition ignores the command and balances the text of both columns.
<example>
\starttext \showframe
% Default method
\blank[force,12cm]
\startcolumns
\dorecurse{16}{a\par}
\column
b
\stopcolumns
\page
% Method 1
\unprotected\installcolumnbreakmethod \s!multicolumn \v!yes
{\scratchdimen\dimexpr\pagegoal/2\relax
\vskip \scratchdimen
\penalty-200 % we can mark and intercept this
\vskip-\scratchdimen}
\blank[force,12cm]
\startcolumns
\dorecurse{16}{a\par}
\column
b
\stopcolumns
\page
% Method 2
\unprotected\installcolumnbreakmethod \s!multicolumn \v!yes
{\scratchdimen\dimexpr\pagegoal/2+\lineheight\relax
\vskip \scratchdimen
\penalty-200 % we can mark and intercept this
\vskip-\scratchdimen}
\blank[force,12cm]
\startcolumns
\dorecurse{16}{a\par}
\column
b
\stopcolumns
\stoptext
</example>
Wolfgang
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2013-03-20 9:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-18 18:32 Xan
2013-03-18 21:34 ` Wolfgang Schuster
2013-03-19 19:50 ` Xan
2013-03-20 9:28 ` Wolfgang Schuster [this message]
2013-03-20 9:40 ` Hans Hagen
2013-03-20 9:52 ` Wolfgang Schuster
2013-03-21 8:40 ` Xan
2013-03-21 22:58 ` Wolfgang Schuster
2013-03-22 9:59 ` Xan
2013-03-22 10:02 ` Xan
2013-03-22 10:15 ` Xan
2013-03-22 10:19 ` Xan
2013-03-20 18:21 ` Keith J. Schultz
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=6AB5D979-057E-4EDB-8F52-26A56EE229EA@gmail.com \
--to=schuster.wolfgang@gmail.com \
--cc=dxpublica@telefonica.net \
--cc=ntg-context@ntg.nl \
--cc=pragma@wxs.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).