Possible bug in fontinst 1.914

[Lars Hellström]

At 13.26 +0200 2002-09-08, Paul Pichaureau wrote:
>  Dear fontinst list,
>
>I have found a possible bug in fontinst.sty (v 1.914). The subdrop,
>supdrop, etc font parameters are _not_ modified by fontinst :

It's more correct to say that the (V)PL-to-MTX converter doesn't convert
them. You're right fontinst should do this and does not, but it is more the
absence of feature than a bug.

[snip]
>For people like me which create their own math font, this is not a
>nice feature !
>
>I've modified fontinst.sty in this way:
>
>\def\NUM#1~#2~#3~{\out_line{\string\setint{num#1}{\pl_real{#3}}}}
>\def\DENOM#1~#2~#3~{\out_line{\string\setint{denom#1}{\pl_real{#3}}}}
>\def\SUP#1~#2~#3~{\out_line{\string\setint{sup#1}{\pl_real{#3}}}}
>\def\SUB#1~#2~#3~{\out_line{\string\setint{sub#1}{\pl_real{#3}}}}
>\def\SUBDROP~#1~#2~{\out_line{\string\setint{subdrop}{\pl_real{#2}}}}
>\def\SUPDROP~#1~#2~{\out_line{\string\setint{supdrop}{\pl_real{#2}}}}
>\def\DELIM#1~#2~#3~{\out_line{\string\setint{delim#1}{\pl_real{#3}}}}
>\def\AXISHEIGHT~#1~#2~{\out_line{\string\setint{axisheight}{\pl_real{#2}}}}
>\def\BIGOPSPACING#1~#2~#3~{\out_line{\string\setint{bigopspacing#1}{\pl_real{#3
>}}}}
>
>Is it correct?

Looks right to me, yes.

I might add that in the newest version (which hasn't been put on CTAN yet,
it only exists on my hard drive) there is a more general mechanism for
handling this: an ETX file can declare that for example fontdimen 18
corresponds to the supdrop fontinst integer. The main reason that something
like this wasn't  implemented years ago is probably that there hasn't been
any guidelines for what  determines what the fontdimens in a font should
mean. (IMO the assignment of fontdimens is a property of the font encoding.)

>BTW, where can I find a comprehesive list of all bug reported for
>fontinst 1.914?

Perhaps at http://tug.org/archives/fontinst/maillist.html ?  I'm afraid
that is as comprehensible as it gets.

Lars Hellström