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:30:54 +0100 [thread overview]
Message-ID: <4D52970E.80408@wxs.nl> (raw)
In-Reply-To: <f47gcwjhz8dw$.dlg@nililand.de>
On 9-2-2011 12:23, Ulrike Fischer wrote:
> Am Tue, 08 Feb 2011 17:07:39 +0100 schrieb Hans Hagen:
>
>>>>> 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. 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.
>
>> 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
>
> What are the search pathes for such virtual lua fonts? I suggested
> the file extension ".vflua" because I thought it would be senseful
> if not the search path for general .lua files is used. I wanted to
> put this virtual fonts in a dedicated location e.g. fonts/vflua/....
I'm not going to hard code something like that as it's a macro specific
issue. You can try (untested):
fonts.formats.vflua = "lua"
Paths and lookups are also a macro package issue and as khaled probably
has specific file lookup code for latex, I suppose that the lookup can
be handled there. If not, we can make the remapper extensible.
Anyhow, "tex" with "other text files" sounds good enough for me. Also, I
suppose that names should be unique and the files that you make in some
latex specific (sub)path in order not to clash. As this is not that
generic, maybe something: tex/latex/fonts/vflua is best.
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:30 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
2011-02-09 11:23 ` Ulrike Fischer
2011-02-09 13:30 ` Hans Hagen [this message]
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=4D52970E.80408@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).