On 11/2/2021 05:43, Hans Hagen via ntg-context wrote:
Hi,
I uploaded a new lmtx. There is a new low level manual
(lowlevel-localboxes) that describes the extended local boxes
interface as well as a layer on top. New is that we have classes which
makes this (engine) mechanism more useable
Hi,
I uploaded a new lmtx. There is a new low level manual
(lowlevel-localboxes) that describes the extended local boxes interface
as well as a layer on top. New is that we have classes which makes this
(engine) mechanism more useable. It definitely is some low level
mechanism but you can
\localbox[linenumber]{}%
\localbox[linenumbertwo]{}%
\localbox[linetext]{L}%
\startlocalbox[linetexttwo]
R
\stoplocalbox
\dorecurse{100}{
\samplefile{tufte}
\par
}
\stop
If you play a bit with these low level mechanism the luametatex /
context
-link-var-var
\goto{\hyphenatedurl{\xmlflush{#1}}}[url(\xmlflush{#1})]
\stopxmlsetups
seems to work now correctly.
it depends abit on what gets flushed, in those cases a low level flush
has to be used
\xmltext
\xmltextonly
\xmlraw
to get the raw data .. depends on content
Hans
dieresis{e} == \\"{e}
> \withring{u} == \\r{u}
> \withhungarumlaut{u} == \\H{u}
> \withcaron {e} == \\v{e}
> \withcedilla {e} == \\c{e}
> \withogonek {e} == \\k{e}
>
> Did I miss one?
>
> Then we can deprecate the short ones (keep them a low
n; also there’s now "manage
presentations" behind the "plus" button. Beware there is only one presenter, 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 mostl
or is this built into the \cite command at a
low level? If I had to, I could define an \autocite command that does
all of these checks first, but if it's possible to keep the common \cite
command instead of forcing users to use a different command, that would
be preferable.
a few quick remarks (
the entry to the list after I invoke the \cite command, or is this built into
the \cite command at a low level? If I had to, I could define an \autocite
command that does all of these checks first, but if it's possible to keep the
common \cite command instead of forcing users to use a differe
tion using the \listcite or
\cite command recursively. But is there a way to conditionally handle
whether or not to add the entry to the list after I invoke the \cite
command, or is this built into the \cite command at a low level? If I had
to, I could define an \autocite command that does all of these ch
ull of tiny s. The problem
> > seems to be that tex4ht runs TeX which typesets everything into DVI
> > with every element carefully placed on a page, and then tex4ht tries
> > to reverse that back into HTML. All this extra HTML will slow down /
> > interfere with the ebook reader wh
e on a particular device.
>
> How I would like it to work is directly from LaTeX to HTML without any low
> level typesetting. If I have a LaTex source paragraph
>
> This is some text with \textbf{some parts} in bold.
>
> The TEX will copy the source text to the destinatio
low level typesetting. If I have a LaTex source paragraph
This is some text with \textbf{some parts} in bold.
so kind of interpreting
The TEX will copy the source text to the destination. If
there's a TeX command, here \textbf, it looks for a Lua function
with that name and invokes
that back into HTML. All this extra HTML
will slow down / interfere with the ebook reader which is doing the
final page layout at runtime on a particular device.
How I would like it to work is directly from LaTeX to HTML without
any low level typesetting. If I have a LaTex source paragraph
> don't see it ... there's a pdf and lowres png .. these are different anyway,
> the low res png has some anti aliasing
>
> Hans
>
>
>
> -
> Hans Hagen | P
in desribing what you expect because i
don't see it ... there's a pdf and lowres png .. these are different
anyway, the low res png has some anti aliasing
Hans
-
Hans Hagen | PRAGMA ADE
Hi again,
Many thanks to Hans and Hans and Henri.
The solution (going to low level) provided by Hans works fine.
Best
Thierry
Le Monday 23 Aug 2021 à 17:13:00 (+0200), Hans Hagen a écrit :
> On 8/23/2021 4:46 PM, Thierry Horsin via ntg-context wrote:
> > Hi everybody.
> >
> &
gt; different name) ?
> > > I could provide a same fixed seed in both files, but for some
> > > reasons I would like to re-use some previous results of
> > > math.random() for which no seed was initially given in another .tex
> > > file.
> > You have to go low lev
th files, but for some reasons I
>> would like to re-use some previous results of math.random() for which no
>> seed was initially given in another .tex file.
> You have to go low level ...
>
> % \ctxlua{utilities.randomizer.setseed(0x1.0741c18b8a4ep-6)}
> % \ctxlua{util
ue to have the same result of
math.random() upon typesetting another file (with a different name) ?
I could provide a same fixed seed in both files, but for some reasons I would
like to re-use some previous results of math.random() for which no seed was
initially given in another .tex file.
You have
) in luametatex the inserts can bubble up
which means that footnotes eventually will end up at the outer level.
So, if you use lmtx, ideally there is no need to use postponing (you
can try your exapmle in lmtx without postponing).
For the curious ... the low level mechanisms involved in this can
postponing (you can
try your exapmle in lmtx without postponing).
For the curious ... the low level mechanisms involved in this can also
be used for other purposes although currently this is not done. There is
plenty of relative new functionality that can/will be applied some day.
Here
Wolfgang), I have to create a solution environment like the attached image.
My problem is adjusting the length of the frame.
Thank you.
Fabrice
\setupbodyfont[newcomputermodern-book,11pt]
\defineframed
[ACFRAME]
[frame=off,
width=fit,
align=flushleft,
location=low
you.
> Fabrice
>
> \setupbodyfont[newcomputermodern-book,11pt]
>
> \defineframed
>[ACFRAME]
>[frame=off,
> width=fit,
> align=flushleft,
> location=low,
> background=color,
> backgroundcolor=lightgray,
> foregroundcolor=,
>
\setupbodyfont[newcomputermodern-book,11pt]
\defineframed
[ACFRAME]
[frame=off,
width=fit,
align=flushleft,
location=low,
background=color,
backgroundcolor=lightgray,
foregroundcolor=,
foregroundstyle=]
\startuseMPgraphic{acframe}
fill OverlayBox
]
[frame=off,
width=fit,
align=flushleft,
location=low,
background=color,
backgroundcolor=lightgray,
foregroundcolor=,
foregroundstyle=]
\setupenumerations
[before={\blank},
after={\blank},
alternative=top,
title=yes,
titleleft={},
titleright
nd quality data files.
>>>>> Does this help?
>>>>> <https://www.naturalearthdata.com>
>>>> i was halfway writing as reader for that fiel format when i noticed that
>>>> is is also quite low res so i gave up on that and started playing
>>
gt;>>> On 15 Jul 2021, at 18:58, Hans Hagen wrote:
>>>>>
>>>>> I was wondering about that too. I admit that I looked into maps years ago
>>>>> but never could find quality data files.
>>>> Does this help?
>>>> <https:
into maps years ago but
never could find quality data files.
Does this help?
<https://www.naturalearthdata.com>
i was halfway writing as reader for that fiel format when i noticed that is is
also quite low res so i gave up on that and started playing (extending) with an
more inter
ering about that too. I admit that I looked into maps years ago
>>>> but never could find quality data files.
>>> Does this help?
>>> <https://www.naturalearthdata.com>
>> i was halfway writing as reader for that fiel format when i noticed that is
>> is a
find quality data files.
>> Does this help?
>> <https://www.naturalearthdata.com>
> i was halfway writing as reader for that fiel format when i noticed that is
> is also quite low res so i gave up on that and started playing (extending)
> with an more interesting alternativ
reader for that fiel format when i noticed that
is is also quite low res so i gave up on that and started playing
(extending) with an more interesting alternative that mojca and i wrote
years ago at a meeting
mp.inject.path(t)
end
\stopluacode
\startMPpage
draw lua.mp.maptopath("slovenia.dat") ;
\stopMPpage
\startMPpage
draw lua.mp.maptopath("usa1.dat") rotated 90 ;
\stopMPpage
\startMPpage
draw lua.mp.maptopath("usa2.dat") ;
\stopMPpage
\stoptext
w
2:3: #1<-oeps
2:4: {\hbox}
2:5: {entering adjusted hbox group (level 2) at line 10}
and the second one:
2:3: \MyPrimitiveCommandB
2:4: {\hbox}
2:5: {entering adjusted hbox group (level 2) at line 11}
not that users do much tracing, but sometimes it helps not to see
clutter in the log for (e.g
}
=
x^1_2^^3__4
$
\stopTEXpage
% a few helpers ... do we need more like that ... we realy want to avoid
% ugly low level messing around (these \, etc are also kind of ugly)
\startTEXpage
$
x\supscr [2pt]{1}
\subscr [3pt]{2}
= x\supsubscr[2pt]{1}{2}
= x\supsubscr[2pt]{1}{2
randomizer? I have no idea what goes on
behind my user interface. Others maybe do.
Another example: The problem only appears when using start-/stopexceptions. Is
there a connection between exceptions and random output on the level of low
level code, maybe?
maybe you have two similar exceptions
that Hans (and Wolfgang et al.) know how things are chained
together.
For example: Which ConTeXt command uses randomizer? I have no idea what goes on
behind my user interface. Others maybe do.
Another example: The problem only appears when using start-/stopexception
first have to
check if we need to add some to the xml definitions
(btw, the lmt metapost commands i.e. the key/value macros fit in well in
the optional argument appeoach, the more low level ones more resemble
the low level context commands for which we have specific definitions)
Whatever you
of the insert interface in
context a bit more (because we use accessors instead of boxes) and
hopefully I didn't forget one. We'll see. Once I'm confident with the
new approach we'll switch to that (low level) interface model and can
progress. Because users don't use inserts directly themselves
h
> > had been requested in the past for t-vim). See the attached file.
> >
> > BTW, shouldn't we have `features=none` in the default mono font setup so
> > that this doesn't happen anyways?
> afaik we already do that
>
> (i'll add some more control, already added
=no]
here)
I need to find a reasonable way to provide control over all these things
... real low level btw is \hyphenationmode\zerocount ... look in
lang-ini.mkxl for all possible flags)
Hans
CFF2 CharStrings of this
> > glyph invokes the rrcurveto operator with 63 arguments, which is
>
> 66 etc .. multiples of 6
Counting is hard... (I assumed that all arguments are created through
blend operators)
>
> > allowed in CFF2 where the argument limit is 513, but
.
a rather low limit right from the start (we can assume only rrcurveto is
affected)
It would be great if ConTeXt could check for this and insert additional
rrcuveto operators when necessary to avoid this issue.
after some experiments ... attached
(no upload yet as i'm renaming some low level
.
At the engine level there is also some occasional cleanup, like
replacing some left-over low level 5.2/5.3 lua api things by 5.4 but
that's kind of ongoing (as lua progresses). In principle users should
not notice such changes, just like probably no one noticed that we now
use a different zip
Hi,
I uploaded a new lmtx version. The update mostly concerns part of the
low level mp-tex interface, a side effect of updating some mechanisms
(one of which MF currently is extending).
Hopefully it won't break users code that uses low level mp-tex interface
features but anyway, if needed
erl programs from TL that use
% additional modules we don't provide. The TL Perl does provide all the
% standard Perl modules.
%
%TEXLIVE_WINDOWS_TRY_EXTERNAL_PERL = 0
%
Part 3: Array and other sizes for TeX, Metafont, etc.
%
% If you want to change some of these sizes only for a certain
xpr(\fontchardp#1\c_math_strut/\glyphscale)*\mathscale#1\relax}
\protect
this sort of excessive scaling has to do with the new (more efficient)
low level scaling model that we're going to switch to later this year,
you can test that by putting this at the top of the file (document
wide sett
\s!depth
\dimexpr(\fontchardp#1\c_math_strut/\glyphscale)*\mathscale#1\relax}
\protect
this sort of excessive scaling has to do with the new (more efficient)
low level scaling model that we're going to switch to later this year,
you can test that by putting this at the top of the file (docum
ord seperators:
\startTEXpage \hsize3mm
firstpart\char"002D secondpart\blank
firstpart\char"2010 secondpart\blank
firstpart\char"2013 secondpart\blank
firstpart\char"2014 secondpart
\stopTEXpage
will work ok. There are provisions for those characters being
he metafun todo files
> I ended up at the fancy shape part (parshapes) running over multiple
> paragraphs and decided to provide a (kind of low level) interface that
> integrates that. The example code is a few decades old but still works ok (i
> might try to improve them a bit some day
Hi,
I uploaded a new lmtx. As I'm currently going through the metafun todo
files I ended up at the fancy shape part (parshapes) running over
multiple paragraphs and decided to provide a (kind of low level)
interface that integrates that. The example code is a few decades old
but still works
t; >
>>> https://tex.stackexchange.com/questions/400257/tag-equation-in-context-with-arbitrary-text
>>> > <
>>> https://tex.stackexchange.com/questions/400257/tag-equation-in-context-with-arbitrary-text
>>> >
>>> >
>>> > but none of them
with
the latest luametatex/lmtx combination. It was crosscompiled on an
intel mac which took ages so it stuck as experiment. Because th eintel
bin runs on the arm mac it has a low priority (unless someone donates
an arm mini to the farm). So, forget about the arm apple bins for now.
We do generate windows
eintel bin
runs on the arm mac it has a low priority (unless someone donates an arm
mini to the farm). So, forget about the arm apple bins for now.
We do generate windows arm but that's because it's easy to do, boit that
we have a machine to test if it actually works.
Btw, in the latest upload
y-text
>> > <
>> https://tex.stackexchange.com/questions/400257/tag-equation-in-context-with-arbitrary-text
>> >
>> >
>> > but none of them works as expected (either the formula counter is still
>> > incrementing with arbitrary conversions or cros
t
> >
> >
> > but none of them works as expected (either the formula counter is still
> > incrementing with arbitrary conversions or cross-references don't work).
>
> Define 'expected' ... \eqno is something low level (a primitive) and we
> have that nilled at the us
tag-equation-in-context-with-arbitrary-text>
but none of them works as expected (either the formula counter is still
incrementing with arbitrary conversions or cross-references don't work).
Define 'expected' ... \eqno is something low level (a primitive) and we
have that nilled at the user
ere we dropped jit and have a less performing backend we expect to
> need more runtime but in the meantime we're quite okay. Not only the engine
> is faster, but also some low level macros benefit a bit from new features. I
> don't know how much lua speedup plays a role but probably not that m
to need more runtime but in the meantime we're quite okay. Not
only the engine is faster, but also some low level macros benefit a bit
from new features. I don't know how much lua speedup plays a role but
probably not that much. For 448 pages (some 20 more than we had before)
we now need 16.5
illa {e} == \\c{e}
> \withogonek {e} == \\k{e}
>
> Did I miss one?
>
> Then we can deprecate the short ones (keep them a low profile, with
> permission to overload). After all, I don't expect someone who needs lots of
> them to use these commands, so more ve
{e} ==
\\u{e}\withdot {c} == \\.{c}\withdieresis{e} ==
\\"{e}\withring{u} == \\r{u}\withhungarumlaut{u} ==
\\H{u}\withcaron {e} == \\v{e}\withcedilla {e} ==
\\c{e}\withogonek {e} == \\k{e}
Did I miss one?
Then we can deprecate the short ones (keep the
them a low profile, with
permission to overload). After all, I don't expect someone who needs
lots of them to use these commands, so more verbose is better then. Aas
I already mentioned, in bib files they are treated differently already.
The low level helper is \chr, that can be used as
\ch
in user group journals and so
but anyway it's kind of new and i still need to flag all visible (low
level) macros and variables (still some 700 to go)
the same is also done for metafun (mostly done but also some to go)
it roughly works as follows:
- primitives are marked as 'primitive
ot* overload commands because there are either
> > alternative ways to achieve the desired result or other commands which
> > can be used.
> >
> >
> > \overloadmode=4
> >
> > \starttext
> >
> > \permanent\def\mycommand#1{[#1]}
> >
> &g
nd{New definition}
\stoptext
Wolfgang
Thank you, Wolfgang (and Hans),
The hook is perfect for this. I had avoided that construction for a long
time thinking that it is too low-level, but looking at it again it seems
to be the right thing here.
I can find no information on \aliased and the pu
[mill.png][height=12pt]
\stopsetups
\startsetups box:demo:106
\externalfigure[hacker.jpg][height=12pt]
\stopsetups
\registerboxglyph category {demo} unicode 103 \relax % rather low level
for now
\registerboxglyph category {demo} unicode 104 \relax % rather low level
for now
\registerboxglyph
par
which cheats on cut and paste (if you know where to click). (It actually
will replace something more low level which is probably not used
anyway.)
Hans
-
Hans Hagen |
Hi,
I'm playing with future font trickery and as a consequence touching some
low level font code. Now, of course we want to be compatible but it
might be that I mess up something the process. At some point I'll do a
more drastic split in the code paths (because when we use these new
tricks
, should not be too hard to solve (with an example) ... keep in mind
that there is no functionality difference between mkiv and lmtx
(although lmtx will evolve), so maybe some oversight in upgrading the
low level interfacing macros (removing indirectness)
2. For some reason, lmtx introduces lots
but for now use a low level
\glyphscale command that takes a number (in goodl old tex tradition a
scale of 1.0 is entered as 1000).
(5) The implementation can be improved a bit (performance wise). There
is a bit more overhead involved but usually I can compensate that.
(6
tafun and
use that (quite efficient too) and then one can even cut'n'paste those
tiny symbols (don't worry ... not much of a challenge so low on my list)
Hans
-
Hans Hagen | PRAGMA ADE
... redefing dotlabel in a compatible way is kind of
ok, but using/redefining \foo_bar_something_internal is a real bad idea
as that is not part of the interface (okay, i know that there are macro
packages out there where it's part of the concept to redefine low level
stuff for styles
bit it takes 32.5 sec
(ubuntu, ssd on usb 3). The Windows Linux Subsystem (version 1) takes
some 11.5 seconds and the domotica fitlet with a low power AMD A10
needs 27.5 sec.) The ratios match measurements of a while ago. In the
meantime the format file got smaller, memory more dynamic
t; just good old intel and arm it is.)
>
> On my rusty laptop the luametatex manual takes between 10 and 10.5 sec
> (depending on load). On the raspberry pi 64 bit it takes 32.5 sec
> (ubuntu, ssd on usb 3). The Windows Linux Subsystem (version 1) takes
> some 11.5 seconds and the domotica fit
manual takes between 10 and 10.5 sec
(depending on load). On the raspberry pi 64 bit it takes 32.5 sec
(ubuntu, ssd on usb 3). The Windows Linux Subsystem (version 1) takes
some 11.5 seconds and the domotica fitlet with a low power AMD A10 needs
27.5 sec.) The ratios match measurements of a while
rks in LMTX when marked lines are removed, but\unknown
\stopelement % <---
\stoptext
ha, i was to optimistic about using some low level macro (needs to
extend it)
xt
> > \section{a}
> > \blank[-2cm,force]\
> > \section{b}
> > \section{c}
> > \stoptext
> >
> > The empty space (\ ) after the \blank is necessary here, without which
> the \blank does nothing.
> > I would like to ask whether there is
> The empty space (\ ) after the \blank is necessary here, without which the
> \blank does nothing.
> I would like to ask whether there is a less hacky way to let \blank work than
> the hidden space.
You c
Hi all,
in a typing environment, I have the problem that not every line is
numbered:
\definetyping
[code]
[numbering=line,
escape={@[,@]}]
\setupcolors[state=start]
\definecolor[nonsigpart][r=.7,g=.7,b=.7]
\defineframed[nonsig]
[location=low
ateinserts % nop in LMTX
\showframe
\setupcaptions[
headstyle={\ss\bfx},
align={flushleft,high},
prefixsegments=none,
location={bottom,low},
hang=yes,
]
\setupfootnotes[
width=\textwidth,
]
\starttext
\startplacefigure[location=page,title={\fakewords{5}{7}\footnote{\fakewords{20}{30}}}]%
overview of the three successive context versions. The second one is
about the state of luametatex and the third discusses a couple of things
introduced last year (luametatex and lmtx). The tokens talk is for low
level tex lovers (or those who need to impress other texies with token
speak), an
string for you to modify.
Many thanks for your explanation, Taco.
> Also, the special (catcode, space handling) rules for setups and \cldcontext
> do not help you.
>
> That does not mean it can’t be done. As I don’t know a of a nice way,
> here is a low-level ‘ugly' way:
>
ty much always ‘a way’, but I do not know of a ’nice’ way.
Your problem is that lxml.flush() and friends do not return a value,
they just do a direct context(‘’) call behind the scenes with no
return string for you to modify.
Also, the special (catcode, space handling) rules for setups and \
the earlier example (Aditya's with my minor
'centering' adjustment)) or yours, I agree - the number is just a bit too low,
and of course, using this method we probably can't make adjustments to that. So
ultimately it looks like I'll have to get my skills up to working with layers
as well
Hi Julian,
Indeed you can modify slightly what Aditya said to obtain what you want: you
can put the overlay into a framed environment as in the following example.
Though, to my taste the number is a little bit too low…
%% begin example
\setuppagenumbering[state=start,location=footer
Hi,
One can suppress hyphenation with:
\setupalign[nothyphenated]
but it has some limitations. The low level switches are \nohyphens and
\dohyphens. Anyway, this mechanism has now been improved a bit:
\starttext
\startbuffer
NEDERLANDS\par Nederlands\par nederlands\par
\CONTEXT \par
a side effect it can be that
> existing code (lmtx only) will behave differently (will be fixed when we
> notice) but also that some low level user tweaking can not work, i.e.
> they are just ignored, but only when they happen mid paragraph which
> actually is always debatable anyway.
Hi Hans,
man
predictable behaviour. As a side effect it can be that existing code (lmtx
only) will behave differently (will be fixed when we notice) but also that some
low level user tweaking can not work, i.e. they are just ignored, but only when
they happen mid paragraph which actually is always debatable anyway
ctable behaviour. As a side effect it can be that existing code (lmtx
> only) will behave differently (will be fixed when we notice) but also that
> some low level user tweaking can not work, i.e. they are just ignored, but
> only when they happen mid paragraph which actually is always deb
(will be fixed when we
notice) but also that some low level user tweaking can not work, i.e.
they are just ignored, but only when they happen mid paragraph which
actually is always debatable anyway.
Now, if for some reasom you get unexpected results and can't wait for a
fix, you can do
On 7/29/2020 6:11 PM, Marcel Fabian Krüger wrote:
there have been a couple of bug fixes after the formal 5.4.0 release but afaik
not in the virtual machine code (which normally is the most sensitive); i used
to mark low level changes so that it got signaled (in context) but the byte
code
> there have been a couple of bug fixes after the formal 5.4.0 release but
> afaik not in the virtual machine code (which normally is the most sensitive);
> i used to mark low level changes so that it got signaled (in context) but the
> byte code version info changed late in
. I didn't test
other platforms yet)
there have been a couple of bug fixes after the formal 5.4.0 release but
afaik not in the virtual machine code (which normally is the most
sensitive); i used to mark low level changes so that it got signaled (in
context) but the byte code version info changed
loe level improvements in the
> engine or the core of context (we do so in articles and wrapups), and
> much goes unnoticed anyway (which is good). But ... the last couple of
> weeks we have been playing with some adapted functionality in lmtx and
> some of the experimental low level code ha
of the experimental low level code has now made it in core.
Normally users will not notice this but who knows.
There are already features in lmtx that are not (and are unlikely to be)
in mkiv (most significant in the metapost related part). When possible
new macros and additions to mechanism
n I was a teenager, so I'm not
sure I want to try it now. Thanks, Hans!
It's low level mkii, never meant for usage outside core code (in this
case in mkii it is used for typesetting color overviews); mkiv still has
the same high level commands but different low level ... nothing to
worry
/popmacro either and now it's in my
to-do readings).
Just wondering ... are there specific low level hel;pers (wrt strings)
that you need in context?
Hans
-
Hans Hagen | PRAGMA ADE
Hi,
> On 25 Jun 2020, at 12:37, Gerben Wierda wrote:
>
> According to the XML manual:
>
> << 2.1 >> TEX versus LUA
>
> It will not come as a surprise that we can access xml files from TEX as well
> as from Lua. In fact there are two methods to deal with xm
%
{\doifelsesometoks\scratchtokstwo
{\appendtoks,{#1}\to\scratchtokstwo}
{\scratchtokstwo{{#1}}}%
\doscriptscheck}
% % a bit more low level:
% \unexpanded\def\scripts
% {\scratchtoksone\emptytoks
%\scratchtokstwo\emptytoks
%\doscriptscheck}
%
% \def\doscriptscheck
% {\doifnextcharelse
According to the XML manual:
<< 2.1 >> TEX versus LUA
It will not come as a surprise that we can access xml files from TEX as well as
from Lua. In fact there are two methods to deal with xml in Lua. First there
are the low level xml functions in the xml namespace. On top of tho
Hi,
I uploaded a new version (both mkiv and lmtx). We removed some low level
no longer used code (older engines), normalized some in the process,
fixed a few things, etc.
=== lmtx only ===
While updating the cld manual I decided to also add an other table
mechanism (in addition to the one
201 - 300 of 1629 matches
Mail list logo
