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 to try
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=luatmetatex 1.6
>
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 file
44:38 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 surprising.
s 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
rendere at so
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-Latin typo
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 a pdf backend, xetex pipes into a dvi backend, luatex has
a pdf
ontinued 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've been built with noses to hold our eyeglasses lest these
eyeglasses fall off while reading, or that we'
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' we had two competing but similar
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-context
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 sets of Cyrillic
oading 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
We have two se
> 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
/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: /opt/local/bin/mktexpk
pdf
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. Now
OS 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[default] [boldened-30]
\definefontfeature[mathextra][boldened-20]
\setupbodyfont[pagella]
\start
x=
$TEXMFDOTDIR;$TEXMF/tex/{luatex,plain,generic,latex,}//
TEXINPUTS.luajithbtex =
$TEXMFDOTDIR;$TEXMF/tex/{luatex,plain,generic,latex,}//
TEXINPUTS.dviluatex =
$TEXMFDOTDIR;$TEXMF/tex/{luatex,plain,generic,latex,}//
TEXINPUTS.lualatex=
$TEXMFDOTDIR;$TEXMF/t
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
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 graphicsmagick 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't checked
w 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 nice
compromise. (Prob
ol 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 microsoft cambria fon
ust 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 approach also for ope
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
).
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 you
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
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 | 8061 GH Hasselt
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 but that
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 suspect.)
Hans
proved.
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/generic/hyph-utf8/loadh
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 do math yet) and
Te
> 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 of the Mongolian section{\dcw%
\\% 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 ConTeXt
nment.oldhome or "??")
\stopluacode
\stoptext
ChkEnv.pdf
Description: Adobe PDF document
-- generator : luat-sta.lua
-- state tag : whatever
return {
["context"]={
["version"]="beta",
},
["engines"]={
["luatex"]=true,
[&quo
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
no
? 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
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 : mkii
).
>
> 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 (upcoming)
, 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 the test
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) real deal
;>
>> 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
th 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 --convert NotoSerifCJKsc-Regular.otf'
Step 3: Run `mtxrun —script fonts --reload’
Step 4: Run `context test.tex’
The
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; 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 configured. Of course there are
>
he 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 used instead of
pd
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
ut keep getting "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 fi
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
ell-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-vdso.so.1 (0x7ffcb2
"ok.log" goto end
echo.
echo The distribution has been downloaded but if you want to run pdfTeX and/or
XeTeX you
echo need to run this script with the following directive:
echo.
echo --platform=all
echo.
echo You then also need to install Ruby in order to be able to use texexec.
After
by name is a pretty good alternative
Well in my view name and code point are both valid and useful
accesses (and I wouldn't trust names too much).
Beside this:
xetex has (for non-legacy fonts) primitives for all accesses: by
char (unicode), slot and name.
whatever ...
luatex hasn't, here the only
ternative
Well in my view name and code point are both valid and useful
accesses (and I wouldn't trust names too much).
Beside this:
xetex has (for non-legacy fonts) primitives for all accesses: by
char (unicode), slot and name.
luatex hasn't, here the only (primitive) access are commands l
shown in the figures the
ligatures have a private Unicode number.
Hm. To clarify. In xetex there is clear distinction between the slot
and unicode. \XeTeXglyph (slot) and \char (unicode) give different
output and \char actively uses the tounicode mapping of the font.
\font\test="[lmro
the lists shown in the figures the
> ligatures have a private Unicode number.
Hm. To clarify. In xetex there is clear distinction between the slot
and unicode. \XeTeXglyph (slot) and \char (unicode) give different
output and \char actively uses the tounicode mapping of the font.
\font\test="[lmroma
for every document and package which uses
the generic fontloader the access to chars in the private area with
\char is now broken in luatex (in xetex it still works fine).
I just got from Claudio Beccari (which seem to have complained to
Luigi) a bug report that the libertine fonts no longer
substitutions will be applied (maybe ligs)
\stoptext
(It could be a font bug, the output with xetex isn't good either).
fonts probably have a limited set of lookups
(the 5 and 7 suggests some inconsistency in the lookups)
i must admit that i've seen so many bad frac implementations that i
never use
={file:linlibertine_r.otf:mode=base;script=latn;language=DFLT;+frac}
\test
787347 125
1/7 1/2 3/4 5/6 7/8 9/10 11/12 31415/27182 1000/100
\stoptext
(It could be a font bug, the output with xetex isn't good either).
--
Ulrike Fischer
https://www.troubleshooting-tex.de
installed.
The 'footnotes' will be placed at the end of the chapters (i.e., they will be
endnotes).
If you run sample.tex through ConTeXt and XeTeX (i.e., MkII) and look at the
final page, you will see that the footnote / endnote marker has not been reset.
Robert
> On 9. Aug 2018, at 16
).
If you run sample.tex through ConTeXt and XeTeX (i.e., MkII) and look at the
final page, you will see that the footnote / endnote marker has not been reset.
Robert
On 9. Aug 2018, at 16:37, Aditya Mahajan wrote:
On Thu, 9 Aug 2018, Robert Zydenbos wrote:
I have tried ‘\resetcounter [footnote
is called. As bypage and
bysection both don't do that, I need to be able to manually adjust the
numbering.”
I have tried ‘\resetcounter [footnote]’ (a suggested solution on that web
page), but it does not work (at least not in MkII+XeTeX). ‘\setupcounter
[footnote] [0]’ (also suggested on that web
installed.
The 'footnotes' will be placed at the end of the chapters (i.e., they will be
endnotes).
If you run sample.tex through ConTeXt and XeTeX (i.e., MkII) and look at the
final page, you will see that the footnote / endnote marker has not been reset.
Robert
> On 9. Aug 2018, at 16
On Thu, 9 Aug 2018, Robert Zydenbos wrote:
I have tried ‘\resetcounter [footnote]’ (a suggested solution on that
web page), but it does not work (at least not in MkII+XeTeX).
‘\setupcounter [footnote] [0]’ (also suggested on that web page) is
rejected as an error.
Can you post a minimal
.”
I have tried ‘\resetcounter [footnote]’ (a suggested solution on that web
page), but it does not work (at least not in MkII+XeTeX). ‘\setupcounter
[footnote] [0]’ (also suggested on that web page) is rejected as an error.
Robert
bos wrote:
>> Sorry, neither of these work (MkII with XeTeX). I get no error
>> messages with Pablo's suggestion, but not the desired result either.
>
> Weird, this works for me (with and without XeTeX):
>
>\setuppapersize[A8]
>\setupnote[footnote][way=by
On 08/08/2018 05:03 PM, Robert Zydenbos wrote:
> Sorry, neither of these work (MkII with XeTeX). I get no error
> messages with Pablo's suggestion, but not the desired result either.
Weird, this works for me (with and without XeTeX):
\setuppapersize[A8]
\setupnote[footnote][way=byc
schrieb am 08.08.18 um 17:03:
Sorry, neither of these work (MkII with XeTeX). I get no error messages with
Pablo's suggestion, but not the desired result either.
Perhaps I need a very primitive command that I can insert at the beginning of
every chapter.
Robert
On 8. Aug 2018, at 16:54, Pablo
Sorry, neither of these work (MkII with XeTeX). I get no error messages with
Pablo's suggestion, but not the desired result either.
Perhaps I need a very primitive command that I can insert at the beginning of
every chapter.
Robert
> On 8. Aug 2018, at 16:54, Pablo Rodriguez wr
Perhaps it is useful that I mention that this is a MkIV problem on my iMac with
TeXLive (2018 version). Using MkII, also with XeTeX, everything ran right out
of the box. For MkIV, I had to run a program to let LuaTeX find all the fonts,
and then it worked.
Robert
On 6/8/2018 11:51 PM, Ulrike Fischer wrote:
I have been playing around with lua fonts and investigating where to
store and how to load them.
The best with luaotfload and latex seems to be currently to get
(with a kpse call) the absolute path and then load with the "xetex"
synt
I have been playing around with lua fonts and investigating where to
store and how to load them.
The best with luaotfload and latex seems to be currently to get
(with a kpse call) the absolute path and then load with the "xetex"
syntax:
\font\duckchessfont =
[\directlua{
a page of a PDF via
>>>>> ConTeXt?
>>>>>
>>>>> Ideally - to process a single page PDF into another file, with
>>>>> the one page cropped...
>>>>
>>>
>>> The ‘pdfcrop’ command from TeXLive can do that for you on
at for you on the
> > command line. It is based around ghostscript which can
> > automatically find the crop area, then uses pdftex,luatex,or xetex
> > to create a new pdf.
> >
> > It is doable to come up with a solution in ConTeXt if you do not
>
from TeXLive can do that for you on the command line.
It is based around ghostscript which can automatically find the crop area,
then uses pdftex,luatex,or xetex to create a new pdf.
It is doable to come up with a solution in ConTeXt if you do not mind
specifying the cropbox manually, but automatic
;
The ‘pdfcrop’ command from TeXLive can do that for you on the command line.
It is based around ghostscript which can automatically find the crop area,
then uses pdftex,luatex,or xetex to create a new pdf.
It is doable to come up with a solution in ConTeXt if you do not mind
specifying the cropbox man
* syntax
while you use/want the xetex syntax
mtxrun --script plain yourtexfile
should work gven that you made a format with
mtxrun --script plain --make
(mtxrun --script font --reload --simple will make a plain database if
needed)
It uses luatex-plain that ships with context as
> On 18. Apr 2018, at 14:04, Hans Hagen <j.ha...@xs4all.nl> wrote:
>
> On 4/18/2018 9:39 AM, Robert Zydenbos wrote:
>>> On 18. Apr 2018, at 09:35, luigi scarso <luigi.sca...@gmail.com> wrote:
>>>
>>> Do you really need mkii ?
>> I'm
On 4/18/2018 9:39 AM, Robert Zydenbos wrote:
On 18. Apr 2018, at 09:35, luigi scarso <luigi.sca...@gmail.com> wrote:
Do you really need mkii ?
I'm afraid so. I need XeTeX for its support of Indic fonts. And for my purposes
MkII is already very, very nice.
the other languages in
On Wed, Apr 18, 2018 at 9:39 AM, Robert Zydenbos <cont...@zydenbos.net>
wrote:
>
> > On 18. Apr 2018, at 09:35, luigi scarso <luigi.sca...@gmail.com> wrote:
> >
> > Do you really need mkii ?
>
> I'm afraid so. I need XeTeX for its support of Indic fonts
t;
as mentioned on http://wiki.contextgarden.net/Manuals, but the server does not
respond.
> On 18. Apr 2018, at 09:39, Robert Zydenbos <cont...@zydenbos.net> wrote:
>
>
>> On 18. Apr 2018, at 09:35, luigi scarso <luigi.sca...@gmail.com> wrote:
>>
>> Do you really need mkii ?
> On 18. Apr 2018, at 09:35, luigi scarso <luigi.sca...@gmail.com> wrote:
>
> Do you really need mkii ?
I'm afraid so. I need XeTeX for its support of Indic fonts. And for my purposes
MkII is already very, ver
On 4/9/2018 12:18 PM, Robert Zydenbos wrote:
On 09.04.2018 09:45, Hans Hagen wrote:
On 4/9/2018 12:33 AM, Robert Zydenbos wrote:
[…] (I need to use Mk II because I need the functionality of XeTeX.)
just curious: what do you mis in mkiv / luatex
Support for Indic scripts / fonts. (I think
On 09.04.2018 09:45, Hans Hagen wrote:
On 4/9/2018 12:33 AM, Robert Zydenbos wrote:
[…] (I need to use Mk II because I need the functionality of XeTeX.)
just curious: what do you mis in mkiv / luatex
Support for Indic scripts / fonts. (I think we had a little bit of
correspondence
On 09.04.2018 00:49, Wolfgang Schuster wrote:
Mk II does not have setupnotation[footnote] yet, and when I
'translated' it to setupfootnotes (which ordinarily ought to work in Mk
II), it unfortunately did not work. (I need to use Mk II because I need
the functionality of XeTeX.)
1
' it to \setupfootnotes (which ordinarily ought to work in Mk
II), it unfortunately did not work. (I need to use Mk II because I need
the functionality of XeTeX.)
just curious: what do you mis in mkiv / luatex
However, Wolfgang gave the solution! I do not know why that is the
solution :-), but it works
when I
'translated' it to \setupfootnotes (which ordinarily ought to work in
Mk II), it unfortunately did not work. (I need to use Mk II because I
need the functionality of XeTeX.)
1. \setupnotation is the new command name for \setupnotedefinition
2. Which language do you use in your document?
Wo
), it unfortunately did not work. (I need to use Mk II because I need
the functionality of XeTeX.)
However, Wolfgang gave the solution! I do not know why that is the
solution :-), but it works.
The best,
Robert
--
Prof. Dr. Robert J. Zydenbos
Institute of Indology and Tibetology
1 - 100 of 2328 matches
Mail list logo
