X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:references:message-id:date:from:reply-to :subject:to:in-reply-to:mime-version:content-type; q=dns; s= default; b=lDfD75HY5tG8lqCbfrFI9AQhc4RyxwOT3qOR5KYWOlp4nw2nyNxDj kuKwZcoiYlI/SJEf+CIrF8QSwmgud0XuxjmTjJswxjX6lg3DlgBfbhq+SGFelB9v PRfw68E+dg9e0bolXgRGTFgtIkpIRBsUiJ7ZQVBZyFNOPnfI9VIL04= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:references:message-id:date:from:reply-to :subject:to:in-reply-to:mime-version:content-type; s=default; bh=1X4L0nTZiAvzc0yoi0Ey6zVSe2M=; b=WZHRFeJhswRPplN1CmUKdTdP6jI5 IOsQ+bMt6nFb9BhdmvtPn9658kdnQw89msC5I3D2EeGKpTJSsox/hwlK1is1gwP0 BJU5zLhohg/2aSRNh3+p5gEMMqwbp6rIDyxQCY2AU0icmVRN3//dQqrlD4AUVx+e ZJKMhIOCEYZbdXc= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.7 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 X-HELO: nm44-vm3.bullet.mail.ne1.yahoo.com References: <1415153294 DOT 16094 DOT YahooMailNeo AT web122105 DOT mail DOT ne1 DOT yahoo DOT com> Message-ID: <1415159537.6554.YahooMailNeo@web122104.mail.ne1.yahoo.com> Date: Tue, 4 Nov 2014 19:52:17 -0800 From: Brent Reply-To: Brent Subject: Re: bug/deficiency in unzip: incompatible with other programs when entry path names have non-ascii chars To: "cygwin AT cygwin DOT com" In-Reply-To: <1415153294.16094.YahooMailNeo@web122105.mail.ne1.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii >On 2014-11-04 18:08, Brent wrote: > >I then reran my complete test suite. Everything now works except the part of >the test where cygwin unzip is to extract a zip file produced by Java. This >particular zip file has entries whose path names are non-ASCII chars. I have >manually verified that this zip file is perfectly extractable by 7zip and >WinZip, so Java does not seem to be the problem. I just realized that there is something I should have mentioned earlier. As of Java 7, its ZipOutputStream constructor now has the option that you can specify what character encoding is used to for stuff like path names. See dhams comment here: https://stackoverflow.com/questions/9974779/using-unicode-characters-for-file-names-inside-a-zip-archive I am explicitly using "UTF-8" for the character encoding (tho I did not have to be explicit: UTF-8 is the default). Could it be that cygwin unzip needs a different character encoding? That would surprise me, since I thought that the Unix world is coalescing around UTF-8 as the default character encoding. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple