[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: KDE 3.1rc6 & fonts



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

On Saturday 11 Jan 2003 10:56 pm, Mario J. Barchéin Molina wrote:
> El Saturday 11 January 2003 23:33, Emmanuel BERRE escribió:
> > Hello,
> >
> > I have updated debian sid last thursday and since I can't use fonts
> > like Nexus or Outcast with KDE. When I select one of this fonts it
> > appears like an helvetica font scheme with a big space size between
> > each characters. I tried to switch on and off antialiasing systeù but
> > nothing changes.
> >
> > Something strange, is that I wasn't able to use antiliasing before
> > this update, when I chose it, nothing happened. Is there a link
> > between the two things ?
> >
> > I just want to know if others have the same problème in order to
> > submit a bug report ?
>
> Yes, I have the same problem with the Linux konsole font, and possibly
> others. I also see the Helvetica font with big spacing In some fonts.
> The antialiasing started to work for me when I installed the sid
> packages, like you. With my previous custom-compiled KDE 3.1
> antialiasing didn't work. I don't know if this is related to the
> fontconfig package changes.

I too have the problem - and whats more, it only happens on one machine and 
not the other.  I am convinced it first occurred when I installed the 
fontconfig package - and although removing the package varies the behaviour, 
I can't get it to go back like it was.  I suspect it has something to do with 
upgrading to libxft2 - but what I don't know.

I used qt designer to write a test program to see if that was the problem, but 
I can't get my test programme to reproduce the problem.  I am slowing working 
up to build a complete chrooted test environment and then to compile kde from 
scratch and put debug on.

I have also reported it as a bug at bugs.kde.org 

http://bugs.kde.org/show_bug.cgi?id=52538     


- - but have had no feedback that anyone else has the problem.  I posted here 
asking someone to check things but noone did.  There is a screen dump of the 
problem which I attached to the bug report - it can be found here

http://bugs.kde.org/attachment.cgi?id=688&action=view

- -- 
Alan Chandler
alan@chandlerfamily.org.uk
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+IXzEuFHxcV2FFoIRAjbcAJ0eUzCBgdJy/Hg8fMkX/D6uD3XvMgCeOXAG
y1LzQuM1GMALuh1L1dngtGQ=
=YD/B
-----END PGP SIGNATURE-----



Reply to: