Alexey Kryukov schrieb am 27.03.2024 um 14:02:
Hi list,
I'd like to know if its is possible to get visually balanced
mixedcolumns in lmtx. For example, if I have \blank's between
paragraphs, I would like them to be stretched or expanded by
a such way that the bottommost lines have the same
Hi list,
I'd like to know if its is possible to get visually balanced
mixedcolumns in lmtx. For example, if I have \blank's between
paragraphs, I would like them to be stretched or expanded by
a such way that the bottommost lines have the same vertical
position -- no matter, how many lines
\input knuth
\stopcolumns
\stoptext
My fault? Bug?
Yes and no.
Simplecolumns are as the name implies a few very simple mechanism and
don't support vertical lines between the columns.
The normal columns environment uses the mixedcolumns code where you have
to use "separator=rule&qu
hile ago with the newer
> (although available since a few years) mixedcolumns environment.
>
> A big difference between the old columns code and new code is that the
> new code relies on a page grid which can lead to extra lines in the
> output, because ConTeXt adds extra space t
example
[...]
end example
The old columns environment was replaced a while ago with the newer
(although available since a few years) mixedcolumns environment.
A big difference between the old columns code and new code is that the
new code relies on a page grid which can lead to extra lines
On 15-11-2019 14:04, Wolfgang Schuster wrote:
> Use separator=rule, the columns environments uses since a few months
> the mixedcolumns mechanism but the you can load the old code base
> with \usemodule[old-multcolumns].
Is the new syntax the default for the new context only?
e.g. t
the mixedcolumns mechanism but the you can load the old code base
with \usemodule[old-multcolumns].
Wolfgang
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl
]}
Another paragraph to make columns uneven.\par\blank[myBlank]
\dorecurse{3}{\input knuth \blank[myBlank]}
\stopmixedcolumns
\stoptext
Is there a way to configure mixedcolumns so that \blank[myBlank] is
stretched or shrinked to get the two columns end aligned at the bottom
of the page?
Thanks
eet_diff.pdf
>>
>> Source code is here:
>>
>> https://github.com/BruXy/gnulinux.guru/tree/master/bash_tahak
>>
>> Did I miss some update which has introduced some different length settings?
>>
>> I have version: 2019.02.14 16:57
>
> The columns-e
/bash_tahak
Did I miss some update which has introduced some different length
settings?
I have version: 2019.02.14 16:57
The columns-environment uses now the newer mixedcolumns code
which create by default different spaces around section titles.
The old columns code can be loaded as a module
/bash_cheatsheet_diff.pdf
Source code is here:
https://github.com/BruXy/gnulinux.guru/tree/master/bash_tahak
Did I miss some update which has introduced some different length
settings?
I have version: 2019.02.14 16:57
The columns-environment uses now the newer mixedcolumns code
which create by default
> https://www.dreiviertelhaus.de
> GPG Key ID 1C9B22FD
>
> Am 2018-11-08 um 18:32 schrieb Wolfgang Schuster
> :
>
>> The columns environment uses now the newer mixedcolumns mechanism which is
>> the reason for the differences in your document.
>>
>>
of time.
Greetlings, Hraban
---
https://www.fiee.net
http://wiki.contextgarden.net
https://www.dreiviertelhaus.de
GPG Key ID 1C9B22FD
Am 2018-11-08 um 18:32 schrieb Wolfgang Schuster
:
> The columns environment uses now the newer mixedcolumns mechanism which is
> the reason for the diffe
The columns environment uses now the newer mixedcolumns mechanism which
is the reason for the differences in your document.
To use the older columns mechanism add \usemodule[old-multicolumns] to
your document.
Wolfgang
Henning Hraban Ramm schrieb am 07.11.18 um 22:53:
In the last days I
trange.
The garden uses MkIV where \color expects a argument (i.e.
\color[]{}).
Below is a example how you can add a colored rule to \startcolumns but
the better solution
is to switch to MkIV and and use mixedcolumns environment which has a
option to change
the color of the rule b
14:32, Fabrice Couvreur <fabrice1.couvr...@gmail.com>
a écrit :
> Hello,
> I notice a space when I use the command \math{\lim\limits_{n \to +\infty}
> 0,8^n=0} and mixedcolumns.
> Thanks.
> Fabrice
> #
>
> \de
Hello,
I notice a space when I use the command \math{\lim\limits_{n \to +\infty}
0,8^n=0} and mixedcolumns.
Thanks.
Fabrice
#
\definemixedcolumns
[sectioncolumns]
[
n=2,
separator=rule,
rulecolor=,
balance=yes
xt
--8<---cut here---end--->8---
It would appear that this problem is still the case, as of the
following version:
i'll fix it (more in tune with mkii as this is the old columns handler)
soon we will default to the mixedcolumns handler and the old mechanism
nothing.
>>
>> \starttext
>> \startcolumns
>> [
>> n=2,
>> rule=on,
>> rulecolor=red,% does nothing
>> rulethickness=5pt,% does nothing
>> ]
>> \input knuth
>> \stopcolumns
>> \stoptext
> You can use mixedcolumns.
Thank
% does nothing
]
\input knuth
\stopcolumns
\stoptext
You can use mixedcolumns.
\starttext
\startmixedcolumns[separator=rule,rulecolor=red,rulethickness=5pt,balance=yes]
\input knuth
\stopmixedcolumns
\stoptext
Furthermore, is there a possibility to control the appearance of the
rule per
with mixedcolumns but could not reproduce in plain vanilla environment.
Also I noticed that if the paragraph is too short the initial overwrites the
next paragraph(s) (to reproduce simply comment out the mixedcolumns).
MWE:
\starttext
\startmixedcolumns[balance=yes]
\dorecurse{10
Dear all,
I am using \starthanging to implement dropcaps (with small pdf files). I use
this Inside mixedcolumns (2 columns).
I’d like to know if there is a better way than \testcolumn[N], N being the
number of lines of the dropcap, to prevent the location of dropcap being cut
between end
Dear all,
Trying to use EB Garamond font Inside mixed columns + use firstline feature
(to make it larger) I get an empty line in output between first line and the
rest of paragraph. If I comment the line containing \setupbodyfont and use
default font the problem disappears (even with larger
On 2014-06-08, 23:34, Hans Hagen wrote:
does
balance=yes
help?
Yes, it helps. Thank you!
Kind regards,
Joshua
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist :
after \stopmixedcolumns. It works with
\start... \stopcolumns, but then the column break (\column) is ignored.
It worked before with mixedcolumns, but I don't know when I updated the
last time.
Kind regards,
Joshua
\stoptext
There should be no pagebreak after \stopmixedcolumns. It works with
\start... \stopcolumns, but then the column break (\column) is ignored.
It worked before with mixedcolumns, but I don't know when I updated the
last time.
does
balance=yes
help
by line -
compilation keeps working without error. I'm no longer sure if it is
indeed a problem with the mixedcolumns environment or the new
bibliography code or a combination of both...
Thomas
___
If your question
in question - compilation worked - uncommented line by line -
compilation keeps working without error. I'm no longer sure if it is
indeed a problem with the mixedcolumns environment or the new
bibliography code or a combination of both...
no, it's one of those ransom issues where a pointer is not set
Hi,
I haven't yet been able to reproduce this in a minimal example, but I'm
trying to place some images within a mixedcolumns environment, and I get
an error message I have never seen before:
pagesflushing realpage 5, userpage 5
Node 1150 has an attribute list that is free
On 3/29/2014 4:02 PM, Thomas A. Schmitz wrote:
Hi,
I haven't yet been able to reproduce this in a minimal example, but I'm
trying to place some images within a mixedcolumns environment, and I get
an error message I have never seen before:
pagesflushing realpage 5, userpage 5
Node
Hi,
I believe I have isolated the problem:
\starttext
balance
\startmixedcolumns[balance=yes,]
\dorecurse{8}{\input{ward}}
\stopmixedcolumns
%\page
strut
\startmixedcolumns[grid=strut,]
\dorecurse{4}{\input{knuth}}
\stopmixedcolumns
\stoptext
When balanced mixedcolumns
}}
\stopmixedcolumns
\stoptext
When balanced mixedcolumns are followed by mixedcolumns using a strut
grid, then the content of the second mixedcolumns will extend into the
footer area on the next page. However, if the content of the strut
grid mixedcolumns is long enough to incur a page break on that next
On 12/3/2013 4:40 PM, Hans Hagen wrote:
On 12/3/2013 3:10 PM, Lars Huttar wrote:
...
Thanks again for your work on this.
We're continually reevaluating whether we can use the beta or need to
stick with the stable version. At the moment, it looks like we'll be
sticking with the stable
On 11/28/2013 1:34 PM, Hans Hagen wrote:
That macro was never meant for mixed columns. I made a variant that
works ok in mixed columns which will be in the next beta.
\setuptolerance[verytolerant]
\starttext
\startmixedcolumns
\dorecurse{4}{\input ward \par}
On 12/3/2013 3:10 PM, Lars Huttar wrote:
On 11/28/2013 1:34 PM, Hans Hagen wrote:
That macro was never meant for mixed columns. I made a variant that
works ok in mixed columns which will be in the next beta.
\setuptolerance[verytolerant]
\starttext
\startmixedcolumns
On 11/28/2013 1:34 PM, Hans Hagen wrote:
That macro was never meant for mixed columns. I made a variant that
works ok in mixed columns which will be in the next beta.
Excellent. I will give it a try.
I see a context-setup-win64 dated 2013-11-28 19:45. Is that beta? I may
wait for the next one
On 11/29/2013 12:26 PM, Lars Huttar (SIL gmail) wrote:
On 11/28/2013 1:34 PM, Hans Hagen wrote:
That macro was never meant for mixed columns. I made a variant that
works ok in mixed columns which will be in the next beta.
Excellent. I will give it a try.
I see a context-setup-win64 dated
On 11/20/2013 10:47 PM, Lars Huttar wrote:
Hello,
On this list I've been advised that mixedcolumns is the latest and
greatest implementation of columns; the one to use. We have switched
over from columnsets to mixedcolumns, and have been very pleased with
the column balancing (for some reason
of mkiv, this gives us a nice table with
the headword separated from the definition.
In the beta, the headword and the definition start at the same
horizontal position, and overlap each other.
We use these lists in the context of mixedcolumns, but the overlap
behavior occurs regardless of mixedcolumns
these lists in the context of mixedcolumns, but the overlap
behavior occurs regardless of mixedcolumns.
Any help would be appreciated. If we can't fix or work around this
problem, we may have to abandon the beta and go back to TeX Live 2013,
which means our page header guide words would be incorrect
framed flushright and bottom, we could
similarly use \testcolumn to prevent the graphic from hanging down
into
the footer (which is what sometimes happened otherwise).
So I'm wondering, is there some way to achieve the equivalent of
\testcolumn in mixedcolumns?
for the moment add \penalty1
On 11/22/2013 4:34 PM, Hans Hagen wrote:
On 11/21/2013 7:01 PM, Lars Huttar wrote:
I now have a MWE that shows the problem.
Where top and bottom work fine outside of columns, in mixedcolumns, any
keyword I use with \getmarking always seem to return the *last* item on
the page. Here's the MWE
\testcolumn to prevent the graphic from hanging down into
the footer (which is what sometimes happened otherwise).
So I'm wondering, is there some way to achieve the equivalent of
\testcolumn in mixedcolumns?
for the moment add \penalty1
OK... where? In the same place we used to use
On 11/21/2013 7:01 PM, Lars Huttar wrote:
I now have a MWE that shows the problem.
Where top and bottom work fine outside of columns, in mixedcolumns, any
keyword I use with \getmarking always seem to return the *last* item on
the page. Here's the MWE:
I changed the example a bit
On 11/22/2013 4:34 PM, Hans Hagen wrote:
On 11/21/2013 7:01 PM, Lars Huttar wrote:
I now have a MWE that shows the problem.
Where top and bottom work fine outside of columns, in mixedcolumns, any
keyword I use with \getmarking always seem to return the *last* item on
the page. Here's the MWE
sometimes happened otherwise).
So I'm wondering, is there some way to achieve the equivalent of
\testcolumn in mixedcolumns?
for the moment add \penalty1
Here is a MWE:
\starttext
\startmixedcolumns[distance=5mm, balance=yes]
\dorecurse {20} {
\testcolumn[8]
\subsection{Subsection
hanging down into
the footer (which is what sometimes happened otherwise).
So I'm wondering, is there some way to achieve the equivalent of
\testcolumn in mixedcolumns?
for the moment add \penalty1
OK... where? In the same place we used to use \testcolumn?
According to http
in the real document, and knowing the meaning of these keywords
would be very helpful in troubleshooting the problem.
Thanks,
Lars
I now have a MWE that shows the problem.
Where top and bottom work fine outside of columns, in mixedcolumns, any
keyword I use with \getmarking always seem to return
On 11/21/2013 1:01 PM, Lars Huttar wrote:
I now have a MWE that shows the problem. Where top and bottom work
fine outside of columns, in mixedcolumns, any keyword I use with
\getmarking always seem to return the *last* item on the page.
I sometimes forget to include our version info.
MKIV
Hello,
On this list I've been advised that mixedcolumns is the latest and
greatest implementation of columns; the one to use. We have switched
over from columnsets to mixedcolumns, and have been very pleased with
the column balancing (for some reason we couldn't get column balancing
to work
wondering, is there some way to achieve the equivalent of
\testcolumn in mixedcolumns?
Here is a MWE:
\starttext
\startmixedcolumns[distance=5mm, balance=yes]
\dorecurse {20} {
\testcolumn[8]
\subsection{Subsection Heading} \input knuth \endgraf
}
\stopmixedcolumns
\stoptext
You can
Dear list,
while \widowpenalty is respected in conventional columns, inside or
outside \startmixedcolumns and \stopmixedcolumns, it is ignored. How can
I make ConTeXt avoid widows in mixedcolumns?
(I can't use conventional columns, some things like distance=... don't
work there.)
Thank you
On 12. November 2013 at 18:36:49, Joshua Krämer (joshua.krae...@gmail.com)
wrote:
Dear list,
while \widowpenalty is respected in conventional columns, inside or
outside \startmixedcolumns and \stopmixedcolumns, it is ignored. How can
I make ConTeXt avoid widows in mixedcolumns?
(I can't use
Dear Wolfgang,
thanks for your answer. Please compare:
\starttext
\startcolumns[distance=5pt]
\input knuth
\stopcolumns
\startmixedcolumns[distance=5pt]
\input knuth
\stopmixedcolumns
\stoptext
___
If your
On 12. November 2013 at 18:45:55, Joshua Krämer (joshua.krae...@gmail.com)
wrote:
Dear Wolfgang,
thanks for your answer. Please compare:
\starttext
\startcolumns[distance=5pt]
\input knuth
\stopcolumns
\startmixedcolumns[distance=5pt]
\input knuth
\stopmixedcolumns
\stoptext
You
Am Tue, 12 Nov 2013 19:00:52 +0100 schrieb Wolfgang Schuster:
\stoptext You have to set the values of the offset key to 0pt to use
only the values for distance:
Thanks, that did the trick. However, I still wonder why \widowpenalty
doesn't work in mixedcolumns. This should be revised. Maybe
\stopcolumns
\stopframedtext
\startframedtext[width=\makeupwidth]
\blank
\startsimplecolumns[n=2,rule=on,balance=yes]
\input tufte
\stopsimplecolumns
\stopframedtext
\stoptext
The new mixedcolumns environment can be used to the typeset columns in a frame.
There is also a predefined
Thanks,
But I think mixedcolumns has to solve a problem width the width of the
frametext. Whereas boxedcolumns honors the width of the enclosing framedtext,
mixedcolumns does not. See the example.
% NOT OK WIDTH NOT RESPECTED
\startframedtext[width=.8\makeupwidth,align=verytolerant
Am 03.10.2013 um 12:02 schrieb H. van der Meer h.vanderm...@uva.nl:
Thanks,
But I think mixedcolumns has to solve a problem width the width of the
frametext. Whereas boxedcolumns honors the width of the enclosing framedtext,
mixedcolumns does not. See the example.
Boxedcolumns
If I remember well, framedtext sets a localhsize for the width of its content.
I guess that is why boxedcolumns stays within the width specified. But is there
a specific reason why mixedcolumns in general does not?
Hans van der Meer
On 3 okt. 2013, at 12:07, Wolfgang Schuster schuster.wolfg
Am 03.10.2013 um 12:26 schrieb H. van der Meer h.vanderm...@uva.nl:
If I remember well, framedtext sets a localhsize for the width of its
content. I guess that is why boxedcolumns stays within the width specified.
But is there a specific reason why mixedcolumns in general does
reason why mixedcolumns in general does not?
The global settings for mixedcolumns are
\setupmixedcolumns
[maxwidth=\makeupwidth]
which forces columns to use the width of the textblock but boxedcolumns uses
this
\definemixedcolumns
[boxedcolumns]
[maxwidth=\availablehsize
boxedcolumns stays within the width specified.
But is there a specific reason why mixedcolumns in general does not?
The global settings for mixedcolumns are
\setupmixedcolumns
[maxwidth=\makeupwidth]
which forces columns to use the width of the textblock but boxedcolumns
uses
Hi,
The horizontal rule for the first page extends to the bottom of the page,
but does not do so on the second page. How do you prevent the vertical rule
from extending to the bottom of the page?
\usemodule[ipsum]
\setuplayout[
topspace=\zeropoint,
height=fit,
width=fit, % Allow text to be
}{\dorecurse{12}{bla }}
\stopsection}
\starttext
\startcolumns[n=2]
\Section{15}
\Section{10}
%\column %%% Why do we need this?!
\Section{10}
\Section{10}
\Section{2}
\stopcolumns
\stoptext
--8---cut here---end---8---
Use the new mixedcolumns
Am 04.06.2013 um 00:35 schrieb Joshua Krämer joshua.krae...@gmail.com:
One other problem has appeared: \startmixedcolumns[align=right] doesn't
work (align=... works with \startcolumns). How can I change the
alignment?
The mixedcolumns doesn’t have a option for this yet but (tolerance
, please say to me.
Can you test your example with the mixedcolumns environment
instead of the normal columns environment (use the latest beta).
Wolfgang
Yes, ofcourse. But what steps I have to do for that. I'm running context
minimals (I don't know if stable or beta).
Thanks,
Xan
Al 21/03/13 23:58, En/na Wolfgang Schuster ha escrit:
Can you test your example with the mixedcolumns environment instead of
the normal columns environment (use the latest beta). Wolfgang
My current version of context is:
2012.07.27 16:41
(context --version produces this)
Sorry,
Xan
, please say to me.
Can you test your example with the mixedcolumns environment
instead of the normal columns environment (use the latest beta).
Wolfgang
Now I have the beta context version. Now I want to use in my example
mixedcolumns. But nothing in the wiki is present of how to work
, please say to me.
Can you test your example with the mixedcolumns environment
instead of the normal columns environment (use the latest beta).
Wolfgang
Yes, it works perfectly (I attach my example).
Can someone put reference on wiki on such environment? Useful for novice
users like me
with the mixedcolumns environment
instead of the normal columns environment (use the latest beta).
Wolfgang
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context
The nested mixedcolumns does not work properly when it reaches the
bottom of the outer mixedcolumns here:
$ context --version
mtx-context | ConTeXt Process Management 0.60
mtx-context |
mtx-context | main context file:
d:/ConTeXt/tex/texmf-local/tex/context/base/context.mkiv
mtx
of the table and or to use multiple columns (the new
mixedcolumns environment
can be also used in a box).
BTW, how can I make that the first column are aligned to the right?
\setupxtable[xcell][1][align=right] doesn't seem to work.
Xtables don’t provide the same method as natural tables to set
pages.
When you have such a large table you have to use a different implementation
but maybe it’s better to look
if you can reduce the size of the table and or to use multiple columns (the
new mixedcolumns environment
can be also used in a box).
Many thanks for your reply, Wolfgang,
I'm
74 matches
Mail list logo