From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Kip Warner <kip@thevertigo.com>
Subject: Re: Clarification on methods of toggling maximum compression
Date: Sat, 11 Aug 2012 00:57:22 +0200 [thread overview]
Message-ID: <502591D2.1020706@wxs.nl> (raw)
In-Reply-To: <1344637191.32545.85.camel@kip-laptop>
On 11-8-2012 00:19, Kip Warner wrote:
> Hey list,
>
> I've noticed at least three methods of setting what I think is the
> generated PDF to maximum compression.
the official way, plays nicely with pdf standards:
> \setupbackend[level=9]
pretty low level, might even disappear (overloaded):
> \pdfcompresslevel9
low level, but wil stay:
> \maximumpdfcompression
> Are these all redundant? Do they do different things? Do I need but one
> to achieve the desired maximum compression of the resulting PDF?
keep in mind that max compression slows down processing and often not
much is gained
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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-08-10 22:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-10 22:19 Kip Warner
2012-08-10 22:57 ` Hans Hagen [this message]
2012-08-10 23:00 ` Kip Warner
2012-08-10 23:05 ` Hans Hagen
2012-08-10 23:26 ` Kip Warner
2012-08-11 10:02 ` Hans Hagen
2012-08-11 18:32 ` Kip Warner
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=502591D2.1020706@wxs.nl \
--to=pragma@wxs.nl \
--cc=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).