THE SSL CERTIFICATE FOR *.POWERARCHIVER.COM HAS EXPIRED.

[Jockel]

Hi,

using PA11.02.03 (11/2008), with this version (and previous ones), opening an archive including filenames with German “Umlauts”, these do not display correctly:
i. E. a filename “dänermark.mdb” displays as “dõnemark.mdb”
This does not happen, if the file was compressed using PA. These files were compressed using a backup software. But, extracting this very archive using filzip
or tugzip displays “in listing after opening” and extracts this filename correctly!
I attached an archive showing that behaviour, the file was created using tugzip, watchout for the filename after extracting using PA!
attachment_t_3432_0_ööääüüß-textdokument.zip

[spwolf]

archive doesnt work properly for me - can you rename it to test.zip and re-upload?

PA reads properly ANSI stored filenames in zip archives, according to specifications. There are quite few zip engines out there that have their own, different specifications, so it could be quite possible that they are using same engine.

[Jockel]

Hi spwolf,

find the renamed archive “test-2.zip” attached!
The previous flename of the archive was supposed to
be “öÖäÄüÜß-Textdokument.zip” same as the name
of the included document!

[Jockel]

strange thing, I renamed the file and the uploader claims, that I already uploaded it previously!
I try sending by e-mail!

[spwolf]

ok…

[spwolf]

ok, here is the problem - archive is created by software that uses non standardized zip unicode support.

Currently PA would not support it even if it had proper unicode support since current engine supports only ANSI zip archives.

Reason those 2 other softwares support it is probably they use the same zip engine so it works for them :-).

I tried opening it with every major compression software we have installed - WZ, WR, 7z, SecureZip and none of them support it either.

Good news is that we will add this support relativly soon :P

[spwolf]

Additionally, way to solve the issue would to force software to save as ANSI… from my knowledge, I can guess what zip engine they use and the way to do it would be to set non-unicode support to German, in Regional and Language settings> Advanced options.

This will force that zip engine to save as ANSI and it will then work in every archiver out there. I hope that helps.

thanks!

[Jockel]

Hi,

well, as I said, two competitors (I did not test any others!) do extract these fine and my customers here receive zip files from many different folks. They can not discuss if senders zip-engine is created by widely spread but non standard….;-)
Certainly a good idea to fix that soon!

[spwolf]

@Jockel:

Hi,

well, as I said, two competitors (I did not test any others!) do extract these fine and my customers here receive zip files from many different folks. They can not discuss if senders zip-engine is created by widely spread but non standard….;-)
Certainly a good idea to fix that soon!

well you can suggest to your customer to get zip utilities that support zip standards, and not invent their own :-).

No major utility will open these files properly, because they are badly created zip files. Luckily, we will be able to add this but again, it is not our fault if someone uses zip software not compatible with zip standards.

[Jockel]

Hi,
@spwolf:

well you can suggest to your customer to get zip utilities that support zip standards, and not invent their own :-)….

Well, my customers will use PA starting the next days (watch orders…), but their influence on their customers is quite limited ;-)

[spwolf]

@Jockel:

Hi,

Well, my customers will use PA starting the next days (watch orders…), but their influence on their customers is quite limited ;-)

its good that we are on the case already :P