From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
Subject: Re: latest beta and ancient greek module
Date: Wed, 1 May 2013 22:45:58 +0200 [thread overview]
Message-ID: <D70E84E0-3568-417C-A3B0-E5C84213F682@gmail.com> (raw)
In-Reply-To: <CALBOmsZuGcTYC1cnJezm8x8K6=D_g3JtOnr14W8QagQyYTmhqQ@mail.gmail.com>
Am 01.05.2013 um 18:03 schrieb Mojca Miklavec <mojca.miklavec.lists@gmail.com>:
> I agree with that one. But apart from the modules that can easily be
> fixed, I use it in many of my (non-mkiv-specific) documents to setup
> the typescripts. I don't mind changing the keyword, but it would be
> nice to have a simple command available for making small snippets of
> code dependent on the engine. (LaTeX has \ifXeTeX, \ifLuaTeX for
> example.)
You can use
\startmode[*mkii]
or
\startmode[*mkiv]
to write different code for MkII and MkIV. With the counter \texengine
you can also check for the engine, one is pdfTeX, two is XeTeX and
three is LuaTeX.
Wolfgang
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2013-05-01 20:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-30 1:24 Alan Bowen
2013-04-30 6:06 ` Thomas A. Schmitz
2013-04-30 11:06 ` Alan Bowen
2013-05-01 14:13 ` Hans Hagen
2013-05-01 14:24 ` Thomas A. Schmitz
2013-05-01 16:03 ` Mojca Miklavec
2013-05-01 16:47 ` Thomas A. Schmitz
2013-05-01 20:45 ` Wolfgang Schuster [this message]
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=D70E84E0-3568-417C-A3B0-E5C84213F682@gmail.com \
--to=schuster.wolfgang@gmail.com \
--cc=mojca.miklavec.lists@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).