On Thu, Apr 18 2024, Peter Münster wrote:
> How could I prevent a column break after the second section title please?
Ok, found it:
\setupitemize[each][autointro]
--
Peter
___
If your quest
Hi,
How could I prevent a column break after the second section title please?
Minimal example:
\starttext
\startcolumns[n=2]
\section{title 1}
\dorecurse{22}{bla\par}
\section{title 2} % Here starts a new column.
\startitemize
\dorecurse{15}{\item bla}
\stopitemize
\stopcolumns
there is a problem with the division lines which always
leave an empty column afterwards.
The following example should add horizontal lines above the first and
third column but this setting results in an error. When I omit the last
\DC the error disappears but as can be seen in the output the second
vertical
position -- no matter, how many lines there are in each column and how
exactly they are aligned.
If I understand correctly, that's how the multicols environment in
LaTeX works, and that's how old-multicolumns worked -- but this module
seems to be no longer supported in lmtx.
I tried
there are in each column and how
exactly they are aligned.
If I understand correctly, that's how the multicols environment in
LaTeX works, and that's how old-multicolumns worked -- but this module
seems to be no longer supported in lmtx.
I tried to disable gridfitting for startcolumns, but it produces
Hello,
I am currently writing my paper for last year's BachoTeX proceedings.
I am using tugboat.mkxl module to design the layout.
In bachotex proceedings, the author's data and abstract are on a single
column and the article is usually typeset on two columns.
Comments in tugboat.mkxl states
etch,
> other = stretch_break,
> }
>
> but there can be more wrong entries.
> > I was not successful in figuring out how the protrusion mechanism can
> > be set in order to keep full stops and commas on the previous line
> > (protruding the column box). Could you pleas
,
}
but there can be more wrong entries.
I was not successful in figuring out how the protrusion mechanism can
be set in order to keep full stops and commas on the previous line
(protruding the column box). Could you please give me a hint,
Wolfgang? Thanks. There's a \color[red]{。} in my example which should
to keep full stops and commas on the previous line (protruding the column
box). Could you please give me a hint, Wolfgang? Thanks. There's a
\color[red]{。} in my example which should not jump to the next line.
My example follows the Kihon-hanmen dimensioning as described in
https://www.w3.org/TR
r][first][style=bold]
\setupTABLE[r][each][
topoffset=1em,bottomoffset=0.5em,
background=sketchylines,
% would be nice if the background wouldn’t start at each column
]
\setupTABLE[c][each][frame=off]
\bTABLE[]
\bTR
\bTD{Stadt}\eTD
\bTD{Land}\eTD
\bTD{Fluss}\eTD
\eTR
\dorecurse
Dear Otared,
Thank you for testing.
I run the sample after changing the column command to ‘\startsimplecolumns …
\stopsimplecolumns’.
I got the same result as your output. And it is same as the result using
\startcolumns … \stopcolumns.
If ‘\vfill’ works, then it is OK for me, but it isn’t
:22, Jeong Dal via ntg-context <ntg-context@ntg.nl> wrote:Dear all,I have a little problem to use “columns” in the following example.If I use “\startcolumnset”, then I have the following problems: 1. The figures is aligned left even though I use \startplacefigure[]. 2. In the second column, the
Dear all,I have a little problem to use “columns” in the following example.If I use “\startcolumnset”, then I have the following problems: 1. The figures is aligned left even though I use \startplacefigure[]. 2. In the second column, the first item located at the end of the page.However, \vfill
\eTABLE
>
> What I've been finding is that previous settings on TABLES appearing earlier
> in the document is impacting later tables. For instance, if one has a frame
> to the right of column 1, then the next table seems to acquire this setting
> as well, even if
is impacting later tables. For instance, if
one has a frame to the right of column 1, then the next table seems to
acquire this setting as well, even if it isn't expected to have any
frames at all.
Note that each unique table is defined inside a macro.
How can I make these table settings only
, if one has a frame to the
right of column 1, then the next table seems to acquire this setting as well,
even if it isn't expected to have any frames at all.
Note that each unique table is defined inside a macro.
How can I make these table settings only apply to the a specific table?
--Joel
On Fri, Jan 26, 2024 at 09:55 (+0100), Aditya Mahajan wrote:
> On Thu, 25 Jan 2024, Jim wrote:
>> The nice thing about your setup above is that it is nice and structured.
>> But if a table calls for some row, column or cell to be treated
>> differently, I guess I am in
On Thu, 25 Jan 2024, Jim wrote:
> The nice thing about your setup above is that it is nice and structured.
> But if a table calls for some row, column or cell to be treated
> differently, I guess I am in for some more reading.
You can do: \setupTABLE[2][3] to select the formatting
vrules don't use tabulate
>> to create the tables.
>> Coincidence? I think not. :-)
> Table which rely on rules to make the content readable have a serious
> problem
> (read Edward Tufte books how you can improve the visual style) but the
> better
> alternative in this c
em,roffset=.5em]
\setupTABLE [column] [each] [leftframe=on,rightframe=on]
\setupTABLE [row] [first]
[topframe=on,bottomframe=on,foregroundstyle=bold]
\setupTABLE [row] [last] [bottomframe=on]
\stopsetups
\startTABLE[setups=ruledtable]
\NC Year \NC Citizens \NC\NR
\NC 1675 \NC ˜428
}]
\starttext
A paragraph before calling the subject.
\subject{\sc The subject}
A paragrapf after the subject was called.
\stoptext
I use the \subject command within a columnset, could that be the problem?
Yes, because text in column(sets)s is typeset on a grid.
Try \showgrid to visualize.
You
No, it seems to have been my mistake. I must apologize. I have tested the
syntax with the preceding column numbers again, and lo and behold: it works.
Unfortunately, I can no longer understand what went wrong with my first test of
the new syntax. In any case, thank you very much for your
ignment[n=2,align={left, right}]
> \NC always aligned to the right \NC = u + at, \NR
> \NC d \NC = ut + \frac12 at^2. \NR
> \stopmathalignment
> \stopformula
> \stoptext
>
> Despite "align={left, right}", the first column is aligned to the right and
> the second to the
,
Minimal example 1:
\starttext
\startformula
\startmathalignment[n=2,align={left, right}]
\NC always aligned to the right \NC = u + at, \NR
\NC d \NC = ut + \frac12 at^2. \NR
\stopmathalignment
\stopformula
\stoptext
Despite "align={left, right}", the first column is aligned to the rig
igures (figure/figcaption). It would also mean having to write ConTeXt
macros that flip the spans and anchors to produce a caption such as:
*Lyrics 1.1.* Meschiya Lake - Lucky Devil
While there are plenty of ways of presenting captions (e.g., multi-column
images with sub-figure numbers) the ma
Am 19.11.23 um 13:27 schrieb Miguel Diaz:
1. Why are the lines printed one over the other when grid=no? how do
profis then use context without grid?
That usually only happens in one of the column modes that requires the
grid. It doesn’t happen in usual one-column typesetting. There must
\geq \frac{1}{2T}$ \NR
> > \stopcases
> > \stopformula
> > \stoptext
>
> There has been changes in the math alignment mechanism a while ago and the
> cases
> environment use math mode for a column entry when you use the \NC tag at the
> begin
> of a cell, to
has been changes in the math alignment mechanism a while ago and
the cases
environment use math mode for a column entry when you use the \NC tag at
the begin
of a cell, to make your example working again remove the $ in the column.
\starttext
\startformula
X(f) =
\startcases
\NC T, \NC
>
>
> Hello, I'm trying to achieve a look similar to a magazine our religious
organization frequently discusses, but unfortunately can't find the correct
settings to do so. Whenever I call a custom note on a column, instead of
the note showing on the bottom of the page, it shows a
does work and works in \columns as
well. This is great until my listing is too long to fit on a page and then I'd
rather have the column continue onto the next page but \columns balances of
course.
3) \tabulate allows a single cell to continue down over the page exactly as I'd
like
Two column text that ends near the foot of a page can push the next line into
the footer rather than starting a new page.
MWE for ConTeXt ver: 2023.09.26 18:19 LMTX :-
\setuppapersize [A4]
\showframe
\starttext
Knuth in knolumns
\dorecurse{30}{\crlf}
\startcolumns
\input knuth
\stopcolumns
)
or the columndistance key (when you have invisible borders).
% Alternative 1:
% \setupTABLE[frame=on,offset=0pt,columndistance=1em]
% Alternative 2:
\setupTABLE [frame=off,offset=0pt,loffset=.5em,roffset=.5em]
\setupTABLE [column] [first] [loffset=0pt]
\setupTABLE [column] [last] [roffset=0pt
=right,
style=\ChapterFont,
beforesection={\pageinjection[chapter:start]},
command=\ChapterStart,
before={\startcolumnset[Spalten]},
after={\vskip-\lineheight}, % fix column start
inbetween=,
aftersection={\stopcolumnset},
]
\startchapter[title={Prolog 2: Reiseführer}][
motto={(quotation
> wrote:
>
> […]
>
>
> I would drop the column check in this case.
>
> for i = 0,9 do
> context.startxrow()
> context.startxcell()
> context(i)
> context.stopxcell()
>
Otared Kavian schrieb am 24.08.2023 um 12:50:
On 24 Aug 2023, at 06:03, Wolfgang Schuster
<mailto:wolfgang.schuster.li...@gmail.com>> wrote:
[…]
I would drop the column check in this case.
for i = 0,9 do
context.startxrow()
context.s
> On 24 Aug 2023, at 06:03, Wolfgang Schuster
> wrote:
>> […]
>
> I would drop the column check in this case.
>
> for i = 0,9 do
> context.startxrow()
> context.startxcell()
> context(i)
> context.stopxcel
elseif j == 2 then
> context(math.mod(i*i,10))
> elseif j == 3 then
> context(i)
> else
> context(math.mod(2*i*i,10))
> end
> context.stopxcell()
> end
> context.stopxrow()
> end
th.mod(i*i,10))
elseif j == 3 then
context(i)
else
context(math.mod(2*i*i,10))
end
context.stopxcell()
end
context.stopxrow()
end
I would drop the column check in this case.
for i = 0,9 do
context.startxrow()
context.star
body) font size
tw : (layout) text width
th : (layout) text height
hs : (current) hsize
vs : (current) vsize
cd : (when set) column distance
cw : (when set) column width
cx : combination cell width
uu : user unit (\METAFUN)
Many thanks for the new release, Hans.
I wonder whether we could have
font size
> tw : (layout) text width
> th : (layout) text height
> hs : (current) hsize
> vs : (current) vsize
> cd : (when set) column distance
> cw : (when set) column width
> cx : combination cell width
> uu : user unit (\METAFUN)
Many thanks for the new release, Hans.
I wo
units but be carefulk
with other combinations as we have (and will have more) built into
context ones, like
pi : pi for Mikael
ft : foot for Alan
fs : (global body) font size
tw : (layout) text width
th : (layout) text height
hs : (current) hsize
vs : (current) vsize
cd : (when set) column
after=\stopcolumns,
]
\definestartstop[timelinea][
after=\column,
]
\definestartstop[timelineb][]
\starttext
\startconcurrent
\starttimelinea
\dorecurse{5}{\input ward}
\stoptimelinea
\starttimelineb
\dorecurse{5}{\input knuth}
\stoptimelineb
\stopconcur
Ok, if you use p for the column definition you can just use \setupalign on
individual cells...
%%%
\starttext
\starttabulate[|pA{verytolerant,extremestretch}|pA{verytolerant,extremestretch}|]
\NC Heading flushleft \NC \setupalign[flushright] Heading flushright \NC \NR
\NC \input
low and overwrite their last line.
...
Also I seem to remember that column sets would enforce grid mode, but
they clearly don’t.
If you enable \setuplayout[grid=yes], lines get placed correctly.
Also floats work well (here and top).
But some columnsetspans still disappear, and footnotes get
the same as in the manual) shows that some
column set spans don’t appear:
\showgrid\showframe
\definecolumnset[Beispiel][n=3]
\definecolumnsetspan[Zwei][n=2,color=blue]
\definecolumnsetspan[Drei][n=3,color=red]
\starttext
\startcolumnset[Beispiel]
\startcolumnsetspan[Drei]% this works
{\bfd
> > > archive : https://bitbucket.org/phg/context-mirror/commits/
> > > > wiki : https://contextgarden.net
> > > >
> > > >
> > _____
a-ade.nl / http://context.aanhet.net
> > archive : https://bitbucket.org/phg/context-mirror/commits/
> > wiki : https://contextgarden.net
> >
> ___
>
>
> --
> ... an anecdote from IBM's Yorkto
tanding up. That
behavior was 100 percent repeatable: he could always log in when sitting and
never when standing.
Most of us just sit back and marvel at such a story; how could that terminal
know whether the poor guy was sitting or standing? Good debuggers, though,
know that there has to be a reaso
Denis:
Thanks, that is very helpful starting point which proves that it is
possible!
I have tried the suggestions there, but, so far:
* I cannot adjust the gap ("distance" or "gutter") between the columns
* It seems impossible to turn-on a column-s
test \item test \stopitemize after \par
{\bf nowhite:} \par before \startitemize[nowhite]
\item test \item test \stopitemize after \par
{\bf joinedup,nowhite:}\par before \startitemize[joinedup,nowhite]
\item test \item test \stopitemize after \column
Thanks Peter. I took a look at your lua pages. I think I would get
entirely lost with that code at this stage, and of course I am not
considering (at least not for now) a two-column approach, but facing
pages. But at least you achieved what you were trying to do at the time.
Hopefully I
Hraban Ramm via ntg-context
wrote:
* If I format a column, e.g. \setupTABLE[c][-1][color=red], body and foot are
formatted, but not the same column in header. I couldn’t find how to format
columns in header.
If you disregard the Wiki page instructions to use \bTH...\eTH then you can
format
"foot" would make sense.
I'd be happy with that, especially as there is already headstyle and headcolor.
>> * Row 1 is the first row of TABLEbody. I couldn’t find how to address the
>> first line of TABLEbody.
>> * If I format a column, e.g. \setupTABLE[c][-1][colo
r "section"); since we
have TABLEhead and TABLEfoot, IMO "head" and "foot" would make sense.
* Row 1 is the first row of TABLEbody. I couldn’t find how to address
the first line of TABLEbody.
* If I format a column, e.g. \setupTABLE[c][-1][color=red], body and
foo
pframe=on,framecolor=black, height=0pt]
\starttext
\bTABLE
\dorecurse{22}{
\bTR\bTD Row #1 column 1 \eTD\bTD Row #1 column 2 \eTD\eTR
}
% Dummy last row
\bTR \eTR
\eTABLE
\stoptext
—
Bruce Horrocks
Hampshire, UK
__
Hi,
There are some footnotes in my text. When I use
\startcolumns...\stopcolumns, the locations of footnotes are not right.
Please see the followging sample:
\starttext
If there is a footnote here\footnote{It's a footnote!}.
\startcolumns[n=2]
\input knuth
\column
\input knuth
\stopcolumns
ooter" (or "section"); since we
have TABLEhead and TABLEfoot, IMO "head" and "foot" would make sense.
* Row 1 is the first row of TABLEbody. I couldn’t find how to address
the first line of TABLEbody.
* Is it possible, and how, to use odd/even only for the body?
*
]
My difficulty is that while there is only ever just a couple of
numbers in the left-hand 'column', the right-hand 'column' may have
several lengthy paragraphs. If I have one relatively short \startTwo
followed by one that is much longer, it will be forced to start on
the next page, leaving
]
\setupparagraphs[Two][1][width=.1\textwidth,style=\bfx,align=tolerant]
\setupparagraphs[Two][2][width=.9\textwidth,style=normal,align=tolerant]
My difficulty is that while there is only ever just a couple of numbers
in the left-hand 'column', the right-hand 'column' may have several
lengthy
difficulty is that while there is only ever just a couple of numbers in the
left-hand 'column', the right-hand 'column' may have several lengthy
paragraphs. If I have one relatively short \startTwo followed by one that is
much longer, it will be forced to start on the next page, leaving too much
s there an easy way to achieve
> this?
You can right align all columns, though I am not sure that this looks better,
because column 2 and 3 now appear to be "too close".
\definemathmatrix[bmatrix]
[matrix:brackets]
[align=all:right,simplecommand=bmatrix]
\starttext
$ a \rightarrow
of numbers
in the left-hand 'column', the right-hand 'column' may have several
lengthy paragraphs. If I have one relatively short \startTwo followed by
one that is much longer, it will be forced to start on the next page,
leaving too much empty space on the previous page.
It is probable that getting
Hi,
I'm getting unexpected results for \xmlpos
With the example below, I was expecting to get the following positions:
1 2 3 4
However the result is: 2 4 6 8, i.e. each time it's exactly the double.
What am I missing?
Background: I need to define column alignment based on the value
ans and
>>> Mikael about the math fonts in Lucida.
>>>
>>> I very much appreciated that article: one sees how the handling of almost
>>> impercebtile details in ConTeXt make us to adhere to and love LuaMetaTeX…
>>> So a great thank you to Hans and Mik
sees how the handling of almost
impercebtile details in ConTeXt make us to adhere to and love LuaMetaTeX… So a
great thank you to Hans and Mikael for all this work!
Regarding the details of vertical alignment in math, I wonder whether the
column « : » in front of the equal sign
lmost
> impercebtile details in ConTeXt make us to adhere to and love LuaMetaTeX… So
> a great thank you to Hans and Mikael for all this work!
>
> Regarding the details of vertical alignment in math, I wonder whether the
> column « : » in front of the equal sign « = », in the c
and Mikael for all this work!
Regarding the details of vertical alignment in math, I wonder whether the
column « : » in front of the equal sign « = », in the combination « := » (used
to define for instance a new variable) should be alos centered around the math
axis, as explained in the article
in this collection is a so called date-driven list generator.
This allows to produce lists with any kind of date interval in days for any
duration. It allows to adjust the number of columns in the list as well as
changing the column heads to the requirements of the list.
I hope that some of you might find
= -3 \NR
\stopmathalignment\stopformula
\item\hspace[big] $\frac{d}{dp}\left( p^3 - 2p \right)$
\stopitemize
\stoptext
I’m also attaching a file with the above issue followed by the correct spacing
in one-column for comparison.
I’m using LMTX (today’s upload, ver: 2022.10.21 21:13 LMTX fmt
er evolved or not.
>
> \placefigure
> [][fig:church]
> {Stephanus Church.}
> {\externalfigure[ma-cb-24][width=.4\textwidth]}
>
> \stopprettyblock
> \setupindenting[next]
> Below, we have two separate columns; but up here, for the nonce, we have but
> the one.
>
> \star
all in the first column
\column
Words, words, words \dots
all in the second column.
And look ye here! Even more words!
\stopcolumns
\stoptext
Many regards
Uschi
-Ursprüngliche Nachricht-
Von: ntg-context Im Auftrag von Oliver Sieber via
ntg-context
Gesendet: Mittwoch, 19
AM MDT, Max Chernoff
wrote:
Hi Joel,
> I'd like to add some area for readers to write in the margins of some
> text. This would leave three lines, like this to the right of the
> text.
Is it okay if there are rules continuously down the right column? If so,
this is fairly sim
Hi Joel,
> I'd like to add some area for readers to write in the margins of some
> text. This would leave three lines, like this to the right of the
> text.
Is it okay if there are rules continuously down the right column? If so,
this is fairly simple to do with layers/backgrounds
]
\setuppagenumbering[location=footer]
\setupcolors[state=start]
%\setupexternalfigure[directory={/Users/graph/Documents/figures,}]
\headTitle{2021. 12. 12.}{Set Theory}{Final Exam}
\starttext
\startcolumnset[exam]
\startitemize[n]
\item The first problem.
\column
\item The second problem.
\column
oes not quite work as tabulate does not seem to allow blanks between
> > the stanzas. See MWE below. Am I missing someting? Is there a better
> > way to achieve this?
>
> How about columnsets or paragraphs?
>
> \definecolumnset[Zwei][n=2]
> \startcolumnset[Zwei]
>
umnsets or paragraphs?
\definecolumnset[Zwei][n=2]
\startcolumnset[Zwei]
\startlines
Starlight, star bright,
first star I see tonight;
\stoplines
\column
\startlines
I wish I may, I wish I might
have the wish I wish tonight.
\stoplines
\stopcolumnset
\defineparagraphs[Zwei][n=2]
\setupparagraphs[Zwei][1][
below. Am I missing someting? Is there a better way to
achieve this?
How about columnsets or paragraphs?
\definecolumnset[Zwei][n=2]
\startcolumnset[Zwei]
\startlines
Starlight, star bright,
first star I see tonight;
\stoplines
\column
\startlines
I wish I may, I wish I might
have the wish I wish
gt;
> On Fri, 12 Aug 2022, Marcin Ciura via ntg-context wrote:
>
> > Dear list,
> >
> > I am typesetting [nothyphenated,flushleft] text in two columns. Some
> words
> > stick through the right margin of the left column, sometimes even
> > overlapping the rig
-context] Keep the right margin in [nothyphenated, flushleft]
columns
On Fri, 12 Aug 2022, Marcin Ciura via ntg-context wrote:
> Dear list,
>
> I am typesetting [nothyphenated,flushleft] text in two columns. Some words
> stick through the right margin of the left column, sometimes even
&
On Fri, 12 Aug 2022, Marcin Ciura via ntg-context wrote:
> Dear list,
>
> I am typesetting [nothyphenated,flushleft] text in two columns. Some words
> stick through the right margin of the left column, sometimes even
> overlapping the right column. How can I make Context obey t
Dear list,
I am typesetting [nothyphenated,flushleft] text in two columns. Some words
stick through the right margin of the left column, sometimes even
overlapping the right column. How can I make Context obey the right margin?
The MWE is below.
Here is the output PDF:
https
On 6/30/22 18:10, Angel M Alganza via ntg-context wrote:
> [...]
> No, you aren't, and it almost does it, except when the fixed width
> column is other than the first one, I'm afraid.
Hi Ángel,
there might be a way to get it, as long as you don’t define height
directly, such as in:
\
Hi Pablo,
On Thu, Jun 30, 2022 at 04:15:10PM +0200, Pablo Rodriguez via ntg-context wrote:
I’m not sure whether I’m totally missing your point,
but I think this is a way that might achieve what you want:
No, you aren't, and it almost does it, except when the fixed width
column is other than
of the trick (the column width).
Is there a way to do the same for the row height, please?
I never looked at xtables, since the wiki says they're used for tables
that need to span several pages, which I don't need.
They’re also tedious, because you can’t setup rows/columns in advance
(like
Hello, Hans,
On Thu, Jun 30, 2022 at 08:16:53AM +0200, Hans Hagen via ntg-context wrote:
\startxtable[option=stretch]
\startxrow
\startxcell[width=3cm,option=fixed] one \stopxcell
Thank you very much, that does part of the trick (the column width).
Is there a way to do the same
to specify as well..
For the moment, I'm doing it "manually", calculating column width as
(\textwidth - width of fixed columns) / # rest of columns
and row height as
(\textheight - height of fixed rows) / # rest of rows
I'm getting the result that I want, but it's a bit tedious.
Is i
ually", calculating column width as
(\textwidth - width of fixed columns) / # rest of columns
and row height as
(\textheight - height of fixed rows) / # rest of rows
I'm getting the result that I want, but it's a bit tedious.
Is it possible to have ConTeXt do all those calculations for me?
Not a bug, although it may be unexpected. It's a grid snapping thing. Try:
\def\example{%
Lorem ipsum. Lorem ipsum. Lorem ipsum.
Lorem ipsum. Lorem ipsum. Lorem ipsum.
Lorem ipsum. Lorem ipsum. Lorem ipsum.
Lorem ipsum. Lorem ipsum. Lorem ipsum.
Lorem ipsum. Lorem ipsum.
Dear Hans and ConTeXt developers,
When you compile the following code with ConTeXt ver: 2021.10.28 10:19, you
will see that:
* in 1-column text the top spacing of the circle is normal,
* in 2-column text, the top spacing of the circle is too large.
Here is the link to the output PDF:
https
>>> for a document:
>>
>> "Intriguing" is definitely right here. I suspect these guidelines were made
>> for typewriters and haven't been updated since.
>>
>>> to limit the number of glyphs per line to 112.
>>
>> 112 characters per line soun
to limit the number of glyphs per line to 112.
>
> 112 characters per line sounds much too long anyways.
>
> From "The Elements of Typographic Style":
> > Anything from 45 to 75 characters is widely regarded as a satisfactory
> > length of line for a single-colum
s per line sounds much too long anyways.
From "The Elements of Typographic Style":
> Anything from 45 to 75 characters is widely regarded as a satisfactory
> length of line for a single-column page set in a serifed text face
> in a text size. The 66-character line (counting both le
Hi,
if the fontsize is smaller than ~11pt and there is \startcolumnsetspan used,
then the two first lines of the second column are not aligned to the
grid (they jump). Making the font bigger, or deleting the
\startcolumnsetspan can both fix the problem. It seems like a bug to
me, but maybe I'm
to use pull quotes, I need to use the dimensions of the different
elements to be typeset, before typesetting, in order to adapt the shapes
of the flow accordingly.
So here is just a basic code to
1/ get the dimensions of an item A that will be typeset, before it is
actually typeset
2/ use
as to the possibility of including such pull quotes in
multi-column presentations, and I have to tell them that to do so I need
to use another program where that is more easily achieved.
So, I just wanted you to know that someone out there appreciates your
efforts with this, one of many I am sure
\startuseMPgraphic{mytest1} % column on the left of the pull quote
lmt_parshape [path = pleft ] ;
fill pleft withcolor \MPcolor{transparentred} ;
\stopuseMPgraphic
\startuseMPgraphic{mytest2} % column on the right of the pull quote
lmt_parshape [path = pright] ;
fill pright withcolor \MPcolor
> 1. I want the baseline grid to evenly (vertically) divide the text
>> > area, but my code produces a smaller height of the first line and an
>> > additional space at the bottom.
>>
>> You did not set footerdistance to zero. So, that takes up some space.
&g
> 2. The number of columns is 21.5, that is the first column
is 0.5 units
> wide and the rest are 1 unit wide.
I believe that columns has to be an integer. Why do you want
fractional columns? Columns are useful because you can say:
\setlayer[name][line=2,column=3]{}
code produces a smaller height of the first line and an
> > additional space at the bottom.
>
> You did not set footerdistance to zero. So, that takes up some space.
>
> > 2. The number of columns is 21.5, that is the first column is 0.5
> units
> > wide and the rest are
y) divide the text
> area, but my code produces a smaller height of the first line and an
> additional space at the bottom.
You did not set footerdistance to zero. So, that takes up some space.
> 2. The number of columns is 21.5, that is the first column is 0.5 units
> wide and the re
1 - 100 of 2478 matches
Mail list logo
