> if a file name contains both single-byte ascii characters and > double-byte CJK characters, then the ContextMenu item's commands are > usually executed twice, as if two separate files were selected: the > first one with the correct filepath, however, the second one with > gabage characters, like ???(0x12), i.e., mostly unknown character > symbols (0x3F) then FormFeed (0x12) as the last character. > > Sean >
I don't really understand how the system represents multi-byte characters, but here is what is happening behind the scenes: 1. Pproctx.dll is run by explorer (which is a unicode app). 2. Explorer sends a DROPFILES structure to pproctx when you select powerpro menu item. 3. pproctx passes the dropfiles handle onto to powerpro. 4. Powerpro looks at the dropfiles structures, notices the fWide flag signalling wide file names, and uses widechartomultibyte to translate the file names. But PowerPro assumes the result is plain single byte characters for processing. I cannot explain what you are seeing by if there are true multi-byte characters, PowerPro won't be handling them.
