UTF8 and cvs issues in 1.7.2

[Corinna Vinschen]

On Mar 26 22:44, lemkemch@t-online.de wrote:
> On Fri, 26 Mar 2010 10:30:28 +0100 Corinna Vinschen 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?

In what case?

If the filename in the file is written incorrectly, it will fail the
same as on Cygwin.

Other than that, the filename in Linux (or any other POSIX OS) is just a
NUL-terminated byte stream.  There is never any charset conversion
necessary on the file API level, the filename has just to match byte by
byte.
The actual charset is only relevant on the UI level and only on that
level you will see, for instance, a question mark in the filename where
an ISO8859-1 character doesn't make sense when using UTF-8.


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