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: Tue, 08 Feb 2011 17:17:22 +0100 [thread overview]
Message-ID: <4D516C92.2090206@wxs.nl> (raw)
In-Reply-To: <1s2e8pqmwqw3t.dlg@nililand.de>
On 8-2-2011 3:41, Ulrike Fischer wrote:
> Am Tue, 08 Feb 2011 15:13:11 +0100 schrieb Hans Hagen:
>
>> On 8-2-2011 10:40, Ulrike Fischer wrote:
>>> Hello,
>>>
>>> The luatex documentation contains in section "7.2.2 Example virtual
>>> font" an example how to define a virtual font "cmr10-red". The font
>>> is defined by adding the code to the define_font callback.
>
>>> Does some interface exists in contex/mkiv which allows to use such
>>> virtual fonts together with the normal font loading code? E.g. could
>>> I move the code for the font to some file ("cmr10-red.vflua") so
>>> that a request \font\mytest="cmr10-red" will simply find this file
>>> and use the code like vf, tfm or otf-files are found and used when
>>> needed?
>
>> It's relatively easy to add support for that.
>
> That would be fine. There are quite often on various lists questions
> about how to "correct" a font, e.g. adjust kerning, or add a missing
> glyph etc and a interface for "virtual lua fonts" would make such
> corrections much easier.
>
> The example in the documentation uses as base font cmr10 and loads
> it with f = font.read_tfm('cmr10',size). How should one load the
> real font when it is an otf?
the lua file has to return a function that then gets a specification and
has to return a tfmtable, something like
return myhackery(specification)
local t = fonts.tfm.read(specification)
-- mess around with t
return t
end
but I didn't test that.
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-08 16:17 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 [this message]
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
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=4D516C92.2090206@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).