-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.
On Tue, Apr 01, 2003 at 11:21:23PM +0300, Dan Armak wrote:
> > Qt doesn't let us use normal X fonts when using fontconfig, at least on
> > Red Hat etc.
>
> Ah yes, I forgot the original problem - fontconfig won't select/return the
> bluesky fonts because they don't provide the latin1 characters.
-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. Why can't lyx use that
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. Why can't lyx use that and the bluesky fonts
> natively?...
Qt doesn't let us use normal X fonts when using fontconfig, at lea
On Tue, Apr 01, 2003 at 04:56:24PM +0300, Dan Armak wrote:
> 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
> ch
-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 app
On Mon, Mar 31, 2003 at 06:57:41PM +0300, Dan Armak wrote:
> Someone please fetch and test http://cvs.gentoo.org/~danarmak/fonts.tar.bz2 .
> These are modified bluesky fonts. Use as a replacement to the bakoma ones (no
> change needed to lyx code).
Can you check if things work if you set LANG=r
-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...
Sorry, my mistake. My scripts
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
-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
I looked at kappa as an example. It:
1) exists in cmmi10 (both bakoma and bluesky-derived versions). So apparently
lyx isn't using that font here. (
-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
(as
On Mon, Mar 31, 2003 at 06:57:41PM +0300, Dan Armak wrote:
>
> Sorry for shouting SOLVED like that, but I've been working on this for the
> last three days, and solved the problem through sheer stubbornness, because I
> started out with zero knowledge... So now I'm really happy :-)
>
> Someone
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello everyone,
Sorry for shouting SOLVED like that, but I've been working on this for the
last three days, and solved the problem through sheer stubbornness, because I
started out with zero knowledge... So now I'm really happy :-)
Someone please f
-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 correct unicode numbers atta
On Sat, Mar 29, 2003 at 08:09:41PM +0300, Dan Armak wrote:
> Hello again,
Hi.
> 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.
OK.
> This is also easily fixed; I used p
-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 hav
16 matches
Mail list logo
