ellis@mergvax.UUCP (Craig Ellis) (04/15/88)
Have have received the mac font decoder which contains the applications
called unpack and convert. I following the instructions of creating a
suitcase file full of fonts and used kermit (binary mode and resource fork)
to transmit to a VAX. From the VAX I downloaded this file to my amiga.
With this file I tried the unpack with and without the -x option (skip
128 header info) and received the guru every time. Has anyone tried using
mac font decoder with any success? Any information would be welcomed.backstro@silver.bacs.indiana.edu (04/17/88)
Yes I've used the font converter on about six or seven different fonts.
Only thing you have to do is:
1> unpack -x <macfontname>
1> dir
{There should be a new file on the disk}
1> convert <unpackedfontname>
or use one of the CLI helpers such as a utility the allows the use of
pattern matching when it's not normally available.
Before you do anything with the convert program re-assign the font directory
to another disk. Hope this helps. Trying to convert a file without
unpacking it first will end up with an immediate GURU.rmariani@watmum.waterloo.edu (Rico Mariani) (04/18/88)
In article <343@mergvax.UUCP> ellis@mergvax.UUCP (Craig Ellis) writes: > > Have have received the mac font decoder which contains the applications > called unpack and convert. I following the instructions of creating a > suitcase file full of fonts and used kermit (binary mode and resource fork) > to transmit to a VAX. From the VAX I downloaded this file to my amiga. > With this file I tried the unpack with and without the -x option (skip > 128 header info) and received the guru every time. Has anyone tried using > mac font decoder with any success? Any information would be welcomed. I've used the program with much success (seeing as I wrote the convert portion of it you might expect that it would work for me :-)). I can't really say for sure what your problem is but I can tell you that neither unpack nor convert are very robust, i.e. they tend to crash if the file is not what they expect... You must make sure that the file you transfered is really an image of the Mac version... check the lengths and see if the add up (don't forget the 128 byte extra header). Make sure that the kermits you used are in image (set file type binary) mode at both ends. I think you'll find that if you transfer carefully then all will be well. -Rico