Re: cm fonts status - SOLVED - v2

-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 f

Re: cm fonts status - SOLVED - v2

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 01 April 2003 23:06, John Levon wrote: > On Tue, Apr 01, 2003 at 04:56:24PM +0300, Dan Armak wrote: > > > Hmm. Looking at it, it provides the mapping of the orig bluesky type1 fonts, > > not that of the bakoma ones.

Re: cm fonts status - SOLVED - v2

-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 fon

Re: cm fonts status - SOLVED

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 31 March 2003 19:30, Dan Armak wrote: > How that name got there, I've no idea, since it is called "kappa" in the > original bluesky type1 font, so either my generating scripts or pfaedit > itself are at fault..

Re: cm fonts status - SOLVED

fault... I'll try to fix this - there's a whole bunch of characters around kappa in msbm10 that have the wrong names (the names of the unicode chars that should be at their address). Meanwhile a quick explanation of when lyx uses unicode values, and when it uses character names, would be

Re: cm fonts status - SOLVED

ut 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 SIG

Re: cm fonts status - SOLVED

wants them. If it doesn't... - -- 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+iGV5UI2RQ41fiVERAoyqAJ9rjDekStSTa44f//HWa0zAQzvvhwCfaszP /2DB6if/o

Re: cm fonts status

-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

cm fonts status

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://w

Re: easy lyx crash

ecessary. Thanks ! Bye. Aborted No time to do more testing right now, but it does happen. - -- 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) iD8DB

Re: Trying to fix the qt + cm fonts issue

1:41, John Levon wrote: > On Tue, Mar 18, 2003 at 09:33:33PM +0200, Dan Armak wrote: > > > qt 3.1.0. lyx 1.3.0. I haven't had time to try lyx cvs yet (and qt 3.1.1/2 has > > Please do, it has different code I think ... > > john > - -- Dan Armak Gentoo Linux develope

Re: Trying to fix the qt + cm fonts issue

qstr(font.rawName()) << endl; I'll try lyx 1.3.x cvs now, with this change. Fetching lyx cvs... - -- 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/Linu

Trying to fix the qt + cm fonts issue

me figure out why it finds cmr10 but not cmmi10. fc-list displays it correctly. So does the font list in qtconfig. I even tried substituting cmr10 for cmmi10 in qtconfig - nothing happened. Weird. Does anyone know what's behind this? What should I do to debug this further? - -- Dan Arm