Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Date: Tue, 24 Oct 2000 11:06:37 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT sources DOT redhat DOT com
Subject: Re: non latin file names?
Message-ID: <20001024110637.A26191@redhat.com>
Reply-To: cygwin AT sources DOT redhat DOT com
Mail-Followup-To: cygwin AT sources DOT redhat DOT com
References: <4 DOT 3 DOT 2 DOT 7 DOT 0 DOT 20001023204853 DOT 00cfe100 AT pop DOT bresnanlink DOT net> <000c01c03d82$ce879a10$21c9ca95 AT mow DOT siemens DOT ru>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.6i
In-Reply-To: <000c01c03d82$ce879a10$21c9ca95@mow.siemens.ru>; from Andrej.Borsenkow@mow.siemens.ru on Tue, Oct 24, 2000 at 10:22:38AM +0400

On Tue, Oct 24, 2000 at 10:22:38AM +0400, Andrej Borsenkow wrote:
>>>Problem 1 - SAMBA and 8-bit characters.
>>>
>>>You must tell SAMBA what OEM code page is used by your client.  This is
>>>probably either 850 or 437.  You better ask on SAMBA list about
>>this problem.
>>
>>most likely this is the problem, I've done some more hacking (trying to
>>answer your previous questions with a step by step demo you could run
>>yourself to do a bare minimum recreation) and I see that whatever error
>>is happening on the xfr from windows to linux via samba it's
>>orthogonal...  gigo...  such that even though the filename becomes
>>garbage on linux, it's at least consistently able to spit it back to me
>>correctly on NT.  I'll follow up with a samba guru I know at work.  The
>>root problem in this case was that, while the two files appeared to
>>have the same file name, with the same glyphs, at a binary level they
>>didn't match...  cygwin on nt wanted to use 0xF3, but the file that
>>came over from linux had 0xA2.
>>
>
>Cygwin is obviously using ANSI code page, while file comes to Linux in
>OEM code page (additionally, SAMBA may, if configured, convert OEM code
>page to whatever local character set is used on server).  Unless all
>parties agree to use single charset - and that should be some version
>of Unicode for general case - problem remains.
>
>Our good fellas in ASCII world are _very_ lucky to not have this
>problem.

Well, we wouldn't have the problem if someone contributed code to
correct it.

It's a free software project, right?

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com