From: Kip Warner <kip@thevertigo.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: \externalfigure and file size
Date: Wed, 18 Jan 2012 16:25:37 -0800 [thread overview]
Message-ID: <1326932737.5532.74.camel@kip-laptop> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1045 bytes --]
Hey list,
I have a number of \externalfigure commands to typeset some svg images.
This is often handy to have them vectorized because it allows for the
user to zoom in on diagrams of great detail.
In other situations, I find that for images that are not so important,
they would benefit from ConTeXt rasterizing them when they are imported.
The reason for this is I find some vector images get enormously bloated
when they are typeset. As an example, I have a Logo.svg of only 6.8 KB.
The m_k_i_v_Logo.pdf intermediate ConTeXt generates is nearly a megabyte
in size. Why? I have no idea, as they both appear to be the same image
with the same gausian blur.
Is there a flag I can pass certain instances of \externalfigure that
tells the image processing backend that a simple rasterized version of
the figure is fine? Or is there a better approach? I don't want to
pre-convert all of these images to raster formats.
--
Kip Warner -- Software Engineer
OpenPGP encrypted/signed mail preferred
http://www.thevertigo.com
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2012-01-19 0:25 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-19 0:25 Kip Warner [this message]
2012-01-19 7:56 ` Mojca Miklavec
2012-01-19 23:51 ` Kip Warner
2012-01-19 8:23 ` luigi scarso
2012-01-19 23:52 ` Kip Warner
2012-01-20 0:51 ` Marco
2012-01-20 1:02 ` Kip Warner
2012-01-20 9:08 ` Hans Hagen
2012-01-20 23:05 ` Kip Warner
2012-01-21 0:07 ` Hans Hagen
2012-01-21 0:12 ` luigi scarso
2012-01-21 0:15 ` Hans Hagen
2012-01-24 23:28 ` Kip Warner
2012-01-21 0:21 ` Marco
[not found] ` <20120121012234.1553b814@homerow>
2012-01-21 0:27 ` Kip Warner
2012-01-21 0:40 ` Marco
2012-01-21 0:55 ` Hans Hagen
2012-01-21 13:32 ` Marco
2012-01-24 0:33 ` Kip Warner
[not found] ` <20120121014245.794d515b@homerow>
2012-01-21 0:45 ` Kip Warner
2012-01-21 0:54 ` Hans Hagen
2012-01-21 3:31 ` Wagner Macedo
2012-01-21 9:40 ` Hans Hagen
2012-01-24 0:44 ` Kip Warner
2012-01-24 0:17 ` Kip Warner
2012-01-24 11:13 ` Marco
[not found] ` <20120124121433.57a167f4@homerow>
2012-01-24 23:20 ` Kip Warner
2012-01-21 1:46 ` luigi scarso
2012-01-20 23:48 ` Wagner Macedo
2012-01-19 10:58 ` Peter Rolf
2012-01-20 0:01 ` Kip Warner
2012-01-20 0:07 ` Pontus Lurcock
2012-01-20 0:23 ` Kip Warner
2012-01-20 0:45 ` Mojca Miklavec
2012-01-20 0:50 ` Pontus Lurcock
2012-01-20 1:26 ` Kip Warner
2012-01-20 0:13 ` Wagner Macedo
2012-01-20 0:23 ` Kip Warner
2012-01-20 0:43 ` Pontus Lurcock
[not found] ` <CAKGY2Pk_pXNNcks+EaEg0fLYh2ENtb3Cas13duoxihr654vQnQ@mail.gmail.com>
2012-01-20 0:51 ` Kip Warner
[not found] ` <CAKGY2Pk8TC8cJUEDvy5HhaS0NvbLmFcYvS3d6Es7vzUpa63ADg@mail.gmail.com>
2012-01-20 1:01 ` Kip Warner
2012-01-20 1:03 ` Mojca Miklavec
2012-01-20 1:30 ` Kip Warner
2012-01-20 8:55 ` luigi scarso
2012-01-20 23:04 ` Kip Warner
2012-01-20 23:36 ` luigi scarso
2012-01-20 0:14 ` Wolfgang Schuster
2012-01-20 1:24 ` Kip Warner
2012-01-20 0:21 ` Marco
2012-01-20 1:21 ` Kip Warner
2012-01-20 10:18 ` Marco
2012-01-20 10:26 ` Hans Hagen
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=1326932737.5532.74.camel@kip-laptop \
--to=kip@thevertigo.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).