[Windows] doesn't open files whose name has extended chars out of current machine's codepage.

[GoogleCodeExporter]

Lazarus/FPC (the IDE used in PeaZip development) currently does not support 
Windows' widechar-based character encoding for internal file handling 
functions, so if the file name contains a character outside machine's codepage 
the string cannot be successfully passed to internal functions.

Original issue reported on code.google.com by giorgio.tani.software@gmail.com on 19 Nov 2010 at 1:05

[GoogleCodeExporter]

Issue 90 has been merged into this issue.

Original comment by giorgio.tani.software@gmail.com on 16 Jul 2011 at 10:26

[GoogleCodeExporter]

Issue 91 has been merged into this issue.

Original comment by giorgio.tani.software@gmail.com on 16 Jul 2011 at 10:26

[GoogleCodeExporter]

Issue 113 has been merged into this issue.

Original comment by giorgio.tani.software@gmail.com on 26 Oct 2011 at 7:30

[GoogleCodeExporter]

Issue 161 has been merged into this issue.

Original comment by giorgio.tani.software@gmail.com on 18 Jun 2012 at 9:20

[GoogleCodeExporter]

Issue 167 has been merged into this issue.

Original comment by giorgio.tani.software@gmail.com on 20 Jun 2012 at 7:16

[GoogleCodeExporter]

Issue 232 has been merged into this issue.

Original comment by giorgio.tani.software@gmail.com on 15 May 2013 at 7:19

[GoogleCodeExporter]

Issue 260 has been merged into this issue.

Original comment by giorgio.tani.software@gmail.com on 16 Aug 2013 at 5:50

[GoogleCodeExporter]

This is probably the same issue, but thought I should add this so more 
references are available for testing when UTF8 is fully supported:

When either the names of the files to be zipped and/or the name of the zip file 
itself contains the Japanese character "ポ", zipping failed with the following 
error:

'Operation stopped, potentially dangerous command detected (i.e. command 
concatenation not allowed within the program): "C:\Program 
Files\PeaZip\res\7z\7z.exe" a -tzip -mm=Deflate -mmt=on -mx5 -mfb=32 -mpass=1 
-sccUTF-8 -mem=AES256 " -wC:\Temp\" ......'

So far this issue only occurs with the character "ポ" and no other Japanese 
characters, and tested on versions 3.1 and 4.7.3 on Windows 7.  Language for 
non-Unicode programs is set to Japanese.

Original comment by steve.ko...@gmail.com on 24 Sep 2013 at 8:38

[GoogleCodeExporter]

Hi, Steve, are you sure only Japanese Chars?

I thought it caused by Compiler itself "not yet" fully ready for Unicode on 
Windows since fact Unicode on Windows was treated more complex than other 
Platform. And now, on Trunk FPC was started to add more "WideString-Aware" but 
I'm so sure still too far to get it ready FPC support Unicode smoothly on 
Windows Platform.

Original comment by oni...@gmail.com on 17 Oct 2013 at 7:30

[GoogleCodeExporter]

I don't believe it's only Japanese characters, judging by the other posts I'm 
sure Chinese, Korean and other double-byte characters have similar issues too.

Japanese is the only language we've been testing on and so far only the 
character "ポ" has problems.

Original comment by steve.ko...@gmail.com on 28 Oct 2013 at 1:29

[GoogleCodeExporter]

I recently used peazip and found also no Arabic support. any arabic charchter 
is shown as "?", and then not accessible, folder or file.

Original comment by mh.sa...@gmail.com on 27 Aug 2014 at 6:54

[GoogleCodeExporter]

Any chances to resolve the issue? Currently the only problem preventing me from 
using peazip. Also Lazarus have already supported unicode no?

Original comment by liuyun1...@gmail.com on 21 Oct 2014 at 9:28

[GoogleCodeExporter]

Did something change? I tested the latest version (5.5.3) of Peazip and still 
no support for Cyrillic (and every UTF-8) files in archives.

Original comment by master.s...@gmail.com on 24 Jan 2015 at 2:29