and
changed the text primitives to use low chars. This renders fine on
all PDF viewers I found (text is garbled, of course), but it still
doesn't print. So now I'm fairly sure now the bug is in the font stream.
foo.doctored.pdf
Description: Adobe PDF document
I finally found a tool
arse
I found another minor nit that's not really triggering a bug but still a
difference to LuaTeX: \eTeXrevision should expand to .2, but it
expands to 2 in MkIX. There is some code out there which uses
constructions like
\number\eTeXversion\eTeXrevision
or even
\ifdim 0\XeTeXrevision pt > 0.9996pt
A
mpatibility to agree with the
original TeX \meaning strings for the 7-bit ASCII subset at least.
I found another minor nit that's not really triggering a bug but still a
difference to LuaTeX: \eTeXrevision should expand to .2, but it
expands to 2 in MkIX. There is some code out there which uses
> ... which means that you can use that at the context end as well
> > (old feature).
> > > Save the following as test.mkix (or add "% macros=mkix" as the
> > first line):
> > >
> > > ```
&g
gt; \startluatemplate
> >
> >\starttyping
> >A and not B
> >\stoptyping
> >
> >\starttyping
> >not (A and not B)
> >\stoptyping
> >
> > \stopluatemplate
> > \stoptext
> >
> > Wh
) and then processes it using the mkix conversion
mechanism. Thus, in terms of output, it should be equivalent to:
\enablemode[A]
\starttext
\startbuffer[luatemplate]
\starttyping
A and not B
\stoptyping
\starttyping
not (A and not B)
\stoptyping
\stopbuffer
\saveb
er the following example:
\enablemode[A]
\starttext
\startluatemplate
\starttyping
A and not B
\stoptyping
\starttyping
not (A and not B)
\stoptyping
\stopluatemplate
\stoptext
What I am thinking is that \startluatemplate ... \stopluatemplate grabs the
content (like a buffer) and the
(old feature).
> Save the following as test.mkix (or add "% macros=mkix" as the
first line):
>
> ```
> \starttext
>
> \starttyping
> A and not B
> \stoptyping
>
> \starttyping
> no
; ... which means that you can use that at the context end as well
> > (old feature).
> > > Save the following as test.mkix (or add "% macros=mkix" as the
> > first line):
> > >
> > > ```
> > > \starttext
>
gt;
>> if tex.modes["A"] and not tex.modes{"B"] then
>> ...
>> end
>
> ... which means that you can use that at the context end as well
(old feature).
> Save the following as test.mkix (or add &quo
n
> >> ...
> >> end
> >
> > ... which means that you can use that at the context end as well (old
> feature).
> > Save the following as test.mkix (or add "% macros=mkix" as the first
> line):
> >
> > ```
> > \starttext
> >
ing as test.mkix (or add "% macros=mkix" as the first line):
```
\starttext
\starttyping
A and not B
\stoptyping
\starttyping
not (A and not B)
\stoptyping
\stoptext
a neat application!
Hans
-
On Sat, 20 Mar 2021, Christoph Reller wrote:
> Of course we can do this in lua:
>
> if tex.modes["A"] and not tex.modes{"B"] then
> ...
> end
... which means that you can use that at the context end as well (old feature).
Save the following as test.mkix (or ad
-ade.com/general/manuals/cld-mkiv.pdf
Unfortunately I haven't finished the new detailed font manual yet.
Hans
Had already seen templates-mkiv.pdf on the website: so we're talking
mkix and mkxi now, eh? One day you will regret having used roman
numerals, when we reach mkcccil or something
guess because mkvi has four letters like mkii and mkiv but mkv ha only three.
So the next versions will be mkix, mkxi, mkxv, mkxx, mkxl, mkli, mklv, and
mkxc. It is gonig to get confusing real soon :)
BTW, does anyone has a minimal example on how to use mkvi syntax. I tried
a few examples
15 matches
Mail list logo
