Am 19.03.2013 um 20:50 schrieb Xan
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