-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello again,
I left the issue alone when it beagn to look like a bug in either qt or
fontconfig. Yesterday I gave it another go, here's a summary of what I've
learned by now (and a call for help):
1. The bluesky type1 computer modern fonts from have the wrong family names
('Computer Modern' and 'Euler' while lyx wants 'cmr10' etc.) but that's very
easily fixed.
2. After that change is made, and fontonfig is told about these fonts, lyx
still gets the default system font when requesting them, except for cmr10.
This is because the other cm fonts do not include the standard latin
characters, and fontconfig refuses to select such fonts. Presumably this is
what someone (I forget who) meant when he told me on lyx-users that
fontconfig didn't support the bluesky fonts.
This is also easily fixed; I used pfaedit to import all the glyphs in cmr10
into every other font. Now all of them are selectable by fontconfig, and lyx
gets them.
However pfaedit segfaults when merging type1 fonts. I have no idea why and
I've failed to fix it. So I've had to save them as truetype and merge that. I
hope there's been no loss of quality or information.
3. Now lyx gets the fonts, but draws squares instead of nearly every
character, and wrong glyphs instead of the rest. This is the current (and I
hope last) problem.
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. (E.g. some good interface
I could use to script massive font changes, while taking the right data from
the bakoma fonts, assuming the glyph names are identical in bakoma and
bluesky). Or alternatively - in what encoding are the bluesky fonts, and how
do I put that info in the font files?
Hope someone can help me, because I'm quit out of my depth here as far as font
editing is concerned... I'm going to keep trying, but may have already
committed some blunders (fex. when going from type1 to truetype, the encoding
seems to have been changed from 'custom' to the unicode definition, don't
know if that's important), so any suggestions would be more than welcome.
- --
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+hdNcUI2RQ41fiVERAlbyAJ0Sqaom/kG9yq3jA0w+stp1054GpQCfXzSD
psV3zELm3q2BDCtV0Bo8wwg=
=ioDM
-----END PGP SIGNATURE-----
