From: "Peter Münster" <pmlists@free.fr>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: bug in \externalfigure
Date: Thu, 01 Aug 2013 15:52:41 +0200 [thread overview]
Message-ID: <87a9l1wmae.fsf@micropit.couberia.selfip.net> (raw)
In-Reply-To: <027C1595-7898-4B75-A677-BA4C24FE9B3F@icloud.com> (Jannik Voges's message of "Thu, 01 Aug 2013 14:27:28 +0200")
On Thu, Aug 01 2013, Jannik Voges wrote:
> The first two \externalfigure-commands (with cow) will give a grey placeholder
> with 'state:unknown' in it.
Yes, you need "\setupexternalfigures[location=default]" for finding the
sample files of the distribution.
> The third \externalfigure-command (\externalfigure[test]) will work,
> and the last one won't. In this example, you will get an empty third
> page and the text after the \externalfigure-command doesn't appear in
> the pdf. 'test' can be a pdf-file or jpeg-file (I only tested whose
> types of files).
If you want, that other people can reproduce your problem, you have at
least 2 possibilities:
1.) You use "\setupexternalfigures[location=default]" and the sample
files of the distribution.
2.) Or if 1.) doesn't work, you provide somewhere the needed files for
reproducing the problem.
See also
http://wiki.contextgarden.net/ConTeXt_Mailing_Lists#Before_asking_on_the_list
--
Peter
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2013-08-01 13:52 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 [this message]
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
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=87a9l1wmae.fsf@micropit.couberia.selfip.net \
--to=pmlists@free.fr \
--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).