Re: How can I get a Unicode @ARGV?

[Anonymous Monk]

I have a script that packed as Executable

Which packer?

and the path passing in becomes ?????.

This part cmd.exe does on its own, you have to chcp 65001 to get it to not molest unicode, or use powershell

See also Win32::Unicode, Win32::Unicode::Native decodes @ARGV

[exilepanda]

Which packer?

I have Cava and PerlApp, but yet I only tried with PerlApp

becomes ?????.

Yes. it turns into question marks.

...chcp 65001...

I think it's too late to chcp too. What I think is while the moment the file path is dropped to the exe file, it's already turned into "?????" before perl accept the argv.. But I have no way to know about...

I use Win32::Unicode::* for other occasions and works fine, only require I have put the right String source first. And I am dead at the very first moment...

[Anonymous Monk]

Yes. it turns into question marks.... I think it's too late to chcp too.

:) That wasn't a question, I was quoting the line I was responding to :)

But I totally missed the drag/drop thing

So you're seeing "??????" in the console? What is Data::Dumper output?

I imagine using Win32::Unicode::Native ought to work, but if it doesn't, these two might

Win32::CommandLine - Retrieve and reparse the Win32 command line

update: it probably won't, no mention of unicode/wchar or GetCommandLineW

Win32::Process::CommandLine - Perl extension for getting win32 process command line parameters

But if they don't, then I think recompiling perl ( runperl.c ) with wmain ought to work, but then that might be tough to manage with with perlapp/cava, though it wouldn't surprise me if this step isn't necessary

But, you know :) you could always compile a foo.exe which uses wmain and calls your perlapp packed perl.exe with -CSD or whatever :)

[Anonymous Monk]

Ok, I did some testing with PAR Packager, version 1.013 (PAR version 1.005)

 pp -M strict -M warnings -M Data::Dump -M Win32::Unicode::Native -M Win32::Process::CommandLine -M Win32::CommandLine   dragdropmeargv.pl

#!/usr/bin/perl --
use strict; use warnings;
use Data::Dump;
dd \@ARGV;
eval 'use Win32::Unicode::Native;';
dd \@ARGV;

{
    use Win32::Process::CommandLine;
    Win32::Process::CommandLine::GetPidCommandLine($$, my $str);
    dd $str;
}

use Win32::CommandLine();
dd [ Win32::CommandLine::argv() ];
dd [ Win32::CommandLine::command_line() ];
#~ scalar <>;
sleep 10;

But the results were disappointing, no unicode

[
  "utf-filedir\\kebab\\cevap.txt",
  "utf-filedir\\kebab\\ra\x9Enjic.txt",
  "utf-filedir\\kebab\\???????.txt",
  "utf-filedir\\kebab\\??????.txt",
  "utf-filedir\\kebab\\?????.txt",
  "utf-filedir\\kebab\\????.txt",
  "utf-filedir\\kebab\\ra\x9Enjic",
  "utf-filedir\\kebab\\cevap.txt",
]
[
  "utf-filedir\\kebab\\cevap.txt",
  "utf-filedir\\kebab\\ra\x9Enjic.txt",
  "utf-filedir\\kebab\\???????.txt",
  "utf-filedir\\kebab\\??????.txt",
  "utf-filedir\\kebab\\?????.txt",
  "utf-filedir\\kebab\\????.txt",
  "utf-filedir\\kebab\\ra\x9Enjic",
  "utf-filedir\\kebab\\cevap.txt",
]
"utf-filedir\\a.exe utf-filedir\\kebab\\cevap.txt utf-filedir\\kebab\\
+raznjic.txt utf-filedir\\kebab\\???????.txt utf-filedir\\kebab\\?????
+?.txt utf-filedir\\kebab\\?????.txt utf-filedir\\kebab\\????.txt utf-
+filedir\\kebab\\raznjic utf-filedir\\kebab\\cevap.txt"
[
  "utf-filedir\\kebab\\cevap.txt",
  "utf-filedir\\kebab\\ra\x9Enjic.txt",
  "utf-filedir/kebab/RANJI~1.TXT",
  "utf-filedir/kebab/0CA1~1.TXT",
  "utf-filedir/kebab/35AA~1.TXT",
  "utf-filedir/kebab/531D~1.TXT",
  "utf-filedir/kebab/DD0B~1.TXT",
  "utf-filedir/kebab/EVAP~1.TXT",
  "utf-filedir/kebab/cevap.txt",
  "utf-filedir\\kebab\\????.txt",
  "utf-filedir\\kebab\\ra\x9Enjic",
  "utf-filedir\\kebab\\cevap.txt",
]
[
  "utf-filedir\\a.exe utf-filedir\\kebab\\cevap.txt utf-filedir\\kebab
+\\ra\x9Enjic.txt utf-filedir\\kebab\\???????.txt utf-filedir\\kebab\\
+??????.txt utf-filedir\\kebab\\?????.txt utf-filedir\\kebab\\????.txt
+ utf-filedir\\kebab\\ra\x9Enjic utf-filedir\\kebab\\cevap.txt",
]