[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Problem with ~ and ^

> > At 12:51 PM 11/24/1999 -0500, you wrote:
> > 
> >  > [Charset iso-8859-1 unsupported, filtering to ASCII...]
> > 
> > What may be confusing is that 8r is a "base" encoding to which the actual font
> > is reencoded.  Typically you use some other encoding at the TeX level, like T1.
> > The TFM file seen by TeX needs to be set up for *that* encoding, not the base
> > encoding.
> > 
> > But like I said, why not use LY1 :-)?
> > 
> > I cannot understand why people torture themselvse with this complex 
> > T1/TS1/8r stuff and AFM2TFM/fontinst.  Weird :-)
> Success.  
> I installed LY1, and configured both my afm2tfm -T LY1 and my *.sty
> files to use LY1, and it works for all characters now.  I have to use
> virtual fonts because I need fake smallcaps and I think only virtual
> fonts can do that.
> I have no idea why the old system did not work, but it was totally
> confusing to me why I had 8r in psfonts.map but T1 in my *.fd file and
> *.sty files.  I am glad to leave the mess of T1/TS1/8r for a clean LY1
> solution that makes sense.
> Thanks to everyone.  Couldn't have done it without you.

OK, I have a problem.  The documents, when converted to PDF via
ghostscript 5.94, have blanks for ligatures like fi, fl, and copyright
symbols.  I have seen this before, and it usually has to do with some
improper encoding.  It looks fine when the PS file is viewed.

Any ideas?  I was really starting to like LY1 too.

  Bruce Momjian                        |  http://www.op.net/~candle
  root@candle.pha.pa.us                |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026