OK fixed it.
Deleted and re-added the file with the character in the filename. I can now save the zip file.

stax

What version of BetterZip do you use? This problem existed in earlier versions, but has been fixed.

Hi Robert
v1.6.2
Nope. Not fixed.
I thought the problem had gone away but two days on and the exact same problem has returned. For two days no problems. I guessed that this was a symptom of using a Zip file that was originally created by Apple's Archive utility - but this seems not to be the case... For the last 2 days I have used BetterZip exclusively.
The first sign of a problem is that the filename in the Zip with the 'e' accute is incorrectly displayed in BetterZip with strange characters where the accented character should be.
The second sign is that "Save" fails saying that the file with the accented character is password protected.
For information, Apple's Archive utility has no issue with the filename.
If I swap the file in BetterZip with exactly the same file only without accented characters in the filename, it works fine.
stax

Could you please create a test archive that leads to the problem and send it to me? I have played around with all kinds of accented and other international characters, but it works flawlessly here. What version of Mac OS X do you have? What language have you set as your primary?

Robert
OS X v10.5.2, English. I'll put something together.
Thanks.
stax

Exactly my main setup. I am really curious now.

Files sent.
stax

Hi!
BetterZip can't extract archive full of files with long filenames in russian (archive was made at windows comp).
All i get is dir with files named with strange chars...
(BetterZip Version 1.6.2 (1.6.2), trial mode)

Zip archives don't store information about the encoding of the file names inside, so BetterZip has to guess what the encoding might be. It always works with UTF-8 files (like those created on a Mac), but can't always figure out the encoding of Windows created archives. The result when you extract the archive with Mac OS X' built in Archive Utility is probably the same, right? I will add the ability to choose the right encoding manually in a future version.

Yeah, build-in archiver do the same - wrong filenames...
Maybe you can "guess" encoding somehow?
At least manual selection is good...
Thanks!

I, too, purchased BetterZip recently, and I have the same version of (1.6.2) as stax. I also have the same problem that stax reported here: any special characters (by that I mean any ASCII characters higher than decimal 127 in the ASCII character set) make BetterZip up-chuck on the file containing the offending character(s). I get the same message too -- BetterZip thinks I've assigned a password to the offending file, when in fact I have not. At least BetterZip doesn't corrupt the entire archive because of the offending file! The workaround is the one stax suggested -- remove the high-order ASCII character(s) from the file and re-ZIP it.

As stax also noted, Apple's Archive utility doesn't stub its toe on these "special" files -- nor, I might add, does Stuffit Deluxe (I have version 10.0.2 of that program). One by one, I'm trying to migrate *all* my Stuffit archives to BetterZip because Stuffit will, on occasion, corrupt entire archives, at which point I can't get them back or restore them, which is unacceptable to me.

Oh, sorry, Stax and I corresponded over e-mail and I didn't post the outcome back here. So here it is: I was able reproduce the problem and it will be fixed in the next version which will be out in a few days.