Am Mon, 18 Jun 2012 08:06:00 +0200 schrieb Patrick Gundlach: >> As an example: I'm interested in "virtual lua fonts", that means >> some lua-code which describes a font build by getting (and >> reordering) glyphs from other real fonts and which can be loaded >> like a real font with the \font command. At some time it could be >> done in context (and so also with luaotfload when it was in sync) >> but you had to use undocumented internal functions with not garanty >> that they didn't change the next day and there wasn't a sane way to >> set up the search pathes for such fonts. It is no fun to develop >> only such ad-hoc solutions. > would having a new font format ending with ".luafont" (or > something similar) and a defined API help? Or what would your > preferred interface be like?
I'm open to everything as long as it is stable and usable ;-). Personally I think that a dedicated extension (.luavf, .luafont, .lvf, or whatever) and a kpse-search path in \fonts, e.g. fonts\lvf or fonts\luafont would be the best. This would prevent arbitrary files to be loaded as fonts. A year ago something like "\font\test=file:myvirtualfont.lua" worked with context, but the lua-files had to be in the standard lua-search path. -- Ulrike Fischer
