ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Rudolf Bahr <quasi@quasi.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Strange behavior concerning pdf-output of externalfigures
Date: Mon, 29 Apr 2019 10:52:59 +0200	[thread overview]
Message-ID: <20190429085259.65ulsdewr5jr5cmm@nan> (raw)
In-Reply-To: <4191cc1a-41b6-07c7-1130-7b54eab914ed@xs4all.nl>

On Sun, Apr 28, 2019 at 11:12:43PM +0200, Hans Hagen wrote:
> On 4/28/2019 8:10 PM, Rudolf Bahr wrote:
> > 
> > Dear list,
> > 
> > I'm getting unexplainable artefacts in the pdf-output.
> > 
> > My MWE is:
> > 
> > ------------------
> > \starttext
> > 
> > \externalfigure
> >      [input.png]
> >      [width=100mm]
> > 
> > \stoptext
> > ------------------
> > 
> > I append the output "MWE.pdf" and the input-figure "input.png" for comparison.
> > 
> > I'm experiencing the artefacts with some figures which are all several years old.
> > Until now it never happened in conTeXt programs. Because I installed a new OS
> > (LinuxMint) on my workstation at the same time I tried 3 pdfviewers (okular,
> > evince, xpdf) all with the same result.
> 
> different inclusion code
> 
> > I'm using LuaMetaTeX, Version 2.00.0,
> > ConTeXt  ver: 2019.04.13 17:25 MKIV beta  fmt: 2019.4.15
> > 
> > Please, do you have any idea what could be the reason?
> no problems here .. can you update?
> 
> Hans


Sorry, but even after updating to
ConTeXt  ver: 2019.04.29 09:02 MKIV beta  fmt: 2019.4.29
I'm experiencing the same artefacts as before.

Please, what means "different inclusion code"?

Rudolf
___________________________________________________________________________________
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-04-29  8:52 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 [this message]
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

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=20190429085259.65ulsdewr5jr5cmm@nan \
    --to=quasi@quasi.de \
    --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).