From: Otared Kavian <otared@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Can I use mkii and mkiv side by side?
Date: Wed, 21 Jan 2015 12:08:53 +0100 [thread overview]
Message-ID: <C370738A-15E5-4C22-B460-3BCE06907B42@gmail.com> (raw)
In-Reply-To: <D84BC753-EA87-421D-851C-25F4F8F5C0B4@rna.nl>
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
and
mkiv.engine
located in the directory
~/Library/TeXShop/Engines
For instance my file mkii.engine contains the following lines:
#!/bin/bash
source /Volumes/OK/context-minimal/tex/setuptex
texexec --autogenerate --synctex=1 "$1"
where
/Volumes/OK/context-minimal/tex/setuptex
is the path to the file setuptex in my Context standalone directory.
Best regards: OK
> On 21 Jan 2015, at 00:36, Gerben Wierda <Gerben.Wierda@RnA.nl> wrote:
>
> 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 side by side? That is, if I configure my TeX setup for mkiv (I am using MacTeX 2014), can I still fall back to the old setup when I fail?
>
> Second, is there some step-by-step instruction to move a project from mkii to mkiv?
>
> G
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to the Wiki!
>
> maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
> archive : http://foundry.supelec.fr/projects/contextrev/
> wiki : http://contextgarden.net
> ___________________________________________________________________________________
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2015-01-21 11:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-20 23:36 Gerben Wierda
2015-01-21 11:08 ` Otared Kavian [this message]
2015-01-21 11:55 ` Keith Schultz
2015-01-21 12:48 ` Otared Kavian
2015-01-21 13:31 ` Keith J. Schultz
2015-01-21 22:01 ` Otared Kavian
2015-01-26 16:19 ` Gerben Wierda
2015-01-26 16:29 ` Wolfgang Schuster
2015-01-26 18:51 ` Keith Schultz
2015-01-26 21:49 ` Gerben Wierda
2015-01-27 12:06 ` Keith J. Schultz
2015-02-23 21:33 ` Gerben Wierda
2015-02-23 21:37 ` Aditya Mahajan
2015-01-21 11:29 ` Keith J. Schultz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C370738A-15E5-4C22-B460-3BCE06907B42@gmail.com \
--to=otared@gmail.com \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).