Bug 76977 - font size in web site content oversized
Summary: font size in web site content oversized
Status: RESOLVED NOT A BUG
Alias: None
Product: kcontrol
Classification: Miscellaneous
Component: general (show other bugs)
Version: 3.2
Platform: RedHat Enterprise Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-03-08 01:36 UTC by joaobr
Modified: 2004-03-14 03:24 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description joaobr 2004-03-08 01:36:12 UTC
Version:           3.2 (using KDE KDE 3.2.0)
Installed from:    RedHat RPMs
OS:          Linux

Whatever fonts or sizes I chose in konqueror or kcontrol the webpage font size is oversized. I get normal size when zooming out -2

I saw bug 74460 and other but no solution for my case. This is on FC1 with kde rpms from ftp.kde.org
Linux is update, x also and it was an upgrade from 3.1.4

All other fontsettings from kcontrol are correct applied even to konqueror bars.

Changing default css settings does not make a difference unless on ftp sites

I already reinstalled qt and kdebase and libs, x and fonts, nothing changes

it must be a global setting since all other users even clean new created see the same problem

changings in khtml.css does not change anything either

I had once a similar problem on fbsd where adobe fonts gave my such a headache but uninstalling them the problem went away too, so I changed X settings and run with only one font, all with no change. X is started with 75x75

Where is the reference font size hidden for incfontsizes and decfontsizes? Because whatever settings regarding font type or size I have, chosing "default font size" it goes back to the "oversized" one. I found what that says this is to i18 related in khtml_part.cpp.
Comment 1 Stephan Kulow 2004-03-08 15:13:55 UTC
what means oversized here? Much too large or a pixel too large?
Comment 2 joaobr 2004-03-08 15:40:32 UTC
On Monday 08 March 2004 11:13, Stephan Kulow wrote:
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.
> http://bugs.kde.org/show_bug.cgi?id=76977
> ------- Additional Comments From coolo kde org  2004-03-08 15:13 -------
> what means oversized here? Much too large or a pixel too large?

means like I wrote
I need to decrease font size two times to get normal appearance
It seems that it displayes 14px if it should be 10px

Jo
Comment 3 joaobr 2004-03-10 01:35:26 UTC
Here is what is going on, seems to be a real bug
I was reviewing my xpdyinfo and I saw that the screen x/y in mm where not ok
I got 75x75 dots and a 1200px monitor

solution: I set in XF86Config my screen dimension in mm as in my case to

DisplaySize  286 214 as for my 14.1" 

what gave my then from xdpyinfo
screen #0:
  dimensions:    1024x768 pixels (286x214 millimeters)
  resolution:    91x91 dots per inch
  depths (7):    24, 1, 4, 8, 15, 16, 32

what resolved my case but not the problem

Then I repeated the upgrade from 3.1.4 on FC1 on another pc and got the same problem (another nb), I repeated the same upgrade on another normal PC and did not got the problem. After some more upgrades I noticed that the problem might be related to monitor size detection for laptops or lcd screens. Appearently normal crt monitors are correctly recgnized. I upgraded one normal pc and selected lcd monitor and got the above problem.

I think somebody could look after this because my problem appears a lot by searching google (since kde3.0 and earlier I found) with the most bizzare tries to solve the problem.

I did not checked resolved because I think it should be done when the problem maker is found
Comment 4 Stephan Kulow 2004-03-10 10:22:43 UTC
thanks for the analysis. it proves it's no KDE problem, but a misconfiguration.  Report to Fedora/Red Hat

Comment 5 joaobr 2004-03-10 10:49:58 UTC
You guys always are looking for the easy way, or not confirmed or you're 
slamming the problem to somebody else. I agree that this may be the case for 
lot's of problems but if you are in charge here you should check the writings 
more carefully to distinguish ...

At least you could pay attention to what I wrote.

I wrote that this happens after upgrading from kde3.1.4 to 3.2 using the rpms 
on kde's ftp

Also I wrote that all machines were working perfectly BEFORE upgrading them.

So under this circunstancies you still write it is misconfiguration and should 
tell that to redhat. You're funny you know. 

Even it is is only misconfiguration but under the view that you find hundreds 
or more similare problems on the net shows that something is wrong. It is not 
the case that everybody is stupid. Misunderstanding like misconfiguration is 
a matter of misexplication what definitly is a bug as well when continiously 
repeated.

So when so many peoples are having troubles with this issue somebody should 
pay attention to that. I know it may be hard having a comercial stand without 
getting payed but it is not only you who spend his time, I spent mine also 
and if I had no interest in helping others I didn't even posted my clue here. 
And last, spending my time I never would have liked to here: let me in peace, 
go away and bother others ...

congratulations

On Wednesday 10 March 2004 06:22, Stephan Kulow wrote:
> |Removed

Comment 6 Stephan Kulow 2004-03-10 11:02:26 UTC
I'm aware that you're problem arose through an update from packages named KDE. But nothing in KDE writes XFree86Config or can tries to estimate the size of your screen. And as a matter of fact, the experts from red hat are the best to help you.

I could very well leave the bug report open for another year, but that wouldn't help you either. So I help you in telling you, that the KDE project can't help you with this problem. I'd love to send you a guy from the service crew, but we just don't have a service crew. 
Comment 7 joaobr 2004-03-10 11:41:00 UTC
the issue is not the state of the bug report, it is the problem itself
also it is not for ME, I can help myself
nobody said that KDE writes to xf86config either, but read on

and then RH? I thought X would be an xfree issue following your line of 
logic ...

My guess here is that it is qt related - provided and needed by kde, right, 
but read on

you say that kde do not write to xf86config and perhaps you answered too 
quick ...

what is if the render ext are not loaded and you enable anti-aliasing in KDE?
what is about enabling sub-pixel hinting?
what is about virtual screens

fact also is that kde admin screws XF86Config when you are using a 
font-server, kde-admin pulls it out and sets all physical font paths in the 
file section



On Wednesday 10 March 2004 07:02, Stephan Kulow wrote:
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.
>
> http://bugs.kde.org/show_bug.cgi?id=76977
>
>
>
>
> ------- Additional Comments From coolo kde org  2004-03-10 11:02 -------
> I'm aware that you're problem arose through an update from packages named
> KDE. But nothing in KDE writes XFree86Config or can tries to estimate the
> size of your screen. And as a matter of fact, the experts from red hat are
> the best to help you.
>
> I could very well leave the bug report open for another year, but that
> wouldn't help you either. So I help you in telling you, that the KDE
> project can't help you with this problem. I'd love to send you a guy from
> the service crew, but we just don't have a service crew.

Comment 8 Craig Drummond 2004-03-12 18:06:19 UTC
Hi,

By "kde admin screws XF86Config" do you mean kfontinst? (i.e. fonts:/, or the 
font-installer KControl module)?

Also, can you send your XF86Config, /etc/X11/fs/config files before, and after 
the screwed up state? That way I can see what is going on? The installer 
should read XF86Config to determine if you are using a font-server. It looks 
for a FontPath specified as "unix/:" - if found, then it should be modifying 
the fs/config file instead. Are you saying that this is not working?

Craig.

Comment 9 joaobr 2004-03-13 00:38:06 UTC
before it was "unix/:7100"

and after it is

fontpath "path"
.. all others available

either way is working but I prefere to stay with a font server and config should not change it without my concern right
Comment 10 Craig Drummond 2004-03-13 02:34:23 UTC
> ------- Additional Comments From joao wipmail com br  2004-03-13 00:38
> ------- before it was "unix/:7100"
>
> and after it is
>
> fontpath "path"
> .. all others available
>
> either way is working but I prefere to stay with a font server and config
> should not change it without my concern right

I agree - obviously somethings going wrong with my checking. Can you please 
open a new bug report on this against the font-installer 
(kcontrol/kfontinst)? On the new report, can you please attach the real 
files.

Thanks.

Craig.

Comment 11 Craig Drummond 2004-03-14 03:24:04 UTC
> I agree - obviously somethings going wrong with my checking. Can you please
> open a new bug report on this against the font-installer
> (kcontrol/kfontinst)? On the new report, can you please attach the real
> files.

OK. I can confirm this error. The check was working the 1st time, but on 
subsequent attempts the setting was always being reset to the non-xfs case. 
I've now committed a fix to KDE_3_2_BRANCH, and HEAD.

Craig.