Mail Archives: cygwin/2000/10/24/11:14:33
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
- Raw text -