ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Cc: Context List <ntg-context@ntg.nl>
Subject: Re: Linux Acroread memory link with Context
Date: Mon, 31 May 1999 01:33:02 +0200	[thread overview]
Message-ID: <3751CAAE.6B0BDCA5@wxs.nl> (raw)
In-Reply-To: <Pine.SGI.4.04.9905291708110.156134-100000@sono>

Matthew Baker wrote:

> So, to me it seems that it is either a Context or pdftex bug since the
> same images converted to PDF with Distiller don't cause problems.  Or if
> not a bug, something which triggers a bug in Linux Acroread that Distiller
> PDF files don't trigger.
> 
> For a test document, all I'm using is several pages of \startcombination
> ... \stopcombination with 9 images in each. Images are 256x384 pixels
> each, so they are not in any way unreasonably big.  I monitor memory usage
> by watching swap space in xosview.
> 
> Any ideas why this might happen?  Next step for me is to try something
> with plain pdftex and includegraphics commands to see if that causes the
> same problem.

This really sounds strange, because we have documents with hundreds of
illustrations and large bitmaps.

Technically context/pdftex uses an xobject, which is the appropriate
structure. You can set \pdfcompresslevel=0 and take a look at the file.
You can try to follow the object pointers. 

I'll ask Thanh too, 

Hans

-----------------------------------------------------------------
                                          Hans Hagen | PRAGMA ADE
              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.nl
-----------------------------------------------------------------


      reply	other threads:[~1999-05-30 23:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-05-29 15:28 Matthew Baker
1999-05-30 23:33 ` Hans Hagen [this message]

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=3751CAAE.6B0BDCA5@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).