Mail Archives: cygwin/2000/10/23/02:54:15
> -----Original Message-----
> From: cygwin-owner AT sources DOT redhat DOT com
> [mailto:cygwin-owner AT sources DOT redhat DOT com]On Behalf Of Chris Abbey
> Sent: Saturday, October 21, 2000 7:57 AM
> To: cygwin AT sources DOT redhat DOT com
> Subject: non latin file names?
>
>
> I'm running current network install on NT4, sp6. The system is
> configured for default (read: us english) locale. There are two
> filesystems involved: /orig is NTFS (actually it's a symlink
> to /cygdrive/f/yada/yada/yada...) /dest is a samba mounted
> e2 partition shared out from RH6.2 (with Samba 2.0.6-9) (again
> it's really /cygdrive/m/more/boring/dirs....).
>
> Within /orig there is a file named "Fadó.txt" (that's F A D 0x0243 dot
> text) windows has NO PROBLEMS with this filename. Cygwin sometimes
> can't cope with it, if I do an ls in the directory it becomes the
> substitution char on screen, but if I pipe the output it is correctly
> rendered. Similarly windows cmd.exe with the default codepage of 437
> renders the right glyph.
>
> I did a `cp -R /orig /dest`. After doing so, the results are the
> same for the file in /dest... cygwin shows it as ? on the console,
> ó in pipes, and windows always shows ó... so the full 8 bits of the
> character name are being retained.
>
It is not a "cygwin" - it is `ls' command, that replaces non-printable
characters with `?'.
> So far, while I find the substitution glyph annoying there really
> isn't anything functionally wrong. Infact, cygwin is ahead of linux
> in that on the console the filename shows up as the completely wrong
> glyph. But this is because I don't have the foggiest clue how to get
> locale configured under Linux. But I don't care that it can't be
> displayed there, as long as all eight bits are preserved (they are).
>
> Here's the problem.
>
> If I create a md5 checksum for this file on Linux and then try to
> verify the file on cygwin it fails because it can't open the file?
>
Which file, sorry? File, that you have copied from NT to Lnux (onto
SAMBA-exported partition)?
> The files are generated by:
>
> find ! -type d -exec md5sum -b {} > /tmp/local.checksums \;
>
> then the local.checksum files are traded between the two
> machines and are verified by:
>
> md5sum -c /tmp/remote.checksums | grep -v OK
>
> which results in either "No such file or directory" or
> "FAILED open or read" (seemingly random which it is, sometimes
> BOTH)
>
Again, please, be more specific about which files exactly.
> Anyone got a clue? is this supposed to work? Am I in uncharted
> territory?
>
O.K., you have (probably) two distinct problems here:
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.
Problem 2 - locale support in Cygwin
Cygwin does not have any locale support at all. There is stub implementation
for setlocale that basically sets locale to C. Two possible implementations
are:
- use own locale database (basically, reimplement standard glibc locale
support)
- rely on Windows locale support if possible.
I prefer the second.
Of course, either needs somebody to implement :-)
-andrej
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
- Raw text -