-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday 31 March 2003 19:32, John Levon wrote:
> On Mon, Mar 31, 2003 at 07:30:26PM +0300, Dan Armak wrote:
> 
> > 1) exists in cmmi10 (both bakoma and bluesky-derived versions). So 
apparently 
> > lyx isn't using that font here. (BTW I'd really appreciate an explanation 
of 
> > what characters it takes from what font, since most of them are present in 
> > several.)
> 
> Look at lib/symbols file.

Hmm. Looking at it, it provides the mapping of the orig bluesky type1 fonts, 
not that of the bakoma ones. Why can't lyx use that and the bluesky fonts 
natively?...

Anyway I decided I was beaten on the path of trying to automagically convert 
the bluesky fonts to ttf ones that look like bakoma's. And having already 
spent about 20 hours on that, I decided I could spare another hour or two 
doing the same thing by hand.
So I've taken the bakoma fonts, removed all glyphs, and copied over the 
bluesky glyphs, changing the font properties as needed. In the end nothing 
remains of the bakoma version but the way the characters are arranged, which 
is what we want. This should be ok wrt bakoma's copyright (IANAL)...

This is still WIP due to issue #2 below, but since I'm prolly not going to do 
anything more with this today, I wanted to update the list. The fonts are at 
http://cvs.gentoo.org/~danarmak/fonts-v2.tar.bz2 - testing appreciated (last 
time it took about 10 minutes for the big problems to be found, but this time 
I've tried to do better testing).

Known issues:

1. Quality loss: tolerable for on-screen editing (imo at least).
Details: I converted the glyphs from postscript to truetype. That's apparently 
a lossy conversion (unlike the other way around) - which I only found out 
when it was too late. I converted to opentype (which has the same spline 
format as type1) which recovered most of the quality (but is still worse than 
the printed bluesky). So it looks worse than the bakoma stuff (due to the 
lossy conversion I suppose), but tolerable for editing (as long as you don't 
write too many formulas :-). Probably something could be done if I started 
all over again... (The font is also smaller than the bakoma one - try using a 
bigger fontsize. Can we get a separate fontsize setting for the mathed?)

Also, the hinting went mad for some reason and most chars were over-hinted 
into smudged oblivion. I told pfaedit to remove all hints/instructions and 
autohint. Now it's usable - but I probably lost some of the custom hinting 
instructions that make bluesky look good (in particular most of the Latin 
alphabet in cmr10 had custom stuff). Again, tolerable (for me) since this is 
just for editing.

2. Some chars won't draw - lyx displays a square instead. This is the major 
thing left to be fixed.

Looking at the kappa char for example (from cmmi10), every other char in the 
font draws OK and AFAICS there's absolutely no difference between it and the 
bakoma one, in the kappa char's properties or otherwise. I really don't know 
what to do about this kappa problem...

A full list of the problematic chars:
\leq \kappa \circleddash \nleqq \upuparrows

3. At some point the characters lost their names and got the names of the 
unicode characters at their encoding positions instead. This doesn't affect 
lyx which draws by encoding value not name (I wish I'd known that sooner), 
but it makes further editing of the fonts icky. If there's sufficiently good 
reason, I can create them again, and hopefully keep the names that time.

4. There are still no eufm10 and wasy10 fonts, because there aren't such 
bakoma fonts (maybe they are in the bigger bakoma collection on ctan though). 
However AFAICS lyx doesn't need/use these fonts anywhere? I tested all the 
characters listed in the matheditor float and they were present without these 
fonts (except for the ones from issue 2 above, and they got drawn as squares 
and not written in red, so they must be from the existing fonts as well).

- -- 
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+iZqMUI2RQ41fiVERAjNRAJ4sp8d1ld7StP838ZQDyreQVSD1ZgCbBoZI
6grXoK17v5YZubRNfpVHpdA=
=WV20
-----END PGP SIGNATURE-----

Reply via email to