[NTG-context] Cron /var/www/aanhet.net/context/bin/cron/context-mirror
receiving incremental file list ./ ctan.lsr document-2.htm download-1.htm download-2.htm logo-ade.png logo-cts.png logo-pod.png rss.xml show-fil.pdf context/latest/ context/latest/cont-mpd.zip context/latest/cont-ppc.zip context/latest/cont-sci.zip context/latest/cont-tmf.zip context/latest/cont-tst.7z context/latest/cont-tst.tar.xz context/latest/cont-tst.zip sent 101,532 bytes received 20,452,723 bytes 3,737,137.27 bytes/sec total size is 449,096,381 speedup is 21.85 Running archiver: New dir: /var/www/aanhet.net/context//htdocs/archives/context-2022-12-22.23 172178703 /var/www/aanhet.net/context//htdocs/archives/context-2022-12-22.23/latest 126745317 /var/www/aanhet.net/context//htdocs/archives/context-2022-12-22.23/current 18956262 /var/www/aanhet.net/context//htdocs/archives/context-2022-12-22.23/alpha 126707516 /var/www/aanhet.net/context//htdocs/archives/context-2022-12-22.23/beta 444591894 /var/www/aanhet.net/context//htdocs/archives/context-2022-12-22.23 444591894 total ___ 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] xtables regression with LMTX 2022-12-21
On 12/22/2022 10:19 PM, Pablo Rodriguez via ntg-context wrote: On 12/22/22 21:14, Rik Kabel via ntg-context wrote: With the latest (2022-12-21) LMTX I see a regression in xtables. The following code: […] The problem appears to be LMTX-specific. (I did not save 2022-12-15 for testing, but did not see the problem with that version.) Hi Rik, I can confirm that the regression only arises in LMTX and in current latest. With LMTX from 2022.12.15 18:12, the xtable is fine. It seems to be related to the replacement of \newdimen and \newcount with \newdimension and \newinteger (which Hans mentioned in https://mailman.ntg.nl/pipermail/ntg-context/2022/107452.html). Indeed, one has to be careful with aliasing them (frozen values). There might be a few more places that need a fix. 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] xtables regression with LMTX 2022-12-21
On 12/22/2022 9:14 PM, Rik Kabel via ntg-context wrote:
With the latest (2022-12-21) LMTX I see a regression in xtables. The
following code:
\starttext
\startxtable
\startxrow
\startxcell
This is a line of text.
\stopxcell
\startxcell
\contextversion
\stopxcell
\stopxrow
\stopxtable
\stoptext
produces this with 2022-12-09:
and this with 2022-12-21:
The problem appears to be LMTX-specific. (I did not save 2022-12-15 for
testing, but did not see the problem with that version.)
thanks for noticing, i uploaded a new lmtx
as a reward i'll reveal a new mechanism:
\useMPlibrary[dum]
\definetextdisplay[steppedbystep][before={\blank[halfline]}]
\starttext \showmakeup[line]
\dostepwiserecurse{10}{25}{1}{
\par
\starttextdisplay
\externalfigure[dummydummy][height=#1mm,text=no]%
\stoptextdisplay
\par
\starttextdisplay[before=\blank,after=\blank] % factor=.5
\externalfigure[dummydummy][height=#1mm,text=no]%
\stoptextdisplay
\par
\startsteppedbystep
\externalfigure[dummydummy][height=#1mm,text=no]%
\stopsteppedbystep
\par
\page
}
\stoptext
this uses a new boxtype, compare
\ruledvbox{test\par test}
\ruledvtop{test\par test}
\ruleddbox{test\par test}
and guess what happens. Still in exploration mode.
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] xtables regression with LMTX 2022-12-21
On 12/22/22 21:14, Rik Kabel via ntg-context wrote: > With the latest (2022-12-21) LMTX I see a regression in xtables. The > following code: > […] > The problem appears to be LMTX-specific. (I did not save 2022-12-15 for > testing, but did not see the problem with that version.) Hi Rik, I can confirm that the regression only arises in LMTX and in current latest. With LMTX from 2022.12.15 18:12, the xtable is fine. It seems to be related to the replacement of \newdimen and \newcount with \newdimension and \newinteger (which Hans mentioned in https://mailman.ntg.nl/pipermail/ntg-context/2022/107452.html). Just in case it helps, Pablo ___ 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] xtables regression with LMTX 2022-12-21
With the latest (2022-12-21) LMTX I see a regression in xtables. The following code: \starttext \startxtable \startxrow \startxcell This is a line of text. \stopxcell \startxcell \contextversion \stopxcell \stopxrow \stopxtable \stoptext produces this with 2022-12-09: and this with 2022-12-21: The problem appears to be LMTX-specific. (I did not save 2022-12-15 for testing, but did not see the problem with that version.) -- Rik ___ 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] LMTX: request for \tracinglostchars=3
Hans Hagen via ntg-context writes: >> LMTX only seems to support =0 (ignore) and =1 (report). Making these >> a fatal error (with exit status != 0) would be useful for automated >> typesetting, as missing characters easily can get lost in the logs, >> and then symbols are missing unnoticed in the output. > > Will never be default, you can play with: > > % \checkmissingcharacters > % \removemissingcharacters > % \replacemissingcharacters > % \handlemissingcharacters > >> (However, \tracinglostchars=3 also doesn't seem to work with >> LuaTeX+MKIV, probably because there is code to fallback to other fonts?) > and if you want to quit: > > \enabledirectives[logs.errors=missing characters] Ok, this is useful. I looked around, but I couldn't find a similar feature for when a font is not found? cu, -- Leah Neukirchenhttps://leahneukirchen.org/ ___ 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] Unconnected \mathboxanchored produces unexpected results
Hi Hans, > can you try the latest binary fron the farm (remake th eformat) I haven’t done that before, so I don’t know. I’d certainly need a link, and I might need some guidance if I run into trouble. I’m happy to try. 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] LMTX: request for \tracinglostchars=3
On 12/22/2022 4:23 PM, Leah Neukirchen via ntg-context wrote: Hi, since TeX Live 2021 (TeX 3.141592653), there is - if \tracinglostchars >= 3, make missing characters an error (not just a log message), and always report the character code in hex. LaTeX also enables this by default these days. Not really our reference -) LMTX only seems to support =0 (ignore) and =1 (report). Making these a fatal error (with exit status != 0) would be useful for automated typesetting, as missing characters easily can get lost in the logs, and then symbols are missing unnoticed in the output. Will never be default, you can play with: % \checkmissingcharacters % \removemissingcharacters % \replacemissingcharacters % \handlemissingcharacters (However, \tracinglostchars=3 also doesn't seem to work with LuaTeX+MKIV, probably because there is code to fallback to other fonts?) and if you want to quit: \enabledirectives[logs.errors=missing characters] 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 ___
[NTG-context] LMTX: request for \tracinglostchars=3
Hi, since TeX Live 2021 (TeX 3.141592653), there is > - if \tracinglostchars >= 3, make missing characters an error (not just > a log message), and always report the character code in hex. LaTeX also enables this by default these days. LMTX only seems to support =0 (ignore) and =1 (report). Making these a fatal error (with exit status != 0) would be useful for automated typesetting, as missing characters easily can get lost in the logs, and then symbols are missing unnoticed in the output. (However, \tracinglostchars=3 also doesn't seem to work with LuaTeX+MKIV, probably because there is code to fallback to other fonts?) cu, -- Leah Neukirchenhttps://leahneukirchen.org/ ___ 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] Unconnected \mathboxanchored produces unexpected results
On 12/22/2022 3:53 PM, Gavin via ntg-context wrote:
Hi Hans, MIkael and list,
I got an unexpected result when I asked for a \mathboxanchored, but then did
not use it with a connector. I expected the \mathboxanchored contents to be
typeset as usual, without a connector. Instead I got “ ::: c3” added into the
formula (“c3” was the anchor’s tag).
MWE and unexpected output below.
Thanks,
Gavin
\starttext
\startboxanchoring[+]
\connectboxanchors[top][top][distance=1ex,arrow=no] {c1}{c2}
%\connectboxanchors[bottom] [bottom] [distance=1ex,arrow=no] {c2}{c3} % <-- I
decided not to use this connector, producing unexpected results.
\startformula
\mathboxanchored[nucleus]{c1}{e}^{\dot\alpha}
\mathboxanchored[nucleus]{c2}{e}_{\mu}
\mathboxanchored[nucleus]{c3}{e}^{\beta} = \frac{1}{\sqrt{2}}
\bar\sigma^{\dot\alpha\beta}_{\mu}
\stopformula
\stopboxanchoring
\stoptext
can you try the latest binary fron the farm (remake th eformat)
-
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
___
[NTG-context] Unconnected \mathboxanchored produces unexpected results
Hi Hans, MIkael and list,
I got an unexpected result when I asked for a \mathboxanchored, but then did
not use it with a connector. I expected the \mathboxanchored contents to be
typeset as usual, without a connector. Instead I got “ ::: c3” added into the
formula (“c3” was the anchor’s tag).
MWE and unexpected output below.
Thanks,
Gavin
\starttext
\startboxanchoring[+]
\connectboxanchors[top][top][distance=1ex,arrow=no] {c1}{c2}
%\connectboxanchors[bottom] [bottom] [distance=1ex,arrow=no] {c2}{c3} % <-- I
decided not to use this connector, producing unexpected results.
\startformula
\mathboxanchored[nucleus]{c1}{e}^{\dot\alpha}
\mathboxanchored[nucleus]{c2}{e}_{\mu}
\mathboxanchored[nucleus]{c3}{e}^{\beta} = \frac{1}{\sqrt{2}}
\bar\sigma^{\dot\alpha\beta}_{\mu}
\stopformula
\stopboxanchoring
\stoptext
anchors-002-copy.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
___
[NTG-context] Accent wrecking \mathboxanchored
Hi Hans, Mikael and list,
I’ve been testing the connectors, which work great with the latest upload. One
problem I found: an accent in the \mathboxanchored causes a "Missing number,
treated as zero” error and no output. MWE below.
Thanks for all of the improvements. I’m making all kinds of connections!
Gavin
\starttext
\startboxanchoring[+]
\connectboxanchors[top][top][distance=1ex,arrow=no] {c1}{c2}
\connectboxanchors[bottom] [bottom] [distance=1ex,arrow=no] {c2}{c3}
\startformula
\mathboxanchored[nucleus]{c1}{e}^{\dot\alpha}
%\mathboxanchored[nucleus]{c2}{e}_{\mu}% <-- This works, without
accent
%\mathboxanchored[nucleus]{c2}{\bar{e}}_{\mu} % <-- This does not work,
with accent
\bar{\mathboxanchored[nucleus]{c2}{e}}_{\mu} % <-- This works, but
connector punches through accent
\mathboxanchored[nucleus]{c3}{e}^{\beta} = \frac{1}{\sqrt{2}}
\bar\sigma^{\dot\alpha\beta}_{\mu}
\stopformula
\stopboxanchoring
\stoptext
___
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] move glyph vertically
On 12/22/22 13:18, Hans Hagen via ntg-context wrote:
> On 12/22/2022 12:54 PM, Pablo Rodriguez via ntg-context wrote:
>> […]
>> Could anyone tell me how could I move vertically single glyphs?
>> […]
>
> so:
>
> \startluacode
> fonts.handlers.otf.addfeature {
> name = "gpos_test",
> type = "single",
> data = {
> [ '¿' ] = { 0, 400 },
> [ '¡' ] = { 0, 400 },
> }
> }
> \stopluacode
Many thanks for your fast reply and help, Hans.
Pablo
___
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] move glyph vertically
On 12/22/2022 12:54 PM, Pablo Rodriguez via ntg-context wrote:
Dear list,
I have the following sample:
\startluacode
fonts.handlers.otf.addfeature {
name = "gpos_test",
type = "single",
data = {
[ '¿' ] = 1000,
[ '¡' ] = 1000,
}
}
\stopluacode
\definefontfeature[ktest][gpost_tes=yes]
\starttext
\startTEXpage[offset=1em]
\feature[+][gpos_test]
¿? ¡!
\stopTEXpage
\stoptext
This tries to move vertically the opening question and exclamation
marks, so they are at the same height that its closing counterparts.
I thought there may be a GPOS feature that could achieve this, but I
must admit I have no idea about how to achive it.
In my document, this should only work with the slanted feature.
Could anyone tell me how could I move vertically single glyphs?
Many thanks for your help,
typos
\definefontfeature[ktest][gpost_tes=yes]
and wrong feature name
\feature[+][gpos_test]
so:
\startluacode
fonts.handlers.otf.addfeature {
name = "gpos_test",
type = "single",
data = {
[ '¿' ] = { 0, 400 },
[ '¡' ] = { 0, 400 },
}
}
\stopluacode
\definefontfeature[ktest][gpos_test=yes]
\starttext
\startTEXpage[offset=1em]
\ruledhbox{¿? xx ¡!}
\addfeature{ktest}
\ruledhbox{¿? xx ¡!}
\stopTEXpage
\stoptext
-
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
___
[NTG-context] move glyph vertically
Dear list,
I have the following sample:
\startluacode
fonts.handlers.otf.addfeature {
name = "gpos_test",
type = "single",
data = {
[ '¿' ] = 1000,
[ '¡' ] = 1000,
}
}
\stopluacode
\definefontfeature[ktest][gpost_tes=yes]
\starttext
\startTEXpage[offset=1em]
\feature[+][gpos_test]
¿? ¡!
\stopTEXpage
\stoptext
This tries to move vertically the opening question and exclamation
marks, so they are at the same height that its closing counterparts.
I thought there may be a GPOS feature that could achieve this, but I
must admit I have no idea about how to achive it.
In my document, this should only work with the slanted feature.
Could anyone tell me how could I move vertically single glyphs?
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://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
___
