filesystem encoding

2004-09-08 Thread Colin JN Breame
Hello, Could anyone direct me to some documentation about how cygwin decodes filenames (e.g. with ls) Thanks ps. cygwin is cool -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.h

Re: filesystem encoding

2004-09-08 Thread Igor Pechtchanski
On Wed, 8 Sep 2004, Colin JN Breame wrote: > Hello, > Could anyone direct me to some documentation about how cygwin decodes > filenames (e.g. with ls) Cygwin is not Unicode-aware (). Basically, it uses the Win32 API methods that make the underlying filesystem map

Re: filesystem encoding

2004-09-08 Thread Colin JN Breame
Igor Pechtchanski wrote: Any names that can't be so mapped are rejected as invalid, and are displayed with '?'s by "ls". Switching to the correct language allows accessing those names. HmmmI have a file that, through windows explorer contains a (long) hypen, but through cywin (ls), the cha

Re: filesystem encoding

2004-09-08 Thread Arturus Magi
Colin JN Breame wrote: Igor Pechtchanski wrote: Any names that can't be so mapped are rejected as invalid, and are displayed with '?'s by "ls". Switching to the correct language allows accessing those names. HmmmI have a file that, through windows explorer contains a (long) hypen, but throug

Re: filesystem encoding

2004-09-09 Thread Colin JN Breame
Arturus Magi wrote: Windows Explorer is Unicode 3.0 compliant on the NT line (I have several files that use a mixture of English, Japanese, and Chinese in the filename and various description fields), and the 9x line can be made partially Unicode-aware. I don't think the em hyphen is a valid c

OT: RE: filesystem encoding

2004-09-09 Thread Gary R. Van Sickle
> Hmm...interesting. Not entirely sure what the implications > of what you are saying are (as I don't really understand codepages). > > Does a codepage represent a character with 16 bits? or 8? > Could you recommend a book or a URL on the subject? Maybe I > should look at this when I have mo

RE: OT: RE: filesystem encoding

2004-09-10 Thread Gary R. Van Sickle
> Gary R. Van Sickle wrote: > > >Welcome to the 21st century, where computers can't even > unambiguously > >represent written text. > > > > > Isn't this something unicode was meant to solve? Yes, and if implemented properly, it mostly does. > or does > unicode still need a codepage to map t