Re: [NTG-context] LMTX problem with doifmode in \setuplayout
Rik Kabel schrieb am 08.06.2021 um 23:01: Yes, that works. Of course, to say that you can never be sure if such combinations will work is not a welcome statement about the state of ConTeXt. More recent LMTX releases also now break older documents that worked (with LMTX and MkIV) before. If there is an error in what was previously written that is only noticed because of tighter enforcement, that is one thing, but an undocumented change to supported behaviour is less to be desired. And that it works with dimensions but not on/off/yes/no is very strange and suggests some other problem may be lurking. Just because it did work doesn't mean it was intended to be used in this case. The different behavior between keywords and dimensions is a result of the different ways how the are implemented and the way TeX (the engine) works when it reads arguments. 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
[NTG-context] Font Maguntia not rendering correctly...
Hi all,i have a text from an old publication typeset in Fraktur. — The font I would like to use here is Unifraktur Maguntia. This Font worked before quite well, however now I get wrong renderings. Please refer to the attached MWE.Context version: 2021.06.01 17:04 LMTX What is oing wrong here?Kind regardsWilli MWE.tex Description: Binary data MWE.pdf Description: Adobe PDF document ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] LMTX problem with doifmode in \setuplayout
On 6/8/2021 10:11 PM, Wolfgang Schuster wrote:
Rik Kabel schrieb am 08.06.2021 um 18:14:
Hello all,
Odd issue with LMTX (works fine with --luatex). \doifelsemode causes a
failure if it is used to set a simple value such as on, off, yes, no,
..., but works with a dimension. Perhaps better illustrated by an example:
\definemode [aaa]
[keep]
\setuplayout [
marking=\doifmodeelse{aaa}{off}{on},
% marking=on,
grid=\doifmodeelse{aaa}{yes}{no},
% grid=yes,
bottom=\doifmodeelse{aaa}{10mm}{20mm},
]
\starttext
This is only a test.
\stoptext
The problem occurs whether or not the mode is enabled. In the example,
it fails with the mode test in the either the marking= or grid= keys,
but has no problem with it in the bottom= key.
The error message says:
The control sequence marked should not appear
between \csname and \endcsname.
pointing to the enabled \doifmodeelse line.
The same issue occurs with the following, using \doifmode:
\definemode [aaa]
[keep]
\setuplayout [
marking=on,
marking=\doifmode{aaa}{off},
]
\starttext
This is only a test.
\stoptext
This did work without complaint a few months ago.
You can never be sure if these combinations (\doifXXX within \setupXXX)
work without problems. The only reliable method in this case is:
% default setup
\setuplayout
[marking=on]
% mode dependent setup
\startmode[aaa]
\setuplayout
[marking=off]
\stopmode
Indeed. I'll make the test more robust (not come up with an error) but
as Wolfgang says, it won't work anyway because \doifmode is a protected
macro.
There is actually a trick:
\expand\doifmode{aaa}{on}
will ignore the protection .. compare
\edef\foo{\doifmode{aaa}{on}}[[\meaningless\foo]]
\edef\foo{\expand\doifmode{aaa}{on}} [[\meaningless\foo]]
only in luametatex/lmtx
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-
___
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
Re: [NTG-context] keep text strictly inside box
Taco Hoekwater schrieb am 08.06.2021 um 08:42:
On 7 Jun 2021, at 23:07, Wolfgang Schuster
wrote:
Use the align key.
\starttext
\startframedtext[width=10cm,align={flushleft,nothyphenated}]
Also, ‘verytolerant’ helps:
align={flushleft,nothyphenated,verytolerant}]
Another option is to add‘broad’ when you have ragged or centered text, e.g.
align={flushleft,broad,nothyphenated}
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
Re: [NTG-context] PDF forms not creating proper children
On Tue, 2021-06-08 at 17:41 +0200, Pablo Rodriguez wrote: > On 6/7/21 10:43 PM, Leonard Janis Robert König wrote: > > Hi Adam, Hi Pablo, > > > > I just noticed your replies, sorry for the late answer! > > > > I could sign forms with both okular as well as mupdf just fine, > > although the behavior is different. The former assumes that the > > field > > is already an existing signature and segfaults when you look at the > > properties, but cann successfully add another signature using the > > "Tools" menu. > Hi Pablo, > I’m afraid that I don’t use Okular. > > > With the latter you can click on the form field to > > trigger a menu to select the signature you want to sign with, and > > it > > "replaces" the "empty" signature generated by ConTeXt. Both work > > fine, > > even with my newer ConTeXt. > > mupdf-gl signs the document, but in a way that only mupdf-gl > understands it. > > Try to open a PDF document signed with mupdf-gl in Acrobat (Reader or > not). You will see that the signature is wrong. Hm, I tested with Okular, Firefox and MasterPDF as I don't have Acrobat on Linux, and both understand the signature, which is why I thought it'd be correct. > > > > On Sun, May 2, 2021 at 5:50 PM Pablo Rodriguez > > > wrote: > > > > [...] > > > > From my experience, only Acrobat deals with child objects in > > > > signatures > > > > generating a valid signature (and rewriting the two objects > > > > into a > > > > single one). > > > > As mentioned above, it seems that mupdf (now?) actually rewrites > > "both" > > signatures into one, however Okular doesn't. > > Sorry, objects is a very special term in PDF parlance. It has nothing > to > do with signatures. > > Just in case it might help, Ah, I see. I'm still a bit unsure what to make of the "fields nested in TABLEs" issue, but maybe further debugging will show at some point. ~ Leo ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] Font Maguntia not rendering correctly...
On 6/8/2021 7:20 PM, Willi Egger wrote: Hi all, i have a text from an old publication typeset in Fraktur. — The font I would like to use here is Unifraktur Maguntia. This Font worked before quite well, however now I get wrong renderings. Please refer to the attached MWE. Context version: 2021.06.01 17:04 LMTX What is oing wrong here? looks ok here ... what if you wipe the cache? - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl - ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] LMTX problem with doifmode in \setuplayout
Rik Kabel schrieb am 08.06.2021 um 18:14:
Hello all,
Odd issue with LMTX (works fine with --luatex). \doifelsemode causes a
failure if it is used to set a simple value such as on, off, yes, no,
..., but works with a dimension. Perhaps better illustrated by an example:
\definemode [aaa]
[keep]
\setuplayout [
marking=\doifmodeelse{aaa}{off}{on},
% marking=on,
grid=\doifmodeelse{aaa}{yes}{no},
% grid=yes,
bottom=\doifmodeelse{aaa}{10mm}{20mm},
]
\starttext
This is only a test.
\stoptext
The problem occurs whether or not the mode is enabled. In the example,
it fails with the mode test in the either the marking= or grid= keys,
but has no problem with it in the bottom= key.
The error message says:
The control sequence marked should not appear
between \csname and \endcsname.
pointing to the enabled \doifmodeelse line.
The same issue occurs with the following, using \doifmode:
\definemode [aaa]
[keep]
\setuplayout [
marking=on,
marking=\doifmode{aaa}{off},
]
\starttext
This is only a test.
\stoptext
This did work without complaint a few months ago.
You can never be sure if these combinations (\doifXXX within \setupXXX)
work without problems. The only reliable method in this case is:
% default setup
\setuplayout
[marking=on]
% mode dependent setup
\startmode[aaa]
\setuplayout
[marking=off]
\stopmode
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
Re: [NTG-context] frameoffset in textbackground?
Hans van der Meer schrieb am 07.06.2021 um 21:46: 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. The textbackground mechanism uses MetaPost to draw the background, lines etc. Not all options are available for each background, e.g. frameoffset works by default only for side lines. 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] LMTX problem with doifmode in \setuplayout
On 6/8/2021 16:11, Wolfgang Schuster wrote:
Rik Kabel schrieb am 08.06.2021 um 18:14:
Hello all,
Odd issue with LMTX (works fine with --luatex). \doifelsemode causes
a failure if it is used to set a simple value such as on, off, yes,
no, ..., but works with a dimension. Perhaps better illustrated by an
example:
\definemode [aaa]
[keep]
\setuplayout [
marking=\doifmodeelse{aaa}{off}{on},
% marking=on,
grid=\doifmodeelse{aaa}{yes}{no},
% grid=yes,
bottom=\doifmodeelse{aaa}{10mm}{20mm},
]
\starttext
This is only a test.
\stoptext
The problem occurs whether or not the mode is enabled. In the
example, it fails with the mode test in the either the marking= or
grid= keys, but has no problem with it in the bottom= key.
The error message says:
The control sequence marked should not appear
between \csname and \endcsname.
pointing to the enabled \doifmodeelse line.
The same issue occurs with the following, using \doifmode:
\definemode [aaa]
[keep]
\setuplayout [
marking=on,
marking=\doifmode{aaa}{off},
]
\starttext
This is only a test.
\stoptext
This did work without complaint a few months ago.
You can never be sure if these combinations (\doifXXX within
\setupXXX) work without problems. The only reliable method in this
case is:
% default setup
\setuplayout
[marking=on]
% mode dependent setup
\startmode[aaa]
\setuplayout
[marking=off]
\stopmode
Wolfgang
Yes, that works. Of course, to say that you can never be sure if such
combinations will work is not a welcome statement about the state of
ConTeXt.
More recent LMTX releases also now break older documents that worked
(with LMTX and MkIV) before. If there is an error in what was previously
written that is only noticed because of tighter enforcement, that is one
thing, but an undocumented change to supported behaviour is less to be
desired. And that it works with dimensions but not on/off/yes/no is very
strange and suggests some other problem may be lurking.
--
Rik
___
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
Re: [NTG-context] LMTX problem with doifmode in \setuplayout
On 6/8/2021 11:44 PM, Wolfgang Schuster wrote: Rik Kabel schrieb am 08.06.2021 um 23:01: Yes, that works. Of course, to say that you can never be sure if such combinations will work is not a welcome statement about the state of ConTeXt. More recent LMTX releases also now break older documents that worked (with LMTX and MkIV) before. If there is an error in what was previously written that is only noticed because of tighter enforcement, that is one thing, but an undocumented change to supported behaviour is less to be desired. And that it works with dimensions but not on/off/yes/no is very strange and suggests some other problem may be lurking. Just because it did work doesn't mean it was intended to be used in this case. The different behavior between keywords and dimensions is a result of the different ways how the are implemented and the way TeX (the engine) works when it reads arguments. and, also in mkiv \dofmode is unexpandable so cannot act as keyword (it might not crash but also doesn't work) that's why wolfgangs suggested \startmode solution is the way to go (also in the past) Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl - ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] PDF forms not creating proper children
Not sure how good it is, but in the poppler discussion this site was mentioned to verify the signature details: https://validator.docusign.com/ I have tried using with poppler's pdfsig and Okular. Adam On Tue, Jun 8, 2021 at 10:14 PM Leonard Janis Robert König wrote: > On Tue, 2021-06-08 at 17:41 +0200, Pablo Rodriguez wrote: > > On 6/7/21 10:43 PM, Leonard Janis Robert König wrote: > > > Hi Adam, Hi Pablo, > > > > > > I just noticed your replies, sorry for the late answer! > > > > > > I could sign forms with both okular as well as mupdf just fine, > > > although the behavior is different. The former assumes that the > > > field > > > is already an existing signature and segfaults when you look at the > > > properties, but cann successfully add another signature using the > > > "Tools" menu. > > > > Hi Pablo, > > > I’m afraid that I don’t use Okular. > > > > > With the latter you can click on the form field to > > > trigger a menu to select the signature you want to sign with, and > > > it > > > "replaces" the "empty" signature generated by ConTeXt. Both work > > > fine, > > > even with my newer ConTeXt. > > > > mupdf-gl signs the document, but in a way that only mupdf-gl > > understands it. > > > > Try to open a PDF document signed with mupdf-gl in Acrobat (Reader or > > not). You will see that the signature is wrong. > > Hm, I tested with Okular, Firefox and MasterPDF as I don't have Acrobat > on Linux, and both understand the signature, which is why I thought > it'd be correct. > > > > > > > On Sun, May 2, 2021 at 5:50 PM Pablo Rodriguez > > > > wrote: > > > > > [...] > > > > > From my experience, only Acrobat deals with child objects in > > > > > signatures > > > > > generating a valid signature (and rewriting the two objects > > > > > into a > > > > > single one). > > > > > > As mentioned above, it seems that mupdf (now?) actually rewrites > > > "both" > > > signatures into one, however Okular doesn't. > > > > Sorry, objects is a very special term in PDF parlance. It has nothing > > to > > do with signatures. > > > > Just in case it might help, > > Ah, I see. I'm still a bit unsure what to make of the "fields nested > in TABLEs" issue, but maybe further debugging will show at some point. > > ~ Leo > > > ___ > 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://context.aanhet.net > archive : https://bitbucket.org/phg/context-mirror/commits/ > wiki : http://contextgarden.net > > ___ > ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] LMTX problem with doifmode in \setuplayout
Hans Hagen schrieb am 09.06.2021 um 00:08:
On 6/8/2021 11:44 PM, Wolfgang Schuster wrote:
Rik Kabel schrieb am 08.06.2021 um 23:01:
Yes, that works. Of course, to say that you can never be sure if
such combinations will work is not a welcome statement about the
state of ConTeXt.
More recent LMTX releases also now break older documents that worked
(with LMTX and MkIV) before. If there is an error in what was
previously written that is only noticed because of tighter
enforcement, that is one thing, but an undocumented change to
supported behaviour is less to be desired. And that it works with
dimensions but not on/off/yes/no is very strange and suggests some
other problem may be lurking.
Just because it did work doesn't mean it was intended to be used in
this case. The different behavior between keywords and dimensions is
a result of the different ways how the are implemented and the way
TeX (the engine) works when it reads arguments.
and, also in mkiv \dofmode is unexpandable so cannot act as keyword
(it might not crash but also doesn't work)
Here is a short example which demonstrates the differences between
LuaTeX (eTeX, pdfTeX etc.) and LuaMetaTeX.
\starttext
\def\one{first}
\def\two{second}
\def\foo{one}
\protected\def\bar{two}
\csname\foo\endcsname
\csname\bar\endcsname
\stoptext
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
Re: [NTG-context] Can't find `t-pgf.tex` and `pgflibrarypgfplots.contourlua.code.tex`
Hello Gavin,
On Mon, 2021-06-07 at 18:04 -0600, Gavin wrote:
> 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 error on line 21 in file /Users/Gavin/context-
> osx-64/tex/texmf-context/tex/context/modules/mkiv/m-tikz.mkiv: ! I
> can't find file `t-pgf.tex'.
> l.21 \input t-pgf.tex
>
For me this builds fine with MkIV (TeX Live 2021 on Arch, specifically
2021.58686-3), however TikZ is incompatible with LMTX right now:
https://github.com/pgf-tikz/pgf/issues/990
There I get the following issue which is slightly different than yours
though:
resolvers | formats | executing runner 'run luametatex
format': /opt/context/lmtx/tex/texmf-linux-64/bin/luametatex --
jobname="texweb" --fmt=/opt/context/lmtx/tex/texmf-cache/luatex-
cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex/cont-
en.fmt --lua=/opt/context/lmtx/tex/texmf-cache/luatex-
cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex/cont-
en.lui cont-yes.mkiv --c:currentrun=1 --c:fulljobname="./texweb.tex" --
c:input="./texweb.tex" --c:kindofrun=1 --c:maxnofruns=9 --
c:texmfbinpath="/opt/context/lmtx/tex/texmf-linux-64/bin"
This is LuaMetaTeX, Version 2.06.12
open source > level 1, order 1, name 'cont-yes.mkiv'
system >
system > ConTeXt ver: 2020.06.30 17:30 MKIV beta fmt:
2020.7.1 int: english/english
system >
system > 'cont-new.mkiv' loaded
open source > level 2, order 2, name
'/opt/context/lmtx/tex/texmf-context/tex/context/base/mkiv/cont-
new.mkiv'
system > beware: some patches loaded from cont-new.mkiv
close source> level 2, order 2, name
'/opt/context/lmtx/tex/texmf-context/tex/context/base/mkiv/cont-
new.mkiv'
system > files > jobname 'texweb', input './texweb',
result 'texweb'
fonts > latin modern fonts are not preloaded
languages > language 'en' is active
open source > level 2, order 3, name './texweb.tex'
modules > 'tikz' is loaded
open source > level 3, order 4, name
'/opt/context/lmtx/tex/texmf-context/tex/context/modules/mkiv/m-
tikz.mkiv'
runtime error : input file 't-pgf.tex' is not found, quitting
mtx-context | fatal error: return code: 256
> The same error in LMTX. The error in Tex Live 2021 is:
>
> tex error > tex error on line 48 in file
> /usr/local/texlive/2021/texmf-
> dist/tex/generic/pgfplots/pgfplots.code.tex: ! I can't find file
> `pgflibrarypgfplots.contourlua.code.tex’.
> l.48 \usepgfplotslibrary{contourlua}
>
> Maybe I’m doing a poor job of maintaining my installations, but maybe
> this is a problem with the download.
You can always check whether your installation or an issue with the
current LMTX here: https://live.contextgarden.net/
Cheers
~ Leo
___
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
[NTG-context] randomizer line-breaking
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 original PDF when I typeset it a third time, the resulting PDF differs on 7 pages, when I typeset it a forth time, the resulting PDF differs on 12 pages, when I typeset it a fifth time, the resulting PDF differs on 0 pages. "differs" means that there a paragraphs (mostly footnotes, rarely in the main text) that show different line-breaking: This doesn't mean wrong hyphenation, just *different* hyphenation, different each time. As you can imagine, I can't provide a minimal example for this, only the entire project-folder and the entire context-standalone. Steffen ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] help with xtreme tables
On 6/8/2021 9:11 AM, Ajith R wrote:
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
the table rows get split into different pages, but the columns get cut at the
right edge of the page.
Is there a way to split the columns as well (repeating the first column as
necessary)?
Also, what is the use of grouping rows within \startxtablenext and
\stopxtablenext?
Note: I am just typing the outline of the code as the cell definitions is very
long and hopefully my requirement is clear without the entire cell definitions.
better look at linetables that
\setuplinetable[n=6,lines=40]
% \setuplinetable[c][1] [width=2cm,background=color,backgroundcolor=red]
% \setuplinetable[c][4]
[width=3cm,background=color,backgroundcolor=yellow]
% \setuplinetable[c][6]
[width=3cm,background=color,backgroundcolor=magenta]
% \setuplinetable[r][even][background=color,backgroundcolor=green]
\starttext
\startlinetablehead
\dorecurse{2}{\dorecurse{5}{\NC head #1 ##1\NC head \NC head \NC
head \NC head \NC head} \NC \NR}
\stoplinetablehead
\startlinetable
\dorecurse{2000}{\dorecurse{5}{\NC cell #1 ##1\NC cell \NC cell \NC
cell \NC cell \NC cell} \NC \NR}
\stoplinetable
\stoptext
a rather old but okay mechanism that splits in two dimensions
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-
___
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
Re: [NTG-context] keep text strictly inside box
> On 7 Jun 2021, at 23:07, Wolfgang Schuster
> wrote:
>
> Use the align key.
>
> \starttext
>
> \startframedtext[width=10cm,align={flushleft,nothyphenated}]
Also, ‘verytolerant’ helps:
> align={flushleft,nothyphenated,verytolerant}]
Best wishes,
Taco
>
> Martinus, zoon van Johannes van Zonnevelt en Johanna
> Teikenbort: getuigen Adrianus van Zonnevelt en Anna
> van Oostbroek.
> \stopframedtext
>
> \stoptext
>
> 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://context.aanhet.net
> archive : https://bitbucket.org/phg/context-mirror/commits/
> wiki : http://contextgarden.net
> ___
___
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
[NTG-context] help with xtreme tables
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 the table rows get split into different pages, but the columns get cut at the right edge of the page. Is there a way to split the columns as well (repeating the first column as necessary)? Also, what is the use of grouping rows within \startxtablenext and \stopxtablenext? Note: I am just typing the outline of the code as the cell definitions is very long and hopefully my requirement is clear without the entire cell definitions. Thanks, ajith NB: Apologies if you get more than one copy of this email because I am re-sending this email as my first attempt appears to have failed ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] randomizer line-breaking
> Am 07.06.2021 um 17:59 schrieb Hans Hagen :
>
> 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
>> file_name-tuc-03.tmp
>> file_name-tuc-04.tmp
>> file_name-tuc-05.tmp
>> Is this right?
> indeed and you can compare them to get some clue about what changes
>
> normally you get one so your style somehow triggers differences
Besides plenty of numbers that differ, there are also entire lines that differ:
One frequent difference for examples is line 2 (macros) and 3 (randomseed) in
this:
utilitydata.job.variables.collected={
["macros"]={},
["randomseed"]=0x1.c14cd54cp-1,
["sectionblockorder"]={ "frontpart", "bodypart", "backpart" },
Another difference that pops up 1000 times is this line
["used"]="fit",
in situation like this:
utilitydata.structures.references.collected={
["02"]={
["*101"]={
["metadata"]=678,
["references"]={
["block"]="bodypart",
["internal"]=102,
["prefix"]="02",
["realpage"]=16,
["reference"]="*101",
["section"]=3,
["used"]="fit",
["view"]="fit",
["x"]=25526152,
["y"]=36448045,
},
},
Does this help?
PS: The entire problem began when I started using hyphenation-exceptions...
Steffen
___
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
[NTG-context] Fwd: help with xtreme tables
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 the table rows get split into different pages, but the columns get cut at the right edge of the page. Is there a way to split the columns as well (repeating the first column as necessary)? Also, what is the use of grouping rows within \startxtablenext and \stopxtablenext? Note: I am just typing the outline of the code as the cell definitions is very long and hopefully my requirement is clear without the entire cell definitions. Thanks, ajith NB: Apologies if you get two copies of this email as I am sending this email a second timr as my first attempt appears to have failed ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] Can't find `t-pgf.tex` and `pgflibrarypgfplots.contourlua.code.tex`
Hans, > On Jun 8, 2021, at 6:36 AM, Hans Hagen wrote: > > On 6/8/2021 9:56 AM, Leonard Janis Robert König wrote: >> Hello Gavin, >> On Mon, 2021-06-07 at 18:04 -0600, Gavin wrote: >>> 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 error on line 21 in file /Users/Gavin/context- >>> osx-64/tex/texmf-context/tex/context/modules/mkiv/m-tikz.mkiv: ! I >>> can't find file `t-pgf.tex'. >>> l.21 \input t-pgf.tex >>> >> For me this builds fine with MkIV (TeX Live 2021 on Arch, specifically >> 2021.58686-3), however TikZ is incompatible with LMTX right now: >> https://github.com/pgf-tikz/pgf/issues/990 >> There I get the following issue which is slightly different than yours > \usemodule[tikz] > \usemodule[pgfplots] > \starttext >Hello > \stoptext > > rusn without error here (so are you sure that you use m-tikz.mkiv from the > distribution)? Yes, I’m using m-tikz.mkiv from the distribution. I opened it to confirm that it has the line \input t-pgf.tex, but I can’t find the file "t-pgf.tex” anywhere on my computer. I also checked the source browser at contextgarden. There m-tikz.mkiv also has the line "\input t-pgf.tex”, but I can’t find the file t-pgf.tex on the source browser either. Where is t-pgf.tex supposed to be? Thanks, Gavin ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
[NTG-context] Fixed: Can't find `t-pgf.tex` and `pgflibrarypgfplots.contourlua.code.tex`
Hi Hans and everyone, The problem was fixed by reinstalling all modules using the instructions at https://wiki.contextgarden.net/Modules. Specifically, I ran these in the directory for my installation: rsync -rltv --del rsync://contextgarden.net/minimals/current/modules/ modules rsync -rlt --exclude=/VERSION --del modules/*/ tex/texmf-modules sh ./install.sh I don’t know what any of that means (except for the last line) or why my modules folder had become empty, but everything is working again. > On Jun 8, 2021, at 7:30 AM, Hans Hagen wrote: > > but we can try to avoid it (probably error prone anyway because i see a > dangling \stopmodule) by moving what is in there to the m- one; can you test > the attached I also tried the modified m-tikz.mkiv that you sent. It also works fine when I typeset my book full of Tik-Z diagrams. I don’t notice any difference. Thanks! Gavin ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] Can't find `t-pgf.tex` and `pgflibrarypgfplots.contourlua.code.tex`
On 6/8/2021 9:56 AM, Leonard Janis Robert König wrote: Hello Gavin, On Mon, 2021-06-07 at 18:04 -0600, Gavin wrote: 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 error on line 21 in file /Users/Gavin/context- osx-64/tex/texmf-context/tex/context/modules/mkiv/m-tikz.mkiv: ! I can't find file `t-pgf.tex'. l.21 \input t-pgf.tex For me this builds fine with MkIV (TeX Live 2021 on Arch, specifically 2021.58686-3), however TikZ is incompatible with LMTX right now: https://github.com/pgf-tikz/pgf/issues/990 There I get the following issue which is slightly different than yours \usemodule[tikz] \usemodule[pgfplots] \starttext Hello \stoptext rusn without error here (so are you sure that you use m-tikz.mkiv from the distribution)? - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl - ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] randomizer line-breaking
On 6/8/2021 12:18 PM, Steffen Wolfrum wrote:
Am 07.06.2021 um 17:59 schrieb Hans Hagen :
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
file_name-tuc-03.tmp
file_name-tuc-04.tmp
file_name-tuc-05.tmp
Is this right?
indeed and you can compare them to get some clue about what changes
normally you get one so your style somehow triggers differences
Besides plenty of numbers that differ, there are also entire lines that differ:
One frequent difference for examples is line 2 (macros) and 3 (randomseed) in
this:
utilitydata.job.variables.collected={
["macros"]={},
["randomseed"]=0x1.c14cd54cp-1,
["sectionblockorder"]={ "frontpart", "bodypart", "backpart" },
that randomseed should be the same between runs (unless one wipes the
tuc file) so are you doing something with random?
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-
___
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
Re: [NTG-context] randomizer line-breaking
> Am 08.06.2021 um 15:01 schrieb Hans Hagen :
>
> On 6/8/2021 12:18 PM, Steffen Wolfrum wrote:
>>> Am 07.06.2021 um 17:59 schrieb Hans Hagen :
>>>
>>> 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
file_name-tuc-03.tmp
file_name-tuc-04.tmp
file_name-tuc-05.tmp
Is this right?
>>> indeed and you can compare them to get some clue about what changes
>>>
>>> normally you get one so your style somehow triggers differences
>> Besides plenty of numbers that differ, there are also entire lines that
>> differ:
>> One frequent difference for examples is line 2 (macros) and 3 (randomseed)
>> in this:
>> utilitydata.job.variables.collected={
>> ["macros"]={},
>> ["randomseed"]=0x1.c14cd54cp-1,
>> ["sectionblockorder"]={ "frontpart", "bodypart", "backpart" },
> that randomseed should be the same between runs (unless one wipes the tuc
> file) so are you doing something with random?
not that I know of.
I searched through both, the project folder and my modules (in context
standalone), both «random» nowhere was to be found.
perhaps I incidently use a command that utilizes random... what could this be?
___
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
Re: [NTG-context] Can't find `t-pgf.tex` and `pgflibrarypgfplots.contourlua.code.tex`
On 6/8/2021 3:00 PM, Gavin wrote:
Hans,
On Jun 8, 2021, at 6:36 AM, Hans Hagen wrote:
On 6/8/2021 9:56 AM, Leonard Janis Robert König wrote:
Hello Gavin,
On Mon, 2021-06-07 at 18:04 -0600, Gavin wrote:
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 error on line 21 in file /Users/Gavin/context-
osx-64/tex/texmf-context/tex/context/modules/mkiv/m-tikz.mkiv: ! I
can't find file `t-pgf.tex'.
l.21 \input t-pgf.tex
For me this builds fine with MkIV (TeX Live 2021 on Arch, specifically
2021.58686-3), however TikZ is incompatible with LMTX right now:
https://github.com/pgf-tikz/pgf/issues/990
There I get the following issue which is slightly different than yours
\usemodule[tikz]
\usemodule[pgfplots]
\starttext
Hello
\stoptext
rusn without error here (so are you sure that you use m-tikz.mkiv from the
distribution)?
Yes, I’m using m-tikz.mkiv from the distribution. I opened it to confirm that it has the
line \input t-pgf.tex, but I can’t find the file "t-pgf.tex” anywhere on my
computer. I also checked the source browser at contextgarden. There m-tikz.mkiv also has
the line "\input t-pgf.tex”, but I can’t find the file t-pgf.tex on the source
browser either.
Where is t-pgf.tex supposed to be?
somplace in a mdoules tree i installed from the garden (but maybe it's
nowaways not there)
but we can try to avoid it (probably error prone anyway because i see a
dangling \stopmodule) by moving what is in there to the m- one; can you
test the attached
(i have a few files in the test suite so when something tikz breaks i
normally get a signal - i'm not a tikz user myself so i rely on otheres
for more detailed reports)
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-
%D A fixed variant if the t-tikz module distributed with tikz.
\ifdefined\pdflastxpos \else
\unprotect
\frozen\overloaded\protected\def\pdflastxpos{\numexpr\clf_lastxpos\relax}
\frozen\overloaded\protected\def\pdflastypos{\numexpr\clf_lastypos\relax}
\protect
\fi
\pushoverloadmode
\pushcatcodetable
\setcatcodetable\texcatcodes
\catcode`\@=11
\catcode`\|=12
\catcode`\!=12
\input t-pgf.tex
\input t-pgffor.tex
\input tikz.code.tex
\popcatcodetable
\popoverloadmode
\permanent\protected\def\tikzerrormessage#1#2#3%
{\writestatus{#1}{#2}}
\ifcase\contextlmtxmode
\let\starttikzsettings\relax
\let\stoptikzsettings \relax
\protected\def\starttikzpicture
{% \dontleavehmode
\begingroup
\ifdefined\PackageError\else \let\PackageError\tikzerrormessage \fi
\tikzpicture}
\protected\def\stoptikzpicture
{\endtikzpicture
\endgroup}
\else
% for now:
\overloadmode\zerocount
% but this will be mandate for settings outside the start .. stop
\permanent\protected\def\starttikzsettings
{\pushoverloadmode}
\permanent\protected\def\stoptikzsettings
{\popoverloadmode}
\permanent\protected\def\starttikzpicture
{\dontleavehmode
\hcontainer\bgroup
% \pushoverloadmode
\ifdefined\PackageError\else \let\PackageError\tikzerrormessage \fi
\tikzpicture}
\permanent\protected\def\stoptikzpicture
{\endtikzpicture
% \popoverloadmode
\egroup}
\fi
% \input t-pgf.tex
\ifx\pgfdefined\undefined
\let\pgfdefined\relax
% \input t-pgfcor.tex
\ifx\pgfcoredefined\undefined
\let\pgfcoredefined=\relax
\input t-pgfsys.tex
\edef\pgfcoreatcode {\the\catcode`\@}
\edef\pgfcorebarcode{\the\catcode`\|}
\edef\pgfcoreexclaimcode{\the\catcode`\!}
\catcode`\@=11
\catcode`\|=12
\catcode`\!=12
\input pgfcore.code.tex
\catcode`\@=\pgfcoreatcode
\catcode`\|=\pgfcorebarcode
\catcode`\!=\pgfcoreexclaimcode
\let\startpgfpicture \pgfpicture
\let\stoppgfpicture\endpgfpicture
\let\startpgfscope \pgfscope
\let\stoppgfscope \endpgfscope
\let\startpgflowlevelscope \pgflowlevelscope
\let\stoppgflowlevelscope \endpgflowlevelscope
\let\startpgfinterruptpath \pgfinterruptpath
\let\stoppgfinterruptpath \endpgfinterruptpath
\let\startpgfinterruptpicture\pgfinterruptpicture
\let\stoppgfinterruptpicture \endpgfinterruptpicture
Re: [NTG-context] randomizer line-breaking
> Am 08.06.2021 um 15:30 schrieb Hans Hagen : > > On 6/8/2021 3:15 PM, Steffen Wolfrum wrote: > >> perhaps I incidently use a command that utilizes random... what could this >> be? > mwe pardon? ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] help with xtreme tables
Hi,
Thanks. I will try as you suggested
ajith
On Tue, Jun 8, 2021 at 1:54 PM, Hans Hagen wrote:
On 6/8/2021 9:11 AM, Ajith R wrote:
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
the table rows get split into different pages, but the columns get
cut at the right edge of the page.
Is there a way to split the columns as well (repeating the first
column as necessary)?
Also, what is the use of grouping rows within \startxtablenext and
\stopxtablenext?
Note: I am just typing the outline of the code as the cell
definitions is very long and hopefully my requirement is clear
without the entire cell definitions.
better look at linetables that
\setuplinetable[n=6,lines=40]
% \setuplinetable[c][1]
[width=2cm,background=color,backgroundcolor=red]
% \setuplinetable[c][4]
[width=3cm,background=color,backgroundcolor=yellow]
% \setuplinetable[c][6]
[width=3cm,background=color,backgroundcolor=magenta]
% \setuplinetable[r][even][background=color,backgroundcolor=green]
\starttext
\startlinetablehead
\dorecurse{2}{\dorecurse{5}{\NC head #1 ##1\NC head \NC head \NC
head \NC head \NC head} \NC \NR}
\stoplinetablehead
\startlinetable
\dorecurse{2000}{\dorecurse{5}{\NC cell #1 ##1\NC cell \NC cell
\NC cell \NC cell \NC cell} \NC \NR}
\stoplinetable
\stoptext
a rather old but okay mechanism that splits in two dimensions
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-
___
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
Re: [NTG-context] randomizer line-breaking
On 6/8/2021 3:15 PM, Steffen Wolfrum wrote: perhaps I incidently use a command that utilizes random... what could this be? mwe - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl - ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] randomizer line-breaking
On 6/8/2021 3:32 PM, Steffen Wolfrum wrote: Am 08.06.2021 um 15:30 schrieb Hans Hagen : On 6/8/2021 3:15 PM, Steffen Wolfrum wrote: perhaps I incidently use a command that utilizes random... what could this be? mwe pardon? we need a mwe Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl - ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] randomizer line-breaking
> Am 08.06.2021 um 16:16 schrieb Aditya Mahajan : > > On Tue, 8 Jun 2021, Steffen Wolfrum wrote: > >> >> >>> Am 08.06.2021 um 15:30 schrieb Hans Hagen : >>> >>> On 6/8/2021 3:15 PM, Steffen Wolfrum wrote: >>> perhaps I incidently use a command that utilizes random... what could this be? >>> mwe > > http://texfaq.org/FAQ-minxampl > https://tex.meta.stackexchange.com/questions/228/ive-just-been-asked-to-write-a-minimal-working-example-mwe-what-is-that > > These are latex centric advice on creating a minimal working example but > broadly applicable for context as well. Before I posted my initial posting «randomizer line-breaking» I already spent days and weeks boiling down this phenomenon. Unfortunately the random output made it impossible for me to make a smaller, but *working* (i.e. showing the bug) example. It just appears sometimes, sometimes it doesn't – in between two runs I changed nothing: «As you can imagine, I can't provide a minimal example for this, only the entire project-folder and the entire context-standalone.» So my hope was that Hans (and Wolfgang et al.) know how things are chained together. For example: Which ConTeXt command uses randomizer? I have no idea what goes on behind my user interface. Others maybe do. Another example: The problem only appears when using start-/stopexceptions. Is there a connection between exceptions and random output on the level of low level code, maybe? Steffen ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] randomizer line-breaking
On 6/8/2021 4:35 PM, Steffen Wolfrum wrote: Am 08.06.2021 um 16:16 schrieb Aditya Mahajan : On Tue, 8 Jun 2021, Steffen Wolfrum wrote: Am 08.06.2021 um 15:30 schrieb Hans Hagen : On 6/8/2021 3:15 PM, Steffen Wolfrum wrote: perhaps I incidently use a command that utilizes random... what could this be? mwe http://texfaq.org/FAQ-minxampl https://tex.meta.stackexchange.com/questions/228/ive-just-been-asked-to-write-a-minimal-working-example-mwe-what-is-that These are latex centric advice on creating a minimal working example but broadly applicable for context as well. Before I posted my initial posting «randomizer line-breaking» I already spent days and weeks boiling down this phenomenon. Unfortunately the random output made it impossible for me to make a smaller, but *working* (i.e. showing the bug) example. It just appears sometimes, sometimes it doesn't – in between two runs I changed nothing: «As you can imagine, I can't provide a minimal example for this, only the entire project-folder and the entire context-standalone.» So my hope was that Hans (and Wolfgang et al.) know how things are chained together. For example: Which ConTeXt command uses randomizer? I have no idea what goes on behind my user interface. Others maybe do. Another example: The problem only appears when using start-/stopexceptions. Is there a connection between exceptions and random output on the level of low level code, maybe? maybe you have two similar exceptions (hyphens removed), comment exceptions and see which one does the harm all the rest is guesswork Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl - ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] randomizer line-breaking
On Tue, 8 Jun 2021, Steffen Wolfrum wrote: > > > > Am 08.06.2021 um 15:30 schrieb Hans Hagen : > > > > On 6/8/2021 3:15 PM, Steffen Wolfrum wrote: > > > >> perhaps I incidently use a command that utilizes random... what could this > >> be? > > mwe http://texfaq.org/FAQ-minxampl https://tex.meta.stackexchange.com/questions/228/ive-just-been-asked-to-write-a-minimal-working-example-mwe-what-is-that These are latex centric advice on creating a minimal working example but broadly applicable for context as well. Aditya ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] PDF forms not creating proper children
On 6/7/21 10:43 PM, Leonard Janis Robert König wrote: > Hi Adam, Hi Pablo, > > I just noticed your replies, sorry for the late answer! > > I could sign forms with both okular as well as mupdf just fine, > although the behavior is different. The former assumes that the field > is already an existing signature and segfaults when you look at the > properties, but cann successfully add another signature using the > "Tools" menu. Hi Leo, I’m afraid that I don’t use Okular. > With the latter you can click on the form field to > trigger a menu to select the signature you want to sign with, and it > "replaces" the "empty" signature generated by ConTeXt. Both work fine, > even with my newer ConTeXt. mupdf-gl signs the document, but in a way that only mupdf-gl understands it. Try to open a PDF document signed with mupdf-gl in Acrobat (Reader or not). You will see that the signature is wrong. >> On Sun, May 2, 2021 at 5:50 PM Pablo Rodriguez wrote: >>> [...] >>> From my experience, only Acrobat deals with child objects in >>> signatures >>> generating a valid signature (and rewriting the two objects into a >>> single one). > > As mentioned above, it seems that mupdf (now?) actually rewrites "both" > signatures into one, however Okular doesn't. Sorry, objects is a very special term in PDF parlance. It has nothing to do with signatures. Just in case it might help, Pablo -- http://www.ousia.tk ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
[NTG-context] LMTX problem with doifmode in \setuplayout
Hello all,
Odd issue with LMTX (works fine with --luatex). \doifelsemode causes a
failure if it is used to set a simple value such as on, off, yes, no,
..., but works with a dimension. Perhaps better illustrated by an example:
\definemode [aaa]
[keep]
\setuplayout [
marking=\doifmodeelse{aaa}{off}{on},
% marking=on,
grid=\doifmodeelse{aaa}{yes}{no},
% grid=yes,
bottom=\doifmodeelse{aaa}{10mm}{20mm},
]
\starttext
This is only a test.
\stoptext
The problem occurs whether or not the mode is enabled. In the example,
it fails with the mode test in the either the marking= or grid= keys,
but has no problem with it in the bottom= key.
The error message says:
The control sequence marked should not appear
between \csname and \endcsname.
pointing to the enabled \doifmodeelse line.
The same issue occurs with the following, using \doifmode:
\definemode [aaa]
[keep]
\setuplayout [
marking=on,
marking=\doifmode{aaa}{off},
]
\starttext
This is only a test.
\stoptext
This did work without complaint a few months ago.
--
Rik Kabel
___
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
