From: Hans Hagen <pragma@wxs.nl>
To: news3@nililand.de, mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Using virtual fonts defined with lua-code
Date: Wed, 09 Feb 2011 14:52:13 +0100 [thread overview]
Message-ID: <4D529C0D.4040700@wxs.nl> (raw)
In-Reply-To: <1g3s6e2eyiplt$.dlg@nililand.de>
On 9-2-2011 10:55, Ulrike Fischer wrote:
> I downloaded the (hopefully) current lua-files from
> http://minimals.contextgarden.net/current/context/alpha/tex/context/base/,
> renamed them and tested with luaotfload [2011/02/04 v1.23 OpenType
> layout system] (as a first step without the new font-lua.lua).
You can best test with the plain format first:
luatex --ini --fmt=luatex-plain
etc as that is the benchmark.
> * register_base_substitution has been renamed to
> registerbasesubstitution (used in luaotfload.lua line 137)
>
> * fonts.define seems to be named fonts.definers now (luaotfload.lua
> line 87)
indeed, and some probably will get cleaned up as some code is still
experimental
> * Instead of logs.report the context files use now report_prepare
> (with a different syntax) which is perhaps the source of the error
> I'm getting now:
You can probably define
function logs.reporter(c)
return function(...)
texio.write(c .. " : " .. string.format(...))
end
end
somewhere if you want some logging.
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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:[~2011-02-09 13:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-08 9:40 Ulrike Fischer
2011-02-08 14:13 ` Hans Hagen
2011-02-08 14:41 ` Ulrike Fischer
2011-02-08 16:17 ` Hans Hagen
2011-02-08 14:46 ` Khaled Hosny
2011-02-08 16:07 ` Hans Hagen
2011-02-09 9:55 ` Ulrike Fischer
2011-02-09 13:52 ` Hans Hagen [this message]
2011-02-09 11:23 ` Ulrike Fischer
2011-02-09 13:30 ` Hans Hagen
2011-02-09 16:09 ` Ulrike Fischer
2011-02-09 16:36 ` Hans Hagen
2011-02-10 10:03 ` Ulrike Fischer
2011-02-10 10:26 ` Hans Hagen
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=4D529C0D.4040700@wxs.nl \
--to=pragma@wxs.nl \
--cc=news3@nililand.de \
--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).