ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Santy, Michael" <Michael.Santy@dynetics.com>
To: <ntg-context@ntg.nl>
Subject: Re: externalfigure and uppercase extensions
Date: Thu, 13 Sep 2007 14:06:19 -0500	[thread overview]
Message-ID: <6703815B292B664DBAEC55EE3192386A20BB65@poseidon.in.dynetics.com> (raw)
In-Reply-To: <mailman.1759.1189705411.2346.ntg-context@ntg.nl>


[-- Attachment #1.1: Type: text/plain, Size: 852 bytes --]



> This makes sense. So much so that perhaps it could be added to the
> core spec-tpd.tex file.

I think it would make more sense for conTeXt to first convert an image's extension to lower case before trying to figure out rule to apply.  Otherwise in order to be correct, you would need an entry for 
"Jpg", "jPg", "jpG", "JPg", "JpG", and "jPG" -- not even counting the permutations for "jpeg".

> You could consider using a case-insensitive file system to store
> your data on, and lowercasing all entity input to ConTeXt, but
> that is more clumsy than the extra \definefileinsertion-s.

I don't think a case-insensitive FS is going to be an option for us (*nix only).

Back to my original question, should "\externalfigure[MY_FIGURE.JPG][type=jpg] work?  Or am I misunderstanding the meaning of the type parameter?

Cheers,
Mike

[-- Attachment #1.2: Type: text/html, Size: 1409 bytes --]

[-- Attachment #2: Type: text/plain, Size: 487 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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

       reply	other threads:[~2007-09-13 19:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1759.1189705411.2346.ntg-context@ntg.nl>
2007-09-13 19:06 ` Santy, Michael [this message]
2007-09-13 20:21   ` Hans Hagen
2007-09-13 21:48   ` Taco Hoekwater
2007-09-24 16:38 Santy, Michael
  -- strict thread matches above, loose matches on Subject: below --
2007-09-13 16:56 Santy, Michael
2007-09-13 17:27 ` Taco Hoekwater

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=6703815B292B664DBAEC55EE3192386A20BB65@poseidon.in.dynetics.com \
    --to=michael.santy@dynetics.com \
    --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).