ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
	Rudolf Bahr <quasi@quasi.de>
Subject: Re: Strange behavior concerning pdf-output of externalfigures
Date: Thu, 16 May 2019 14:40:07 +0200	[thread overview]
Message-ID: <a96d0c1d-b865-5515-d88b-f5057a640e79@xs4all.nl> (raw)
In-Reply-To: <20190516102117.ww5c4tyihm662mls@nan>

On 5/16/2019 12:21 PM, Rudolf Bahr wrote:
> The problem with artefacts in .png images is still unsolved for me.
> I can circumvent it by using .jpg or .tiff images instead of .png images
> as long as no transparent areas in the images are needed. As far as I know
> .jpg and .tiff formats cannot handle transparancy, do they?
> 
> Now in .log files messages like
> "luatex warning  > pdfe: invalid 11 0 R object at offset 223611"
> can be seen. Please, what do they mean?
Does that come from an pdf generated by image magick>? If so, the 
problem is there ... the last years I've seen lots of converted files 
with bogus pdf objects. (Kind of harmless but still.)

Hans


-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

      reply	other threads:[~2019-05-16 12:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-28 18:10 Rudolf Bahr
2019-04-28 21:12 ` Hans Hagen
2019-04-29  8:52   ` Rudolf Bahr
2019-04-29  9:41     ` Rudolf Bahr
2019-04-29 11:18     ` Hans Hagen
2019-04-29 12:45       ` Rudolf Bahr
2019-04-29 22:32       ` Alan Braslau
2019-04-30 14:56         ` Rudolf Bahr
2019-05-16 10:21 ` Rudolf Bahr
2019-05-16 12:40   ` 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=a96d0c1d-b865-5515-d88b-f5057a640e79@xs4all.nl \
    --to=j.hagen@xs4all.nl \
    --cc=ntg-context@ntg.nl \
    --cc=quasi@quasi.de \
    /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).