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 .png-externalfigures
Date: Tue, 21 May 2019 10:07:01 +0200	[thread overview]
Message-ID: <6f47df88-9417-3c80-8ef6-8ce7e298d81b@xs4all.nl> (raw)
In-Reply-To: <20190517082323.ky25slf6y7k53vur@nan>

On 5/17/2019 10:23 AM, Rudolf Bahr wrote:
> 
> On Thu, May 16, 2019 at 02:40:07PM +0200, Hans Hagen wrote:
>> 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
> 
> 
> No. I never use neither ImageMagick nor GraphicsMagick to generate images in
> .pdf-format. Even with my scanner software I produce always .jpg-images though it
> is capable to produce .pdf-output too. The only .pdf-files I'm doing are made by
> ConTeXt-LMTX!
> 
> I shall append another, interesting MWE. There is a .png-image which is, as it
> occasionally happens, represented as it should, by ConTeXt. And then the same .png-image
> to which I added a red frame by GIMP2.10. This one shows artefacts in ConTeXt!
> 
> I'm adding the .log-file too. There again is a luatex-warning, as I could observe them
> often in ConTeXt-LMTX:
the second image has a mask which is split off (an all 0xFF mask btw) .. 
it shows ok in acrobat so maybe gimp is at fault here?

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-21  8:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-17  8:23 Rudolf Bahr
2019-05-21  8:07 ` Hans Hagen [this message]
2019-05-23  6:43   ` Rudolf Bahr

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=6f47df88-9417-3c80-8ef6-8ce7e298d81b@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).