in reply to Writing UTF8 Filename
Why? Let me suggest that unless you have a really, seriously, inescapably unavoidable and compulsory reason for doing this, you would be much better off not doing it. Just don't.
The current state of support for non-ASCII characters in file names is not what I would call "stable" (or "sane" or "worth the hassle"). It is likely to vary in significant and perplexing ways across various (versions of) operating systems and file/text transfer protocols. Even on a single system where non-ASCII file names seem to "work", you are likely to discover a crippling amount of "variability" among various applications currently running on that system in terms of how (or whether) they deal with non-ASCII characters in file names.
If you are just trying to spruce up the appearance of your music collection, use a database or XML structure that relates sensible (ASCII-only) file names to whatever sort of strings you want to see as the list of files.
If you actually do believe there is an unavoidable, compulsory need for this, try to think of a work-around that involves using ASCII-only strings. If you can't... well, perhaps other replies here will help, but the solution may be OS dependent, and you might regret it later. Good luck.
(BTW, you might find it easier to use the perl built-in function "rename" -- it saves you from worrying about what happens to non-ASCII data being passed as command-line args to a sub-shell.)
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^2: Writing UTF8 Filename
by Juerd (Abbot) on Nov 17, 2007 at 09:47 UTC | |
by amiribarksdale (Acolyte) on Nov 17, 2007 at 22:39 UTC | |
by Juerd (Abbot) on Nov 18, 2007 at 00:00 UTC | |
|
Re^2: Writing UTF8 Filename
by eserte (Deacon) on Nov 17, 2007 at 16:34 UTC | |
by graff (Chancellor) on Nov 17, 2007 at 17:00 UTC | |
by tye (Sage) on Nov 17, 2007 at 18:27 UTC | |
by Juerd (Abbot) on Nov 18, 2007 at 00:12 UTC | |
by tye (Sage) on Nov 18, 2007 at 00:52 UTC | |
|