[Octave-bug-tracker] [bug #46292] Axes with absolute "units" have wrong dimensions in printout

[ederag]

Follow-up Comment #19, bug #46292 (project octave):

Dear Ben, am I too tired, or are you still missing the point 
(Your axes units still not "centimeters") ?
Thanks for your scripts, but it is not only achieving the final result that
matter (this I figured as much now, after so much work on that). The point is
to get it right even when axes units are in centimeters.

Regarding your observations about dpi, here are some links, maybe related:
http://fr.mathworks.com/help/matlab/creating_guis/dpi-aware-behavior-in-matlab.html?searchHighlight=screenpixelsperinch

Now (2015b) pixels are absolute values (like points, but conversions
system-specific). On mac a pixel is like a point (1/72 "). On windows it is
(1/96 "). Crazy ?
Only on linux do pixels stay screen pixels.

Aidtopia answer is old but interesting:
https://social.msdn.microsoft.com/Forums/windowsdesktop/en-US/73412a1a-36c5-406c-8fcd-fc62e74c5bb5/display-resolution-and-font-size?forum=windowsuidevelopment



    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?46292>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/