suit file

[Jan Willem Stumpel]

I have a font for an exotic language (Javanese) that I want to
convert to UTF-8 encoding. Problem is, the font file was made on a
Macintosh using Fontographer, and it has a .suit file extension
that Fontforge doesn't know how to handle.

Anyone knows of a conversion tool under Linux that can change a
"*.suit" file to ttf?

Regards, Jan

[Rich Felker]

Post by Jan Willem Stumpel
I have a font for an exotic language (Javanese) that I want to
convert to UTF-8 encoding. Problem is, the font file was made on a
Macintosh using Fontographer, and it has a .suit file extension
that Fontforge doesn't know how to handle.
Anyone knows of a conversion tool under Linux that can change a
"*.suit" file to ttf?

Googling for suit file format turns up lots of SEO-spam sites with no
details on what the format really looks like. I think it's just some
sort of primitive archive format that contains the ttf (or several
ttf's) and you may be able to search for a ttf header within it and
then just throw away the suit crap at the beginning using dd.

Rich

[Ben Wiley Sittler]

It's a font "suitcase", and IIRC the font data is actually in the
"resource" fork. At least under Mac OS X, fontforge seems to be able
to deal with these. If you have the file on a non-Mac OS machine it
may well be corrupt, since non-Mac filesystems do not preserve the
resource fork data.

Post by Rich Felker

Post by Jan Willem Stumpel
I have a font for an exotic language (Javanese) that I want to
convert to UTF-8 encoding. Problem is, the font file was made on a
Macintosh using Fontographer, and it has a .suit file extension
that Fontforge doesn't know how to handle.
Anyone knows of a conversion tool under Linux that can change a
"*.suit" file to ttf?

Googling for suit file format turns up lots of SEO-spam sites with no
details on what the format really looks like. I think it's just some
sort of primitive archive format that contains the ttf (or several
ttf's) and you may be able to search for a ttf header within it and
then just throw away the suit crap at the beginning using dd.
Rich
--
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/linux-utf8/

[Jan Willem Stumpel]

Post by Ben Wiley Sittler
It's a font "suitcase", and IIRC the font data is actually in
the "resource" fork. At least under Mac OS X, fontforge seems
to be able to deal with these. If you have the file on a
non-Mac OS machine it may well be corrupt, since non-Mac
filesystems do not preserve the resource fork data.

This file was sent to me by a friend, from a Mac computer, by
e-mail, and then saved on my ext3 HD. Any danger that it was
corrupted, or incomplete?

Regards, Jan

[Ben Wiley Sittler]

If it was packaged up correctly on the sending side (using BinHex,
probably) then the bits might still be intact. I believe fontforge can
read binhex'ed files even on non-Mac OS operating systems and from any
filesystem.

Good luck!
-Ben

Post by Jan Willem Stumpel

Post by Ben Wiley Sittler
It's a font "suitcase", and IIRC the font data is actually in
the "resource" fork. At least under Mac OS X, fontforge seems
to be able to deal with these. If you have the file on a
non-Mac OS machine it may well be corrupt, since non-Mac
filesystems do not preserve the resource fork data.

This file was sent to me by a friend, from a Mac computer, by
e-mail, and then saved on my ext3 HD. Any danger that it was
corrupted, or incomplete?
Regards, Jan
--
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/linux-utf8/

[Rich Felker]

Post by Jan Willem Stumpel

Post by Ben Wiley Sittler
It's a font "suitcase", and IIRC the font data is actually in
the "resource" fork. At least under Mac OS X, fontforge seems
to be able to deal with these. If you have the file on a
non-Mac OS machine it may well be corrupt, since non-Mac
filesystems do not preserve the resource fork data.

This file was sent to me by a friend, from a Mac computer, by
e-mail, and then saved on my ext3 HD. Any danger that it was
corrupted, or incomplete?

Often old Mac email programs will send both the data fork and resource
fork as attachments when sending email. You might need a good mail
reader like mutt which can let you select which mime element you want
to save in order to get the resource fork saved as its own file.

Rich