From: Alan BRASLAU <alan.braslau@cea.fr>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: bug in \externalfigure
Date: Thu, 1 Aug 2013 16:43:02 +0200 [thread overview]
Message-ID: <20130801164302.2eb1c8d7@iram-hb-003386.extra.cea.fr> (raw)
In-Reply-To: <CAG5iGsD8CkUoNDeZm6UiaKaLHFHDDfEy0=1RYQUXTsdG_zdCAQ@mail.gmail.com>
On Thu, 1 Aug 2013 16:01:27 +0200
luigi scarso <luigi.scarso@gmail.com> wrote:
> On Thu, Aug 1, 2013 at 3:56 PM, Aditya Mahajan <adityam@umich.edu>
> wrote:
>
> >
> > 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.
> >
> > +1.
-1
One might have png, jpeg, pdf, eps and other figure files. The choice
of which will be used depends eventually on where the file is to be
found... (and setupexternalfigures). This is a *feature*. It has
nothing to do with LaTeX.
Of course, one can always specify an extension explicitly if one so
wishes...
Furthermore, the file extension is simply a convenient label which
makes no difference whatsoever on any serious system. (but not so on
more primitive operating systems. ;)
Alan
___________________________________________________________________________________
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 14:43 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 [this message]
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=20130801164302.2eb1c8d7@iram-hb-003386.extra.cea.fr \
--to=alan.braslau@cea.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).