W3C home > Mailing lists > Public > www-svg@w3.org > April 2009

Re: units other than pixels very unprecise? (how should 'top' width /height larger than screen be handled?)

From: Ruud Steltenpool <svg@steltenpower.com>
Date: Tue, 21 Apr 2009 22:51:41 +0200
Message-ID: <49EE31DD.80002@steltenpower.com>
To: www-svg@w3.org
 >>Vista, Opera+Firefox
 >screen that is obviously not the calculated 96 dpi (17.1" 1920x1200)

 > It never is, never has been, and never will be. Windows works with
so-called "logical inches" rather than actual inches, and conventional
software can deal with at most two values for DPI, either 96 dpi
(normal) or 120 dpi (large).

ah right, non-scalability of OS and therefore apps using it.
Thanks for the explanation.

 >Even if Windows could rely on monitors to report their actual nominal
DPI, most monitors have enough adjustability in their image sizes that
it wouldn't be very accurate.

Most likely much more accurate than the 38% off it is now, so useful, 
though indeed not for when precision is needed. Back when they started 
Windows we had CRTs with settings that kept drifting. Now things are 
somewhat better.

 > Many applications that really do care about image size (e.g., graphics
editing software, CAD, etc.) allow you to calibrate your monitors, but
the calibration is specific to the application. You can do the same with
an SVG application running inside a browser, but it would be up to you
to provide the calibration functionality, and to save and retrieve the
parameters as necessary.

Yes, webapp coders can handle it (ask user to pick up a ruler) would 
work. At the same time (for re-use reasons at some point in time) can't 
we in the SVG spec. ask the SVG implementers to provide that functionality?


Ruud Steltenpool
Received on Tuesday, 21 April 2009 20:52:23 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 March 2017 09:47:17 UTC