Re: [NTG-context] \WORD regression
On 12/10/2021 8:20 AM, Henning Hraban Ramm via ntg-context wrote:
Am 09.12.21 um 19:00 schrieb Henning Hraban Ramm via ntg-context:
\starttext
\WORD{größer}
\stoptext
\WORD used to handle "ß" correctly, i.e. convert it to "SS"; now it
makes "sS".
(If the current font contains an uppercase ß that would be even
better, but those are rare).
I can’t tell when it changed (some LMTX versions ago) and can’t check
MkIV, since "mtxrun --generate --luatex" doesn’t work.
Hans sent me a fix, I guess it will be included in the next upload.
And yes, uppercase ß (ẞ, U1E9E) would be even better, even according to
the official German orthography rules since 2017, but there are still
not many fonts that have it.
if needed we could catch that with a fallback feature (could cover more
such cases)
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] Problem with log coordinates in metafun graph module
Dear list,
I dived into m-grap.mpiv and found that "log" coordinates are now called
"logarithmic". So
setcoords(logarithmic, linear)
is the new way and it works with the last ConTeXt version.
Jean-Philippe,
> Le 8 déc. 2021 à 11:49, Jean-Philippe Rey via ntg-context
> a écrit :
>
> Dear list,
>
> Log coordinates seem to be broken in the last version of
> ConTeXt/metafun/graph.
>
> Here is my failing example
>
> ===
> \usemodule[graph]
> \starttext
> \startMPcode{graph}
> draw begingraph(100mm, 100mm);
> setcoords(log, linear); % works fine with setcoords(linear, linear);
> gdraw (1e-3, 10) -- (10, 30);
> endgraph;
> \stopMPcode
> \stoptext
> ===
>
> which produces nothing but works with ConTeXt ver: 2021.01.05 10:45 LMTX.
>
> You will find attached the log file which contains
>
> metafun > log > error: A primary expression can't begin with ','
>
> Thank you for your help.
___
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] \WORD regression
Am 09.12.21 um 19:00 schrieb Henning Hraban Ramm via ntg-context:
\starttext
\WORD{größer}
\stoptext
\WORD used to handle "ß" correctly, i.e. convert it to "SS"; now it
makes "sS".
(If the current font contains an uppercase ß that would be even better,
but those are rare).
I can’t tell when it changed (some LMTX versions ago) and can’t check
MkIV, since "mtxrun --generate --luatex" doesn’t work.
Hans sent me a fix, I guess it will be included in the next upload.
And yes, uppercase ß (ẞ, U1E9E) would be even better, even according to
the official German orthography rules since 2017, but there are still
not many fonts that have it.
Hraban
___
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] using the newcolumnsets module
Dear Hans, Bruce Horrocks, I test the file using MacVim and confirm that it works fine. Thus, something happened in my system or environment of vscode. I may reinstall vscode. Thank you. Best regards, Dalyoung ___ 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] using the newcolumnsets module
Dear Bruce Horrocks, Thank you for your test. I have moved the file to the local and run it. But the result is same. However, since your try worked well, the problem is mine not LMTX. I am using the editor “vscode”, and there may be something changed in my system recently. I’ll try using other editors. Thank you. Best regards, Dalyoung > Message: 4 > Date: Thu, 9 Dec 2021 17:19:48 + > From: Bruce Horrocks >> On 9 Dec 2021, at 16:32, Hans Hagen via ntg-context >> wrote: >> >> On 12/9/2021 1:27 PM, Jeong Dal via ntg-context wrote: >> >>> error messages: >> >>> Documents/com~apple~CloudDocs/texMain/ColumnsetTest.tex', result >>> '/Users/graph/Library/Mobile >> >>> Documents/com~apple~CloudDocs/texMain/ColumnsetTest.tex''" terminated with >>> exit code: 1.* >> no clue ... does lmtx also fail? is it an apple binary issue? >> >> Hans >> > > It works fine for me under macOS Monterey and LMTX version: > > mtx-context | current version: 2021.12.03 15:20 > > Dalyoung: the error line that Hans quoted implies that your .tex file is on > your iCloud drive. Try moving it to a local, hard drive. > > — > Bruce Horrocks > Hampshire, UK > ___ 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] using the newcolumnsets module
Dear Hans, >> Documents/com~apple~CloudDocs/texMain/ColumnsetTest.tex''" terminated >> with exit code: 1.* > no clue ... does lmtx also fail? is it an apple binary issue? I am running LMTX now. It opens and closes "*-newcolumnsets.mkiv” files(we can find the lines in the log file). I also tested the files which had no problem a month ago, but got the same error message now. I reinstalled context and test it. But the result is same. I am going to test it more. Thank you. Best regards, Dalyoung ___ 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] \WORD regression
\starttext
\WORD{größer}
\stoptext
\WORD used to handle "ß" correctly, i.e. convert it to "SS"; now it
makes "sS".
(If the current font contains an uppercase ß that would be even better,
but those are rare).
I can’t tell when it changed (some LMTX versions ago) and can’t check
MkIV, since "mtxrun --generate --luatex" doesn’t work.
Hraban
___
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] double underbars
Am 30.11.21 um 16:17 schrieb Hans Hagen via ntg-context:
Another question: what do you mean with a dy-shift version?
Nested bars have a parameter ‘dy’ which controls the vertical shifts
needed to make sure that they do not overlap. Text backgrounds do not
have that option at all.
i've added that so one can nest the mp driven ones but still within the
same category ... i'll look into a mix (more complex management wise so
typically a rainy weekend thing; i know how to do it but ...)
If I use \overbar within \underbar, the same dy is used, i.e. in the
example, the first \overbar is in the right location, while the second
is too high:
\starttext
\overbar{Über} \underbar{Unterstrich \underbar{steigt \overbar{auf} den
\underbar{Unterberg}}}.
\stoptext
Hraban
___
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] [DKIM] using the newcolumnsets module
> On 9 Dec 2021, at 16:32, Hans Hagen via ntg-context > wrote: > > On 12/9/2021 1:27 PM, Jeong Dal via ntg-context wrote: > >> error messages: > >> Documents/com~apple~CloudDocs/texMain/ColumnsetTest.tex', result >> '/Users/graph/Library/Mobile > >> Documents/com~apple~CloudDocs/texMain/ColumnsetTest.tex''" terminated with >> exit code: 1.* > no clue ... does lmtx also fail? is it an apple binary issue? > > 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 > - It works fine for me under macOS Monterey and LMTX version: mtx-context | current version: 2021.12.03 15:20 Dalyoung: the error line that Hans quoted implies that your .tex file is on your iCloud drive. Try moving it to a local, hard drive. — Bruce Horrocks Hampshire, UK ___ 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] xml processing: if elseif else / switch case
Denis Maier via ntg-context schrieb am 09.12.2021 um 18:24: Thanks for all the answers. That's helpful. But I think that does not work with the xml tests, or does it? I mean, is this a general mechanism? Since you didn't provide a example with your problem there is no way to tell how to improve it. 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] xml processing: if elseif else / switch case
Thanks for all the answers. That's helpful. But I think that does not work with the xml tests, or does it? I mean, is this a general mechanism? Denis Von: ntg-context im Auftrag von Hans Hagen via ntg-context Gesendet: Donnerstag, 9. Dezember 2021 17:53:42 An: mailing list for ConTeXt users Cc: Hans Hagen Betreff: Re: [NTG-context] xml processing: if elseif else / switch case On 12/9/2021 5:30 PM, Joey McCollum via ntg-context wrote: > Thanks for correcting that, Wolfgang. I must have added the other \fi > instances because I was trying to use \orelse in MKIV and couldn't get > it to work. Is it only supported in LMTX? yes, it's one of the native luametatex features (already there for a while) 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 ___ ___ 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] xml processing: if elseif else / switch case
On 12/9/2021 5:30 PM, Joey McCollum via ntg-context wrote: Thanks for correcting that, Wolfgang. I must have added the other \fi instances because I was trying to use \orelse in MKIV and couldn't get it to work. Is it only supported in LMTX? yes, it's one of the native luametatex features (already there for a while) 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] xml processing: if elseif else / switch case
Thanks for correcting that, Wolfgang. I must have added the other \fi
instances because I was trying to use \orelse in MKIV and couldn't get it
to work. Is it only supported in LMTX?
Joey
On Thu, Dec 9, 2021 at 11:30 AM Hans Hagen via ntg-context <
ntg-context@ntg.nl> wrote:
> On 12/9/2021 5:11 PM, Wolfgang Schuster via ntg-context wrote:
> > Joey McCollum via ntg-context schrieb am 09.12.2021 um 15:08:
> >> I believe \orelse might be what you want. It works with most \if...
> >> macros, and it avoids nesting of \doifelse constructs. Here's an
> >> example, which I use in conditionally removing preceding punctuation
> >> if any other keys are defined before a specific one in an assignment:
> >>
> >> ```
> >> % If any of the preceding keys was specified, then replace any
> >> preceding punctuation with a space
> >> % and typeset the number with its CSL abbreviation, followed by a
> >> comma
> >> \ifdefined\btxsbllocvol
> >> \removeunwantedspaces\removepunctuation\btxspace
> >> \orelse\ifdefined\btxsbllocno
> >> \removeunwantedspaces\removepunctuation\btxspace
> >> \fi
> >> \orelse\ifdefined\btxsbllocpt
> >> [...]
> >> \fi
> >> ```
> >
> > The \fi at the end of each \orelse branch is wrong.
> >
> > \ifdefined\btxsbllocvol
> > ...
> > \orelse\ifdefined\btxsbllocno
> > ...
> > \else
> > ...
> > \fi
> and when 'string' comparison is needed one can do:
>
> \starttext
>
> \def\foo{foo}
> \def\ofo{ofo}
> \def\oof{oof}
>
> \def\XXX{ofo}
>
> \ifcstok\XXX\foo
> FOO
> \orelse\ifcstok\XXX\ofo
> OFO
> \orelse\ifcstok\XXX\oof
> OOF
> \else
> XXX
> \fi
>
> \def\XXX{\ofo}
>
> \iftok{\XXX}{\foo}%
> FOO
> \orelse\iftok{\XXX}{\ofo}%
> OFO
> \orelse\iftok{\XXX}{\oof}%
> OOF
> \else
> XXX
> \fi
>
> \ifcstok{\XXX}\foo
> FOO
> \orelse\ifcstok{\XXX}\ofo
> OFO
> \orelse\ifcstok\XXX}\oof
> OOF
> \else
> XXX
> \fi
>
> \stoptext
>
> watch the subtle differences. It all makes coding in tex primitives a
> bit more visual appealing and readable. Oone of the objectives of lmtx
> is that users can read the context code without pondering too much about
> the syntax or getting depressed by possibly obscure helper macros and
> expansion trickery.
>
> 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
>
> ___
>
___
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] [DKIM] using the newcolumnsets module
On 12/9/2021 1:27 PM, Jeong Dal via ntg-context wrote: error messages: Documents/com~apple~CloudDocs/texMain/ColumnsetTest.tex', result '/Users/graph/Library/Mobile Documents/com~apple~CloudDocs/texMain/ColumnsetTest.tex''" terminated with exit code: 1.* no clue ... does lmtx also fail? is it an apple binary issue? 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] xml processing: if elseif else / switch case
On 12/9/2021 5:11 PM, Wolfgang Schuster via ntg-context wrote:
Joey McCollum via ntg-context schrieb am 09.12.2021 um 15:08:
I believe \orelse might be what you want. It works with most \if...
macros, and it avoids nesting of \doifelse constructs. Here's an
example, which I use in conditionally removing preceding punctuation
if any other keys are defined before a specific one in an assignment:
```
% If any of the preceding keys was specified, then replace any
preceding punctuation with a space
% and typeset the number with its CSL abbreviation, followed by a
comma
\ifdefined\btxsbllocvol
\removeunwantedspaces\removepunctuation\btxspace
\orelse\ifdefined\btxsbllocno
\removeunwantedspaces\removepunctuation\btxspace
\fi
\orelse\ifdefined\btxsbllocpt
[...]
\fi
```
The \fi at the end of each \orelse branch is wrong.
\ifdefined\btxsbllocvol
...
\orelse\ifdefined\btxsbllocno
...
\else
...
\fi
and when 'string' comparison is needed one can do:
\starttext
\def\foo{foo}
\def\ofo{ofo}
\def\oof{oof}
\def\XXX{ofo}
\ifcstok\XXX\foo
FOO
\orelse\ifcstok\XXX\ofo
OFO
\orelse\ifcstok\XXX\oof
OOF
\else
XXX
\fi
\def\XXX{\ofo}
\iftok{\XXX}{\foo}%
FOO
\orelse\iftok{\XXX}{\ofo}%
OFO
\orelse\iftok{\XXX}{\oof}%
OOF
\else
XXX
\fi
\ifcstok{\XXX}\foo
FOO
\orelse\ifcstok{\XXX}\ofo
OFO
\orelse\ifcstok\XXX}\oof
OOF
\else
XXX
\fi
\stoptext
watch the subtle differences. It all makes coding in tex primitives a
bit more visual appealing and readable. Oone of the objectives of lmtx
is that users can read the context code without pondering too much about
the syntax or getting depressed by possibly obscure helper macros and
expansion trickery.
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] xml processing: if elseif else / switch case
Joey McCollum via ntg-context schrieb am 09.12.2021 um 15:08: I believe \orelse might be what you want. It works with most \if... macros, and it avoids nesting of \doifelse constructs. Here's an example, which I use in conditionally removing preceding punctuation if any other keys are defined before a specific one in an assignment: ``` % If any of the preceding keys was specified, then replace any preceding punctuation with a space % and typeset the number with its CSL abbreviation, followed by a comma \ifdefined\btxsbllocvol \removeunwantedspaces\removepunctuation\btxspace \orelse\ifdefined\btxsbllocno \removeunwantedspaces\removepunctuation\btxspace \fi \orelse\ifdefined\btxsbllocpt [...] \fi ``` The \fi at the end of each \orelse branch is wrong. \ifdefined\btxsbllocvol ... \orelse\ifdefined\btxsbllocno ... \else ... \fi 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] xml processing: if elseif else / switch case
I believe \orelse might be what you want. It works with most \if... macros, and it avoids nesting of \doifelse constructs. Here's an example, which I use in conditionally removing preceding punctuation if any other keys are defined before a specific one in an assignment: ``` % If any of the preceding keys was specified, then replace any preceding punctuation with a space % and typeset the number with its CSL abbreviation, followed by a comma \ifdefined\btxsbllocvol \removeunwantedspaces\removepunctuation\btxspace \orelse\ifdefined\btxsbllocno \removeunwantedspaces\removepunctuation\btxspace \fi \orelse\ifdefined\btxsbllocpt \removeunwantedspaces\removepunctuation\btxspace \fi \orelse\ifdefined\btxsbllocp \removeunwantedspaces\removepunctuation\btxspace \fi \orelse\ifdefined\btxsbllocn \removeunwantedspaces\removepunctuation\btxspace \fi \orelse\ifdefined\btxsbllocfig \removeunwantedspaces\removepunctuation\btxspace \fi \orelse\ifdefined\btxsbllocop \removeunwantedspaces\removepunctuation\btxspace \fi \orelse\ifdefined\btxsbllocbk \removeunwantedspaces\removepunctuation\btxspace \fi \orelse\ifdefined\btxsbllocep \removeunwantedspaces\removepunctuation\btxspace \fi \orelse\ifdefined\btxsbllocchap \removeunwantedspaces\removepunctuation\btxspace \fi \orelse\ifdefined\btxsbllocv \removeunwantedspaces\removepunctuation\btxspace \fi \orelse\ifdefined\btxsbllocfol \removeunwantedspaces\removepunctuation\btxspace \fi \orelse\ifdefined\btxsbllocfrag \removeunwantedspaces\removepunctuation\btxspace \fi \orelse\ifdefined\btxsbllocpl \removeunwantedspaces\removepunctuation\btxspace \fi \orelse\ifdefined\btxsblloccol \removeunwantedspaces\removepunctuation\btxspace \fi \orelse\ifdefined\btxsbllocl \removeunwantedspaces\removepunctuation\btxspace \fi \orelse\ifdefined\btxsbllocsv \removeunwantedspaces\removepunctuation\btxspace \fi \orelse\ifdefined\btxsbllocsec \removeunwantedspaces\removepunctuation\btxspace \fi \fi ``` Joey On Thu, Dec 9, 2021, 3:19 AM Denis Maier via ntg-context wrote: > Hi, > > > > I was wondering whether we have tests similar to «if-else if-else» or > «switch case» in context’s xml processing. (And even in context more > general...) I have found these doifelse tests, but elseif doesn’t seem to > exist. Is that correct? If yes, could that be added? Of course, you can > always just nest doifelse-constructs, but that will become ugly quickly. > Being able to specify multiple branches would be handy. > > > > Best, > > Denis > > ___ > 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] using the newcolumnsets module
Dear all,
I made an exam form by the help of the experts in this list.
However, it was not working after recent update.
Here is a code which I made for the test.
If I use “\startcolumns \stopcolumns”, then it has no problem.
But using “\startcolumnset[exam] … \stopcolumnset” produces error message
“return code 11”.
It loads “m-newcolumnset.tex” without problem.
What is the cause of this error?
Thank you for reading.
Best regards,
Dalyoung
\startuseMPgraphic{verticalrule0}
if CurrentColumn < NOfColumns :
draw rightboundary OverlayBox shifted (4mm,0);
setbounds currentpicture to OverlayBox enlarged 2.5mm;
fi;
\stopuseMPgraphic
\startuseMPgraphic{squareBox}
draw topboundary OverlayBox leftenlarged 1mm rightenlarged 1mm;
draw rightboundary OverlayBox shifted (1mm,0); %if CurrentColumn = 1:
shifted(-2mm,0) fi ;
draw leftboundary OverlayBox shifted (-1mm,0); %if CurrentColumn = 2:
shifted(2mm,0) fi ;
draw bottomboundary OverlayBox leftenlarged 1mm rightenlarged 1mm;
\stopuseMPgraphic
\defineoverlay
[headerBox]
[\useMPgraphic{squareBox}]
\startuseMPgraphic{verticalrule3}
draw rightboundary OverlayBox shifted (1mm,0); %if CurrentColumn = 1:
shifted(-2mm,0) fi ;
draw leftboundary OverlayBox shifted (-1mm,0); %if CurrentColumn = 2:
shifted(2mm,0) fi ;
draw bottomboundary OverlayBox leftenlarged 1mm rightenlarged 1mm;
\stopuseMPgraphic
\defineoverlay
[verticalrule]
[\useMPgraphic{verticalrule3}]
\definecolumnset
[exam]
[n=2,
background=verticalrule]
\setuplayout[width=19cm, height=26cm, header=1cm, footer=.5cm,backspace=1cm]
\setupheader[before=\vfil, after=\vfil]
\setupbackgrounds[header][text][frame=off, background=headerBox,
align=lohi]%topframe=
\setupbackgrounds[footer][text][frame=off, background=screen]
\define[3]\headTitle{\setupheadertexts[][\bf #1 \hfill #2 \hfill #3 \hfill
ID: \hskip 2cm Name: \hskip 2cm]}
\setupmathematics[autopunctuation=no, integral=nolimits]
\setupbodyfont[rm,10pt]
\setuppagenumbering[location=footer]
\setupcolors[state=start]
%\setupexternalfigure[directory={/Users/graph/Documents/figures,}]
\headTitle{2021. 12. 9.}{Set Theory}{Final Exam}
\usemodule[newcolumnsets]
\starttext
\startcolumns[rule=on,n=2,leftframe=on]
%\startcolumnset[exam]
\startitemize[n]
\item The first problem.
\vfill
\column
\item The second problem.
\vfill
\column
\item The third problem.
\vfill
\column
\stopitemize
%\stopcolumnset
\stopcolumns
\stoptext
error messages:
system > ConTeXt ver: 2021.11.30 19:49 LMTX fmt: 2021.12.1 int:
english/english
system >
system > 'cont-new.mkxl' loaded
open source > level 1, order 1, name
'/Users/graph/ConTeXtL/tex/texmf-context/tex/context/base/mkxl/cont-new.mkxl'
system > beware: some patches loaded from cont-new.mkiv
close source> level 1, order 1, name
'/Users/graph/ConTeXtL/tex/texmf-context/tex/context/base/mkxl/cont-new.mkxl'
system > files > jobname '/Users/graph/Library/Mobile
Documents/com~apple~CloudDocs/texMain/ColumnsetTest', input
'/Users/graph/Library/Mobile
Documents/com~apple~CloudDocs/texMain/ColumnsetTest.tex', result
'/Users/graph/Library/Mobile
Documents/com~apple~CloudDocs/texMain/ColumnsetTest'
fonts > latin modern fonts are not preloaded
languages > language 'en' is active
open source > level 1, order 2, name '/Users/graph/Library/Mobile
Documents/com~apple~CloudDocs/texMain/ColumnsetTest.tex'
fonts > preloading latin modern fonts (third stage)
fonts > 'fallback modern-designsize rm 10pt' is loaded
colors > 'rgb' color space is supported
colors > 'cmyk' color space is supported
modules > 'newcolumnsets' is loaded
open source > level 2, order 3, name
'/Users/graph/ConTeXtL/tex/texmf-context/tex/context/base/mkiv/m-newcolumnsets.mkiv'
close source> level 2, order 3, name
'/Users/graph/ConTeXtL/tex/texmf-context/tex/context/base/mkiv/m-newcolumnsets.mkiv'
mtx-context | fatal error: return code: 11
The terminal process "zsh '-c', 'export
PATH=~/ConTeXtL/tex/texmf-osx-64/bin:$PATH;mtxrun --autogenerate --script
context --autopdf --purge '/Users/graph/Library/Mobile
Documents/com~apple~CloudDocs/texMain/ColumnsetTest.tex''" terminated with exit
code: 1.
___
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] xml processing: if elseif else / switch case
Hi, I was wondering whether we have tests similar to or in context's xml processing. (And even in context more general...) I have found these doifelse tests, but elseif doesn't seem to exist. Is that correct? If yes, could that be added? Of course, you can always just nest doifelse-constructs, but that will become ugly quickly. Being able to specify multiple branches would be handy. Best, Denis ___ 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 ___
