Hi,
I'd like to understand more of the inner workings of LMTX.
When I understand it right, most of the code is now processed in Lua but
I was not able to find it.
For example, I tried to find out how setupitemgroup is handled (just as
an example of a more complex command). The wiki has a (kind
Hi,
We were considering to drop the virtual math fonts mechanism (which has
served its purpose in the transition in the very early days of luatex
but became obsolete as math fonts evolved) but in the end we were forced
keep this feature and even upgrade it because we liked iwona, kurier and
Hi,
I uploaded the first 2023 lmtx. There are not that many changes, most
relate to updating manuals. Currently we're looking at the metafun /
luametafun and lowlevel manuals - adding some accumulated todo's.
Keep in mind that when we update manuals that is is not automatically
reflected in
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
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).
Hi,
I uploaded lmtx. Most significate:
- A slightly different implementaqtion of font modes 'base' and 'none'
(hopefully no side effects).
- A few math updates (like primes done a bit differently, we made some
choices here).
- Limited support for colr format 1 as needed for the rather
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 = {
> ['“'] = { "`", "`" },
> ['”'] = { "'", "'" },
>
On 11/11/2022 10:19 PM, Leah Neukirchen via ntg-context wrote:
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:
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
On 10/13/2022 8:36 PM, Henning Hraban Ramm via ntg-context wrote:
Am 13.10.22 um 19:41 schrieb Pablo Rodriguez via ntg-context:
On 10/13/22 00:50, Max Chernoff via ntg-context wrote:
On Wed, 2022-10-12 at 13:14 +0200, Leah Neukirchen wrote:
[...]
The last version of font-cff.lua should also
On 10/13/2022 7:41 PM, Pablo Rodriguez via ntg-context wrote:
On 10/13/22 00:50, Max Chernoff via ntg-context wrote:
On Wed, 2022-10-12 at 13:14 +0200, Leah Neukirchen wrote:
[...]
The last version of font-cff.lua should also copy the hinting-related
values of the CFF properly (/BlueScale,
Now! I am astonished about this blog! Super that you, Leah and Hans, insisted
to find out what the culprit was! Thank you both so much for your effort!
Kind regards
Willi
> On 11 Oct 2022, at 21:07, Leah Neukirchen via ntg-context
> wrote:
>
> Hans Hagen via ntg-context writes:
>
>> On
Am 13.10.22 um 19:41 schrieb Pablo Rodriguez via ntg-context:
On 10/13/22 00:50, Max Chernoff via ntg-context wrote:
On Wed, 2022-10-12 at 13:14 +0200, Leah Neukirchen wrote:
[...]
The last version of font-cff.lua should also copy the hinting-related
values of the CFF properly (/BlueScale,
On 10/13/22 00:50, Max Chernoff via ntg-context wrote:
> On Wed, 2022-10-12 at 13:14 +0200, Leah Neukirchen wrote:
>> [...]
>> The last version of font-cff.lua should also copy the hinting-related
>> values of the CFF properly (/BlueScale, /StemSnap[HV] etc).
>> We fixed that on the side. ;)
>
>
On Wed, 2022-10-12 at 13:14 +0200, Leah Neukirchen wrote:
> > Seeing that you're modifying the font encoding, could you perhaps
> > reconsider supporting hinting in LMTX?
> >
> >https://mailman.ntg.nl/pipermail/ntg-context/2022/106311.html
> >
> > Even with a high resolution screen, I can
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.
>>
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.
> >
> > Once we're confident that we can catch it
On Tue, 11 Oct 2022, Leah Neukirchen via ntg-context wrote:
> Hans Hagen via ntg-context writes:
> > Once we're confident that we can catch it Leah (who does the low level
> > introspective testing with viewers, printers and tools) likely will
> > report on it and there will be a test file for
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.
>>>
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.
\setupbackend[level=0,compresslevel=0]
\starttext
Just a
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.
>
> \setupbackend[level=0,compresslevel=0]
> \starttext
> Just a line of text.
> \stoptext
>
> When I print
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
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 so kind and share which model you have?
We have
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?
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?
we basically use the old pre 1.6 embedding, same as
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?
> we basically use the old pre 1.6 embedding, same as luatex
I saw that the new code renumbers the glyphs, so
On 10/5/2022 6:02 PM, Pablo Rodriguez via ntg-context wrote:
It happens both with LuaMetaTeX and LuaTeX. When playing with certain
levels of zooming, some blank spots are displayed inside the characters
(printing is fine).
Such artifacts can result from operating in the extremes and one has
On 10/3/22 20:57, Leah Neukirchen via ntg-context wrote:
>> [...]
>> \setupbackend[level=0,compresslevel=0]
>> \starttext
>> Just a line of text.
>> \stoptext
>> [...]
>
> On Acrobat DC on macOS, there is a visible difference between the two files:
Hi Leah,
this issue also happens with PDF.js
Am 04.10.22 um 18:11 schrieb Hans Hagen via ntg-context:
it is hidden in preflight, some tiny entry in a menu "browse internal
.." or so but as adobe loves to change user interfaces with each version
i have no clue where you can find it
Oops, I completely forgot that was part of Callas
On 10/4/2022 5:52 PM, Leah Neukirchen via ntg-context wrote:
I looked into /StemV 0 (which was different in MKIV) but that works
with the TTF files, too. Also should be ignored for Type 3 anyway.
Does your test have type 3 fonts? Should be no problem.
Hans
On 10/4/2022 5:44 PM, Henning Hraban Ramm via ntg-context wrote:
Am 04.10.22 um 14:59 schrieb Hans Hagen via ntg-context:
On 10/4/2022 2:35 PM, Leah Neukirchen via ntg-context wrote:
Are there any tools to analyze this CID font stream?
You can browse the glyphs with full acrobat
You can?
On 10/4/2022 6:03 PM, Henning Hraban Ramm via ntg-context wrote:
Am 04.10.22 um 15:21 schrieb Angel M Alganza via ntg-context:
On Tue, Oct 04, 2022 at 01:59:45PM +0200, Henning Hraban Ramm via
ntg-context wrote:
How do you send the files “directly” to the printer? Copy to lpt queue?
In my
Am 04.10.22 um 15:21 schrieb Angel M Alganza via ntg-context:
On Tue, Oct 04, 2022 at 01:59:45PM +0200, Henning Hraban Ramm via
ntg-context wrote:
How do you send the files “directly” to the printer? Copy to lpt queue?
In my case, as I explained in my original email, I plug in a USB drive
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
Am 04.10.22 um 14:59 schrieb Hans Hagen via ntg-context:
On 10/4/2022 2:35 PM, Leah Neukirchen via ntg-context wrote:
Are there any tools to analyze this CID font stream?
You can browse the glyphs with full acrobat
You can? Not with Acrobat Pro v9 or before.
Hraban
On Tue, Oct 04, 2022 at 01:59:45PM +0200, Henning Hraban Ramm via ntg-context
wrote:
How do you send the files “directly” to the printer? Copy to lpt queue?
In my case, as I explained in my original email, I plug in a USB drive
into the printer USB port, and I pick up the file to print from
On 10/4/2022 2:35 PM, Leah Neukirchen via ntg-context wrote:
Are there any tools to analyze this CID font stream?
You can browse the glyphs with full acrobat (but I haven't a full
acrobat installed ... I lost it when I upgraded my laptop and have no
plans to buy a new version as I don't need
Hi,
does (the obsolete)
\enabledirectives[backend.pdf.forcecidset]
help
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038
On 10/4/2022 2:35 PM, Leah Neukirchen via ntg-context wrote:
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
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
Am 04.10.22 um 12:53 schrieb Leah Neukirchen via ntg-context:
Another data point: Brother B205 doesn't print it either.
But would all of these use the same licensed PDF renderer...
Print the test page of all these printers. Does it say something about
the PDF/PostScript engine (RIP) and its
On 10/4/2022 12:53 PM, Leah Neukirchen wrote:
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 PDF to the
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 PDF to the printer)
>>> on a Ricoh MP3053 or on a
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 PDF to the printer)
on a Ricoh MP3053 or on a Samsung CLP-680DW, I just get an empty page.
I
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 PDF to the printer)
on a Ricoh MP3053 or on a Samsung CLP-680DW, I just get an empty page.
I believe that is the exact same problem I have and that I described a
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 settings.
>>
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 settings.
\setupbackend[level=0,compresslevel=0]
\starttext
Just a line
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]
> \starttext
> Just a line of
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
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,
At the ctx meeting we released luametatex, that is, the source code is
now in the context zip (so it grew a few MB). At the same time Mojca set
up some contextgarden repositories on github. We're working on a setup
for users to generate older snapshots, if needed (for instance because
On 9/22/2022 2:23 PM, Leah Neukirchen via ntg-context wrote:
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
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
On 8/4/2022 8:52 PM, Michael Urban via ntg-context wrote:
I get a different result for mkiv and lmtx for the following input:
\starttext
Even now, a six footer is two
standard deviations from the mean. Remember, 5\prime{}7\prime\prime{} is 50th
percentile today
for a 15 year old.
\stoptext
I get a different result for mkiv and lmtx for the following input:
\starttext
Even now, a six footer is two
standard deviations from the mean. Remember, 5\prime{}7\prime\prime{} is 50th
percentile today
for a 15 year old.
\stoptext
With mkiv, the prime marks for inches and feet are where I
Hello,
Some years ago I wrote an introduction to ConTeXt in German:
https://github.com/AKielhorn/Context-Intro
But that was long ago.
Today LMTX is state of the art and I tried to build it with a recent LMTX.
This lead to problems because LMTX does not include modules.
Therefore my question
Never mind. Apparently lmtx changed the default for \setupindenting from
'next' to 'first'?
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
The following produces different results in mkiv and lmtx (to which I am brand
new):
\setupinitial[distance=1pt,font=Serif at 36pt,n=2]
\setupindenting[medium,yes]
\starttext
\placeinitial
\input knuth
\stoptext
The mkiv output is the desired effect. It works fine in lmtx if I do not
Hello list,
thank you all for your advices.
Aditya was right. There was some mess in PATH variable.
Lesson learned: start with explicit paths to executables.
Still where mtxrun (Windows) was pointing to the right one, which was
fooling me.
I've noticed the problem with antivirus SW during the
> On 14 Jun 2022, at 12:20, Jano Kula via ntg-context
> wrote:
>
> Do you have an idea how to fix problem?
> I will be thankful for an advice, it is quite urgent (everything was working
> yesterday).
Do you have an anti-virus product installed?
In the past I've noticed that Symantec
Hello,
I do not understand what you did!
I went to "http://www.pragma-ade.com/install.htm"
downlaoded the 64 bit Microsoft Windows file
"context-win64.zip".
I did create a folder c:\data\context
wher I did put the .zip file and unzipped it.
I got
On Tue, 14 Jun 2022, Jano Kula via ntg-context wrote:
> Hello list,
>
> I cannot make fresh install of lmtx to work. The structure after unzipping:
> C:\data\context\bin\beta
> C:\data\context\bin\beta\bin
> C:\data\context\bin\beta\tex
> C:\data\context\bin\beta\tex\texmf
>
Hello,
I didn't mention the platform: context-setup-win64.
Thank you,
Jano
On Tue, Jun 14, 2022 at 1:20 PM Jano Kula wrote:
> Hello list,
>
> I cannot make fresh install of lmtx to work. The structure after unzipping:
> C:\data\context\bin\beta
> C:\data\context\bin\beta\bin
>
Hello list,
I cannot make fresh install of lmtx to work. The structure after unzipping:
C:\data\context\bin\beta
C:\data\context\bin\beta\bin
C:\data\context\bin\beta\tex
C:\data\context\bin\beta\tex\texmf
C:\data\context\bin\beta\tex\texmf-cache
C:\data\context\bin\beta\tex\texmf-context
etc.
On 3/5/2022 9:39 PM, Richard Mahoney via ntg-context wrote:
Something I've noticed for a little while now, although it may be
long standing, I'm not sure. If one ends some of the lines in
the input files with a full stop (.) and a back slash (\) then LMTX
will fail to compile with a fatal error.
Something I've noticed for a little while now, although it may be
long standing, I'm not sure. If one ends some of the lines in
the input files with a full stop (.) and a back slash (\) then LMTX
will fail to compile with a fatal error. The only way to recover is
to go through each of the files
list for ConTeXt users
To: Richard Mahoney via ntg-context
Cc: Hans Hagen
Subject: Re: [NTG-context] LMTX-latest | SciTE 5.1.6 --- 5.2.1 | Not
working with tex/texmf-context/context/data/scite
Date: Thu, 3 Mar 2022 08:53:06 +0100
Mailer: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0)
Gecko
On 3/3/2022 12:08 AM, Richard Mahoney via ntg-context wrote:
[Gentoo]
I've found that the config included with LMTX in:
tex/texmf-context/context/data/scite
does not work with SciTE 5.1.6+
The latest version that seems to be working is SciTE 5.1.5.
Version 5.1.5 Scintilla: 5.1.4 Lexilla:
[Gentoo]
I've found that the config included with LMTX in:
tex/texmf-context/context/data/scite
does not work with SciTE 5.1.6+
The latest version that seems to be working is SciTE 5.1.5.
Version 5.1.5 Scintilla: 5.1.4 Lexilla: 5.1.3
compiled for GTK:3.24.29
Nov 14 2021 12:15:50
Is anyone
Hi,
There haven't been updates and the reason is that we're in the middle of
math and/or wrapping up on transliteration / indic (for which there is
also a nice wiki page being made).
Concerning math, we're progressing with some rather flexible spacing,
penalty, linebreak extensions but
Problems I and II are apparently solved in the latest update. As for III,
the following works:
\definefont[ARABICFONT][file:almfixed.otf*arabic at 28pt]
\noheaderandfooterlines
\setupwhitespace[big]
% \starttext
\startTEXpage[offset=1ex]
% \setupdirections[bidi=global,method=one]
For III: See attached!
On Wed, 10 Nov 2021 09:00:26 -0700, Idris Samawi Hamid ادريس سماوي حامد
wrote:
Dear Hans and gang,
Consider the following MWE:
==
\definefont[ARABICFONT][file:Adobe_Naskh.ttf*arabic at 28pt]
% \definefont[ARABICFONT][file:Amiri-Regular_0.ttf*arabic at
Dear Hans and gang,
Consider the following MWE:
==
\definefont[ARABICFONT][file:Adobe_Naskh.ttf*arabic at 28pt]
% \definefont[ARABICFONT][file:Amiri-Regular_0.ttf*arabic at 28pt]
% \definefont[ARABICFONT][file:Scheherazade-Regular.ttf*arabic at 28pt]
%
On 9/20/2021 12:34 PM, Floris van Manen via ntg-context wrote:
I try to update my lmtx installation, but it seems that there is no
contact with the server somehow...
Any hints?
Because our provider stops with web stuff we are in transition. You can
try again (there was a redirect to https that
The server is on its way to the context meeting and got no wifi on the train ;)
HR
PS: nonsense, of course
> Am 20.09.2021 um 12:34 schrieb Floris van Manen via ntg-context
> :
>
> I try to update my lmtx installation, but it seems that there is no contact
> with the server somehow...
> Any
I try to update my lmtx installation, but it seems that there is no
contact with the server somehow...
Any hints?
$ ./install.sh
mtx-install | provide valid server and instance
The following settings were used:
server : lmtx.contextgarden.net,lmtx.pragma-ade.com,lmtx.pragma-ade.nl
On Mon, 23 Aug 2021, Aditya Mahajan via ntg-context wrote:
> On Mon, 23 Aug 2021, Benjamin Buchmuller via ntg-context wrote:
>
> > This is the setup I have been using, but I'm unsure if the problem could be
> > related to the other problem I had. (Not scaled to a MWE, but short
> > enough.) I
On 8/23/2021 7:42 PM, Aditya Mahajan wrote:
On Mon, 23 Aug 2021, Benjamin Buchmuller via ntg-context wrote:
This is the setup I have been using, but I'm unsure if the problem could be
related to the other problem I had. (Not scaled to a MWE, but short enough.) I
figured the issue by removing
On Mon, 23 Aug 2021, Benjamin Buchmuller via ntg-context wrote:
> This is the setup I have been using, but I'm unsure if the problem could be
> related to the other problem I had. (Not scaled to a MWE, but short enough.)
> I figured the issue by removing some of the lines.
I get the same
This is the setup I have been using, but I'm unsure if the problem could be
related to the other problem I had. (Not scaled to a MWE, but short enough.) I
figured the issue by removing some of the lines.
\usemodule[vim]
\definetextbackground[codebkg]
[
frame=on,
On 8/23/2021 12:55 AM, Benjamin Buchmuller via ntg-context wrote:
Hi,
Here is another thing which worked previously for me:
ConTeXt ver: 2021.07.30 00:57 LMTX fmt: 2021.8.8 int: english/english
Now:
ConTeXt ver: 2021.08.22 11:54 LMTX fmt: 2021.8.22 int: english/english
Error:
lua
On 8/23/2021 12:10 AM, Benjamin Buchmuller via ntg-context wrote:
Hi,
Thanks for having had a look into the t-vim.
At least the document compiles fine (I get a PDF), although multiple complaints from the lua end
when I use "$" or "#" in my source, for example
#!/usr/bin/bash
etc.
Hi,
Here is another thing which worked previously for me:
ConTeXt ver: 2021.07.30 00:57 LMTX fmt: 2021.8.8 int: english/english
Now:
ConTeXt ver: 2021.08.22 11:54 LMTX fmt: 2021.8.22 int: english/english
Error:
lua error:
registered function call [396]:
Benjamin Buchmuller via ntg-context schrieb am 23.08.2021 um 00:10:
Hi,
Thanks for having had a look into the t-vim.
At least the document compiles fine (I get a PDF), although multiple complaints from the lua end
when I use "$" or "#" in my source, for example
#!/usr/bin/bash
etc.
Hi,
Thanks for having had a look into the t-vim.
At least the document compiles fine (I get a PDF), although multiple complaints
from the lua end when I use "$" or "#" in my source, for example
#!/usr/bin/bash
etc. culminating in
Sorry, but I'm not programmed to handle this case;
I'll
On 8/19/2021 10:07 PM, Aditya Mahajan via ntg-context wrote:
On Thu, 19 Aug 2021, Hans Hagen via ntg-context wrote:
Hi,
Here are the highlights of todays update:
- somewhat more compact tuc files, not for all documents, but it can
accumulate; also less memory used then; i could bring down an
On Thu, 19 Aug 2021, Hans Hagen via ntg-context wrote:
> Hi,
>
> Here are the highlights of todays update:
>
> - somewhat more compact tuc files, not for all documents, but it can
> accumulate; also less memory used then; i could bring down an extreme
> 2000 page 5 column doc tuc file down to
Hi,
Here are the highlights of todays update:
- somewhat more compact tuc files, not for all documents, but it can
accumulate; also less memory used then; i could bring down an extreme
2000 page 5 column doc tuc file down to 5% -- it was 70 MB; for the
luametatex manual it reducec the tuc
On 7/28/2021 1:45 PM, Henning Hraban Ramm via ntg-context wrote:
Am 28.07.2021 um 11:46 schrieb Hans Hagen :
On 7/28/2021 10:31 AM, Henning Hraban Ramm via ntg-context wrote:
Am 28.07.2021 um 08:50 schrieb Hans Hagen via ntg-context :
On 7/27/2021 11:44 PM, T. Kurt Bond via ntg-context
> Am 28.07.2021 um 11:46 schrieb Hans Hagen :
>
> On 7/28/2021 10:31 AM, Henning Hraban Ramm via ntg-context wrote:
>>> Am 28.07.2021 um 08:50 schrieb Hans Hagen via ntg-context
>>> :
>>>
>>> On 7/27/2021 11:44 PM, T. Kurt Bond via ntg-context wrote:
Hello.
I'm trying to get LMTX to
On 7/28/2021 10:31 AM, Henning Hraban Ramm via ntg-context wrote:
Am 28.07.2021 um 08:50 schrieb Hans Hagen via ntg-context :
On 7/27/2021 11:44 PM, T. Kurt Bond via ntg-context wrote:
Hello.
I'm trying to get LMTX to use my fonts on Fedora 33 Linux. I've got LMTX
installed in the
> Am 28.07.2021 um 08:50 schrieb Hans Hagen via ntg-context
> :
>
> On 7/27/2021 11:44 PM, T. Kurt Bond via ntg-context wrote:
>> Hello.
>> I'm trying to get LMTX to use my fonts on Fedora 33 Linux. I've got LMTX
>> installed in the directory /sw/versions/context/lmtx and I've put copies of
On 7/27/2021 11:44 PM, T. Kurt Bond via ntg-context wrote:
Hello.
I'm trying to get LMTX to use my fonts on Fedora 33 Linux. I've got
LMTX installed in the directory /sw/versions/context/lmtx and I've put
copies of the fonts I'd like to use in
/sw/versions/context/lmtx/tex/texmf-fonts.
Hello.
I'm trying to get LMTX to use my fonts on Fedora 33 Linux. I've got LMTX
installed in the directory /sw/versions/context/lmtx and I've put copies of
the fonts I'd like to use in /sw/versions/context/lmtx/tex/texmf-fonts.
Some of them are truetype and some of them are opentype. When I run
[still working to somewhat reproduce my old mkii setup in LMTX]
The following is a minimal example that shows the following:
context test2.tex results in
The first line after the initials not as much indented as it should be
Character protrusion in a footnote does not work (see “refer-“ at the
Pablo Rodriguez schrieb am 18.07.2021 um 18:16:
On 7/18/21 3:35 PM, Gerben Wierda wrote:
I am trying to find out how to move this setup in mkii
23 \usemodule[lettrine]
24 >> \setuplettrine[Lines=3,
25 Hang=.5,
26 Oversize=0,
27
On 7/18/21 3:35 PM, Gerben Wierda wrote:
> I am trying to find out how to move this setup in mkii
>
> 23 \usemodule[lettrine]
> 24 >> \setuplettrine[Lines=3,
> 25 Hang=.5,
> 26 Oversize=0,
> 27 Raise=0,
> 28
I am trying to find out how to move this setup in mkii
23 \usemodule[lettrine]
24 >> \setuplettrine[Lines=3,
25Hang=.5,
26Oversize=0,
27Raise=0,
28Findent=0pt,
29Nindent=0em,
30
> Am 14.07.2021 um 20:26 schrieb jdh :
>
>
> I've downloaded and ran the install...sh script from the directory:
> /opt/context-lmtx
Is this on Linux?
> It indicates that it completed successully, but there is no 'tex' directory
> anywhere in the resulting /opt/context-lmtxdirectory
1 - 100 of 435 matches
Mail list logo
