From: Ulrike Fischer <news3@nililand.de>
To: ntg-context@ntg.nl
Subject: Re: Using virtual fonts defined with lua-code
Date: Wed, 9 Feb 2011 10:55:38 +0100 [thread overview]
Message-ID: <1g3s6e2eyiplt$.dlg@nililand.de> (raw)
In-Reply-To: <4D516A4B.3040907@wxs.nl>
Am Tue, 08 Feb 2011 17:07:39 +0100 schrieb Hans Hagen:
>>> It's relatively easy to add support for that. However, when I've
>>> done that Khaled has to make sure that it also works in his wrapper
>>> code as I don't know to what extend he overloads code. I can only
>>> test in the plain variant and context.
>> I keep it as minimal as possible (I've even some "feature requests" to
>> keep our local changes more smaller, but no time to check it now).
> You only need to load one extra file:
>
> loadmodule('font-lua.lua')
>
> Then, if
>
> \font\mine=file:luatex-fonts-demo-vf-1.lua at 12pt
>
> \mine \input tufte \par
>
> works ok, you're fine, otherwise you can delay integration.
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).
It doesn't work currently. I identified already some problematic
changes between the versions used currently by luaotfload and the
newest context files:
* 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)
* 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:
J:/MiKTeX2.9/tex/luatex/luaotfload/otfl-luat-ovr.lua:19: bad arg
ument #2 to 'format' (string expected, got nil).
--
Ulrike Fischer
___________________________________________________________________________________
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 9:55 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 [this message]
2011-02-09 13:52 ` Hans Hagen
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='1g3s6e2eyiplt$.dlg@nililand.de' \
--to=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).