ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Santy, Michael" <Michael.Santy@dynetics.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>,
	"mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: escaping filenames with externalfigure
Date: Thu, 3 Jan 2008 07:35:10 -0600	[thread overview]
Message-ID: <6703815B292B664DBAEC55EE3192386A20BD90@poseidon.in.dynetics.com> (raw)
In-Reply-To: <47758483.2080904@wxs.nl>


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

Hans,

> no time for a detailed answer now, but in xml mode you can make { } 
> letters which solves the problem

Could you please elaborate a bit?  I'm not familiar with ConTeXt's XML mode (other than for processing MathML).  One thing that I suspect is that XML mode would have an issue with '<' and '>' in the filenames.

Another thought: The image filenames are encoded in my original xml documents according to RFC 1738 (http://www.blooberry.com/indexdot/html/topics/urlencoding.htm).  In my XML -> ConTeXt XSL stylesheets I'm decoding those filenames.  Would it be useful for others if the externalfigure could understand url encoded filenames similar to something like this:

%
% includes the file "flower{1.jpg"
%
\externalfigure[flower%7B1.jpg][encoding=rfc1738]

This would give ConTeXt a general-purpose filename escaping mechanism.

Cheers,
Mike

[-- Attachment #1.2: Type: text/html, Size: 1461 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:[~2008-01-03 13:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-27 14:09 Santy, Michael
2007-12-27 14:55 ` Hans Hagen
2007-12-27 15:02   ` Santy, Michael
2007-12-27 14:56 ` Hans Hagen
2007-12-27 15:05   ` Santy, Michael
2007-12-27 15:09   ` Wolfgang Schuster
2007-12-27 15:00 ` Wolfgang Schuster
2007-12-27 15:16   ` Santy, Michael
2007-12-27 15:27     ` Wolfgang Schuster
2007-12-27 15:58       ` Santy, Michael
2007-12-28 23:19         ` Hans Hagen
2008-01-03 13:35           ` Santy, Michael [this message]

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=6703815B292B664DBAEC55EE3192386A20BD90@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).