-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday 31 March 2003 19:07, Dekel Tsur wrote: > I had a problem with the following symbols: \kappa, \upuparrows, > \backepsilon, \nleqq, \backepsilon and \circleddash.
If you can tell me in which fonts these are supposed to be, I can add them (assuming I can find them somewhere in the bleusky or other texmf type1 fonts). Or I could just check all the bakoma fonts to see which have these... (Assuming the character names are also 'kappa', 'upuparrows' etc?) For the latter two I would need to know the "unicode" values to use as well (what does lyx expect them to be?) I say "unicode", because the values used by bakoma aren't the real unicode values for these chars - they are some weird custom and (to me) meaningless values, which is why lyx can't use any truly unicode font that provides the necessary symbols. It took me two days to realize that, after which I just spent several hours scripting pfaedit to grab the character name --> 'unicode' value mappings from the bakoma fonts, and rearranging the bluesky fonts to match. > They appear as a square (the latter two also appear as squares when using > the bakoma fonts, so it is possible that the problem is in lib/symbols). > I'll investigate later. > Also, eufm10.ttf is missing That's because bakoma doesn't have eufm10 either (nor wasy10). I intentionally didn't put in anything that doesn't exist in the bakoma package, because I wouldn't know what unicode values to give the chars. - -- 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+iGq7UI2RQ41fiVERAiRSAJ45MTJMbpLqlhgxkgiyyoz7CWkoDgCdE3py Vvx4nThJh5OTPX1hDhtuLeQ= =wFJL -----END PGP SIGNATURE-----
