From: Hans Hagen Outside <pragma@wxs.nl>
Subject: Re: { in input file names
Date: Mon, 21 Jun 2004 23:04:16 +0200 [thread overview]
Message-ID: <40D74D50.3080803@wxs.nl> (raw)
In-Reply-To: <20040621194516.GC2592@puritan.pcp.ath.cx>
Nikolai Weibull wrote:
>Hi.
>Another one of my sort of weird questions. I have a file with { in it's
>
>
weird indeed, are you searching for the limits of tex/context/your-os?
>file name and context doesn't seem to enjoy it much:
>
>
i only enjoy names that match [a-z0-9\-]
>% mkdir {test}
>% cd {test}
>% mkdir output
>% touch a.tex && ed a.tex
>0
>0a
>\starttext
>Hello
>\stoptext
>.
>wq
>27
>% texexec --runpath=output a.tex
>
>
You can put this somewhere (cont-loc.tex or so) since i'm not that sure
if it does not interfere, so i (and others) need to test this for a long
time
% supp-fil
\bgroup % todo: _ cleanup
\catcode`\/=\@@active
\catcode`\:=\@@active
\catcode`\~=\@@active
\gdef\sanitizefilename#1\to#2%
{\bgroup
\edef/{\string/}%
\edef:{\string:}%
\edef~{\string~}%
\expanded{\xdef\noexpand\sanitizedfilename{#1}}%
\egroup
\let#2\sanitizedfilename%
\convertcommand\sanitizedfilename\to#2}
\egroup
% core-job
\def\usepath[#1]%
{\def\docommando##1%
{\doifelse{##1}\v!reset
{\let\allinputpaths\empty}
{\sanitizefilename#1\to\ascii
%\convertcommand\ascii\to\ascii
\addtocommalist\ascii\allinputpaths}}%
\processcommalist[#1]\docommando}
\def\usesubpath[#1]% new, see webschrift for usage
{\ifx\allinputpaths\empty
\sanitizefilename#1\to\allinputpaths
\else
\def\docommando##1%
{\def\dodocommando####1%
{\sanitizefilename####1\to\ascii
\addtocommalist{##1/\ascii}\allinputpaths}%
\processcommalist[#1]\dodocommando}%
\processcommacommand[\allinputpaths]\docommando
\fi}
next prev parent reply other threads:[~2004-06-21 21:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-21 19:45 Nikolai Weibull
2004-06-21 21:04 ` Hans Hagen Outside [this message]
2004-06-22 10:51 ` Nikolai Weibull
2004-06-22 12:38 ` Hans Hagen
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=40D74D50.3080803@wxs.nl \
--to=pragma@wxs.nl \
--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).