ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: output file size with repeated image
Date: Tue, 14 Apr 2015 19:39:00 +0200	[thread overview]
Message-ID: <552D50B4.5010907@wxs.nl> (raw)
In-Reply-To: <552D4949.8090407@gmx.es>

On 4/14/2015 7:07 PM, Pablo Rodriguez wrote:
> Dear list,
>
> I have the following sample:
>
>      \setupexternalfigure[location=default]
>      \starttext
>      \startmode[repeated-image]
>      \dorecurse{10}{
>          \dorecurse{10}{
>              \dorecurse{10}{
>                  \externalfigure[cow]\input zapf\par}}}
>      \stopmode
>      \startmode[single-image]
>      \externalfigure[cow]
>      \dorecurse{10}{
>          \dorecurse{10}{
>              \dorecurse{10}{
>                  \input zapf\par}}}
>      \stopmode
>      \startmode[no-image]
>      \dorecurse{10}{
>          \dorecurse{10}{
>              \dorecurse{10}{
>                  \input zapf\par}}}
>      \stopmode
>      \stoptext
>
> Output file sizes with different modes are the following:
>
>      --mode=repeated-image    745KB
>
>      --mode=single-image      303KB
>
>      --mode=no-image          302KB
>
> Although the image is the same (and it is only embedded once) file size
> with repeated image is almost two and a half times that the version with
> a single image.
>
> Is this right or am I missing something?

(1) each reference to an image takes some 40 bytes (uncompressed)
(2) when you include the image n times you get 3 times as many pages 
which means 400 more page descriptions etc, so you need to add 2 times 
no image minus font overhead which is about what you see

context does some aggressive object sharing anyway so on the average the 
pdf files produced are quite efficient

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
___________________________________________________________________________________

  reply	other threads:[~2015-04-14 17:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-14 17:07 Pablo Rodriguez
2015-04-14 17:39 ` Hans Hagen [this message]
2015-04-14 18:17   ` Pablo Rodriguez

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=552D50B4.5010907@wxs.nl \
    --to=pragma@wxs.nl \
    --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).