From owner-freebsd-questions@FreeBSD.ORG Mon Feb 16 20:32:00 2009 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 61398106564A for ; Mon, 16 Feb 2009 20:32:00 +0000 (UTC) (envelope-from mihai.dontu@gmail.com) Received: from mail.bitdefender.com (mail.bitdefender.com [91.199.104.2]) by mx1.freebsd.org (Postfix) with ESMTP id 9CC3E8FC16 for ; Mon, 16 Feb 2009 20:31:59 +0000 (UTC) (envelope-from mihai.dontu@gmail.com) Received: (qmail 31549 invoked from network); 16 Feb 2009 22:05:08 +0200 DomainKey-Status: no signature Received: from unknown (HELO ?10.10.14.115?) (10.10.14.115) by mail.bitdefender.com with AES256-SHA encrypted SMTP; 16 Feb 2009 22:05:08 +0200 From: Mihai =?utf-8?q?Don=C8=9Bu?= Organization: Home To: freebsd-questions@freebsd.org Date: Mon, 16 Feb 2009 22:05:17 +0200 User-Agent: KMail/1.9.9 References: <499498A4.4000103@webvolution.net> <20090212235015.U97916@wojtek.tensor.gdynia.pl> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Content-Disposition: inline Message-Id: <200902162205.17644.mihai.dontu@gmail.com> X-BitDefender-Scanner: Clean, Agent: BitDefender qmail 3.0.2 on elfie.dsd.hq, sigver: 7.23708 X-BitDefender-Spam: No (0) X-BitDefender-SpamStamp: v1, build 2.8.1.62144, bayes score: 500(0), pbayes score: 241(0), neunet score: 0(0), flags: [VALID_REPLY; SIGN_NO_LINK_NMD_08; LEGIT_SUMM_200_WORDS; EXEC_H_HAS_ONE_RECV], total: 0(775) X-BitDefender-CF-Stamp: none Cc: Wojciech Puchar , Daniel Leal Subject: Re: accents in file names 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, 16 Feb 2009 20:32:00 -0000 On Friday 13 February 2009, Chuck Swiger wrote: > On Feb 12, 2009, at 2:50 PM, Wojciech Puchar wrote: > >>> accented letter to my freebsd box, the accented letter simply > >>> disappear. > >> > >> UFS supports 8-bit characters except for "/" and "\0", but you also > >> need to run a terminal with UTF8 support and use a correct font to > >> view such things. > > > > why? i use ISO-8859-2 > > You've answered "why" when you state that you set up a locale which > supports ISO Latin-X charset. If you are running in the default C/ > POSIX locale, using the US-ASCII character set and a font that only > knows about 7-bit ASCII glyphs, then you won't get accented characters. > > > UFS doesn't deal with encoding at all, just store what you give > > That's right, which means you need to use filenames encoded in UTF8 > rather than in arbitrary Unicode. UTF-8 is what we prefer these days, but the filesystem can handle anything that is ASCII compatible (like you said: Shift_JIS, EUC-JP etc.). Now, I assume Daniel was copying "filé.txt" from a non-UFS (Windows box, FAT32, NTFS etc) filesystem to UFS, because this is the only case I can think of and in which such a problem might appear. > People in Asia tend to want UTF-16 > or UTF-32 encoding (although historical encodings like Big5, Shift- > JIS, and now GB18030 for China are still rather popular, and those are > multibyte encodings), and things like gcc's implementation of > widechars or Python are standardizing on UTF-32. -- Mihai Donțu