From: Marco <netuse@lavabit.com>
To: ntg-context@ntg.nl
Subject: Re: \externalfigure and file size
Date: Fri, 20 Jan 2012 01:21:31 +0100 [thread overview]
Message-ID: <20120120012131.26bf636a@homerow> (raw)
In-Reply-To: <1327017688.5532.98.camel@kip-laptop>
On 2012-01-19 Kip Warner <kip@thevertigo.com> wrote:
> Whatever ConTeXt is doing with it, that 7KB SVG gets bloated to nearly a
> meg at 976KB. This happens as Logo.svg is transformed into intermediate
> m_k_i_v_Logo.pdf.
I had similar issues some weeks ago. A workaround
was to use \pdfcompresslevel9 You can also try
\maximumpdfcompression, which is apparently preferred
(see some recent thread on the list).
Marco
___________________________________________________________________________________
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 prev parent reply other threads:[~2012-01-20 0:21 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-19 0:25 Kip Warner
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 [this message]
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=20120120012131.26bf636a@homerow \
--to=netuse@lavabit.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).