In cp950: dir/b
It shows the files with unicode char correctly. However, dir/b > list.txt
the content inside list turns into "????"
In cp65001: dir/b It shows the files with monster char. However, dir/b > list.txt gives the correct list.
Most confused me is that when you can see the String right, it doesn't mean the Data is right, vice versa. And I actually have no idea why Unicode chars can show correctly when dir (or drop a file path in the cmd console) in cp950, but then can't manipulate(@ARGV) later.