Am 11.08.25 um 17:43 schrieb Hans Hagen via ntg-context:
On 8/11/2025 5:24 PM, John Was wrote:
Hello
In XeTeX, for emergencies (e.g. two lines left dangling on the last
page of a chapter) I keep in reserve:
\def\tightspaceskip{\spaceskip 0.15em plus 0.2em}
\def\verytightspaceskip
On 8/11/2025 5:24 PM, John Was wrote:
Hello
In XeTeX, for emergencies (e.g. two lines left dangling on the last page
of a chapter) I keep in reserve:
\def\tightspaceskip{\spaceskip 0.15em plus 0.2em}
\def\verytightspaceskip{\spaceskip 0.125em plus 0.15em}
These seem both to work in
Hello
In XeTeX, for emergencies (e.g. two lines left dangling on the last page of
a chapter) I keep in reserve:
\def\tightspaceskip{\spaceskip 0.15em plus 0.2em}
\def\verytightspaceskip{\spaceskip 0.125em plus 0.15em}
These seem both to work in ConTexT - of course you can fiddle till you come
terlinear spacing. If I wanted to do the same in ConTexT, what would
>> > be the preferred method (both in the preamble and in the text itself)?
>>
>> Native support for Unicode in plain TeX is possible since more than 2
>> decades with the introduction of XeTeX.
>
> small scans that appeared in running text without disturbing the
> > interlinear spacing. If I wanted to do the same in ConTexT, what would
> > be the preferred method (both in the preamble and in the text itself)?
>
> Native support for Unicode in plain TeX is possible since more than
do the same in ConTexT, what would
be the preferred method (both in the preamble and in the text itself)?
Native support for Unicode in plain TeX is possible since more than 2
decades with the introduction of XeTeX.
Ideally I would want the label option to work for the benefit of any
On 8/8/2025 9:21 PM, user691586 via ntg-context wrote:
I meant of course "natively active in Plain TeX". I was referring to the
format, and applies to the pdftex, xetex, luatex engines too.
it is unrelated to engines: any can define any character active
what luametatex adds is mor
matters, and I was
aiming at re-using code as is in context.
in what sense natively .. all characters can be active and i bet that in
plain (and maybe also latex) the quite (') is active in math
in context | is actuallly active
side note:
- in mkii (pdftex,xetex) we use what we call
I meant of course "natively active in Plain TeX". I was referring to the
format, and applies to the pdftex, xetex, luatex engines too.
___
If your question is of interest to others as well, please add an en
Thanks Mikail
I'll look into this when I'm back at my desk. In XeTeX I'm used to
looseness always working when the number is positive (generally just 1, of
course), even if that produces horrible interword spacing, while if the
number is negative it sometimes doesn't work
, and so on. I
can do all these in XeTeX but realize I may have to accept some
compromise in ConTeXt. The one thing I think wouldn't be acceptable is
the note numbers standing to the left of the text area.
Do you have a example (input + output)?
tures such as fitting a short note within the break line
of a previous longer note, centring two (or more) short notes at the foot
of a page with a 24pt gap between each, adding a 3pt space at the end of a
note which has overrun onto the next page, and so on. I can do all these
in XeTeX but realize
kerville in
> > particular (though after just a few days I can't claim any expertise in
> > reading ConTexT log files). But it does seem to want to survey the
> > entire database of fonts, whether or not I need them.
> >
> > I don't know if it would help to ca
ed, e.g. (from my days of typesetting the *Medieval Latin
Dictionary from British Sources*), in XeTeX style:
\font\mldrten="[D:/BACKUPS/FONTBKUP/MLD/MLD-Regular.ttf]" at 10pt
Best wishes
John *🇪🇺 * Слава Україні!
* 🇺🇦*
<http://www.avg.com/email-signature?utm_medium=email&
s file
location, which I have occasionally had to do for exotic sorts that are
rarely required, e.g. (from my days of typesetting the /Medieval Latin
Dictionary from British Sources/), in XeTeX style:
\font\mldrten="[D:/BACKUPS/FONTBKUP/MLD/MLD-Regular.ttf]" at 10pt
Does it make a
dword{abolished}
\hyphenatedword{contributes}
\stoptext
At the moment I am using XeTeX-type font calls while I work out other
aspects of ConTexT. If that is all that is holding things up I can go
over to ConTexT's native system if necessary, though in a typical file
header I would have
Hello
The file uhyphens.tex is just a list of word hyphenations where I don't
agree with the breaks that TeX gives (I insist on pre-1980s rules for
English!). For example:
\hyphenation{%
.
abo-lished
.
con-tri-butes
.
}
At the moment I am using XeTeX-type font calls while I
nt a yogh and am obliged to use a
particular typeface (because of house style for a journal or book
series) that doesn't have the character, I would give in the file header
in XeTeX:
\catcode"0292=\active
\defʒ{\yogh}
(I have \yogh defined as 'put \char"0292 here, groupe
Hello Taco
That's very interesting - slightly different from XeTeX (\def\def instead
of \def, for example), but I think I'll be able to work things out from
there. Many thanks.
Best wishes
John *🇪🇺 * Слава Україні!
* 🇺🇦*
<http://www.avg.com/email-signature?utm_medium=ema
nted that I can't use \catcode = \active to do anything
> useful - I do often use that, particularly to fetch a character not in the
> typeface. For example, if I want a yogh and am obliged to use a
> particular typeface (because of house style for a journal or book series)
>
I can't use \catcode = \active to do anything useful -
> I do often use that, particularly to fetch a character not in the typeface.
> For example, if I want a yogh and am obliged to use a particular typeface
> (because of house style for a journal or book series) that doesn
face (because of house style for a journal or book series)
that doesn't have the character, I would give in the file header in XeTeX:
\catcode"0292=\active
\defʒ{\yogh}
(I have \yogh defined as 'put \char"0292 here, grouped within {}, from
Junicode'.) That allows me to keep
font, and that the equivalent
in XeTeX works as expected for both opening and closing marks.
What you see for the closing quotation mark are two single quotation
marks which are the same character as the apostroph but you don't get
the correct double quotation mark.
While the best solu
Thanks for the prompt response. Something not too obtrusive would be ideal
- though of course I could always just introduce the correct opening
quotation mark by search and replace. It's odd that trep = yes works for
closing quotation marks in this font, and that the equivalent in XeTeX
wor
Hello
I have found that trep=yes gives me correct closing quotation marks in the
commercial font Baskerville MT Pro if I type the simple ' as usual in TeX;
but opening quotation marks remain as ` or ``.
In XeTeX I could get round this with e.g.:
\catcode"0060=\active% 0060 is the po
th the fontcall system I'm used to:
> >>
> >> \font\umirtenpointsevenfive = "MinionPro-Regular:+onum:mapping=tex-
> >> text:letterspace=1.6" at 10.75pt
> >
> > Not clear to me what the second command (after `\font`) means in plain
> > Engli
7;t generate an error, but when you actually
try to use pstricks it fails - but there will be another way). Edmac is
not likely to be needed for the books I have in mind, but it is
essential for editions that I typeset from time to time with XeTeX and I
don't think anything else will give
to use pstricks it fails - but there will be another way). Edmac is not
likely to be needed for the books I have in mind, but it is essential for
editions that I typeset from time to time with XeTeX and I don't think
anything else will give me the same control (surprisingly, in ConText
ex-
text:letterspace=1.6" at 10.75pt
Not clear to me what the second command (after `\font`) means in plain
English.
The context version is
\definefont [umirtenpointsevenfive] [file:MinionPro-Regular*
at 10.75pt]
and it creates the font switch \umirtenpointsevenfive like the x
On 6/14/25 12:37, John Was wrote:
> Good day, Contexters
Hi John,
welcome to the mailing list.
> I've been using plain TeX for many years (EmTeX, if anyone can remember
> that, and latterly XeTeX), but my motivation for getting acquainted with
> ConText, rather late in lif
Good day, Contexters
I've been using plain TeX for many years (EmTeX, if anyone can remember
that, and latterly XeTeX), but my motivation for getting acquainted with
ConText, rather late in life, is the need to produce tagged PDFs that will
be accessible to the visually impaired (generally
Hi Hraban,
On Sun, May 4, 2025 at 6:44 PM Henning Hraban Ramm wrote:
>
> I found this interesting: https://crates.io/crates/talmudifier
> (it uses a Rust version of XeTeX)
>
> Is such a layout a challenge for the new columns engine?
Didn't we discuss this kind of layout at
I found this interesting: https://crates.io/crates/talmudifier
(it uses a Rust version of XeTeX)
Is such a layout a challenge for the new columns engine?
The description of the algorithm reads like ConTeXt should be able to do
it better/faster.
Hraban
fonts are implemented like traditional tex fonts. This
makes math in the engine behave like xetex. The primitives that relate
to controling some aspects of math rendering are obsolete (we also
removed experimental additional italics mode code). This change doesn't
affect ConTeXt (MkIV) be
Jürgen Hanneder via ntg-context schrieb am 10.08.2024 um 11:10:
Dear Richard,
Are you after a Context version of something such as
Xetex Devanagari?
https://github.com/wujastyk/xetex-devanagari
Indeed. In my XeTeX publications settling the font was quite
straightforward:
\usepackage
Dear Richard,
Are you after a Context version of something such as
Xetex Devanagari?
https://github.com/wujastyk/xetex-devanagari
Indeed. In my XeTeX publications settling the font was quite straightforward:
\usepackage{polyglossia,fontspec,xunicode}
\setmainfont{Adobe Text Pro
Hello Jürgen,
Are you after a Context version of something such as
Xetex Devanagari?
https://github.com/wujastyk/xetex-devanagari
Best, Richard
--
T +6433121699 M +64210640216
rmaho...@indica-et-buddhica.org
https://indica-et-buddhica.com/
Indica et Buddhica
Littledene Bay Road Oxford
That's it! Many thanks to Hans, Hraban and especially Wolfgang for his
solution. This environment should become part of ConTeXt!
I have been a LaTeX/XeTeX/LuaLaTeX user for over 30 years and used it to
write my papers during my studies and use it for almost all my writing.
Now I wanted t
5 sec) but LMTX generates more pages so it is
> > faster.
>
> puzzling
>
> > Of course, this is a meaningless experiment from a practical point of view
> > as a 1000 page document will be more complex than just text.
> % engine=pdftex 1.2
> % engine=luatmetate
iment from a practical point of view as a
1000 page document will be more complex than just text.
% engine=pdftex 1.2
% engine=luatmetatex 1.6
% engine=luatex 1.8
% engine=xetex 2.4
\starttext
\dorecurse{500} {
\input knuth \par
}
\stoptext
125 pages, so how does your test
8 AM
Subject [NTG-context] Re: Toggling the symbol for the zero-width joiner and
related Unicode control characters
(It seems he never considered making it an opentype feature in the font itself,
but since his focus is/was XeTeX/HB (HB is rather rigid and dictatorial) I
guess that's not surpri
lt, as do other Arabic fonts.
(It seems he never considered making it an opentype feature in the font itself,
but since his focus is/was XeTeX/HB (HB is rather rigid and dictatorial) I
guess that's not surprising.)
I admit that I don't follow what happens with xetex (they changed the
s he never considered making it an opentype feature in the font itself,
but since his focus is/was XeTeX/HB (HB is rather rigid and dictatorial) I
guess that's not surprising.)
But therein lies the problem: ConTeXt shows the rendering by default, and we
need to turn it off. Since most non-
d plans at
meetings.
Also keep in mind that we're talking frontend here; omega is dvi based
so like regular tex and etex whatever it does with fonts is not really
related to the engine bu tup to the backend: the engine only needs
metrics (omega extended tfm into ofm for that).
pdftex brought
rbon footprint lasted more
on books than on shelves really, not for selling out fast but rather
discontinued quickly) and that its goal was solely within this input
processing spectrum. Because it wasn't.
Or heck
or heck. Let's go even further. By making the dubious assertion
that we'
processing
and th efont part was mostly going beyond 8 bit fonts but i might have
missed something (omega was never productin ready).
It is xetex that hooked into opentype although pdftex can actually deal
with truetype fonts to some extend. Before there was something
'opentype
ng if LuaTeX is better than
pdfTeX/XeTeX, and some are complaining that LuaLaTeX is too slow, of
course...)
HR
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-co
ns at once is definitely the correct approach.
That's what the rest of the TeX world already does (at least LuaTeX
and XeTeX; pdfTeX not of course), see
https://github.com/hyphenation/tex-hyphen/blob/master/hyph-utf8/tex/generic/hyph-utf8/loadhyph/loadhyph-sr-latn.tex
We have two s
Yes, loading both patterns at once is definitely the correct approach.
That's what the rest of the TeX world already does (at least LuaTeX
and XeTeX; pdfTeX not of course), see
https://github.com/hyphenation/tex-hyphen/blob/master/hyph-utf8/tex/generic/hyph-utf8/loadhyph/loadhyph-sr-latn.tex
; seen from the user side.
>
> In my case things improved when I switched to Adishila (in XeTeX):
>
> \newfontfamily\sanskritfont[Script=Devanagari,Mapping=RomDev,Scale=1.45]{Adi
> shilaSan}
>
> This is, to my taste, the nicest Sanskrit font, but it is difficult to
>
ave to
do with the Devanagarī font, or its interaction with (Xe)TeX. Perhaps
this is the same phenomenon
seen from the user side.
In my case things improved when I switched to Adishila (in XeTeX):
\newfontfamily\sanskritfont[Script=Devanagari,Mapping=RomDev,Scale=1.45]{AdishilaSan}
This is, to
).
See there : https://ctan.org/tex-archive/macros/xetex/hyphenation/sanhyph
And his involvement in the discussion about Devanagari romanisation for
translitteration and/or specific UTF8 specification in order to respect
Devanagari and Brahmi hyphenation with XeTeX.
https://tug.org/pipermail
/sbin:/Users/rjhb/doc/cvs/rjhb/perl5/bin:.:/Applications/Qt/current/clang_64/bin:/usr/X11/bin
dvipdfmx: /opt/local/bin/dvipdfmx
dvips: /opt/local/bin/dvips
fmtutil: /opt/local/bin/fmtutil
kpsewhich: /opt/local/bin/kpsewhich
luatex: /opt/local/bin/luatex
mktexpk
mplex font context agreed more often with uniscribe
than xetex, but in the end on ehas to make the font okay for all i guess).
When we started with opentype (luatex showed up in 2005) we took
uniscribe as reference so that is our benchmark. And lack of specs made
us figure out things stepwise. No
ke the book
said? These are ‘predefined typescripts’ as the book said after all. Thanks. I
use MacOS if that helps
current version of ConTeXt: 2021.03.05 19:11
looks like you combine some mkii examples (xtx is a mkii xetex file, and
there is no gyr) with mkiv
Here is a simple way:
\definefontfeature
//
TEXINPUTS.luajittex =
$TEXMFDOTDIR;$TEXMF/tex/{luatex,plain,generic,latex,}//
TEXINPUTS.luahbtex=
$TEXMFDOTDIR;$TEXMF/tex/{luatex,plain,generic,latex,}//
TEXINPUTS.luajithbtex =
$TEXMFDOTDIR;$TEXMF/tex/{luatex,plain,generic,latex,}//
TEXINPUTS.dviluatex =
$
On Fri, 30 Apr 2021 at 20:53, Nicola wrote:
>
> This installs and configures repos for Alpine Linux 3.12. Then,
> I install TeX Live as follows:
>
> apk add texlive-full texlive-xetex texlive-luatex texlive-dev
> apk add ghostscript ghostscript-fonts ghostscript
quot;; | tee
-a /etc/apk/repositories
apk update
This installs and configures repos for Alpine Linux 3.12. Then,
I install TeX Live as follows:
apk add texlive-full texlive-xetex texlive-luatex texlive-dev
apk add ghostscript ghostscript-fonts ghostscript-dev
apk add graphics
implemented in pdftex and xetex.
Two TeX January 2021 DEK buglet fixes (H.Hagen)
Mark math glyphs as protected (in order to prevent processing
as text in base mode).
Removed width/ic compensation for traditional math code path.
When restricted system commands is enabled os.setenv has no effect
Hi,
The 2021 texlive code is currently being frozen. This means that Mojca
will check-in the current context release right before tl gets deep frozen.
The MKII code (mkii and mpii files) hasn't changed so it should still
work well with pdftex and xetex although I admit that I haven'
: new method (more lmtx-ish)
(actually with mkii in pdftex we need .3 seconds, xetex freezes with
100K but needs 0.53 for 10K, luatex needs 0.18)
but I'm sure you don't care much about that so I just implements a
variant with warning which takes .19 seconds per 100K so it's a nic
t; school which work ok for virtual constructs that only use those 8 bit
> fonts but often fail for gyre fonts)
>
> now, the gust foundation fonts are a mix: they are opentype, have its
> parameters and properties but have the wrong width and assume the italic
> hackery
>
> the micros
ow, the gust foundation fonts are a mix: they are opentype, have its
parameters and properties but have the wrong width and assume the italic
hackery
the microsoft cambria font is the reference for opentype math (and to
some extend microsoft word also is)
afaik xetex uses the old tex approa
n for a similar book?
I submitted the PDF to the publisher already last August. At the time I was not
yet aware of this happy development in MkIV, and so the book was made with MkII
using XeTeX as the backend. But in view of the various advances that were made
with MkIV, I hope to make the next boo
uggestions).
For those who are curious how I used ConTeXt MkII with the XeTeX backend, a
sample chapter is available at http://e.pc.cd/XlhotalK (and then click on
"Direkt herunterladen").
Robert Zydenbos
___
If
Hans,
just accidentally, I discovered that \XeTeX\ misbehaves:
\starttext
\input{zapf} \XETEX\ \input{knuth}
\stoptext
BTW, this is the MWE after I saw
http://www.pragma-ade.com/general/manuals/luametatex.pdf#page=15.
I hope it helps,
Pablo
--
http://www.ousia.tk
(In the process I saw that I bugged the xetex logo but that has to
wait for a next upload. Hardly critital I suspect.)
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8
p less but who knows. It's not easy to squeeze out
> more (the bottleneck is in the lua code as the (con)tex(t) code is
> pretty efficient so we pay a price for flexibility).
>
> (In the process I saw that I bugged the xetex logo
ex(t) code is
pretty efficient so we pay a price for flexibility).
(In the process I saw that I bugged the xetex logo but that has to wait
for a next upload. Hardly critital I suspec
improved.
There's no reason why it wouldn't load both scripts at the same time
(at least for Unicode engines, which is the only thing that's
currently supported anyway).
This is what XeTeX loads, for example:
https://github.com/hyphenation/tex-hyphen/blob/master/hyph-utf8/tex/gen
p and also The Tectonic Typesetting System (
> https://tectonic-typesetting.github.io/en-US/).
What are you even talking about? ConTeXt has been using a forked TeX
engine for at least a decade. LuaTeX is solely developed by and for the
ConTeXt people.
BTW, SILE is something completely different (and can't
dentLine
>>
>> > above\\% to demonstrate that the lines are being stacked as
>> > normal\rotatebox{-90}{%\XeTeXupwardsmode1\\% successive lines will be
>> > stacked upwards instead of downwards\begin{minipage}{4em}% this will be
>> > the vertical length o
ᡤᡳᠰᡠᠨ\\% direct Unicode input of Manchu letters2 ᠮᠠᠨᠵᡠ ᡤᡳᠰᡠᠨ }%
End font\end{minipage}\XeTeXupwardsmode0 }% End rotatebox\noindentLine
underneath \end{document}|
and I see XeTeX uses the primitive |\XeTeXupwardsmodeand some other
tricks to get the proper display of Manchu text, so maybe MKII can do
ᡤᡳᠰᡠᠨ}% End font\end{minipage}\XeTeXupwardsmode0}% End rotatebox
\noindent
Line underneath\end{document}
and I see XeTeX uses the primitive \XeTeXupwardsmode and some other tricks
to get the proper display of Manchu text, so maybe MKII can do the magic
using XeTeX as an engine. How would one use Co
e
context(environment.oldhome or "??")
\stopluacode
\stoptext
ChkEnv.pdf
Description: Adobe PDF document
-- generator : luat-sta.lua
-- state tag : whatever
return {
["context"]={
["version"]="beta",
},
["engines"]={
["luatex&
ngine=luatex" at the
top line of the source file (but no pdftex and xetex in this installer).
FWIW, the lmtx installation ships with the latest experimental luatex
binary but normally that should not have consequences, but it does
permits testing occasional updates.
Hans
The binary f
e
> the engine in the usual way with "% engine=luatex" at the top line of the
> source file (but no pdftex and xetex in this installer).
I updated LMTX on MacOSX 10.13 today.
The luatex binary in not executable, thus when I run
axel$ context --luatex --version
mtx-context
ource file (but no pdftex and xetex in this installer).
FWIW, the lmtx installation ships with the latest experimental luatex
binary but normally that should not have consequences, but it does
permits testing occasional updat
phics, images, diagrams
#
# probably no
#
# >? Math, nat. sci., comp. sci.
#
# no, context stuff comes with context already
#
# >? Music
#
# unlikely
#
# >? Necessary programmes and files
#
# what is that
#
# >? PSTricks
#
# only if used
#
# >? Additional
? SW for graphics and fonts
no
? XeTeX etc.
not for mkiv
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69
? SW for graphics and fonts
? XeTeX etc.
Thanks in advance.
(After completion I can put it on the wiki.)
Best wishes,
Tomáš
___
If your question is of interest to others as well, please add an entry to the
Wiki
rse be the yearly tex live snapshots and these will
have the year attached to them.
So, effectively nothing changes, apart from the fact that we no longer
use the labels (and distinction on the website).
I like this change.
A more fundamental distinction is between the versions:
pdftex|xetex
he website).
>
> I like this change.
>
>> A more fundamental distinction is between the versions:
>>
>> pdftex|xetex : mkii (probaly not used that much any longer)
>> luatex|luajittex : mkiv (also the test for luatex dev)
>> luametatex : lmtx (the
them.
So, effectively nothing changes, apart from the fact that we no longer
use the labels (and distinction on the website).
I like this change.
A more fundamental distinction is between the versions:
pdftex|xetex : mkii (probaly not used that much any longer)
luatex|luajittex : mkiv (also th
t from the fact that we no longer
use the labels (and distinction on the website).
A more fundamental distinction is between the versions:
pdftex|xetex : mkii (probaly not used that much any longer)
luatex|luajittex : mkiv (also the test for luatex dev)
luametatex : lmtx (the (upcoming)
;
>> Can someone give me an explanation of what I did wrong? Hit me with all the
>> technical concepts. I’m competent with fontspec on XeTeX.
>>
>> Step 1: Copy NotoSerifCJKsc-Regular.otf to ~/context/tex/texmf-local/fonts
>>
>> Step 2: Run `mtxrun --script font --conver
.stackexchange.com/questions/453143/noto-cjk-font-not-usable-with-context
>
> <https://tex.stackexchange.com/questions/453143/noto-cjk-font-not-usable-with-context>
>
> Can someone give me an explanation of what I did wrong? Hit me with all the
> technical concepts. I’m compet
ll the
technical concepts. I’m competent with fontspec on XeTeX.
Step 1: Copy NotoSerifCJKsc-Regular.otf to ~/context/tex/texmf-local/fonts
Step 2: Run `mtxrun --script font --convert NotoSerifCJKsc-Regular.otf'
Step 3: Run `mtxrun —script fonts --reload’
Step 4: Run `context test.tex’
On Mon, 12 Aug 2019 at 13:42, Jon Wong wrote:
>
> I was able to use `context’ but not `texexec’. The latter (`texexec —pdf
> test.tex’) tells me that some format file (`cont-en.fmt’) can’t be found.
>
> Is `texexec’ obsolete?
texexec is only for Mark II (8-bit pdfTeX, XeTeX)
t because font encodings are
> gone and input is utf8 by default that might need to be changed.
> Structure has more options. I think the biggest conceptual change in the
> setups has been the way footnotes are co
e options. I think the biggest conceptual change in the
setups has been the way footnotes are configured. Of course there are
new commands too.
So, a small example triggering the issue would help,
Hans
ps. Of course the biggest change is that luatex is
ligatures especially for the keys above 0x
However, I cannot get it run with latest mkiv.
It is no problem with xetex. It should print only the
five keys and not the ones for every single letter.
Herbert
\font\keyboard=LibertinusKeyboard-Regular.otf
\starttext
\keyboard
Tab
Entf
Enter
Capslock
However, I cannot get it run with latest mkiv.
It is no problem with xetex. It should print only the
five keys and not the ones for every single letter.
Herbert
\font\keyboard=LibertinusKeyboard-Regular.otf
\starttext
\keyboard
Tab
Entf
Enter
Capslock
Windows
\stoptext
a remnant
from Mark II, as in pdfTeX and XeTeX it would have resulted in an error;
in ConTeXt it just becomes a no-op, which thus shadows LuaTeX’s
behaviour that could actually have been useful.
The situation in Mark IV is documented in languages-mkiv.pdf which is
part of the distribution: Hans re
On 2/23/19 10:51 AM, Wolfgang Schuster wrote:
> [...]
>> Is this because I am using MkII with XeTeX?
>
> Is there a reason why you stick with MkII or XeTeX.
Hi Wolfgang,
support for Indic languages seems to be the reason to use MkII.
Pablo
--
http
; but keep getting "chapter 4.0".
You have to create a minimal working example for this because I can’t
tell why you get this output.
Is this because I am using MkII with XeTeX?
Is there a reason why you stick with MkII
"chapter 4.0".
>
> Is this because I am using MkII with XeTeX?
>
> Robert
>
>> On 22. Feb 2019, at 20:47, Wolfgang Schuster
>> wrote:
>>
>> Robert Zydenbos schrieb am 22.02.19 um 17:14:
>>> Dear wizards of ConTeXt,
>>> In the final
s because I am using MkII with XeTeX?
Robert
> On 22. Feb 2019, at 20:47, Wolfgang Schuster
> wrote:
>
> Robert Zydenbos schrieb am 22.02.19 um 17:14:
>> Dear wizards of ConTeXt,
>> In the final stage of completing a book project, I was wondering how to
>> aut
Hi
We currently have
mkii : which uses pdftex/xetex
mkiv : which uses lua(jit)tex 1.10
and next year we will also have
lmtx : which runs luatex
functionally there is no difference between mkiv and lmtx but there are
some diferences under the hood. It might also turn out to be a bit
tem commands
--shell-restrictedrestrict system commands to a list of
commands given in texmf.cnf
are part of the picture. Hans and I have to discuss this point.
Just to say: on my linux box, xetex from the official deb package has not
hb hardcoded:
# ldd `which xetex `
linux-vds
1 - 100 of 2559 matches
Mail list logo
