<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div><blockquote type="cite" class=""><div class="">On Aug 28, 2015, at 6:21 AM, Pantxo Diribarne <<a href="mailto:pantxo.diribarne@gmail.com" class="">pantxo.diribarne@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class=""><div class=""><div class="">Hi,<br class=""><br class=""></div>In Octave we are using the default <span class=""><tt class="">GL2PS_USE_CURRENT_VIEWPORT</tt></span>
argument in the page initialization. This leads to a mismatch between
the original figure size (for which the viewport is returned in pixels)
and the ouput eps/pdf that has the same size in points. To sum up: a 400x400
*pixels* opengl window will be printed as a 400x400 *points* eps file.<br class=""><br class=""></div><div class="">This would not really matter if we had only vectorial objects in our figures ... but we have text that are supposed to have a fixed size. For this we use (intentionally???) a nasty trick which leads to have a font size on-screen that is lower than it should (a 10 pts font is displayed as 10 pixels one...)<br class=""></div><div class=""><br class=""></div><div class="">How should we go if we want to draw an eps that has the same *physical* size has our on-screen figure, e.g. is there a way to specify the screen resolution so that gl2ps is able to translate pixels to points?<br class=""><br class=""></div><div class="">Pantxo</div></div></div></div></blockquote><br class=""></div><div>The root object (handle = 0) includes the property “ScreenPixelsPerInch”. This can be used to determine the physical figure size. Then it *should* be as simple as setting PaperPosition property to the physical size.</div><div><br class=""></div><div>I had worked on the displayed fontsize, and recall some confusion (on my part) when reading the Matlab docs and examining the rendered results. My confusion was compounded by my display’s resolution being 72 pixels/inch.</div><div><br class=""></div><div>My present display has 129 pixels/inch. As a test, I tried ...</div><div><br class=""></div><div><div><span class="Apple-tab-span" style="white-space:pre"> </span>clf ()</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>text (0.5, 0.5, {‘FOO’,’BAR'}, 'fontsize', 72, 'horizontalalignment', 'center')</div></div><div><br class=""></div><div>… in both Octave (default branch) and Matlab.</div><div><br class=""></div><div>The results are below. The lines are separated by 110 pixels high for Matlab and 84 for Octave.</div><div><br class=""></div><div>I think the intention was that the on screen size should be correct and that the print() function would handle the scaling between pixels and points.</div><div><br class=""></div><div>Ben</div><div><br class=""></div><div><br class=""></div><div><img apple-inline="yes" id="8EF11426-8FB2-479A-B1A3-D100DE7E7C8A" height="420" width="560" apple-width="yes" apple-height="yes" src="cid:6EAE7898-02BD-440C-ADBE-C52C83C4E379@cfl.rr.com" class=""><img apple-inline="yes" id="5A5801BA-CB76-4ECE-AAE4-F305EFE12A69" height="420" width="560" apple-width="yes" apple-height="yes" src="cid:037A654C-B6C0-44B5-96C9-33D8F579FE5E@cfl.rr.com" class=""></div><br class=""></body></html>