From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: Wrong image size evaluation
Date: Thu, 18 May 2006 17:28:42 +0200 [thread overview]
Message-ID: <446C92AA.1000908@elvenkind.com> (raw)
In-Reply-To: <ops9q5aif39niby6@localhost>
nico wrote:
> Hello,
>
> I have some troubles with a PNG image, that is not correctly rendered by
> context (too small). The difference I've found with another correctly
> displayed image is that the file does not contain any resolution unit (but
> a pixels/inch default seems reasonable).
But pixels/cm is equally reasonable, and that is why pdftex ignores
invalid settings in PNG images completely, and uses its internal
default instead. You can control that default resolution by setting
\pdfimageresolution to an appropriate guess:
{\pdfimageresolution=72 \externalfigure[ch01dia1.png]}
Cheers, Taco
next prev parent reply other threads:[~2006-05-18 15:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-18 15:00 nico
2006-05-18 15:28 ` Taco Hoekwater [this message]
2006-05-18 16:23 ` nico
2006-05-18 17:06 ` Sanjoy Mahajan
2006-05-18 17:21 ` Taco Hoekwater
2006-05-18 20:29 ` gnwiii
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=446C92AA.1000908@elvenkind.com \
--to=taco@elvenkind.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).