-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday 29 March 2003 20:09, Dan Armak wrote: > If I'm right, it is caused by encoding info problems. The bakoma fonts, for > reference, are encoded as "ISO 10646-1 (Unicode, BMP)" (according to pfaedit) > and have the correct unicode numbers attached to the various glyphs. The > bluesky fonts OTOH have the (apparently) unicode glyph names, but don't have > the numbers (pfaedit shows most characters as U+????). The question is, > assuming I'm right, how to get those numbers there.
I've tried saving a type1 font (.pfb) in unicode encoding and pfaedit told me type1 only supports 1-byte encodings. Which I don't fully understand, because the bluesky fonts have more than 256 characters each, again according to pfaedit. It seems the merging of cmr into the other fonts made a mishmash of the encodings, but even without the merging I can't get it to work right. If there's anyone around who knows fonts, of you know of the 'right' place to ask for help, please tell. - -- Dan Armak Gentoo Linux developer (KDE) Matan, Israel Public GPG key: http://www.gentoo.org/~danarmak/danarmak-gpg-public.key -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+hdwXUI2RQ41fiVERAvr+AJ9HxJwKh38UUzKX0O2mG5ZYnKcduACePsEt VFDvCAWpm07yNQXZvyvfW94= =vSrh -----END PGP SIGNATURE-----
