-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday 01 April 2003 23:21, Dan Armak wrote: > OK, I'll look at the problematic chars tomorrow. With any luck they will have > a single cause of failure and I will find it :-)
It looks like there's some problem in pfaedit, the font editor I use. (If you know of any other font editor I could try please tell me, I couldn't find anything else that handles both type1 and truetype). If I open the cmsy font from bakoma, pfaedit converts it to its internal postscript format. Saving as truetype again is basically exporting from pfaedit's pov. Now, if I export the cmsy font agin, _making no changes_, the newly created font won't provide the 'broken' characters such as /leq. If I open the new font in pfaedit again, though, the characters are still there and look perfectly ok, so I don't really know what the problem is. I'm going to mail the pfaedit-devel list asking for help. - -- 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+ivqdUI2RQ41fiVERAjMIAJ4vPzEPifjZ5HQwGnIUNYvWexGcSQCdH1ps sB5CEK88d+RROpU7LuK+FvE= =FJnE -----END PGP SIGNATURE-----
