Re: patch -- fix resolution in pango (win32 backend)

[Tor Lillqvist <tml iki fi>]

Joaquin Cuenca Abela writes:
 > If you're ready to give a fake dpi for big monitors, why are you
 > reluctant to give a fake dpi for desktop monitors?

Because desktop monitors are all viewed at more or less the same
distance, regardless of size. Huge screens are usually viewed at a
(much) larger distance. What would be really correct would be to
specify the viewing angle of the screen. But specifying the width and
height is equivalent, as long as the viewing distance is
constant.

 > Certainly not.  If you're using a 1900x1200 resolution you will
 > have buttons, icons, scroll bars, everything with the same number
 > of pixels, but not with the same size.  Fonts are not an exception.

Maybe, maybe not. Some might prefer to see the increased pixel amount
used just for the benefit of smoother font outlines, for instance.

 > But nobody expects to have their fonts growing with the resolution,
 > while everything else remains with the same size.

(You mean fonts growing in pixels, I assume.) So, why is then that a
Pango font specification has the size *in points*, not in pixels?

Oh well, I think I am understanding some of your points better
now. But I still don't see how your arguments are related to using
those "logical inches" in the Windows API. Or is there a nonlinear
relationship between the true monitor size and its size in logical
inches? (Like, if the monitor is 24", Windows might indeed say its
size is 24 logical inches, but if it is 15", Windows says its size is
maybe 17 logical inches? Ouch.)

--tml