Re: [NTG-context] Spacing problem around decimal point

[Jim via ntg-context]

Hi all,

I d/l'ed that binary, replaced the TeXlive version (which is dated March
11, even though I just updated texlive 5 minutes ago) and, lo and behold,
the PDF now looks like it should.

So from my point of view, that particular issue is resolved.

Sorry about your issues with Mac security.  I have this feeling that Apple
is slowly iterating towards a state where they sell you an expensive
computer with a beautiful acrylic and polished stainless steel stand and
ask you just to admire it, but don't touch it.  :-)

Jim

On Tue, Mar 28, 2023 at 14:56 (-0600), Gavin via ntg-context wrote:

> Hi Hans, Jim, Bruce, et.al.

> Han’s asked me

>> can you pick up a binary from:

>> https://dl.contextgarden.net/build/luametatex/work/

>> and test it?

> Maybe. I picked up the binary, but testing it is not quite as easy as it 
> might be due to the MacOS security settings. I’ll see what I can do, but I 
> know very little about Unix/Darwin.

> Since this appears to be an issue across multiple platforms, I’d welcome 
> anyone else checking the new binary. (Thanks, Günter!)

> Best,
> Gavin
> ___
> If your question is of interest to others as well, please add an entry to the 
> Wiki!

> maillist : ntg-context@ntg.nl / 
> https://www.ntg.nl/mailman/listinfo/ntg-context
> webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
> archive  : https://bitbucket.org/phg/context-mirror/commits/
> wiki : https://contextgarden.net
> ___
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

Re: [NTG-context] registered function call [1160]:...live/2023/texmf-dist/tex/context/base/mkiv/l-sandbox.lua:87: cannot open /.: Permission denied - Alpine Linux

[Hans Hagen via ntg-context]

On 3/28/2023 7:05 PM, Carlos via ntg-context wrote:

On Mon, Mar 27, 2023 at 03:43:47PM +0200, Hans Hagen via ntg-context wrote:

On 3/27/2023 3:31 PM, Carlos via ntg-context wrote:


mkiv lua stats  > loaded fonts: 4 files: latinmodern-math.otf, 
lmroman10-regular.otf, lucidabrightregular.ttf, lucidasansregular.ttf


i admit never having seen lucida ttf files (but when opentype ttf files are
used with an afm file present then no map files are needed at all because
we're in wide font mode and encidings are ignored)



I hadn't either.  But everything aligned and thought it was nice.

You're right that loading a map file is not needed, but If you're concerned 
about afm files then bring these files over to the working directory, and then 
mtxrun --generate the same

So yes. Even though the file was something like (intended originally to load 
the map file, correct?) but since the map file is no longer necessary then afm 
should suffice

\starttypescript [serif] [lucida] [texnansi]

\definefontsynonym[LucidaBrightDemiBold][texnansi-lucidabrightdemibold][encoding=texnansi]

\definefontsynonym[LucidaBrightDemiItalic][texnansi-lucidabrightdemiitalic][encoding=texnansi]

\definefontsynonym[LucidaBrightItalic][texnansi-lucidabrightitalic][encoding=texnansi]

\definefontsynonym[LucidaBrightRegular][texnansi-lucidabrightregular][encoding=texnansi]
\stoptypescript


these encodings only make sense with mkii (in which case the map file 
tells pdftex if a ttf or pfb file is used)


in mkiv encodings are ignored,  when a ttf/otf file is used no afm is 
read, and when a pfb fils is used the afm is used (ligature adn kerning 
info etc) but a wide font is assembled


(when a ttf is used the lucidaot typescript file can serve as example)

in mkxl we assume the otf files sold by TUG are used (recently the math 
font was updated)



and not with the file specification as in:


\starttypescript [mylucidaserif] % or mylucidasans
   \definefontsynonym[LucidaBrightRegular][file:LucidaBrightRegular]
   \definefontsynonym[LucidaBrightItalic] [file:LucidaBrightItalic]
   \definefontsynonym[LucidaBrightBold]   [file:LucidaBrightDemiBold]
\stoptypescript

and \setups[font:fallback:serif:sans] wouldn't be needed either

you'd end up with


in mkxl (lmtx)

\setupbodyfont[lucida]

will load open type definitions


mkiv lua stats  > loaded patterns: en::1, load time: 0.000
mkiv lua stats  > loaded fonts: 4 files: lucidabrightregular.otf, 
lucidasansregular.otf, latinmodern-math.otf, lmroman10-regular.otf


so why not use lucida math fonts?


mkiv lua stats  > font engine: otf 3.133, afm 1.513, tfm 1.000, 12 instances, 5 
shared in backend, 3 common vectors, 2 common hashes, load time 16.898 seconds



i assume that you don't get this 16 seconds load time each run


You're correct. That's why you recommended to use otf first .
even with type one fonts 17 sec load time for a few fonts is not okay, i 
expect more something like:


mkiv lua stats  > loaded fonts: 3 files: lucidabrightmathot.otf, 
lucidabrightot.otf, lucidasansot.otf
mkiv lua stats  > font engine: otf 3.133, afm 1.513, tfm 1.000, 14 
instances, 10 shared in backend, 6 common vectors, 4 common hashes, load 
time 0.161 seconds


(so 100 times less load time here)

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 / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

Re: [NTG-context] Spacing problem around decimal point

[Bruce Horrocks via ntg-context]

> On 28 Mar 2023, at 21:56, Gavin via ntg-context  wrote:
> 
> Hi Hans, Jim, Bruce, et.al.
> 
> Han’s asked me
> 
>> can you pick up a binary from:
>> 
>> https://dl.contextgarden.net/build/luametatex/work/
>> 
>> and test it?
> 
> Maybe. I picked up the binary, but testing it is not quite as easy as it 
> might be due to the MacOS security settings. I’ll see what I can do, but I 
> know very little about Unix/Darwin.
> 
> Since this appears to be an issue across multiple platforms, I’d welcome 
> anyone else checking the new binary. (Thanks, Günter!)

The x86_64-darwinlegacy from that download link version has fixed the problem 
on the Mac. Thank-you all involved.

\starttext
\startformula
v = \frac{1.32}{1.41} = 0.935
\stopformula
\stoptext

gives the attached.
—
Bruce Horrocks
Hampshire, UK


tt.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 / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

Re: [NTG-context] Spacing problem around decimal point

[Gavin via ntg-context]

Hi Hans, Jim, Bruce, et.al.

Han’s asked me

> can you pick up a binary from:
> 
> https://dl.contextgarden.net/build/luametatex/work/
> 
> and test it?

Maybe. I picked up the binary, but testing it is not quite as easy as it might 
be due to the MacOS security settings. I’ll see what I can do, but I know very 
little about Unix/Darwin.

Since this appears to be an issue across multiple platforms, I’d welcome anyone 
else checking the new binary. (Thanks, Günter!)

Best,
Gavin
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

Re: [NTG-context] Text editors

[Jan-Erik Hägglöf via ntg-context]

HI!

I’ve been using emacs and played around with configuration and finally found a 
good and very useful setup using LMTX installation.

Also I’ve customized with help from YAsnippet my own snippets så it goes very 
fast.

Below I have a setup on my macos that uses

- ConTeXt LMTX
- emacs-lisp setting in ~/.emacs.d/init.el
- customized setting for preview with Skim pdf reader
- YASnippet snippets on my dropbox cloudstoring so I can use it on several 
computers and has a macro syntax easy to learn.
- Bind-keys for fast build and preview on two pane "side by side editor and 
previewer" in "TeXshop style”.
  C-å Build document and C-c C-v for fast preview in Skim

Something to start playing with below to put in your init.el file


;; This is for getting preferred position and size of the emacs editor frame
(add-to-list 'default-frame-alist '(top . 25))
(add-to-list 'default-frame-alist '(left . 1))
(add-to-list 'default-frame-alist '(height . 56))
(add-to-list 'default-frame-alist '(width . 120))

;; For solving path issues install:  do M-x package-install RET 
exec-path-from-shel RETl
(when (memq window-system '(mac ns x))
  (exec-path-from-shell-initialize))

;; For configuring context
(add-to-list 'auto-mode-alist '("\\.tex\\'" . context-mode))
(eval-after-load 'tex '(add-to-list 'TeX-command-list
'("LuaMetaTeX"
"mtxrun --autogenerate --script context %t" TeX-run-command nil
(context-mode) :help "Run LuaMetaTeX")))

(defun myctx ()
"Saves the current buffer and runs ConTeXt, all with no prompts or further 
interaction."
  (interactive)
  (save-buffer)
  (TeX-command "LuaMetaTeX" 'TeX-master-file -1))
 ;; (add-hook 'ConTeXt-mode-hook 'turn-on-smartparens-strict-mode)
(add-hook 'ConTeXt-mode-hook (lambda () (define-key ConTeXt-mode-map (kbd 
"C-å") 'myctx)))

(setq TeX-output-view-style '("^pdf$" "." "open -a Skim.app %o"))

(setq TeX-view-program-list
  '(("Skim" "open -a Skim.app %o")
))

(add-hook 'ConTeXt-mode-hook (lambda () (setq TeX-view-program-selection 
'((output-pdf "Skim")

;; YASnippet config

(use-package yasnippet
  :config
  (setq yas-snippet-dirs '("~/Dropbox/filer/system/emacsgrejer/snippets"))
  (yas-global-mode 1)
  (setq yas/triggers-in-field t))

Hope this helps and gives some inspiration to get started if you choose emacs

/Jan-Erik



> 26 mars 2023 kl. 10:22 skrev Alexandre Christe via ntg-context 
> :
> 
> Dear ConTeXt users,
> 
> I'm wondering what kind of typesetting system / syntax highlighting / 
> completion you're using.
> 
> I've been using myself the simple_Context package for SublimeText which I 
> scavenged a while ago before it was made unavailable (I wanted to attach but 
> it's too big for the list). But it's sort of a dead-end.
> 
> Open to anything from vim/neovim to emacs or more exotic. Maybe it would be 
> nice to show the config. (And yes I've seen the Wiki page 
> https://wiki.contextgarden.net/Text_Editors but I've the feeling some content 
> is outdated.)
> 
> Thanks in advance,
> Alex
> ___
> If your question is of interest to others as well, please add an entry to the 
> Wiki!
> 
> maillist : ntg-context@ntg.nl / 
> https://www.ntg.nl/mailman/listinfo/ntg-context
> webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
> archive  : https://bitbucket.org/phg/context-mirror/commits/
> wiki : https://contextgarden.net
> ___

___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

Re: [NTG-context] registered function call [1160]:...live/2023/texmf-dist/tex/context/base/mkiv/l-sandbox.lua:87: cannot open /.: Permission denied - Alpine Linux

[Carlos via ntg-context]

On Mon, Mar 27, 2023 at 03:43:47PM +0200, Hans Hagen via ntg-context wrote:
> On 3/27/2023 3:31 PM, Carlos via ntg-context wrote:
> 
> > mkiv lua stats  > loaded fonts: 4 files: latinmodern-math.otf, 
> > lmroman10-regular.otf, lucidabrightregular.ttf, lucidasansregular.ttf
> 
> i admit never having seen lucida ttf files (but when opentype ttf files are
> used with an afm file present then no map files are needed at all because
> we're in wide font mode and encidings are ignored)
> 

I hadn't either.  But everything aligned and thought it was nice. 

You're right that loading a map file is not needed, but If you're concerned 
about afm files then bring these files over to the working directory, and then 
mtxrun --generate the same 

So yes. Even though the file was something like (intended originally to load 
the map file, correct?) but since the map file is no longer necessary then afm 
should suffice

\starttypescript [serif] [lucida] [texnansi]

\definefontsynonym[LucidaBrightDemiBold][texnansi-lucidabrightdemibold][encoding=texnansi]

\definefontsynonym[LucidaBrightDemiItalic][texnansi-lucidabrightdemiitalic][encoding=texnansi]

\definefontsynonym[LucidaBrightItalic][texnansi-lucidabrightitalic][encoding=texnansi]

\definefontsynonym[LucidaBrightRegular][texnansi-lucidabrightregular][encoding=texnansi]
\stoptypescript

\starttypescript [sans] [lucida] [texnansi]

\definefontsynonym[LucidaSansDemiBold][texnansi-lucidasansdemibold][encoding=texnansi]

\definefontsynonym[LucidaSansDemiOblique][texnansi-lucidasansdemioblique][encoding=texnansi]

\definefontsynonym[LucidaSansOblique][texnansi-lucidasansoblique][encoding=texnansi]

\definefontsynonym[LucidaSansRegular][texnansi-lucidasansregular][encoding=texnansi]
\stoptypescript

\starttypescript [mono] [lucida] [texnansi]

\definefontsynonym[LucidaSansTypewriterBold][texnansi-lucidatypewriterbold][encoding=texnansi]

\definefontsynonym[LucidaSansTypewriterBoldOblique][texnansi-lucidayypewriterboldoblique][encoding=texnansi]

\definefontsynonym[LucidaSansTypewriterOblique][texnansi-lucidatypewriteroblique][encoding=texnansi]

\definefontsynonym[LucidaSansTypewriterRegular][texnansi-lucidatypewriterregular][encoding=texnansi]
\stoptypescript

\starttypescript [serif] [lucida] [name]
\usetypescript[serif][fallback]
\definefontsynonym[Serif]  [LucidaBrightRegular]
\definefontsynonym[SerifBold]  [LucidaBrightDemi]
\definefontsynonym[SerifItalic][LucidaBrightItalic]
\definefontsynonym[SerifBoldItalic][LucidaBrightDemiItalic]
\stoptypescript

\starttypescript [sans] [lucida] [name]
\usetypescript[sans][fallback]
\definefontsynonym[Sans][LucidaSansRegular]
\definefontsynonym[SansItalic]  [LucidaSansOblique]
\definefontsynonym[SansBold][LucidaSansDemiBold]
\definefontsynonym[SansBoldItalic]  [LucidaSansDemiOblique]
\stoptypescript

\starttypescript [mono] [lucida] [name]
\usetypescript[mono][fallback]
\definefontsynonym[Mono]
[LucidaSansTypewriterRegular]
\definefontsynonym[MonoItalic]  [LucidaSansTypewriterOblique]
\definefontsynonym[MonoBold][LucidaSansTypewriterBold]
\definefontsynonym[MonoBoldItalic]  
[LucidaSansTypewriterBoldOblique]
\stoptypescript

\starttypescript [Lucida] 
\definetypeface[MyLucida][rm][serif][lucida][default][encoding=texnansi]
\definetypeface[MyLucida][ss][sans][lucida][default][encoding=texnansi]
\definetypeface[MyLucida][tt][mono][lucida][default][encoding=texnansi]
\stoptypescript



and not with the file specification as in:


\starttypescript [mylucidaserif] % or mylucidasans
  \definefontsynonym[LucidaBrightRegular][file:LucidaBrightRegular]
  \definefontsynonym[LucidaBrightItalic] [file:LucidaBrightItalic]
  \definefontsynonym[LucidaBrightBold]   [file:LucidaBrightDemiBold]
\stoptypescript

and \setups[font:fallback:serif:sans] wouldn't be needed either 

you'd end up with  


mkiv lua stats  > loaded patterns: en::1, load time: 0.000
mkiv lua stats  > loaded fonts: 4 files: lucidabrightregular.otf, 
lucidasansregular.otf, latinmodern-math.otf, lmroman10-regular.otf
mkiv lua stats  > font engine: otf 3.133, afm 1.513, tfm 1.000, 12 instances, 5 
shared in backend, 3 common vectors, 2 common hashes, load time 0.306 seconds 
mkiv lua stats  > math tweaking time: 0.055 seconds, 12 math goodie tables


> > mkiv lua stats  > font engine: otf 3.133, afm 1.513, tfm 1.000, 12 
> > instances, 5 shared in backend, 3 common vectors, 2 common hashes, load 
> > time 16.898 seconds
> > mkiv lua stats  > math tweaking time: 0.102 seconds, 12 math goodie tables
> > mkiv lua stats  > font embedding time: 0.004 seconds, 2 fonts
> 
> i assume that you don't get this 16 seconds load time each run

Re: [NTG-context] Text editors

[Alain Delmotte via ntg-context]

Hi!

Le 26/03/2023 à 10:39, jbf via ntg-context a écrit :


Every user has his or her own preferred test editor. Over 
years I have used Emacs for just about everything except 
the kitchen sink, but not, as it happens, for ConTeXt.


For what it's worth here is what I use:

(1) TeXworks. All one has to do is indicate the correct 
path to ConText in the setup for this program, depending 
on your OS and where you have installed it, e.g. 
home/yourname/bin/context/tex/texmf-linux-64/bin if you 
are using Linux and have installed it in \bin. Then choose 
ConTeXt (LuaTeX) as the processing tool.


(2) But to make things a lot easier, I also use Federico's 
text expander Espanso 
https://espanso.org 
. This just saves so much time, 
especially for so many \start...\stop sequences.  For 
example, in espanso I might have:


You can do the same inside TeXworks. There are completion 
files in the folder 
C:\Users\yourname\AppData\Roaming\TUG\TeXworks\completion.


It is not yet completed for Context, but it should not be 
difficult to do that.


But thanks Julian, this is an interesting information

Alain


Julian

On 26/3/23 19:22, Alexandre Christe via ntg-context wrote:

Dear ConTeXt users,

I'm wondering what kind of typesetting system / syntax 
highlighting / completion you're using.


I've been using myself the simple_Context package for 
SublimeText which I scavenged a while ago before it was 
made unavailable (I wanted to attach but it's too big for 
the list). But it's sort of a dead-end.


Open to anything from vim/neovim to emacs or more exotic. 
Maybe it would be nice to show the config. (And yes I've 
seen the Wiki page 
https://wiki.contextgarden.net/Text_Editorsbut I've the 
feeling some content is outdated.)


Thanks in advance,
Alex

___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist :ntg-context@ntg.nl  /https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  :https://www.pragma-ade.nl  /http://context.aanhet.net
archive  :https://bitbucket.org/phg/context-mirror/commits/
wiki :https://contextgarden.net
___


___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist :ntg-context@ntg.nl  /https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  :https://www.pragma-ade.nl  /http://context.aanhet.net
archive  :https://bitbucket.org/phg/context-mirror/commits/
wiki :https://contextgarden.net
___
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

Re: [NTG-context] xtable - what might prevent splitting?

[Wolfgang Schuster via ntg-context]

jbf schrieb am 28.03.2023 um 10:43:


Got it! But I would not have picked that up from reading 
http://www.pragma-ade.nl/general/manuals/xtables-mkiv.pdf, which was 
my guide for this particular exercise. It certainly says 
\placetable[here,split] but there is no mention of the \start...stop 
version of that.


Anyway, I now understand what I need to do, so thank you.

Julian

On 28/3/23 19:37, Wolfgang Schuster wrote:

\startplacetable [location={here,split}]


When you use the old \place... commands you have to write

\placetable [here,split} {...} {...}

BTW: \placetable expects either {...} or \bgoup ...\egroup as second 
mandatory argument, in your case you has been lucky because \startxtable 
has an \bgroup in its definition but you shouldn't rely on this.


Wolfgang

___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

Re: [NTG-context] xtable - what might prevent splitting?

[jbf via ntg-context]

Got it! But I would not have picked that up from reading 
http://www.pragma-ade.nl/general/manuals/xtables-mkiv.pdf, which was my 
guide for this particular exercise. It certainly says 
\placetable[here,split] but there is no mention of the \start...stop 
version of that.


Anyway, I now understand what I need to do, so thank you.

Julian

On 28/3/23 19:37, Wolfgang Schuster wrote:

\startplacetable [location={here,split}]___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

Re: [NTG-context] xtable - what might prevent splitting?

[Wolfgang Schuster via ntg-context]

jbf via ntg-context schrieb am 28.03.2023 um 10:27:


I cannot understand why my xtable setup does not split to the next 
page. As far as I can see I have it set up correctly... though 
obviously not! What might be wrong? Below is a sample. In the real 
case the number of rows would demand a second page.


\setupxtable[width=4cm,option={stretch,width}]

\setupxtable[split=yes]

\starttext

\placetable[here]{}

\startxtable

\startxrow

\startxcell cell one \stopxcell

\startxcell cell two \stopxcell

\startxcell cell three\stopxcell

\stopxrow

... and so on and so forth for twenty or so rows, but certainly enough 
to require a second page


\stopxtable

\stoptext



You have to pass the "split" keyword to the float command, e.g.

\startplacetable [location={here,split}]
    \startxtable
    ...
    \stopxtable
\stopplacetable

Wolfgang

___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

[NTG-context] xtable - what might prevent splitting?

[jbf via ntg-context]

I cannot understand why my xtable setup does not split to the next page. 
As far as I can see I have it set up correctly... though obviously not! 
What might be wrong? Below is a sample. In the real case the number of 
rows would demand a second page.


\setupxtable[width=4cm,option={stretch,width}]

\setupxtable[split=yes]

\starttext

\placetable[here]{}

\startxtable

\startxrow

\startxcell cell one \stopxcell

\startxcell cell two \stopxcell

\startxcell cell three\stopxcell

\stopxrow

... and so on and so forth for twenty or so rows, but certainly enough 
to require a second page


\stopxtable

\stoptext

Julian
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___