[metapost] Strange infont results

Ovidiu Gheorghies ogh at info.uaic.ro
Fri Jul 8 10:59:23 CEST 2005

> > - For s0 and s1: ``<<'' and ``>>'' are replaced by one corresponding
> > specific character, but the bounding box is larger than the text: the more
> > such characters exist, the longer than the resulting text the bounding box
> > is.
> I have this problem too, it is caused by tyxtt being a virtual font.
> You shouldn't use virtual fonts with infont, because they are never
> interpreted as a virtual font, only as a "normal" TFM. As a result
> of that, the encoding vector is usually wrong and vf-generated ligatures
> remain "hidden" until being processed by either dvips or pdftex
> postprocessing.

Can you recommend me some fixed-size fonts (like Courier New) that I can 
use? It is important for me that this font does not display a ``~'' 
instead of a space when used with infont. 

Is there a simple way of seeing how the installed TeX fonts look like 
(I'm on linux)? My current approach is use a script which iterates 
over the directory of existing fonts and create a TeX document which 
display some text using each of these fonts.

> > - For g0..g3: in g2 the closing ``]'' is not shown, but in all other it's 
> > - For c0 and c1: in c1 the closing ``}'' is not shown, unlike in c0.
> Both examples work OK for me. Is your tyxtt.vf really OK? (perhaps try
> running vftovp -- vptovf on it). Also perhaps there is a problem with
> your metapost executable (I use 0.901)
Running vftovp txytt.vf apparently gives no error.

My mpost executable sais:
This is MetaPost, Version 0.641 (Web2C 7.5.4)
so I guess it's older. I use the latest Fedora Core release, 4.
Has the MetaPost team released a RPM with the newer version in a yum 
repository yet?


More information about the metapost mailing list