[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Groff] Re: Resource forks in OSX
From: |
Alejandro López-Valencia |
Subject: |
Re: [Groff] Re: Resource forks in OSX |
Date: |
Tue, 10 Sep 2002 22:46:38 -0500 |
Rob Scovell wrote:
> Non comprendo ... from the manual it looks like
> .ft IPA
> and
> \f[IPA]
> are equivalent.
Just covering that .ft may be taking only 1 or 2 char wide values...
Dunno, I've forgotten.
> I have tried changing this and it doesn't work.
> Here is the .afm file, in case that's up the creek, but I don't think
> so:
'tis fine.
Did you use
afmtodit -ns -d ./DESC -i 0 TIPA____.AFM generate/nullmap TIPA ?
One thing you can do is to create an encoding file...
delete all the cruft making sure you have only lines that look like
this:
C 32 ; WX 250 ; N space ; B 0 0 0 0 ;
name the file, say, tiphonenc.
gawk -F";" '{ print $3 $1 }' tiphonenc > tiphonenc1
then
gawk -F" " '{ print $2 " " $4 }' tiphonenc1 > tiphonenc2
(Of course this can be done in one pass, but I haven't used awk in a
long time).
And a map file:
gawk -F" " '{ print $1 " " $1 }' tiphonenc2 > tiphonmap
Now run:
afmtodit -ns -d ./DESC -e tiphonenc2 -i 0 TIPA____.AFM
tiphonmap TIPA
After this, you have entries that look like:
equalsuperscript 444,510,0,0,-10 3 0075 --
equalsuperscript
And you can call this glyph as: \f[TIPA]\[turnedcomma]\fP
Works here....
Re: [Groff] Re: IPA font problem (was Resource Forks in OSX), Rob Scovell, 2002/09/10
Re: [Groff] Re: Resource forks in OSX, Werner LEMBERG, 2002/09/11