I have a standard ConTeXt project setup (products, environment, chapters
subdirectory). In the chapters subdirectory there is a Makefile. I’ve just
installed mkiv. Can someone tell me what I need to change in this Makefile to
compile my project with mkiv instead of mkii?
OPEN=echo
On Mon, 23 Feb 2015, Gerben Wierda wrote:
I have a standard ConTeXt project setup (products, environment, chapters
subdirectory). In the chapters subdirectory there is a Makefile. I’ve just
installed mkiv. Can someone tell me what I need to change in this Makefile to
compile my project with
Hi Gerben,
Sorry, one typo!
The file is tools-mkiv.pdf.
It is not in the MacTeX distribution!
You get it with Standalone, I normally use that!
But you can get it at:
http://www.pragma-ade.nl/general/manuals/tools-mkiv.pdf
http://www.pragma-ade.nl/general/manuals/tools-mkiv.pdf
regards
I don’t use TeXShop for these projects. I use a separate editor in a shell and
a Makefile (very old-fashioned). The Makefile contains stuff like:
OPEN=echo
MODE=--mode=standalone
ONCE=
.SUFFIXES: .pdf .tex .open
.pdf.open:
open $
.tex.pdf:
texexec --pdf ${MODE} ${ONCE} $
Am 26.01.2015 um 17:19 schrieb Gerben Wierda gerben.wie...@rna.nl:
[…]
So, what would be easiest for me if I know what commend to use instead of the
texexec command.
You can use
context filename
to process your document with MkIV and
context —pdftex filename
to process your
Hi Gerben,
I would not say old-fasshoined , but old school.
Wolgang said to use context, but that is just a script that calls mtxrun!
So you can use:
mtxrun —script context
for other options look for:
tool-mkiv.pdf
I am sure your makefiles are more complex.
regards
Keith.
Am
On 26 Jan 2015, at 19:51, Keith Schultz keithjschu...@icloud.com wrote:
Hi Gerben,
I would not say old-fasshoined , but old school.
Wolgang said to use context, but that is just a script that calls mtxrun!
So you can use:
mtxrun —script context
for other options look for:
Hi Keith,
I got it! With the proper setting of paths it works without sourcing setuptex.
Thus I have for my installation of mkii:
--
#!/bin/bash
export PATH=/Volumes/OK/context-minimal/tex/texmf-osx-64/bin:$PATH
texexec --autogenerate --synctex=1 $1
Hi Gerben,
Mkii and Mkiv are to different animals and live side by side.
You do not need to change your TeX setup at all!
All you need to do is change the call to start the processing.
Mkiv can be called with the context …
or
mtxrun -script context …
What I do not know is in what kind of
Hi Gerben,
Indeed this is possible to use mkii and mkiv side by side.
In particular if you use TeXShop, it is enough to say at the beginning of your
TeX file
%!TEX TS-program = mkii
or
%!TEX TS-program = mkiv
where it is assumed that you have created two files named
mkii.engine
Hi Otared and Gerben,
I do not know which version of TeXShop you are using but the more recent ones
have Engines for ConTeXt, already.
If they are not already installed you can find them in:
~/Libraries/TeXShop/Engines/Inactive
just more the Contex( LuaTeX).engine into Engines and restart
Hi Keith,
Thanks for your attention.
Indeed I use the latest TeXShop (version 3.49) but regarding the content my
mkii.engine file if I remove the line
source /Volumes/OK/context-minimal/tex/setuptex
then I cannot typeset with my standalone installation of Context: I tried to
use a set path
Hi Otared,
actually, just setting the PATH variable will work, but you have to set it
with the proper command!
The Standard TexShop engines use the tcsh shell and not bash !!
either change the first line to
#!/bin/tcsh
or set the path bash style
export
I have a finished mkii project and I’d like to be able to export it to a format
that can be a start for other distributions (such as epub or the like). For
this, I get the impression I need mkiv.
Now, before I go on trying to move my project to mkiv I have a question. Can I
run mkii and mkiv
14 matches
Mail list logo
