From: "John R. Culleton" <john@wexfordpress.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: OpenType in ConTeXt
Date: Sat, 11 Aug 2007 10:09:13 -0400 [thread overview]
Message-ID: <200708111009.13364.john@wexfordpress.com> (raw)
In-Reply-To: <46B9678C.2020807@elvenkind.com>
On Wednesday 08 August 2007, Taco Hoekwater wrote:
> Wolfgang Werners-Lucchini wrote:
> >>>> well, i still use texfont for type 1 fonts, but for open type
> >>>> i use luatex anyway which can handle it directly (actually,
> >>>> mkiv also usese afm files instead of tfm when available, so
> >>>> texfont is not needed any more)
> >>>
> >>> How stable/reliable is LuaTeX for general use?
> >>
> >> Well, "not at all" is the wisest answer I can give.
> >
> > Is it possible to run both (mkiv/LuaTeX and mkii/pdfTeX) in
> > parallel?
>
> Certainly. In the past year, I have been happy running all of these
> at the same time:
>
> texexec | texexec --pdftex % engine=pdftex
> texexec --aleph % engine=aleph
> texexec --luatex % engine=luatex
> texexec --xetex % engine=xetex
Is there a phrase or a sentence that will describe the distinguishing
characteristcs and/or status of each of these choices? Well, we know
about the first one :<) I am bewildered by the rapid changes.
--
John Culleton
_________________________________________________________________
Need personalized email and website? Look no further. It's easy
with Doteasy $0 Web Hosting! Learn more at www.doteasy.com
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2007-08-11 14:09 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.493.1186473146.2346.ntg-context@ntg.nl>
2007-08-07 20:18 ` Wolfgang Werners-Lucchini
2007-08-07 20:50 ` Arthur Reutenauer
2007-08-08 6:49 ` Taco Hoekwater
2007-08-11 14:09 ` John R. Culleton [this message]
2007-08-11 15:52 ` Hans Hagen
2007-08-07 20:18 ` Wolfgang Werners-Lucchini
2007-08-11 21:06 ` Patrick Gundlach
[not found] <mailman.458.1186422999.2346.ntg-context@ntg.nl>
2007-08-06 23:24 ` Wolfgang Werners-Lucchini
2007-08-07 7:52 ` Patrick Gundlach
2007-08-05 13:51 Pascal de Bruijn
2007-08-06 7:45 ` Patrick Gundlach
2007-08-06 17:20 ` Pascal de Bruijn
2007-08-06 17:54 ` Arthur Reutenauer
2007-08-06 20:01 ` Pascal de Bruijn
2007-08-06 20:07 ` Patrick Gundlach
2007-08-07 17:33 ` Pascal de Bruijn
2007-08-11 21:06 ` Patrick Gundlach
2007-08-06 20:10 ` Hans Hagen
2007-08-07 6:46 ` Pascal de Bruijn
2007-08-07 7:16 ` Taco Hoekwater
2007-08-07 17:02 ` Hans van der Meer
2007-08-07 17:09 ` luigi scarso
2007-08-07 19:14 ` Hans Hagen
2007-08-09 20:36 ` John R. Culleton
2007-08-10 15:45 ` Pascal de Bruijn
2007-08-09 13:09 ` Oliver Buerschaper
2007-08-09 14:26 ` Hans Hagen
2007-08-09 16:28 ` Hans van der Meer
2007-08-09 16:47 ` Taco Hoekwater
2007-08-09 17:17 ` Peter Münster
2007-08-07 9:36 ` Hans Hagen
2007-08-06 18:03 ` Patrick Gundlach
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=200708111009.13364.john@wexfordpress.com \
--to=john@wexfordpress.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).