Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Injected-Via-Gmane: http://gmane.org/ To: cygwin AT cygwin DOT com From: "Dylan Cuthbert" Subject: Re: Cygwin, Rsync and 8-bit chars (SJIS) Date: Tue, 16 Sep 2003 23:05:52 +0900 Lines: 70 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: 7bit X-Complaints-To: usenet AT sea DOT gmane DOT org X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 After reading up some more about Cygwin's libs, I think the double-backslashes that are appearing are causing cygwin to think the path is a DOS path, not a posix-style one. The reason the backslashes are there is because SJIS uses them as the second 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 parsing temporarily, by using [env CYGWIN=nodospaths tty ntsec rsync "blah"] for example? Anybody got a clue as to what to do here? It seems as if Cygwin might be broken when it comes to SJIS filenames because of this, maybe the "is this a DOS path" check could be more stringent? If the path has forward slashes, even one, maybe it can be left untouched? Regards --------------------------------- Q-Games, Dylan Cuthbert. http://www.q-games.com "Dylan Cuthbert" wrote in message news:bk7499$7c9$1 AT sea DOT gmane DOT org... > Hi there, > > I'm having a problem with SJIS encoded (windows) filenames and rsync'ing > them anywhere. It doesn't happen for all files and as far as I can make out > the problem occurs when the filename is fully japanese (as opposed to some > 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? I'm > not sure how and why it has a triple backslash sequence as the filename > displayed is simply 3 japanese characters. Anyway, rsync chokes, it says it > cannot find the file and displays the correct (and existing) filename in > 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 sequences in > them. Anyone have any ideas 1) how the double/triple-slashes get there in > the first place, and 2) how to fix the problem? 3) why this problem occurs > 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 stuff > that cygwin does? Any way to turn that off if that's the case? > > Regards > > --------------------------------- > Q-Games, Dylan Cuthbert. > http://www.q-games.com > > > -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/