On 27 Apr 01, at 18:19, Frank Heckenbach wrote:
Hi Chief,
I can send you a sample zip file if you want.
Yes, please.
Attached. It was produced by a Danish customer, and inside the zip file is a bitmap that shows exactly what the other filenames should look like (so that the issue is not confused any further). Windows handles them correctly if I call OEMToChar (formerly OEMToAnsi) before displaying the filenames or before calling Rewrite.
I'm using:
UnZip 5.32 of 3 November 1997, by Info-ZIP. Maintained by Greg Roelofs. Send bug reports to the authors at Zip-Bugs@lists.wku.edu; see README for details.
and I cannot exactly say that it "fails most miserably".
YMHV (your mileage has varied ;-))
E.g., the small ligature ae is coded in the zip file as #$a1, and unzip converts it to #$e6 which is the correct latin1 code for this character.
Both the zip listing (unzip -l) and the directory listing after unpacking look just like the included graphics, both in xterm (XFree86 3.3.2(68)) and on the console after setting the default font (setfont default8x16 ; loadunimap) -- I usually use a different font which does not contain all of the Danish characters, but those that it does are still shown correctly.
So I conclude that the charset conversion code in unzip is indeed quite right.
Ok. Perhaps its a font problem with Mandrake 7.1. I am downloading the sources now, to see exactly what portable continuation they have used ...
Best regards, The Chief -------- Prof. Abimbola A. Olowofoyeku (The African Chief) Author of: Chief's Installer Pro for Win32 http://www.bigfoot.com/~African_Chief/chief32.htm Email: African_Chief@bigfoot.com