![](https://secure.gravatar.com/avatar/9e7785e70cf330d459899d007d59bff8.jpg?s=120&d=mm&r=g)
On Fri, 17 Feb 2017 17:51:11 +0100, Alan Braslau
On Fri, 17 Feb 2017 17:04:27 +0100 "j. van den hoff"
wrote: On Fri, 17 Feb 2017 15:43:29 +0100, Hans Hagen
wrote: * if `scale=' is not the way to achieve invariant and unambiguous size of images embedded in the document, what is? `width=XXX cm'? i.e.: how is this supposed to be done correctly(TM)? just use width=4cm and so
understood, will do (thanks to henning, too, for answering). in any case, I have settled for `width={fraction}\textwidth' as the most convenient solution. but if you don't mind explaining: _why_ is `scale' causing me a problem in the first place? what is the actual intended (and good) use of this parameter?
scale= is EXTREMELY useful when combining external figures and one wants to retain uniform linewidths, text pointsizes, etc. Using width= (or height=) in such a case will lead to very poor results, indeed.
OK, thanks. will try to remember that. -- but in this case (important/useful parameter...) I am still wondering, why the same value (say: scale=750) leads to totally different figure size in the pdf output for two different machines/OSes? I understand that scale=1000 means "original size" but in want sense? it seems to dependent on the machine/engine's idea of dpi resolution or something like that ... joerg
Alan
P.S. Personally, I find that scale=1000 meaning 1 is an unfortunate left-over from the previous century - prehistoric days. In the chemistry module rewrite, we take abs(scale)>10 in units of 1000, just to confuse things. (Hans: I would suggest dropping this...).
-- Using Opera's revolutionary email client: http://www.opera.com/mail/