Re: cm fonts status - SOLVED - v2

[Dan Armak]

-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. (If you 
know of any other font editor I could try please tell me, I couldn't find 
anything else that handles both type1 and truetype).

If I open the cmsy font from bakoma, pfaedit converts it to its internal 
postscript format. Saving as truetype again is basically exporting from 
pfaedit's pov. Now, if I export the cmsy font agin, _making no changes_, the 
newly created font won't provide the 'broken' characters such as /leq. If I 
open the new font in pfaedit again, though, the characters are still there 
and look perfectly ok, so I don't really know what the problem is. I'm going 
to mail the pfaedit-devel list asking for help.

- -- 
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+ivqdUI2RQ41fiVERAjMIAJ4vPzEPifjZ5HQwGnIUNYvWexGcSQCdH1ps
sB5CEK88d+RROpU7LuK+FvE=
=FJnE
-END PGP SIGNATURE-

Re: cm fonts status - SOLVED - v2

[Dan Armak]

-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. (If you 
know of any other font editor I could try please tell me, I couldn't find 
anything else that handles both type1 and truetype).

If I open the cmsy font from bakoma, pfaedit converts it to its internal 
postscript format. Saving as truetype again is basically exporting from 
pfaedit's pov. Now, if I export the cmsy font agin, _making no changes_, the 
newly created font won't provide the 'broken' characters such as /leq. If I 
open the new font in pfaedit again, though, the characters are still there 
and look perfectly ok, so I don't really know what the problem is. I'm going 
to mail the pfaedit-devel list asking for help.

- -- 
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+ivqdUI2RQ41fiVERAjMIAJ4vPzEPifjZ5HQwGnIUNYvWexGcSQCdH1ps
sB5CEK88d+RROpU7LuK+FvE=
=FJnE
-END PGP SIGNATURE-

Re: cm fonts status - SOLVED - v2

[Dan Armak]

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

Re: cm fonts status - SOLVED - v2

[Dan Armak]

-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 and the bluesky fonts 
  natively?...
 
 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... bummer.

  A full list of the problematic chars:
  \leq \kappa \circleddash \nleqq \upuparrows
 
 This isn't a full list :)

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 :-)

- -- 
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+ifTEUI2RQ41fiVERAvsLAKCCZbvDqdNL1tSokrLPseuF9/zmvgCfZB+v
5O9WqNlVBnlyECfOtJ/Phv0=
=p0R0
-END PGP SIGNATURE-

Re: cm fonts status - SOLVED - v2

[Dan Armak]

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

Re: cm fonts status - SOLVED - v2

[Dan Armak]

-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 and the bluesky fonts 
> > natively?...
> 
> 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... bummer.

> > A full list of the problematic chars:
> > \leq \kappa \circleddash \nleqq \upuparrows
> 
> This isn't a full list :)

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 :-)

- -- 
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+ifTEUI2RQ41fiVERAvsLAKCCZbvDqdNL1tSokrLPseuF9/zmvgCfZB+v
5O9WqNlVBnlyECfOtJ/Phv0=
=p0R0
-END PGP SIGNATURE-

Re: cm fonts status - SOLVED

[Dan Armak]

-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 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).
Just put the fonts somewhere under /usr/share/fonts, run fc-cache as root and 
as user, run lyx with a qt3.1 interface (that uses fontconfig+xft2) and see 
if the matheditor's formulas show the right characters.

Someone please confirm that it works (and I wonder about the xforms frontend, 
since it doesn't use fontconfig afaik...), and if it does work, I'll provide 
details about it if anyone wants them. If it doesn't... shudder

- -- 
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/oymnp56fAt6djnU=
=Zl44
-END PGP SIGNATURE-

Re: cm fonts status - SOLVED

[Dan Armak]

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

Re: cm fonts status - SOLVED

[Dan Armak]

-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. (BTW I'd really appreciate an explanation of 
what characters it takes from what font, since most of them are present in 
several.)
2) exists in bakoma msbm10 as kappa at unicode address 007b. It also exists 
in my bluesky-derived font at 007b, but isn't called kappa. Rather, it's 
called braceleft, which is the unicode char that really owns location 007b. 
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...

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 much appreciated.

- -- 
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+iG0iUI2RQ41fiVERAnV/AJ9CJOt3XIIFbuAUfnmNtV5mU05t+wCfT2BA
fEHuGjGXkbPgeoOj6t3UIPA=
=huWs
-END PGP SIGNATURE-

Re: cm fonts status - SOLVED

[Dan Armak]

-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 actually told pfaedit to change every 
character's name to match its new unicode value! So most characters now have 
wrong names...

Problem is, if I tell pfaedit not to change the names (call from script 
SetUnicodeValue(value, 0) ) it segfaults... Don't know why, or how to go 
around it, yet...

- -- 
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+iG/zUI2RQ41fiVERAvcfAJ9JEQA6yQ+GiotfOHU38cvF1fT5mACfQiCH
w52n1GuG0bGFb6AHeRqP5Aw=
=BPyM
-END PGP SIGNATURE-

Re: cm fonts status - SOLVED

[Dan Armak]

-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 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).
Just put the fonts somewhere under /usr/share/fonts, run fc-cache as root and 
as user, run lyx with a qt3.1 interface (that uses fontconfig+xft2) and see 
if the matheditor's formulas show the right characters.

Someone please confirm that it works (and I wonder about the xforms frontend, 
since it doesn't use fontconfig afaik...), and if it does work, I'll provide 
details about it if anyone 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/oymnp56fAt6djnU=
=Zl44
-END PGP SIGNATURE-

Re: cm fonts status - SOLVED

[Dan Armak]

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

Re: cm fonts status - SOLVED

[Dan Armak]

-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. (BTW I'd really appreciate an explanation of 
what characters it takes from what font, since most of them are present in 
several.)
2) exists in bakoma msbm10 as "kappa" at unicode address 007b. It also exists 
in my bluesky-derived font at 007b, but isn't called "kappa". Rather, it's 
called "braceleft", which is the unicode char that really owns location 007b. 
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...

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 much appreciated.

- -- 
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+iG0iUI2RQ41fiVERAnV/AJ9CJOt3XIIFbuAUfnmNtV5mU05t+wCfT2BA
fEHuGjGXkbPgeoOj6t3UIPA=
=huWs
-END PGP SIGNATURE-

Re: cm fonts status - SOLVED

[Dan Armak]

-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 actually told pfaedit to change every 
character's name to match its new unicode value! So most characters now have 
wrong names...

Problem is, if I tell pfaedit not to change the names (call from script 
SetUnicodeValue(value, 0) ) it segfaults... Don't know why, or how to go 
around it, yet...

- -- 
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+iG/zUI2RQ41fiVERAvcfAJ9JEQA6yQ+GiotfOHU38cvF1fT5mACfQiCH
w52n1GuG0bGFb6AHeRqP5Aw=
=BPyM
-END PGP SIGNATURE-

cm fonts status

[Dan Armak]

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

Re: cm fonts status

[Dan Armak]

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

I've tried saving a type1 font (.pfb) in unicode encoding and pfaedit told me 
type1 only supports 1-byte encodings. Which I don't fully understand, because 
the bluesky fonts have more than 256 characters each, again according to 
pfaedit.

It seems the merging of cmr into the other fonts made a mishmash of the 
encodings, but even without the merging I can't get it to work right. If 
there's anyone around who knows fonts, of you know of the 'right' place to 
ask for help, please tell.

- -- 
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+hdwXUI2RQ41fiVERAvr+AJ9HxJwKh38UUzKX0O2mG5ZYnKcduACePsEt
VFDvCAWpm07yNQXZvyvfW94=
=vSrh
-END PGP SIGNATURE-

cm fonts status

[Dan Armak]

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

Re: cm fonts status

[Dan Armak]

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

I've tried saving a type1 font (.pfb) in unicode encoding and pfaedit told me 
type1 only supports 1-byte encodings. Which I don't fully understand, because 
the bluesky fonts have more than 256 characters each, again according to 
pfaedit.

It seems the merging of cmr into the other fonts made a mishmash of the 
encodings, but even without the merging I can't get it to work right. If 
there's anyone around who knows fonts, of you know of the 'right' place to 
ask for help, please tell.

- -- 
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+hdwXUI2RQ41fiVERAvr+AJ9HxJwKh38UUzKX0O2mG5ZYnKcduACePsEt
VFDvCAWpm07yNQXZvyvfW94=
=vSrh
-END PGP SIGNATURE-

Re: easy lyx crash

[Dan Armak]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Thursday 20 March 2003 18:45, John Levon wrote:
 On Thu, Mar 20, 2003 at 04:13:23PM +0100, Jos van den Oever wrote:
 
  I just crashed lyx 1.3.1. The recipe is easy:
 
 xforms frontend ?
 
  - open lyx
  - press Alt-F to open the File menu
  - press i (for import, which is not acivated and the cause of the problem)
 
 Why isn't the menu activated ?
 
 It is for me as it should be.

Well, I can reproduce it too (incl. the menu shortcut not working - the menu 
item selection indicator just disappears). QT frontend (qt 3.1.2).

It says:
[EMAIL PROTECTED] danarmak $ lyx -dbg all
Setting debug level to all

I reproduce the crash
lyx: SIGSEGV signal caught
Sorry, you have found a bug in LyX. Please read the bug-reporting instructions 
in Help-Introduction and send us a bug report, if necessary. 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)

iD8DBQE+efm0UI2RQ41fiVERAobDAJ0Z2rfyBiyq5Rx/3htd4krUXIjT/QCfUkOA
vGI5PVfFjfnW2bPIaI3/+xU=
=WHco
-END PGP SIGNATURE-

Re: easy lyx crash

[Dan Armak]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Thursday 20 March 2003 18:45, John Levon wrote:
> On Thu, Mar 20, 2003 at 04:13:23PM +0100, Jos van den Oever wrote:
> 
> > I just crashed lyx 1.3.1. The recipe is easy:
> 
> xforms frontend ?
> 
> > - open lyx
> > - press Alt-F to open the File menu
> > - press i (for import, which is not acivated and the cause of the problem)
> 
> Why isn't the menu activated ?
> 
> It is for me as it should be.

Well, I can reproduce it too (incl. the menu shortcut not working - the menu 
item selection indicator just disappears). QT frontend (qt 3.1.2).

It says:
[EMAIL PROTECTED] danarmak $ lyx -dbg all
Setting debug level to all


lyx: SIGSEGV signal caught
Sorry, you have found a bug in LyX. Please read the bug-reporting instructions 
in Help->Introduction and send us a bug report, if necessary. 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)

iD8DBQE+efm0UI2RQ41fiVERAobDAJ0Z2rfyBiyq5Rx/3htd4krUXIjT/QCfUkOA
vGI5PVfFjfnW2bPIaI3/+xU=
=WHco
-END PGP SIGNATURE-

Trying to fix the qt + cm fonts issue

[Dan Armak]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hello,

I've been trying to fix this (known) issue. In brief, it consists of qt (when 
using version 3.1 compiled with fontconfig+xft2 support) not picking up the 
bluesky computer modern fonts (why?). Therefore the matheditor displays weird 
symbols (or in lyx 3.1.x cvs, the symbols' names). The lyx INSTALL etc. 
recommend using the BaKoMa fonts package (aka latex-ttf-fonts.tar.gz), but it 
has a restrictive non-commercial, no-embedded-redistribution license.

Dekel Tsur made clear the problem was that the bluesky fonts have a family 
name of 'Computer Modern', while lyx requests family names like cmr10, cmmi10 
etc. So I decided simply to edit the bluesky fonts (using pfaedit if that's 
important). I added the right names, converted them to truetype to make sure 
fontconfig picked them up, put them in /usr/share/fonts and reran fc-cache.

Now I have:
[EMAIL PROTECTED] danarmak $ fc-list | grep cm
cmex10:style=Medium
cmsy10:style=Medium
cmr10:style=Medium
cmmi10:style=Medium

Looks ok. But, when running lyx -dbg font, I get:
snip
Family eufm10 isAvailable ?found family Eufm10
Family cmsy10 isAvailable ?found family Cmsy10
Family cmmi10 isAvailable ?found family Cmmi10
Family cmr10 isAvailable ?found family Cmr10
Family cmex10 isAvailable ?found family Cmex10
Family msam10 isAvailable ?found family Msam10
Family msbm10 isAvailable ?found family Msbm10
Family wasy10 isAvailable ?found family Wasy10
Family symbol isAvailable ?found family Symbol
snip
Looking for font family cmr10 ...  got it !
snip
Looking for font family cmmi10 ...  FAILED :-(
Font 'cmm, Medium, Upright, Normal, math, Emphasis Off, Underline Off, Noun 
Off, Language: English' matched by
Luxi Sans-11.8:snip...

I can't for the life of 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 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+d2WZUI2RQ41fiVERAqPiAJ9ptrCqz5011Gk9EjSfKVeAL+135QCfZZcH
tEgYrBCUeaCoGgKNfErKa5Y=
=fJrg
-END PGP SIGNATURE-

Re: Trying to fix the qt + cm fonts issue

[Dan Armak]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Tuesday 18 March 2003 20:40, John Levon wrote:
 What qt + lyx versions are these ? latest 1.3.1cvs ?

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 
issues here - I hope I don't upgrade qt in a month form now to determine 
that's the source of all problems... But that's really unlikely.)

 
 Can you add some code to output font.rawName() in
 frontends/qt2/qfont_loader.C:getSymbolFont() ? Just add several lines of
 lyxerr  rawname is   fromqstr(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/Linux)

iD8DBQE+d3SNUI2RQ41fiVERAqdcAJ95qJ4kWbe5lJ5DHrzZxddgzzc4mQCfdhrX
z2d9xyoYyEnZhBd9V+T2bM0=
=l7U+
-END PGP SIGNATURE-

Re: Trying to fix the qt + cm fonts issue

[Dan Armak]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

OK, tried lyx 1.3.1 cvs. (BTW I do have qt 3.1.2 - I forgot about that :-)

I added three debug printouts as you suggested at the locations in
getSymbolFont, they say what statement they're after and print
font.rawName(). Now I get the logfile attached.

The first debug statement I added is right after the creation and init of
font. With the fonts that aren't found for whatever reason (although they
show up in fc-list _and_ in qtconfig), Luxi Sans is specified as the font at
this stage already. Now what?

On Tuesday 18 March 2003 21: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 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+d6KoUI2RQ41fiVERAowUAJ9aXpuM80daSfsooLM0AHMjagBrMACeOMQ8
dBOi9jmaBwMuRz/118ynfXM=
=nBvF
-END PGP SIGNATURE-


log.gz
Description: GNU Zip compressed data

Trying to fix the qt + cm fonts issue

[Dan Armak]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hello,

I've been trying to fix this (known) issue. In brief, it consists of qt (when 
using version 3.1 compiled with fontconfig+xft2 support) not picking up the 
bluesky computer modern fonts (why?). Therefore the matheditor displays weird 
symbols (or in lyx 3.1.x cvs, the symbols' names). The lyx INSTALL etc. 
recommend using the BaKoMa fonts package (aka latex-ttf-fonts.tar.gz), but it 
has a restrictive non-commercial, no-embedded-redistribution license.

Dekel Tsur made clear the problem was that the bluesky fonts have a family 
name of 'Computer Modern', while lyx requests family names like cmr10, cmmi10 
etc. So I decided simply to edit the bluesky fonts (using pfaedit if that's 
important). I added the right names, converted them to truetype to make sure 
fontconfig picked them up, put them in /usr/share/fonts and reran fc-cache.

Now I have:
[EMAIL PROTECTED] danarmak $ fc-list | grep cm
cmex10:style=Medium
cmsy10:style=Medium
cmr10:style=Medium
cmmi10:style=Medium

Looks ok. But, when running lyx -dbg font, I get:

Family eufm10 isAvailable ?found family Eufm10
Family cmsy10 isAvailable ?found family Cmsy10
Family cmmi10 isAvailable ?found family Cmmi10
Family cmr10 isAvailable ?found family Cmr10
Family cmex10 isAvailable ?found family Cmex10
Family msam10 isAvailable ?found family Msam10
Family msbm10 isAvailable ?found family Msbm10
Family wasy10 isAvailable ?found family Wasy10
Family symbol isAvailable ?found family Symbol

Looking for font family cmr10 ...  got it !

Looking for font family cmmi10 ...  FAILED :-(
Font 'cmm, Medium, Upright, Normal, math, Emphasis Off, Underline Off, Noun 
Off, Language: English' matched by
Luxi Sans-11.8:

I can't for the life of 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 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+d2WZUI2RQ41fiVERAqPiAJ9ptrCqz5011Gk9EjSfKVeAL+135QCfZZcH
tEgYrBCUeaCoGgKNfErKa5Y=
=fJrg
-END PGP SIGNATURE-

Re: Trying to fix the qt + cm fonts issue

[Dan Armak]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Tuesday 18 March 2003 20:40, John Levon wrote:
> What qt + lyx versions are these ? latest 1.3.1cvs ?

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 
issues here - I hope I don't upgrade qt in a month form now to determine 
that's the source of all problems... But that's really unlikely.)

> 
> Can you add some code to output font.rawName() in
> frontends/qt2/qfont_loader.C:getSymbolFont() ? Just add several lines of
> lyxerr << "rawname is " << fromqstr(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/Linux)

iD8DBQE+d3SNUI2RQ41fiVERAqdcAJ95qJ4kWbe5lJ5DHrzZxddgzzc4mQCfdhrX
z2d9xyoYyEnZhBd9V+T2bM0=
=l7U+
-END PGP SIGNATURE-

Re: Trying to fix the qt + cm fonts issue

[Dan Armak]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

OK, tried lyx 1.3.1 cvs. (BTW I do have qt 3.1.2 - I forgot about that :-)

I added three debug printouts as you suggested at the locations in
getSymbolFont, they say what statement they're after and print
font.rawName(). Now I get the logfile attached.

The first debug statement I added is right after the creation and init of
font. With the fonts that aren't found for whatever reason (although they
show up in fc-list _and_ in qtconfig), Luxi Sans is specified as the font at
this stage already. Now what?

On Tuesday 18 March 2003 21: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 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+d6KoUI2RQ41fiVERAowUAJ9aXpuM80daSfsooLM0AHMjagBrMACeOMQ8
dBOi9jmaBwMuRz/118ynfXM=
=nBvF
-END PGP SIGNATURE-


log.gz
Description: GNU Zip compressed data