Thanks for that, Mark. I was really after that 'neat' way of doing it but now that you did all the research for me, I'd say that's also a neat way - for me! :)

Staffan



On Sat, Jan 26, 2013 at 5:42 PM, Mark Miesfeld <miesfeld@gmail.com> wrote:
Here is a list from MSDN:

  • Use any character in the current code page for a name, including Unicode characters, except characters in the range of zero (0) through 31, or any character that the file system does not allow. A name can contain characters in the extended character set (128–255). However, it cannot contain the following reserved characters:

    < > : " / \ | ? *

Which brings up a point I meant to add when I said it depends on the operating system - it also depends on which file system in use.  I believe that FAT has some reserved characters that NTFS does not.

The < > : " /\ | ? *  characters are the ones I usually think of as the illegal characters.  But, 0 through 31 should be added to that.  Using ooRexx, you are not going to get access to Unicode file names.

--
Mark Miesfeld


------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnnow-d2d
_______________________________________________
Oorexx-users mailing list
Oorexx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-users