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
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
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
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
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
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
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
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
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).
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”
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).
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
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",
>
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,
Dear list,
I have the following sample:
\startluacode
fonts.handlers.otf.addfeature {
name = "gpos_test",
type = "single",
data = {
[ '¿' ] = 1000,
[ '¡' ] = 1000,
}
}
\stopluacode
15 matches
Mail list logo
