From: Alan Braslau <alan.braslau@cea.fr>
To: "j. van den hoff" <veedeehjay@gmail.com>, Hans Hagen <pragma@wxs.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \externalfigure question
Date: Fri, 17 Feb 2017 09:51:11 -0700 [thread overview]
Message-ID: <20170217095111.77dbee23@zoo.hsd1.co.comcast.net> (raw)
In-Reply-To: <op.yvtaxpevp7eajd@marco.fz-rossendorf.de>
On Fri, 17 Feb 2017 17:04:27 +0100
"j. van den hoff" <veedeehjay@gmail.com> wrote:
> On Fri, 17 Feb 2017 15:43:29 +0100, Hans Hagen <pragma@wxs.nl> 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.
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...).
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2017-02-17 16:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-17 14:20 j. van den hoff
2017-02-17 14:42 ` Henning Hraban Ramm
2017-02-17 14:43 ` Hans Hagen
2017-02-17 16:04 ` j. van den hoff
2017-02-17 16:51 ` Alan Braslau [this message]
2017-02-17 17:05 ` j. van den hoff
2017-02-17 17:43 ` Hans Hagen
2017-02-17 17:42 ` Hans Hagen
2017-02-17 18:06 ` Alan Braslau
2017-02-17 18:20 ` Hans Hagen
2017-02-17 18:20 ` j. van den hoff
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170217095111.77dbee23@zoo.hsd1.co.comcast.net \
--to=alan.braslau@cea.fr \
--cc=ntg-context@ntg.nl \
--cc=pragma@wxs.nl \
--cc=veedeehjay@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).