[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: bug in ae virtual fonts, or in fontinst, or in vptovf/vftovp?
- To: Vladimir Volovich <vvv@vvv.vsu.ru>
- Subject: Re: bug in ae virtual fonts, or in fontinst, or in vptovf/vftovp?
- From: Olaf Weber <olaf@infovore.xs4all.nl>
- Date: 13 Jan 1999 14:28:10 +0100
- Cc: tex-fonts@csc-sun.math.utah.edu, fontinst@cogs.susx.ac.uk, tex-k@tug.org, enge@nada.kth.se
- In-Reply-To: Vladimir Volovich's message of "27 Sep 1998 14:55:01 +0400"
- References: <m3iui9kepm.fsf@vvv.vsu.ru>
Vladimir Volovich writes:
> Hi,
> when i'm trying to produce vpl file for the ae fonts from vf and tfm
> files, i get a "bad vf file" error from vftovp, e.g.:
> % vftovp aer10.vf aer10.tfm aer10.vpl
> Bad VF file: Oversize dimension has been reset to zero.
See my other mail for this issue. Bug in vptovf, fixed in web2c 7.3.
...
> and this is definitely a bug in vftovp, since error message goes to
> stdout instead of stderr; and the last line in vpl file
> (COMMENT THE TFM AND/OR VF FILE WAS BAD, SO THE DATA HAS BEEN CHANGED!)
> comes without a newline character, which is also a bug.
Fixes will be in web2c 7.3 as well.
--
Olaf Weber