Leah Neukirchen via ntg-context writes:
> Hi,
>
> I was looking into the SciTE setup when I found that
> tex/texmf-context/context/data/scite/context/scite-context-internal.properties
> only contained NUL bytes.
>
> Deleting and reinstalling doesn't fix it.
>
> I have
Hi,
I was looking into the SciTE setup when I found that
tex/texmf-context/context/data/scite/context/scite-context-internal.properties
only contained NUL bytes.
Deleting and reinstalling doesn't fix it.
I have now checked the other files there and these files seem to have
gotten corrupted at
Hi,
LMTX prints a bit weird error message for undefined control sequences:
\starttext
\zong
\stoptext
tex error > tex error on line 2 in file ./foo.tex: Undefined control
sequence \undefined
\zong
Shouldn't it print "\zong" in the "tex error" line too?
--
Leah Neukirchen
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,
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).
Thangalin via ntg-context writes:
> Thoughts? Suggestions for improvement?
If you are looking for technical suggestions, every RUN line will
create a layer even if you delete files later. I'd suggest making the
final image by copying the root directory of a multistage container,
e.g.
Hans Hagen via ntg-context writes:
> can you show what is wrong and what it should be with
>
> fonts.handlers.otf.addfeature {
> name = "germantexlig",
> type = "ligature",
> data = {
> ['“'] = { "`", "`" },
> ['”'] = { "'", "'" },
>
Hi,
as Hans recommended in the last video meeting, I tried to implement
the texquotes feature using OTF features, and hit two problems:
1) To support German quotes as well, I have two ligatures that end
up as the same glyph:
`` -> “
"' -> “
This can't be in the same ligature
"Thomas A. Schmitz via ntg-context" writes:
> On 10/23/22 21:34, Otared Kavian via ntg-context wrote:
>> Hi Thomas,
>> Both your examples typeset fine with my installation of LMTX
>> (version 2022.10.22 11:23) on MacOS 11.7.
>> (Indeed you previous file test file reporting the background issue
Hans Hagen via ntg-context writes:
> I'll add
>
> \setupbodyfontenvironment
> [all]
> [12pt]
> [x=4pt,
>small=4pt]
>
> as option (assuming we have no performance hit).
It would also be nice to be able to
\setupbodyfontenvironment[all][default][x=0.8]
(I solved my actual problem by
Hi,
playing around with \definebodyfontenvironment with latest LMTX,
I found this possibly buggy behavior:
\definebodyfontenvironment[12pt][small=6pt] % x=6pt works here
\setupbodyfont[12pt]
\starttext
normal {\tx tx} {\small small}
\stoptext
With \definebodyfontenvironment[12pt][x=6pt] I can
Leah Neukirchen via ntg-context writes:
> Max Chernoff via ntg-context writes:
>
>> Hi Leah,
>>
>>> I was typesetting some German text on a narrow page when I discovered
>>> the justification wasn't as good as expected. I think I tracked this
>>&
Max Chernoff via ntg-context writes:
> Hi Leah,
>
>
>> > Leah and I are zooming in on the issue. It might relate to wrong font
>> > matrix default behavior in the pdf printer driver, and GS got a fix
>> > for that long ago, so maybe old printers with not-updated drivers can
>> > be affected.
>>
Hans Hagen via ntg-context writes:
> On 10/9/2022 8:03 AM, Max Chernoff via ntg-context wrote:
>> Hi all,
>>
>>> I use LuaMetaTeX 2.10 20220918 + ConTeXt LMTX 2022.09.11.
>>>
>>> Here's a tiny test document, I disabled PDF compression but it also
>>> doesn't work with the default settings.
>>>
Henning Hraban Ramm via ntg-context writes:
> Am 11.10.22 um 20:00 schrieb Leah Neukirchen via ntg-context:
>> Hello,
>> I noticed the following problem:
>> \showframe
>> \startluacode
>>fonts.protrusions.vectors.pure[0x201C] = { 1, 1 }
>> \stopluacode
Hello,
I noticed the following problem:
\showframe
\startluacode
fonts.protrusions.vectors.pure[0x201C] = { 1, 1 }
\stopluacode
\definefontfeature[default][default][protrusion=pure]
\setupalign[hanging]
\starttext
This text is unquoted.
“This text is quoted manually.”
\quotation{This
Henning Hraban Ramm via ntg-context writes:
> Am 09.10.22 um 17:33 schrieb Leah Neukirchen via ntg-context:
>> Hi,
>> last week we had a long thread about non-printing PDF on this list
>> and
>> together with Hans I tracked down the issue and we found a fix.
>&
Hans Hagen via ntg-context writes:
> On 10/9/2022 3:52 PM, Leah Neukirchen via ntg-context wrote:
>> Wolfgang Schuster via ntg-context writes:
>>
>>> Leah Neukirchen via ntg-context schrieb am 09.10.2022 um 15:19:
>>>> Hi,
>>>
Hi,
last week we had a long thread about non-printing PDF on this list and
together with Hans I tracked down the issue and we found a fix.
Since it changes some details of how PDFs are generated by LMTX, we'd
like to test this change first on a wide range of software and
printers.
So please: Try
Wolfgang Schuster via ntg-context writes:
> Leah Neukirchen via ntg-context schrieb am 09.10.2022 um 15:19:
>> Hi,
>>
>> is there a way to have something like
>>
>> \setuppapersize[A5][A4]
>>
>> but have the "inner paper size" be a compute
Hi,
is there a way to have something like
\setuppapersize[A5][A4]
but have the "inner paper size" be a computed fit like in
\startTEXpage?
Or, alternatively, is there is a way to print crop marks around
an environment like \startTEXpage?
Thanks,
--
Leah Neukirchen
Hans Hagen via ntg-context writes:
> On 10/6/2022 2:42 PM, Leah Neukirchen wrote:
>
>> But I also found yet another printer model that doesn't print:
>> the HP Color LaserJet 4700 (Model Q7492A, Firmware 20060821 46.031.1).
>> Since you seem to own the only printer that works ;) would
>> you be
Hans Hagen via ntg-context writes:
> On 10/6/2022 12:31 PM, Ulrike Fischer via ntg-context wrote:
>> Am Tue, 4 Oct 2022 18:09:28 +0200 schrieb Hans Hagen via
>> ntg-context:
>>
Hans, is it possible that LMTX uses some technique that is “too modern”
for some built-in PDF interpreter?
Hans Hagen via ntg-context writes:
> Hi,
>
> does (the obsolete)
>
> \enabledirectives[backend.pdf.forcecidset]
>
> help
No; same blank page. :(
(Also MKIV works without CIDSet...)
I looked into /StemV 0 (which was different in MKIV) but that works
with the TTF files, too. Also should be
Hans Hagen writes:
> what is sent to the printer .. maybe not pdf but something the printer
> driver produces
For the Ricoh and Samsung printers, we printed the raw PDF directly
over JetDirect (port 9100). For the Brother, the "upload PDF"
function was used. So no outside printer drivers
Hans Hagen via ntg-context writes:
> On 10/4/2022 4:16 AM, Angel M Alganza via ntg-context wrote:
>> On Mon, Oct 03, 2022 at 07:17:10PM +0200, Leah Neukirchen via
>> ntg-context wrote:
>>
>>> When I print this "directly" (i.e. sending the raw P
Hans Hagen via ntg-context writes:
> On 10/3/2022 7:17 PM, Leah Neukirchen via ntg-context wrote:
>> Hi,
>> I use LuaMetaTeX 2.10 20220918 + ConTeXt LMTX 2022.09.11.
>> Here's a tiny test document, I disabled PDF compression but it also
>> doesn't work with the default
Leah Neukirchen via ntg-context writes:
> Hi,
>
> I use LuaMetaTeX 2.10 20220918 + ConTeXt LMTX 2022.09.11.
>
> Here's a tiny test document, I disabled PDF compression but it also
> doesn't work with the default settings.
>
> \setupbackend[level=0,compresslevel=0]
&g
Hi,
I use LuaMetaTeX 2.10 20220918 + ConTeXt LMTX 2022.09.11.
Here's a tiny test document, I disabled PDF compression but it also
doesn't work with the default settings.
\setupbackend[level=0,compresslevel=0]
\starttext
Just a line of text.
\stoptext
When I print this "directly" (i.e. sending
Max Chernoff via ntg-context writes:
> Hi Leah,
>
>> I was typesetting some German text on a narrow page when I discovered
>> the justification wasn't as good as expected. I think I tracked this
>> down to differences in hyphenation points, namely, ConTeXt has fewer:
>>
>> \starttext
>>
Hans Hagen via ntg-context writes:
>> After a bunch of debugging, it turns out that LMTX breaks the TikZ
>> 'quotes'
>> library, which works using code ala:
>> \def\tikz@enable@node@quotes{%
>>\pgfkeyssetvalue{/handlers/first char syntax/the character
>> "}{\tikz@quote@parser}%
>>
Hi,
I was typesetting some German text on a narrow page when I discovered
the justification wasn't as good as expected. I think I tracked this
down to differences in hyphenation points, namely, ConTeXt has fewer:
\starttext
\language[de]
\showhyphens{Zusammenhang}
\showhyphens{anderswo}
Hi,
I'm trying to get tikz-cd to run on LMTX and some examples already
work fine, but I had a problem with text on arrows.
To reproduce:
\usemodule[tikz]
\usetikzlibrary[cd]
\starttext
\starttikzcd
A \arrow{r}{A} \NC B \NR
\stoptikzcd
\stoptext
This builds fine on MkIV from TeXLive 2022 with
33 matches
Mail list logo
