From: Sietse Brouwer <sbbrouwer@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: use plain LuaTeX in ConTeXt standalone
Date: Thu, 2 May 2013 15:06:50 +0200 [thread overview]
Message-ID: <CAF=dkzwa_kLreu3+pLBwz_RaMORQLtPR009-02e1BuZr5_un-w@mail.gmail.com> (raw)
In-Reply-To: <517C3C9A.4050205@wxs.nl>
Hi Hans,
Currently
mtxrun --script font --reload --simple
creates luatex-fonts-names.lua, the font list/database for Plain LuaTeX;
and
mtxrun --script font --reload
creates names.tma and names.tmc, the font list for ConTeXt.
Perhaps it makes sense if
mtxrun --script font --reload
always creates all font lists? That way users of Plain LuaTeX could
never run into 'oh damn, I forgot to create the font database' —
things would go right automatically. And the --simple flag would no
longer be needed.
Does that make sense, or am I overlooking some complexity?
Cheers,
Sietse
___________________________________________________________________________________
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:[~2013-05-02 13:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-20 9:12 Tim Li
2013-04-20 10:05 ` Marco Patzer
2013-04-20 10:21 ` Tim Li
2013-04-20 10:37 ` Marco Patzer
2013-04-20 10:43 ` Tim Li
2013-04-20 11:39 ` Hans Hagen
2013-04-27 13:22 ` Marco Patzer
2013-04-27 21:01 ` Hans Hagen
2013-05-02 13:06 ` Sietse Brouwer [this message]
2013-05-06 16:47 ` Hans Hagen
2013-04-20 10:38 ` Hans Hagen
2013-04-20 10:46 ` Marco Patzer
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='CAF=dkzwa_kLreu3+pLBwz_RaMORQLtPR009-02e1BuZr5_un-w@mail.gmail.com' \
--to=sbbrouwer@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).