> -----Original Message-----
> 
> Suggestion, before too many people start relying on it, replace the
> random/arbitrary substitution with some standard encoding like
> urlencoding.

So, translate model T file names like CUST*S.DO -> CUST%2AS.DO in the TPDD 
folder, and vice versa?  I wonder whether it's more likely to encounter model T 
files with legit % signs in their names than with legit ^ signs in their 
names...

What would be really great would be if there is some character the model T 
disallows in filenames but which unix and windows do allow, then translate the 
asterisk to that character.  :)







        jim

Reply via email to