From: "j. van den hoff" <veedeehjay@gmail.com>
To: "ntg-context@ntg.nl" <ntg-context@ntg.nl>
Subject: \externalfigure question
Date: Fri, 17 Feb 2017 15:20:54 +0100 [thread overview]
Message-ID: <op.yvs544s0p7eajd@marco.fz-rossendorf.de> (raw)
I am unsure about the "canonical" way to scale images to the desired size.
my current understanding is, that `scale=' should do what I want in a way
portable across `context' incarnations. so currently I use commands like
\externalfigure[image.png][scale=750]
to adjust the image size to my taste.
my problem: the same document looks completely different regarding image
size in the produced pdf with standalone installations on osx64 and
linux-64. actually, on oxx64 I have to use something like `scale=1500'
where on linux-64 `scale=750' seemingly does about the same.
questions:
* what am I missing? why does the same document compile differently? I can
only guess that `context' (or luatex?) has two different opinions of dpi
resolution on the two machines when producing the pdf? where can I
control/check this?
* 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)?
thx/joerg
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
___________________________________________________________________________________
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 reply other threads:[~2017-02-17 14:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-17 14:20 j. van den hoff [this message]
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
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=op.yvs544s0p7eajd@marco.fz-rossendorf.de \
--to=veedeehjay@gmail.com \
--cc=ntg-context@ntg.nl \
/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).