On Thu, 27 May 2004 22:18:20 +0100, you wrote:
wineprefixcreate doesn't create a config file. This means we use a (wrong) formula to decide what the DPI is supposed to be.
Why do you mean (wrong) ? Do you not get the dpi values used by X? Or is it that is uses the X values but those are wrong?
It's wrong because nobody tells the system how big their monitor is these days so it always picks a DPI that is too small.
Here X gets it from the monitor at start-up (via the logic of the video card). I did not realize that my situation is not normal.
Somehow, I think setting a proper dpi should ideally be done in X. But in practice ...
I agree with you that 95 dpi is about the minimum that is being used today. But I would keep this the minimum: if the dpi is set bigger then it is probably intentional. Either monitor magic or from a careful system administration.
Rein.
On Fri, 28 May 2004 11:11:32 +0200, Rein Klazes wrote:
Why do you mean (wrong) ? Do you not get the dpi values used by X? Or is it that is uses the X values but those are wrong?
Well, I talked a bit with Huw about this so apologies to him if I mangled what he said, but ... it seems that the functions we use to get the size of the screen don't always return correct values. I don't know why.
Here X gets it from the monitor at start-up (via the logic of the video card). I did not realize that my situation is not normal.
If you mean via DDC then I guess this should work in most places, but for whatever reason it does not work here :( In particular, xdpyinfo says:
screen #0: dimensions: 1024x768 pixels (321x241 millimeters) resolution: 81x81 dots per inch
So it appears to know the screen size (I measured with a ruler and 321x241 is right), but it gets the DPI too small anyway. At 81 dpi the text is hardly readable.
I agree with you that 95 dpi is about the minimum that is being used today. But I would keep this the minimum: if the dpi is set bigger then it is probably intentional. Either monitor magic or from a careful system administration.
Yep, this only affects the default when nothing is specified in the config file (in fact in the default config file this was always specified anyway so this is just restoring the old behaviour in the absence of he config file really).
thanks -mike
On Fri, May 28, 2004 at 01:59:02PM +0100, Mike Hearn wrote:
On Fri, 28 May 2004 11:11:32 +0200, Rein Klazes wrote:
Why do you mean (wrong) ? Do you not get the dpi values used by X? Or is it that is uses the X values but those are wrong?
Well, I talked a bit with Huw about this so apologies to him if I mangled what he said, but ... it seems that the functions we use to get the size of the screen don't always return correct values. I don't know why.
Here X gets it from the monitor at start-up (via the logic of the video card). I did not realize that my situation is not normal.
If you mean via DDC then I guess this should work in most places, but for whatever reason it does not work here :( In particular, xdpyinfo says:
screen #0: dimensions: 1024x768 pixels (321x241 millimeters) resolution: 81x81 dots per inch
So it appears to know the screen size (I measured with a ruler and 321x241 is right), but it gets the DPI too small anyway. At 81 dpi the text is hardly readable.
Well actually 1024 pixels in 321mm is about 81dpi, so the XServer is doing the sums correctly. I guess what we need to know is what resolution Windows returns on this same machine.
Huw.
On Fri, May 28, 2004 at 01:59:02PM +0100, Mike Hearn wrote:
screen #0: dimensions: 1024x768 pixels (321x241 millimeters) resolution: 81x81 dots per inch
So it appears to know the screen size (I measured with a ruler and 321x241 is right), but it gets the DPI too small anyway. At 81 dpi the text is hardly readable.
No, this is quite good. If you want to be exact, it's 81.028x80.943 dots per inch, so 81x81 is pretty good.
Yep, this only affects the default when nothing is specified in the config file (in fact in the default config file this was always specified anyway so this is just restoring the old behaviour in the absence of he config file really).
Well, I don't think we should have this in the config file normally. That is, this value is (correctly) determined automatically. If it's not, it has to be corrected for X anyway, so we should just use what X gives us. However, Windows may adjust the real DPI, so we may have to apply a correction factor. I'd personally nuke this Wine-specific option altogether.
On Fri, 28 May 2004 13:59:02 +0100, you wrote:
If you mean via DDC then I guess this should work in most places,
Yes, I can find the size here back in the /var/log/XFree86.log, similar to what xdpyinfo reports.
but for whatever reason it does not work here :( In particular, xdpyinfo says:
screen #0: dimensions: 1024x768 pixels (321x241 millimeters) resolution: 81x81 dots per inch
So it appears to know the screen size (I measured with a ruler and 321x241 is right), but it gets the DPI too small anyway. At 81 dpi the text is hardly readable.
Sorry, I believe you that your font is too small too read, but dpi means nothing else then dots-per-inch. And you have:
1024 dots per 321/25.4=12.6 inches which is 81.0 dpi.
Are you watching a font with a known size? Try selecting same font and size in eg gnome-terminal. The sizes should be the same.
Rein.
-
Dimitrie O. Paun -
Huw D M Davies -
Mike Hearn -
Rein Klazes