From kde-bugs-dist Thu Jun 07 06:04:58 2001 From: Paul Date: Thu, 07 Jun 2001 06:04:58 +0000 To: kde-bugs-dist Subject: Bug#26565: select text doesn't apply font change X-MARC-Message: https://marc.info/?l=kde-bugs-dist&m=99189484515593 On Sunday 03 June 2001 11:04 pm, you wrote: > On Sunday 03 June 2001 20:45, Paul wrote: > > Hi, > > > > Saga continues... > > > > I found that to reproduce this you have to select more than a single > > word. For instance selecting just yesterday as I might of lead you too > > believe wasn't enough. > > No, you said the last two words, and that's what I tried.... > > > So I tried 'I did this' and change the font to gothic I then get 'I did > > thi' > > > > Move of the screen to force a repaint does not redraw the screen with the > > correct chars. > > > > The page is started as A4, and this is the third sentence in the > > document, I can do it anywhere. In fact I just noticed that if I just > > type in this font it does the same screwy things and it looks like the > > cursor is one char behind where it is attempting to print the char you > > just wrote. > > So it starts to look more and more like a bug in the font metrics of that > particular font. > Can you test the same font with another KDE program, then with a Qt-only > program, then with an X program ? This way we can see at which level the > bug is. I don't know what program is puely QT and X that would support this font, any ideas as I'd need to download these. In KPresenter using the same font I get the exact same problem. I tried to test this in star office but it doesn't have this font and actually looks as though it has its own fonts since most of the ones it listed I have no where else. > > Do you use font anti-aliasing ? No > What's your X server's DPI setting ? (xdpyinfo | grep resolution) 75 x 75 dpi > > > So if you had a word of 5 chars the cursor is at 4 and the 5 char is only > > half resembled on the screen. > > > > By half I mean if it were an X you'd see a greater sign (>) looking part > > of the X. (Hope that makes sense). > > Yes, I understand that. It's basically that the font metrics are incorrect > (width too small).