I have read the documents in question, and understand what they say. Really. I have been handling these character set issues for a while, including the Unicode/ISO conversions back and forth in Perl (and iso-8859-x, and "modified utf-7 for IMAP", etc..). I just thought I'd insist on this so that you wouldn't think that I don't understand the basic issues at hand.
Do you understand the difference between a Perl unicode string, and a UTF-8 encoded string? That's a bit more complicated than converting between encodings back and forth, and it's the key issue at hand.
What I did learn from you, was that I should apparently not blindly convert my filenames to utf8
Or anything else. A filename, once converted or encoded, is no longer the same filename.
failed the "-f" test and an open() test, and I was, and still am, trying to figure out why.
You really, really need to have the error message. If you don't want to output it to STDERR or STDOUT, you can open a log file and write it there. Without the error message, you can only guess what's wrong. Guessing absolutely sucks, because it takes too much time.
I now am close to believing that there are gremlins at play.
If you're on Linux, use strace(1) to find where the gremlins are.
Do I just pick up your last message and hit reply, or start a new question ?
You can continue with the old thread, but it's harder to notice the new message then. I hate to say this, but you're better off starting a new thread. Don't forget to refer to the old one.
In reply to Re^5: utf8 in directory and filenames
by Juerd
in thread utf8 in directory and filenames
by soliplaya
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |