[Fontinst] \resetslot in multislot.sty would be nice to have working

Reuben Thomas rrt at sc3d.org
Tue Aug 6 00:59:33 CEST 2013


On 5 August 2013 22:35, Lars Hellström <Lars.Hellstrom at residenset.net>wrote:

> Reuben Thomas skrev 2013-08-03 22.02:
>
>> I beg to differ: I'm trying to write customized versions of t1.etx,
>>
>
> Oh, cool! May I ask to what ends they are customised?


To add long s ligatures (in my case, for use with Adobe Caslon Expert
fonts).


> Is there a reason you don't just do those tasks in the opposite order,
> i.e., go
>
> \encoding
>
> % First do my stuff:
>
> \nextslot{n}
> \setslot{whatever}...\**endsetslot
>
> % Then fill in the rest as in T1 encoding:
> \inputetx{t1}
>
> \endencoding
>

Yes, because either I use multislot, and then end up overriding rather than
adding to slots, or I don't use multislot, in which case the \inputetx{t1}
will add to the slots I want to override. I can't both override and add to
slots either with or without multislot.sty.


> ? Then it is always the first \setslot that does what you want,


I want to add to the existing definition.

You may be lucky with how vptovf deals with multiple definitions here.
> (Which in principle one shouldn't rely on, but OTOH as software goes,
> vptovf is probably one of the more fixed fulcrums one might come across.)


Exactly, I'd rather not rely on this.


> Could you clarify what you mean by "add to a slot" here? I don't see what
> it could possibly correspond to in a virtual font.


I want to add a ligature rule to an existing glyph, i.e.

\inputetx{t1}

\setslot{some glyph defined in t1.etx}
  \ligature{...}
\endsetslot


> t1.etx is not particularly in flux, so shipping the patched versions is
> probably far more user-friendly than shipping a bunch of patches.


I don't think so, as you can't read a patched version to see how it's
different. A patch is both easy to read, and easy to apply.

-- 
http://rrt.sc3d.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tug.org/pipermail/fontinst/attachments/20130805/cdf03ef4/attachment.html>


More information about the fontinst mailing list