Hello list,
Tik-Z files seem to have gone missing in the ConTeXt. Here’s a MWE:
\usemodule[tikz]% Error in current MkIV and LMTX, but OK in TeX
Live 2021
\usemodule[pgfplots]% Error in Tex Live 2021
\starttext
Hello
\stoptext
The error is in MkIV is:
tex error > tex
Hi,
I have a table with around 120 rows and 120 columns which fits an A0
paper. I want it to be split so that it fits A4 sized papers.
When I tried using xtables :
\startxtable[split=repeat,header=repeat]
\startxtablehead
...
\stopxtablehead
\startxtablebody
.
.
.
\stopxtablebody
> Am 07.06.2021 um 16:39 schrieb Hans Hagen :
>
> Not that I know of ... but you can run wiht --keeptuc and see if there are
> differences in the tuc file that create some oscillation.
Ok. Each run now creates 4 additional files:
file_name-tuc-02.tmp
file_name-tuc-03.tmp
Hans van der Meer schrieb am 07.06.2021 um 22:57:
As can be seen in this screenshot, the text overshoots on the right side
the boundary of the fairly narrow \framedtext.
My intent is to not hyphenate the names, even if that means a ragged
edge on the right side.
But at the same time the text
As can be seen in this screenshot, the text overshoots on the right side the
boundary of the fairly narrow \framedtext.
My intent is to not hyphenate the names, even if that means a ragged edge on
the right side.
But at the same time the text must absolutely stay within the confines of the
Hi Adam, Hi Pablo,
I just noticed your replies, sorry for the late answer!
> On the viewers, I cannot recall exactly what I've done earlier in the
> year,
> but indeed, most likely I have tried evince after signing it from the
> command line. From
>
In the following MWE for a textbackground the parameter backgroundoffset has the expected effect. But for positive values only. A backgroundoffset=-10pt has no visible effect.But the real problem is the parameter frameoffset. No effect at all, whatever frameoffset= is set to.
dr. Hans van der Meer
On 6/7/2021 6:17 PM, Hans van der Meer wrote:
The code below seems ok in \startsection[title=] but not when I program
the parameter collection with \def\setupparameters{\getparameters[prefix]}
In that case even [title={enclosed value}] crashes with error message:
Use of \doMacro doesn't match
On 6/3/2021 11:25 AM, Christoph Reller wrote:
Hi,
On Windows, we have the consola font. Consider the MWE:
\starttext
\definedfont[name:consola*default at 12 pt]
-
\stoptext
The output PDF is correctly generated with recent versions of ConTeXt
LMTX. The hyphen is, however, mapped to a soft
> Am 06.06.2021 um 22:02 schrieb Hans Hagen :
>
> On 6/6/2021 3:34 PM, Steffen Wolfrum wrote:
>> This minimal I ran with «ConTeXt ver: 2021.06.04 17:28 MKI» and got two PDF
>> files:
>> One «test.pdf» as expected and one called «test-pdf-keep.pdf».
>> What's the reason behind this double
The code below seems ok in \startsection[title=] but not when I program the
parameter collection with \def\setupparameters{\getparameters[prefix]}
In that case even [title={enclosed value}] crashes with error message: Use of
\doMacro doesn't match its definition.
Obviously I am missing something
On 6/7/2021 5:44 PM, Steffen Wolfrum wrote:
Am 07.06.2021 um 16:39 schrieb Hans Hagen :
Not that I know of ... but you can run wiht --keeptuc and see if there are
differences in the tuc file that create some oscillation.
Ok. Each run now creates 4 additional files:
file_name-tuc-02.tmp
On 6/7/2021 4:32 PM, Steffen Wolfrum wrote:
Hi Hans,
is there some kind of randomizer involved in line-breaking?
I have a 458 pages project, a book of humanities.
When I immediately typeset (engine=luatex) it a second time, the resulting PDF
differs on 14 pages, diffpdf-compared to the
13 matches
Mail list logo
