X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Fri, 26 Mar 2010 10:30:28 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: UTF8 and cvs issues in 1.7.2 Message-ID: <20100326093028.GR7718@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Mar 26 00:24, lemkemch AT t-online DOT de wrote: > Erik Blake wrote: > >On 03/25/2010 05:05 PM, lemkemch wrote: > >> orion> cvs -qn up -l > >> U Ãppel.txt > >> cvs update: warning: `âppel.txt' is not (any longer) pertinent > >>> And frankly, I can't see how the terminal could influence the > >> behavior of the cvs executable. I am not talking about the > >> displayed characters here but that cvs wants to update a file. > >I wonder if the problem is that CVS/Entries was created under one > >charset, but you are now using a different charset. I suppose you could > >use iconv to convert the file to the correct encoding. Or it may be a > >sign that cvs has not yet been recompiled to be charset-aware. > > Yes, that sort of it is. Further experiments show this: > > CVS/Entries written by 1.5: > > /äppel.txt/1.1/Thu Mar 25 22:14:59 2010// > > With 1.7 it changes to (module character corruption through e mail): > > /äppel.txt/1.1/Thu Mar 25 22:14:59 2010// > > The positive is that the cvs update doesn't actually change > the file on disk. All that happens is changing CVS/Entries. > Still annoying. > > The fix I found is > > setenv LANG C.ISO-8859-1 > > But somehow that doesn't smell right. I explained that a lot in this list and in the User's Guide. The problem is that Windows uses UTF-16 under the hood. So there's no filename based operation without the requirement to convert from a multibyte to the widechar charset. What you can do is either to use ISO-8859-1 sort of like above, or you convert the file content to UTF-8 so you can use UTF-8 from now on. I'm really sorry that this is necessary, but it's really not my fault. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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