From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: bug in \externalfigure
Date: Thu, 1 Aug 2013 09:56:24 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1308010953420.3506@nqv-guvaxcnq> (raw)
In-Reply-To: <20130801130854.GA8003@homerow>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1007 bytes --]
On Thu, 1 Aug 2013, Marco Patzer wrote:
> On 2013–08–01 Jannik Voges wrote:
>
>> I found a bug in the current ConTeXt Beta with externalfigure. The following minimal example will show you what happens
>>
>>
>> \starttext
>>
>> \externalfigure[cow]
>>
>> \externalfigure[cow][width=10cm]
>>
>> \page
>>
>> \externalfigure[test]
>
> This reads in the file
>
> texmf-modules/doc/fonts/urw/garamond/test.tex
>
> which is not desired. But I assume you have a “test” graphic in your
> current directory which is used instead, so this is unrelated to
> your problem.
I think that the advice of omitting the file extension given in most LaTeX
introductions is more trouble than it is worth in ConTeXt. Omitting file
extensions is important if you are generating both dvi and pdf outputs. In
ConTeXt, one never uses the DVI output, so I think that one should ALWAYS
specify the file extension. That removes a lot of headaches with the wrong
file being sourced.
Aditya
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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:56 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 [this message]
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
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=alpine.DEB.2.02.1308010953420.3506@nqv-guvaxcnq \
--to=adityam@umich.edu \
--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).