On Fri, 26 Mar 2010 15:51:38 -0600 Erik Blake wrote:
On 03/26/2010 03:44 PM, lemke...@t-online.de wrote:
>> 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.
>> The only problem is this file is none of my business. It's CVS's
file.
> What does cvs on linux do in this case?
The same thing; it's just that you've probably never used CVS on Linux
with two different charset encodings between the two uses. Really, the
change in charset from cygwin 1.5 to 1.7 is a rare event, but it can
certainly cause some grief if you aren't expecting it.
Well, on Cygwin 1.7.2 the contents of CVS/Entries depend on my setting
of LANG. This I find strange but I understand why it happens. Does
that also happen on Linux? I guess not as the filename is still a stream
of bytes even in local aware Linux (I haven't used Linux for ages).
Michael
--
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
