This is the mail archive of the
mailing list for the Cygwin project.
Re: Cygwin, Rsync and 8-bit chars (SJIS)
Ok, What's a managed mount when its at home? I've found lots of messages
talking about its bugs but nothing explaining what it is yet or what about
it that is useful.
Q-Games, Dylan Cuthbert.
"Igor Pechtchanski" <firstname.lastname@example.org> wrote in message
> This seems like a good excuse to try the managed mount mode. Search the
> August archives for it. Be aware, though, that this is a *highly*
> experimental feature, and it currently requires a newly-created directory.
> On Tue, 16 Sep 2003, Dylan Cuthbert wrote:
> > After reading up some more about Cygwin's libs, I think the
> > double-backslashes that are appearing are causing cygwin to think the
> > is a DOS path, not a posix-style one.
> > The reason the backslashes are there is because SJIS uses them as the
> > character in the encoding of some of its double-byte characters, I can't
> > change that unfortunately.
> > If this is the case then I could really do with some secret CYGWIN flag
> > (couldn't find it in the user guide) that can disable the DOS path
> > temporarily, by using [env CYGWIN=nodospaths tty ntsec rsync "blah"]
> > example?
> > Anybody got a clue as to what to do here? It seems as if Cygwin might
> > broken when it comes to SJIS filenames because of this, maybe the "is
> > DOS path" check could be more stringent? If the path has forward
> > even one, maybe it can be left untouched?
> > Regards
> > ---------------------------------
> > Q-Games, Dylan Cuthbert.
> > http://www.q-games.com
> > "Dylan Cuthbert" <email@example.com> wrote in message
> > firstname.lastname@example.org">news:email@example.com...
> > > Hi there,
> > >
> > > I'm having a problem with SJIS encoded (windows) filenames and
> > > them anywhere. It doesn't happen for all files and as far as I can
> > out
> > > the problem occurs when the filename is fully japanese (as opposed to
> > > english text followed by some japanese text).
> > >
> > > One of the bad filenames in question is:
> > >
> > > 'ls -b's output:
> > >
> > > \225\\\216\206.doc
> > >
> > > It has a triple-backslash sequence in it, maybe this is the problem?
> > > not sure how and why it has a triple backslash sequence as the
> > > displayed is simply 3 japanese characters. Anyway, rsync chokes, it
> > it
> > > cannot find the file and displays the correct (and existing) filename
> > > japanese (when using a regular bash window)
> > >
> > > [some time passes]
> > > I just checked all the errors (about 5% of all japanese files) and the
> > > errors occur in the filenames with double-slash or triple-slash
> > in
> > > them. Anyone have any ideas 1) how the double/triple-slashes get
> > > the first place, and 2) how to fix the problem? 3) why this problem
> > > at all, shouldn't rsync be simply getting the file strings and passing
> > them
> > > onto the file system library or does the file system library do some
> > arsing
> > > about with backslashes because of that c:\ conversion to /cygdrive/c
> > > that cygwin does? Any way to turn that off if that's the case?
> > >
> > > Regards
> > >
> > > ---------------------------------
> > > Q-Games, Dylan Cuthbert.
> > > http://www.q-games.com
> |\ _,,,---,,_ firstname.lastname@example.org
> ZZZzz /,`.-'`' -. ;-;;,_ email@example.com
> |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D.
> '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
> "I have since come to realize that being between your mentor and his route
> to the bathroom is a major career booster." -- Patrick Naughton
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html