[NTG-context] regular online meet-up
You’re invited to our regular online meet-up, this upcoming Wednesday, March 13th, 19:00 CET (UTC+1) at https://lecture.senfcall.de/hen-rbr-rku-oke (same, but shorter: https://u.mtxrun.eu/ctxmtg) ConTeXt users of all levels are welcome! Do you have a subject that you’d like to talk about? Looking forward to seeing you, Hraban (Same blurb as always:) [Howto] * No special software installation required; most modern browsers should work (WebRTC required). * Open the URL above, accept the privacy statement, * enter your name, * click "join" (or "start" if you’re the first), * click "with microphone", allow your browser to access it, check the audio. * Your microphone is muted if you join. Activate microphone and/or camera with the buttons at the bottom. * Minimize the default presentation with the "screen" button, bottom right. * If you’d like to share your screen or upload a file, you can make yourself the presenter: Click on your user name, change the setting, then you’ll see the "screen sharing" button beside the camera button; also there’s now "manage presentations" behind the "plus" button. Beware there is only one presenter at a time, so don’t kill someone else’s presentation. [Technical hints] * Sound is usually better if you use a headset (less noise for everyone). * Connection problems are mostly due to low bandwidth or high latency on your side, e.g. with mobile connections. * Sometimes leaving and re-entering helps. * If audio/video doesn’t work for you, you can still use the text chat. * Screen sharing needs a lot of bandwidth. * BigBlueButton documentation applies: https://bigbluebutton.org/teachers/tutorials/ [Netiquette] * Please use a name that we recognize from here. Some feel uncomfortable with anonymous lurkers. * Mute your microphone while you’re not talking. * It’s nice to show your face at least when you join. * If there are connection problems, stop camera sharing. * The room is set to “everyone’s a moderator“, I trust you... ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Document metadata after context --extra=select script
Greetings,
I set a document's title with the following code:
\expanded
{\setupmetadata
[title={Document Title}]}
I then create a derivative document with a selection of pages using
ConTeXt's select script.
context --extra=select [options] list-of-files
The metadata title of this document is "mtx-context-select." While I can
use any number of utilities to manually tweak the title, is there a ConTeXt
way to preserve or assign metadata values when using these scripts?
--
With kind regards,
Michael
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___
[NTG-context] Re: Japanese
Emanuel,
Your sample seems to work fine on CTX MKIV 2024.01.24 version , as far
as I see the final PDF output. And ConTeXt doesn't complain, even in the
log !
Best//JP
Le 10/03/2024 à 17:43, Emanuel Han via ntg-context a écrit :
Hi all,
I added
https://wiki.contextgarden.net/Chinese_Japanese_and_Korean#Meeting_the_JIS_X_4051_Requirements_for_Japanese_Text_Layout
with attached working example code and to-do list.
Thanks for any contributions!
The working example code is still a work in progress. Its text layout
output meets already some of the requirements (see comments in the
code). Among the ones to still be implemented are:
*
solid setting (no extra spacing between characters)
https://www.w3.org/TR/jlreq/#fig1_8 if no requirement for
line-adjustment https://www.w3.org/TR/jlreq/#term.line-adjustment
*
aligning of the lines to the Kihon-hanmen (optimizing the code
below in this regard)
*
positioning and realm of headings
https://www.w3.org/TR/jlreq/#fig3_1_9
https://www.w3.org/TR/jlreq/#fig3_1_15 et al, and
https://www.w3.org/TR/jlreq/#fig3_1_4
*
positioning of yokugo-ruby https://www.w3.org/TR/jlreq/#fig2_3_24
*
inline cutting note (warichu) https://www.w3.org/TR/jlreq/#fig2_4_1
*
emphasis with sesame dot or bullet
*
itemization https://www.w3.org/TR/jlreq/#fig2_5_6
*
indenting of quotation paragraphs
https://www.w3.org/TR/jlreq/#fig2_5_7
*
tab setting https://www.w3.org/TR/jlreq/#fig2_6_1
*
furiwake https://www.w3.org/TR/jlreq/#fig2_7_2
*
jidori https://www.w3.org/TR/jlreq/#fig2_7_4
*
math https://www.w3.org/TR/jlreq/#fig2_7_6 and
https://www.w3.org/TR/jlreq/#fig2_7_62
*
tategaki (writing vertically)
Best regards
Emanuel
On März 2 2024, at 7:00 pm, Wolfgang Schuster
wrote:
Emanuel Han schrieb am 01.03.2024 um 16:23:
Dear Wolfgang,
thank you for your valuable remarks. I integrated them, see
corrected attached example.
Yes, correct layout examples exist. They're all showing
vertical writing, but the rules and principles are exactly the
same for horizontal writing.
*
position of the headers and footers:
https://www.w3.org/TR/jlreq/#fig1_30
See my attached gongitsune.tex example how you can squeeze text in
a very narrow header/footer.
*
aligning lines to the text box:
https://www.w3.org/TR/jlreq/#fig1_3
You can use the lines key for \setuplayout to let ConTeXt
calculate the necessary value for the text height.
*
protrusion of ruby: https://www.w3.org/TR/jlreq/#fig_ad1_6
You're getting this for free because ruby text doesn't take up
vertical space, in case vertical text is working it would now
stick into the margins as expected.
\starttext
\ruledhbox{a \ruby{x}{y} b}
\stoptext
*
In my previous mail, I wrote wrong amounts of lines. They
should be 46 lines on one page, while the actual example
doesn't show the 46th line.
It would be important to identify the reason why only 24
characters are used to create a line when 25 could be used.
Then we can develop a method to turn that mechanism off or
circumvent it.
Quotation from https://www.w3.org/TR/jlreq:
/In principle, when composing a line with //ideographic
(cl-19) //, //hiragana
(cl-15) // and //katakana
(cl-16) // characters, no
extra spacing appears between their //character frame
//. This is
called solid setting (see //Figure 5
//)./
1. ConTeXt has a mechanism to typeset Japanese texts.
2. There are flaws in the output it produces but this nothing
which can't be fixed.
3. To fix the problems someone has to be passionate to fix them
and we're willing to help here.
As you can see in my second example file japanese.tex there is a
font feature to create half sized parentheses etc. which isn't
supported yet by ConTeXt's mechanism for japanese and in case your
willing to improve it this should be taken care of as well.
Wolfgang
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist :ntg-context@ntg.nl
/https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage :https://www.pragma-ade.nl /https://context.aanhet.net (mirror)
archive :https://github.com/contextgarden/context
wiki :https://wiki.contextgarden.net
[NTG-context] Re: How can I do this?
Hi Hans and Hraban,
Thank you both for your remarks: indeed I am aware of the commands \m{} and
\dm{} in ConTeXt, but for my work with math stuff I use the usual dollar signs
for inline maths, since in this way it is easier for me to read the source on
the one hand, and and on the hand when exchanging parts of a file with people
using Plain TeX or LaTeX, it is more standard.
Best regards: Otared
> On 10 Mar 2024, at 10:16, Hans Hagen via ntg-context
> wrote:
>
> On 3/8/2024 6:36 PM, Henning Hraban Ramm wrote:
>> Am 08.03.24 um 17:56 schrieb Otared Kavian:
>>> Hi Ursula,
>>>
>>> The reason for which you did not get the expected result is that you have «
>>> } » missing in your file, that is the closing brace after your italic
>>> command
>>> « {\it » at the end of your document.
>>> Moreover you did not have a \stoptext in your file, and a math command « \m
>>> » was not written correctly. Talking of math, I personnaly prefer to
>>> enclose in-line math between dollar signs $, that is writing « $\exists x
>>> \in H$ » instead of « \m{\exists x \in H} ».
>> Well, better stay with the modern ConTeXt approach of \m{}.
> for regular inline math we just use \im{...} (which has an \dm{...} companion
> with displaystyle
>
> 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://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
> webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
> archive : https://github.com/contextgarden/context
> wiki : https://wiki.contextgarden.net
> ___
Otared Kavian
e-mail: ota...@gmail.com
Phone: +33 6 88 26 70 95
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___
[NTG-context] Re: \em issue in MkXL (2024.03.05 11:26)
On 3/10/2024 11:48 AM, Wolfgang Schuster wrote:
Hans Hagen via ntg-context schrieb am 10.03.2024 um 10:46:
On 3/10/2024 9:32 AM, Pablo Rodriguez via ntg-context wrote:
On 3/9/24 16:04, Wolfgang Schuster wrote:
Pablo Rodriguez via ntg-context schrieb am 08.03.2024 um 19:39:
[...]
\enableexperiments[fonts.compact]
Which seeems weird to me. Or at least, I thought I read that Hans
enabled it by default in LMTX.
AFAIR Hans uses the setting in his own documents.
I have been using it for a while.
I hope the issue with \glyphslant might be fixed to enable it again.
Then my question is whether this was caused by simply enabling compact
fonts or by doing it twice.
The results happen when you use compact mode and is a result of
\glyphslant which keeps the value of the italic style even when you
switch back to the upright style.
Many thanks for your explaination,
using the low level commands
\glyphscale
\glyphxscale
\glyphyscale
\glyphslant
\glyphweight
directly can have side efects when at an outer level these are also
set, so you need to accumulate, like
\starttext
test {\glyphscale 2000 test \glyphscale \numericscaled1.2\glyphscale
test} test
test {\glyphslant 500 test \glyphslant \numericscaled2.0\glyphslant
test} test
test {\glyphweight 100 test \glyphweight\numericscaled2.0\glyphweight
test} test
\stoptext
The problem is that compact mode uses them to apply the slanted feature
without any manual use of the commands from a user.
\enableexperiments[fonts.compact]
\definefontfamily[mainface][rm][TeX Gyre Termes]
[it={style:regular, features:{default,slanted}},
sl={style:regular, features:{default,slanted}}]
\setupbodyfont[mainface]
\starttext
\startstyle[style=italic]normal {\em emphasized} normal\stopstyle
\stoptext
The only way to mask the effect is to create a new fontfeature with the
minimum slant value and apply it to the upright style.
\definefontfeature [unslanted] [slant=0.001]
\definefontfamily[mainface][rm][TeX Gyre Termes]
[features={default,unslanted},
it={style:regular, features:{default,slanted}},
sl={style:regular, features:{default,slanted}}]
ok, i'll fix that (build is down so no update)
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://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___
[NTG-context] Re: Japanese
Hi all,
I added
https://wiki.contextgarden.net/Chinese_Japanese_and_Korean#Meeting_the_JIS_X_4051_Requirements_for_Japanese_Text_Layout
with attached working example code and to-do list.
Thanks for any contributions!
The working example code is still a work in progress. Its text layout output
meets already some of the requirements (see comments in the code). Among the
ones to still be implemented are:
solid setting (no extra spacing between characters)
https://www.w3.org/TR/jlreq/#fig1_8 if no requirement for line-adjustment
https://www.w3.org/TR/jlreq/#term.line-adjustment
aligning of the lines to the Kihon-hanmen (optimizing the code below in this
regard)
positioning and realm of headings https://www.w3.org/TR/jlreq/#fig3_1_9
https://www.w3.org/TR/jlreq/#fig3_1_15 et al, and
https://www.w3.org/TR/jlreq/#fig3_1_4
positioning of yokugo-ruby https://www.w3.org/TR/jlreq/#fig2_3_24
inline cutting note (warichu) https://www.w3.org/TR/jlreq/#fig2_4_1
emphasis with sesame dot or bullet
itemization https://www.w3.org/TR/jlreq/#fig2_5_6
indenting of quotation paragraphs https://www.w3.org/TR/jlreq/#fig2_5_7
tab setting https://www.w3.org/TR/jlreq/#fig2_6_1
furiwake https://www.w3.org/TR/jlreq/#fig2_7_2
jidori https://www.w3.org/TR/jlreq/#fig2_7_4
math https://www.w3.org/TR/jlreq/#fig2_7_6 and
https://www.w3.org/TR/jlreq/#fig2_7_62
tategaki (writing vertically)
Best regards
Emanuel
On März 2 2024, at 7:00 pm, Wolfgang Schuster
wrote:
> Emanuel Han schrieb am 01.03.2024 um 16:23:
> >
> > Dear Wolfgang,
> > thank you for your valuable remarks. I integrated them, see corrected
> > attached example.
> > Yes, correct layout examples exist. They're all showing vertical writing,
> > but the rules and principles are exactly the same for horizontal writing.
> > position of the headers and footers: https://www.w3.org/TR/jlreq/#fig1_30
> See my attached gongitsune.tex example how you can squeeze text in a very
> narrow header/footer.
> > aligning lines to the text box: https://www.w3.org/TR/jlreq/#fig1_3
> You can use the lines key for \setuplayout to let ConTeXt calculate the
> necessary value for the text height.
> > protrusion of ruby: https://www.w3.org/TR/jlreq/#fig_ad1_6
> You're getting this for free because ruby text doesn't take up vertical
> space, in case vertical text is working it would now stick into the margins
> as expected.
> \starttext
> \ruledhbox{a \ruby{x}{y} b}
> \stoptext
>
>
> >
> > In my previous mail, I wrote wrong amounts of lines. They should be 46
> > lines on one page, while the actual example doesn't show the 46th line.
> > It would be important to identify the reason why only 24 characters are
> > used to create a line when 25 could be used. Then we can develop a method
> > to turn that mechanism off or circumvent it.
> > Quotation from https://www.w3.org/TR/jlreq:
> > In principle, when composing a line with ideographic (cl-19)
> > (https://www.w3.org/TR/jlreq/#cl-19), hiragana (cl-15)
> > (https://www.w3.org/TR/jlreq/#cl-15) and katakana (cl-16)
> > (https://www.w3.org/TR/jlreq/#cl-16) characters, no extra spacing appears
> > between their character frame
> > (https://www.w3.org/TR/jlreq/#term.character-frame). This is called solid
> > setting (see Figure 5 (https://www.w3.org/TR/jlreq/#fig1_8)).
>
>
> 1. ConTeXt has a mechanism to typeset Japanese texts.
> 2. There are flaws in the output it produces but this nothing which can't be
> fixed.
> 3. To fix the problems someone has to be passionate to fix them and we're
> willing to help here.
> As you can see in my second example file japanese.tex there is a font feature
> to create half sized parentheses etc. which isn't supported yet by ConTeXt's
> mechanism for japanese and in case your willing to improve it this should be
> taken care of as well.
> Wolfgang
japanese_mwe.tex
Description: TeX document
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___
[NTG-context] Re: \em issue in MkXL (2024.03.05 11:26)
Hans Hagen via ntg-context schrieb am 10.03.2024 um 10:46:
On 3/10/2024 9:32 AM, Pablo Rodriguez via ntg-context wrote:
On 3/9/24 16:04, Wolfgang Schuster wrote:
Pablo Rodriguez via ntg-context schrieb am 08.03.2024 um 19:39:
[...]
\enableexperiments[fonts.compact]
Which seeems weird to me. Or at least, I thought I read that Hans
enabled it by default in LMTX.
AFAIR Hans uses the setting in his own documents.
I have been using it for a while.
I hope the issue with \glyphslant might be fixed to enable it again.
Then my question is whether this was caused by simply enabling compact
fonts or by doing it twice.
The results happen when you use compact mode and is a result of
\glyphslant which keeps the value of the italic style even when you
switch back to the upright style.
Many thanks for your explaination,
using the low level commands
\glyphscale
\glyphxscale
\glyphyscale
\glyphslant
\glyphweight
directly can have side efects when at an outer level these are also set,
so you need to accumulate, like
\starttext
test {\glyphscale 2000 test \glyphscale \numericscaled1.2\glyphscale
test} test
test {\glyphslant 500 test \glyphslant \numericscaled2.0\glyphslant
test} test
test {\glyphweight 100 test \glyphweight\numericscaled2.0\glyphweight
test} test
\stoptext
The problem is that compact mode uses them to apply the slanted feature
without any manual use of the commands from a user.
\enableexperiments[fonts.compact]
\definefontfamily[mainface][rm][TeX Gyre Termes]
[it={style:regular, features:{default,slanted}},
sl={style:regular, features:{default,slanted}}]
\setupbodyfont[mainface]
\starttext
\startstyle[style=italic]normal {\em emphasized} normal\stopstyle
\stoptext
The only way to mask the effect is to create a new fontfeature with the
minimum slant value and apply it to the upright style.
\definefontfeature [unslanted] [slant=0.001]
\definefontfamily[mainface][rm][TeX Gyre Termes]
[features={default,unslanted},
it={style:regular, features:{default,slanted}},
sl={style:regular, features:{default,slanted}}]
Wolfgang
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___
[NTG-context] Re: \em issue in MkXL (2024.03.05 11:26)
On 3/10/24 10:46, Hans Hagen via ntg-context wrote: > [...] > using the low level commands > > \glyphscale > \glyphxscale > \glyphyscale > \glyphslant > \glyphweight > > directly can have side efects when at an outer level these are also set, > so you need to accumulate, like > [...] > which you will now wikify... Many thanks for your reply, Hans. I will wikify this, once I figure out where it can fit in the wiki (in due time, since ConTeXt is more and more complex for me lately and my free time is less and less these days). I only used \enableexperiments[fonts.compact] and then \em. I thought when I (mis)read your messages that compact fonts is the way to go in LMTX. This was the reason I enabled them (the sooner we test new features today, the less issues will be faced with them tomorrow). \glyphslant came into the conversation after experiencing an issue triggered by enabling compact fonts. Sorry for being explicitly verbose, but I intend to have the \em behavior also fixed in compact fonts. Many thanks for your help, Pablo ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: \em issue in MkXL (2024.03.05 11:26)
On 3/10/2024 9:32 AM, Pablo Rodriguez via ntg-context wrote:
On 3/9/24 16:04, Wolfgang Schuster wrote:
Pablo Rodriguez via ntg-context schrieb am 08.03.2024 um 19:39:
[...]
\enableexperiments[fonts.compact]
Which seeems weird to me. Or at least, I thought I read that Hans
enabled it by default in LMTX.
AFAIR Hans uses the setting in his own documents.
I have been using it for a while.
I hope the issue with \glyphslant might be fixed to enable it again.
Then my question is whether this was caused by simply enabling compact
fonts or by doing it twice.
The results happen when you use compact mode and is a result of
\glyphslant which keeps the value of the italic style even when you
switch back to the upright style.
Many thanks for your explaination,
using the low level commands
\glyphscale
\glyphxscale
\glyphyscale
\glyphslant
\glyphweight
directly can have side efects when at an outer level these are also set,
so you need to accumulate, like
\starttext
test {\glyphscale 2000 test \glyphscale \numericscaled1.2\glyphscale
test} test
test {\glyphslant 500 test \glyphslant \numericscaled2.0\glyphslant
test} test
test {\glyphweight 100 test \glyphweight\numericscaled2.0\glyphweight
test} test
\stoptext
which you will now wikify ...
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://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___
[NTG-context] Re: How can I do this?
On 3/8/2024 6:36 PM, Henning Hraban Ramm wrote:
Am 08.03.24 um 17:56 schrieb Otared Kavian:
Hi Ursula,
The reason for which you did not get the expected result is that you
have « } » missing in your file, that is the closing brace after your
italic command
« {\it » at the end of your document.
Moreover you did not have a \stoptext in your file, and a math command
« \m » was not written correctly. Talking of math, I personnaly prefer
to enclose in-line math between dollar signs $, that is writing «
$\exists x \in H$ » instead of « \m{\exists x \in H} ».
Well, better stay with the modern ConTeXt approach of \m{}.
for regular inline math we just use \im{...} (which has an \dm{...}
companion with displaystyle
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://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___
[NTG-context] Re: \em issue in MkXL (2024.03.05 11:26)
On 3/9/24 16:04, Wolfgang Schuster wrote: > Pablo Rodriguez via ntg-context schrieb am 08.03.2024 um 19:39: >> [...] >>\enableexperiments[fonts.compact] >> >> Which seeems weird to me. Or at least, I thought I read that Hans >> enabled it by default in LMTX. > > AFAIR Hans uses the setting in his own documents. I have been using it for a while. I hope the issue with \glyphslant might be fixed to enable it again. >> Then my question is whether this was caused by simply enabling compact >> fonts or by doing it twice. > > The results happen when you use compact mode and is a result of > \glyphslant which keeps the value of the italic style even when you > switch back to the upright style. Many thanks for your explaination, Pablo ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
