From: Hans Hagen <pragma@wxs.nl>
To: Aditya Mahajan <adityam@umich.edu>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Use figures without file extension
Date: Sat, 26 May 2012 16:23:14 +0200 [thread overview]
Message-ID: <4FC0E752.9080002@wxs.nl> (raw)
In-Reply-To: <alpine.LNX.2.02.1205260959020.2561@ybpnyubfg.ybpnyqbznva>
On 26-5-2012 16:04, Aditya Mahajan wrote:
> On Sat, 26 May 2012, Hans Hagen wrote:
>
>> On 26-5-2012 04:08, Aditya Mahajan wrote:
>>> Currently, ConTeXt only recognizes the type of figure from the file
>>> extension. If a filename does not have an extension, \externalfigure
>>> fails.
>>>
>>> For example:
>>>
>>> $ cp `luatools hacker.jpg` something
>>
>> ah .. i see, no extension .. too tricky to support that as they we'd
>> need to run an identify on the image which is probably not what we want
>
> However adding `method=jpeg` works, even if the image is not a jpeg!
>
>> i've made a simple 'identify' but am yet unsure how to use that in the
>> current lookup strategy (as i want to avoid too much overhead ...
>> using images without suffix is bad anyway)
>
> I am using a script to typeset rss feed to a pdf for reading on kindle.
> Some blog engines (e.g. typepad) do not set an extension for the image.
> As such, I cannot control the input. For the moment, I am using a
> workaround:
>
> \let\normalexternalfigure\externalfigure
> \unexpanded\def\externalfigure
> {\dodoubleargument\rssfeed_externalfigure}
>
> \def\rssfeed_externalfigure[#1][#2]%
> {\normalexternalfigure[#1][\c!scale=2000, \c!method=JPEG, #2]}}
>
> Notice the method=JPEG.
>
> But, I think that I'll need to wrap a custom wrapper anyways, and some
> pages contain gif images which cause luatex to crash.
I'll add a virtual type 'auto':
\externalfigure[yourname.auto]
-----------------------------------------------------------------
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
___________________________________________________________________________________
next prev parent reply other threads:[~2012-05-26 14:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-26 2:08 Aditya Mahajan
2012-05-26 9:28 ` Hans Hagen
2012-05-26 13:39 ` Hans Hagen
2012-05-26 14:04 ` Aditya Mahajan
2012-05-26 14:23 ` Hans Hagen [this message]
2012-05-26 14:26 ` luigi scarso
2012-05-27 1:43 ` Rogers, Michael K
2012-05-27 2:49 ` Aditya Mahajan
2012-05-27 13:09 ` Rogers, Michael K
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=4FC0E752.9080002@wxs.nl \
--to=pragma@wxs.nl \
--cc=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).