in reply to Re^5: Character encoding in console in Windows
in thread Character encoding in console in Windows

Well, the whole drag-and-drop mystery has been cleared up, but there is no solution for the original issue. Can anyone help?
  • Comment on Re: Character encoding in console in Windows

Replies are listed 'Best First'.
Re^2: Character encoding in console in Windows
by BrowserUk (Patriarch) on Sep 11, 2010 at 22:55 UTC

    As I cannot test this, and have no prior knowledge of it, I'm probably the wrong one to ask.

    However, my guess would be that you need to set STDIN to expect utf2le, in order to be able to read the unicode into perl.

    Once you have the unicode, you will need to use Win32::Unicode::File->open() in order to be able to open files with unicode names.

    But that is all speculation on my behalf. When ikegami drops by he'll be able to give you chapter and verse on the Unicode stuff. Just be patient.


    Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
    "Science is about questioning the status quo. Questioning authority".
    In the absence of evidence, opinion is indistinguishable from prejudice.
      I'll read this thread in detail tonight. I'm out of time for now.
        Thank you. For your information: this is for a script that will be used on Windows, Linux and Mac. It seems to have no problem with non-ASCII filenames in Linux (Ubuntu, anyway), but it fails in Windows and Mac OS X.
        If it doesn't require too many changes, I'd like to make it work with non-ASCII characters on Windows, but it's not critically important. If you can give me a simple step by step on how to make it work, I'll be grateful. Otherwise, I can always warn users to rename their files.