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: bug in \externalfigure
Date: Fri, 02 Aug 2013 13:13:11 +0200	[thread overview]
Message-ID: <51FB9447.2030904@wxs.nl> (raw)
In-Reply-To: <9FBDCAB8-9C4B-4580-9B80-90EC163E5906@icloud.com>

On 8/1/2013 5:19 PM, Jannik Voges wrote:
> You are right. I was a little bit confused, because I didn't know, that you have to add 'location=default' to get the sample files, so I thought, that might also be buggy. 'test' is a test-file (pdf, jpeg, ...) in the current directory (I have not mentioned that). In my second Mail I included the source files with 'test.pdf'. You can see the bug there or when you compile the example below. This time, the sample files are loaded correctly and you will see, that the second graphic and sentence are missing.
>
> \setupexternalfigures[location=default]
>
> \starttext
>
> \externalfigure[cow.pdf]
>
> \page
>
> This text will appear.
>
> \externalfigure[cow.pdf][width=10cm]
>
> This text will not appear.
>
> \stoptext

i can't repeat your problem here .. two figures and two texts show up

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
___________________________________________________________________________________


  parent reply	other threads:[~2013-08-02 11:13 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-01 12:27 Jannik Voges
2013-08-01 13:08 ` Marco Patzer
2013-08-01 13:44   ` Jannik Voges
2013-08-01 13:56   ` Aditya Mahajan
2013-08-01 14:01     ` luigi scarso
2013-08-01 14:43       ` Alan BRASLAU
2013-08-01 14:54         ` luigi scarso
2013-08-01 14:55         ` Hans Hagen
2013-08-01 14:14     ` Marco Patzer
2013-08-01 13:51 ` Aditya Mahajan
2013-08-01 13:52 ` Peter Münster
2013-08-01 15:19   ` Jannik Voges
2013-08-01 20:34     ` Peter Münster
2013-08-01 21:32       ` Jannik Voges
2013-08-02  7:56         ` Peter Münster
2013-08-02 11:13     ` Hans Hagen [this message]
2013-08-02 18:36       ` Jannik Voges
2013-08-02 18:55         ` Hans Hagen
2013-08-02 19:05           ` Jannik Voges
2013-08-02 19:35             ` Hans Hagen
2013-08-02 19:49               ` Jannik Voges
2013-08-02 19:58                 ` Hans Hagen
2013-08-02 20:08                   ` Jannik Voges
2013-08-03 10:45                     ` Jannik Voges

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=51FB9447.2030904@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).