From owner-freebsd-questions@FreeBSD.ORG Mon May 23 15:24:50 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 08D28106564A for ; Mon, 23 May 2011 15:24:50 +0000 (UTC) (envelope-from f.bonnet@esiee.fr) Received: from hp9.esiee.fr (hp9.esiee.fr [147.215.1.4]) by mx1.freebsd.org (Postfix) with ESMTP id BB2C28FC08 for ; Mon, 23 May 2011 15:24:49 +0000 (UTC) Received: from mail.esiee.fr (mail.esiee.fr [147.215.1.3]) by hp9.esiee.fr (Postfix) with ESMTP id 406C914E94DB; Mon, 23 May 2011 17:24:25 +0200 (CEST) X-DKIM: OpenDKIM Filter v2.3.2 hp9.esiee.fr 406C914E94DB DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=esiee.fr; s=MAILOUT; t=1306164265; bh=401eCi/pmCU9aKr+20oMoQlJKos/5QDa+DWo8gm0Dnk=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=ot1Y6XHioZqR/+AD22GCdsAIY6lTDCRe8gvJQWsGkR7Ns6ZUilvz1vMPk4zYiH0eg hHvu38RRDtRvKJITpSyxbWBvb5HqgYlV4DIJVxDx9i1bOMpx+cZHhwp6WKoYfHMSgT g0qwzBeZgVEZ8gjPw5C/ynRJe1ZXeUrYOeaWyYIU= Received: from mail (localhost [127.0.0.1]) by VAMS.dummy (Postfix) with SMTP id 225F9105441E; Mon, 23 May 2011 17:24:48 +0200 (CEST) Received: from [147.215.1.21] (lisa.esiee.fr [147.215.1.21]) by mail.esiee.fr (Postfix) with ESMTP id 1885B105441D; Mon, 23 May 2011 17:24:48 +0200 (CEST) Message-ID: <4DDA7C40.2090609@esiee.fr> Date: Mon, 23 May 2011 17:24:48 +0200 From: Frank Bonnet User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.17) Gecko/20110424 Thunderbird/3.1.10 MIME-Version: 1.0 To: Robert Bonomi References: <201105231308.p4ND8pTY029948@mail.r-bonomi.com> In-Reply-To: <201105231308.p4ND8pTY029948@mail.r-bonomi.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: Filename containing French characters ? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 May 2011 15:24:50 -0000 On 05/23/2011 03:08 PM, Robert Bonomi wrote: >> Date: Mon, 23 May 2011 06:54:44 +0200 >> From: Frank Bonnet >> To: freebsd-questions@freebsd.org >> Subject: Re: Filename containing French characters ? >> >> Le 22/05/2011 17:31, Mike Jeays a ecrit : >>> On Sun, 22 May 2011 17:00:48 +0200 Frank Bonnet >>> wrote: >>> >>>> Hello >>>> >>>> I'm going mad trying to Open a file which the filename contains one or >>>> more French characters ( file not found ) Is there some magical >>>> receipe to do so ? Or do I have to forget trying ??? >>>> >>>> Thanks >>> If the first few characters is not accented, type 'mv "', then the >>> first few characters, in a command line, and press 'tab' so the >>> auto-completion works. Don't forget the closing quote. Then rename it >>> to something else. >> Access right are OK ( 644 ) the completion does not work, the operating >> system says file not found when I try to open it with any program. >> >> when I type the "ls -l" command the file is displayed with a "?" in place >> of the French (accentuated ) character >> >> I tried UTF8 or iso8859-1 as MM-CHARSET and fr_FR.ISO8859-1 as LANG >> global variables but it still don-t work > The *easy* work-arouond -- it does -not- solve the real problem, but does > let you work with the file -- is to rename the file. Not easy the file is created by a software that extract it from a SQL database > *Assuming* you are seeing the rest of the filename, _after_ the '?' character, > then issue an 'mv' command, using the source file name _exactly_ as shown > (i.e., _with_ the '?' in place of the unprintable character), and using a > destination file name that is _without_ any accented characters in it. > > If that mv fails, try repeating it, but using an '*' instead of the '?'. > > Oh, there is one more situation that can cause the kind of problem you are > seeing. Does the 'ls -l' show it as an _actual_ file, or a 'symlink' (to > a file that does not exist)? A 'dangling symlink' can give all sorts of > "strange" errors. > no it is not a symlink it's a "real" file