From: Henning Hraban Ramm <texml@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \externalfigure question
Date: Fri, 17 Feb 2017 15:42:03 +0100 [thread overview]
Message-ID: <AD1D9A71-713E-45D9-BB26-8036EFEC1656@fiee.net> (raw)
In-Reply-To: <op.yvs544s0p7eajd@marco.fz-rossendorf.de>
Am 2017-02-17 um 15:20 schrieb j. van den hoff <veedeehjay@gmail.com>:
> 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)?
I can’t tell you anything about the difference in calculations, otherwise it depends on what you want to achieve: I always use width= or height=, because I need specific sizes of my images. Or I define maxwidth=\textwidth. I never had a case where the actual scaling would have been important - maps might be a use case.
Greetlings, Hraban
---
http://www.fiee.net
http://wiki.contextgarden.net
GPG Key ID 1C9B22FD
___________________________________________________________________________________
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 14:42 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 [this message]
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=AD1D9A71-713E-45D9-BB26-8036EFEC1656@fiee.net \
--to=texml@fiee.net \
--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).