Hi:
At 11:43 AM 98/08/05 +0200, you wrote:
>as I have seen from lw35nfsx.zip, your ly1<fam>.fd files start
>with a header claiming that they were generated using fontinst,
>although I strongly suspect that they were actually generated
>by editing t1<fam>.fd files and forgetting to do some clean up.
Yes, you are quite right. We will remove those misleading comments.
>- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>
>As I have already received a user request asking how to generate
>LY1-encoded .fd files using fontinst v1.8 for some Bitstream fonts,
>I would like to ask you to make clear that your LY1 files have
>nothing to do with fontinst and that the maintainer of fontinst
>(which happens to be me at the moment) should not be bothered.
>
>Anyway, as I am trying to be a helpful person, I have suggested
>the following (untested) solution to the problem:
>...
>- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>
>I am not completely sure if the result of installing a TFM file
>using 8y.etx and 8y.mtx will be exactly the same as what you get
>with your tools. Fontinst certainly does a little more than just
>plain reencoding, as it also adds ligature programs and kern pairs
>for accented characters.
Yes, this is also done by AFMtoTFM which is what we use, although
there may be some differences in details. The key thing is that there
is only a single TFM file, and no need for VF or anything like TS1.
Regards Louis.