Re: @Char trademark - lout says it's not there, but it's in the AFM

[Valeriy E. Ushakov]

On Wed, Sep 03, 2008 at 21:46:07 -0700, Clint Olsen wrote:

> On Sep 03, Ludovic Court?s wrote:
> > That's because is an "unencoded" character (the "C -1" in the AFM file),
> > and Lout isn't able to handle them, unfortunately.  You get similar
> > messages for fonts that have many ligatures attached to unencoded
> > characters, such as the Latin Modern font family.
> > 
> > One solution is to edit the AFM file so that this character is mapped to
> > some ASCII value.
>
> I assigned this 252 since that was available, but that didn't work.
> Does it have to be encoded in 7 or 8 bits to work?  Also, how does
> the character glyph get selected for the output?  It can't be as
> simple as changing the AFM.  I would expect something required on
> the pfa/pfb side, too?

IIRC, the problem is not with the afm file, that just documents
default encoding vector of the font.  To be able to use a glyph, you
need the glyph mapped with the LCM file (from maps directory) and
latin1 maps lout uses don't map trademark symbol.

SY, Uwe
-- 
address@hidden                       |       Zu Grunde kommen
http://snark.ptc.spbu.ru/~uwe/          |       Ist zu Grunde gehen