# Re: [NTG-context] Re: { in input file names

Nikolai Weibull wrote:

* Hans Hagen Outside <[EMAIL PROTECTED]> [Jun 22, 2004 10:40]:

Another one of my sort of weird questions. I have a file with { in

weird indeed, are you searching for the limits of tex/context/your-os?

Nah, I'm just getting used to Tom Lord's naming scheme
http://wiki.gnuarch.org/moin.cgi/FunkyFileNames
since I use GNU Arch for revision control.

I have my project files in ~/src/{projects}/

file name and context doesn't seem to enjoy it much:

i only enjoy names that match [a-z0-9\-]

[a-z0-9{=,+-] on my side

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

[cut]

OK, that worked fine for me. I'll report any problems.

so, we probably can only do:

\def\usepath[#1]% test for a real long time, permits ../{name} i.e. braces
{\def\docommando##1%
{\doifelse{##1}\v!reset
{\let\allinputpaths\empty}
{\sanitizefilename#1\to\ascii
\convertcommand\ascii\to\ascii
\processcommalist[#1]\docommando}

\def\usesubpath[#1]% test for a real long time, permits ../{name} i.e. braces
{\ifx\allinputpaths\empty
\sanitizefilename#1\to\allinputpaths
\else
\def\docommando##1%
{\def\dodocommando####1%
{\sanitizefilename####1\to\ascii
\convertcommand\ascii\to\ascii
\processcommalist[#1]\dodocommando}%
\processcommacommand[\allinputpaths]\docommando
\fi}

-----------------------------------------------------------------
-----------------------------------------------------------------
_______________________________________________