Won't open archives with Asian symbols in name

[baenmy]

Hi.
I have a bug here:

Code: Select all

INFO: Couldn't find any files inside the archive 'F:\New folder\[テスト]ファイ䖁名のテスト例.zip'! (Wrong file extension?)

The program won't scan archives (upd.: files of any type) with Asian symbols in a filename or file path.

Placed in a filename, Asian characters cause a 'Wrong file extension' error.
Placed somewhere in path, they cause the bug when the program will skip every file placed in the path's folder or subfolders. Like that:

Code: Select all

Scan: F:\[テスト]ファイ?名のテスト例
Scanned files: 0

As you can see, not all Asian characters cause the bug. Some are fine. In my example, 䖁 character is the one that wasn't encoded properly.

Upd.: For some reason, enabling 'use unicode utf-8 for worldwide language support' in Windows 10 helps to bypass the problem when the program refuses to scan folders with Asian characters in the path. But it still doesn't help with archives.
Unicode-Text Support option doesn't help.
Changing system locale to Asian doesn't help either.
Is there any way to fix this?

[Administrator]

I cant reproduce this problem here. AllDup doesnt have problems with these unicode characters:

Code: Select all

26.05.2020 21:19:21 - AllDup 4.4.28
26.05.2020 21:19:21 - Search Method: File content Byte by Byte (100%)
26.05.2020 21:19:21 - 1.Source folder: D:\[テスト]ファイ䖁名のテスト例
26.05.2020 21:19:21 - Option: Compare files from all source folders
26.05.2020 21:19:21 - Option: Ignore ID3 Tags of MP3 files
26.05.2020 21:19:21 - Option: Ignore metadata of FLAC files
26.05.2020 21:19:21 - Option: Ignore metadata of JPEG/CR2 files
26.05.2020 21:19:21 - Option: Archive Files: 7z, arj, cab, cb7, cbr, cbt, cbz, ePub, gz, iso, lha, lzh, nrg, rar, tar, zip
26.05.2020 21:19:21 - Determine file count of all source folders...
26.05.2020 21:19:21 - File count: 6
26.05.2020 21:19:21 - Scan: D:\[テスト]ファイ䖁名のテスト例
26.05.2020 21:19:22 - Found 6 duplicates with a total of 2,74 MB inside folder 'D:\[テスト]ファイ䖁名のテスト例'
26.05.2020 21:19:22 - Scanned files: 10
26.05.2020 21:19:22 - Groups: 1
26.05.2020 21:19:22 - Scanned archives: 4
26.05.2020 21:19:22 - Files from archives: 4
26.05.2020 21:19:22 - Extracted files: 4
26.05.2020 21:19:22 - File comparison count: 5
26.05.2020 21:19:22 - Duplicates: 6 (60%) (2,74 MB)
26.05.2020 21:19:22 - Elapsed time: 00:00:01

Im sure the problem at your computer has something to do with your windows unicode settings...

[baenmy]

I cant reproduce this problem here. AllDup doesnt have problems with these unicode characters:

Thanks, you helped me to find the reason for the wrong behavior.
Many users who use non-JP locale cannot view Japanese characters properly or launch JP software without bugs, so they are forced to set the Language for non-Unicode programs to Japanese. This option is ON permanently (because it needs a reboot when you want to return it back to English).
So, for some reason, AllDup works incorrectly when it set to Japanese.

Since you can't reproduce the bug, I thought your system locale is probably German or English, so I've tried to set the language for non-Unicode programs back to English and it started to work properly. Which is odd, because you turn non-Unicode programs locale to JP to solve JP text-related bugs, not the other way around.

Anyway, thank you!

[Administrator]

Maybe there is somewhere an option to exclude apps to be affected from this unicode setting?