From: Alan Braslau <braslau.list@comcast.net>
To: Marco Patzer <lists@homerow.info>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: degrade module
Date: Mon, 18 Feb 2019 08:25:05 -0700 [thread overview]
Message-ID: <20190218082505.558e4b71@comcast.net> (raw)
In-Reply-To: <20190218101320.145280d8@homerow>
On Mon, 18 Feb 2019 10:13:20 +0100
Marco Patzer <lists@homerow.info> wrote:
> Yes. I didn't put much thought into it and assumed there is a better
> solution.
My working solution is to put figures in subdirectories by resolution,
that is externally, once and for all, using whatever is your favorite tool
to "degrade" pixel resolution to whatever value one desires, then setting
global macro (\FigRes) to this subdirectory name.
So, for example,
\def\FigRes{300/}
...
\externalfigure [\FigRes MyFigureName]
I do this as I have *very* high resolution images as my source
(also high resolution "depth", i.e. 16 bit) and it makes no sense
to include these as is in my documents.
It's very robust.
Alan
___________________________________________________________________________________
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:[~2019-02-18 15:25 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-14 19:49 Lutz Haseloff
2019-02-14 20:22 ` Marco Patzer
2019-02-14 20:37 ` Peter Münster
2019-02-14 20:32 ` Peter Münster
2019-02-14 20:41 ` Wolfgang Schuster
2019-02-14 21:00 ` Peter Münster
2019-02-14 20:44 ` Hans Hagen
2019-02-15 6:56 ` Lutz Haseloff
2019-02-15 7:24 ` Henning Hraban Ramm
2019-02-15 7:25 ` Marco Patzer
2019-02-15 9:22 ` Lutz Haseloff
2019-02-15 10:08 ` Marco Patzer
2019-02-15 10:48 ` Lutz Haseloff
2019-02-15 11:23 ` Marco Patzer
2019-02-17 11:14 ` Peter Münster
2019-02-18 9:13 ` Marco Patzer
2019-02-18 10:03 ` Peter Münster
2019-02-18 15:25 ` Alan Braslau [this message]
2019-02-18 21:09 ` Peter Münster
2019-02-18 21:23 ` Alan Braslau
2019-02-18 22:50 ` Peter Münster
2019-02-18 23:21 ` Alan Braslau
2019-02-19 9:42 ` Peter Münster
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=20190218082505.558e4b71@comcast.net \
--to=braslau.list@comcast.net \
--cc=lists@homerow.info \
--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).