ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: Kip Warner <kip@thevertigo.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Clarification on methods of toggling maximum compression
Date: Sat, 11 Aug 2012 12:02:28 +0200	[thread overview]
Message-ID: <50262DB4.2010708@wxs.nl> (raw)
In-Reply-To: <1344641215.32545.93.camel@kip-laptop>

On 11-8-2012 01:26, Kip Warner wrote:
> On Sat, 2012-08-11 at 01:05 +0200, Hans Hagen wrote:
>> hm, suspicious
>
> Really? It's over 300 pages in length and contains plenty of vector
> graphics (more text). But actually that 70 MB seems an overestimate and
> I must have been looking at something else.
>
>> yes, that's best because as soon as that command is called, the set
>> value of 'level' is used, no matter what other values has been set
>
> Here is the result of some experimentation:
>
> 23,396,929 Bytes using just \setupbackend[level=9].
>
> 21,945,243 Bytes using the aforementioned, \pdfcompresslevel9, and
> \maximumpdfcompression.
>
> 23,396,827 Bytes using none of those three.
>
> So I guess I'm still not sure which one to use since the one you said
> should be sufficient doesn't seem to compress it fully.
>
>> never use \pdf* commands directly .. way too low level and use the oher
>> command only for fast tests (i use it in small test files)

I made

\setupbackend[level=9]

listen to that setting also if no 'format' is set. Also, in the report 
at the end of a run, the compress levels are reported so that you can 
check it.


-----------------------------------------------------------------
                                           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
___________________________________________________________________________________


  reply	other threads:[~2012-08-11 10:02 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
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 [this message]
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=50262DB4.2010708@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).