From mboxrd@z Thu Jan 1 00:00:00 1970 From: OGAWA Hirofumi Subject: Re: msdos filesystem ignores codepage argument? Date: Mon, 29 Dec 2014 08:06:10 +0900 Message-ID: <87vbkvs7bx.fsf@devron.myhome.or.jp> References: <549DE622.6050504@ubuntu.com> <87zja7so8x.fsf@devron.myhome.or.jp> <54A0807A.8000803@ubuntu.com> Mime-Version: 1.0 Content-Type: text/plain Cc: linux-fsdevel To: Phillip Susi Return-path: Received: from mail.parknet.co.jp ([210.171.160.6]:47334 "EHLO mail.parknet.co.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751476AbaL1XGP (ORCPT ); Sun, 28 Dec 2014 18:06:15 -0500 In-Reply-To: <54A0807A.8000803@ubuntu.com> (Phillip Susi's message of "Sun, 28 Dec 2014 17:13:14 -0500") Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Phillip Susi writes: > On 12/28/2014 12:00 PM, OGAWA Hirofumi wrote: >> codepage option is to specify what codepage is used as on-disk >> encode in FAT, not how convert to encoding to show. >> >> And msdos driver doesn't have the feature to encoding conversion >> between on-disk and user (codepage is used only to upper/lower case >> conversion basically). IOW, msdos assumes the user and on-disk >> encodings are same. > > Umm... so you are saying the argument does nothing on purpose? What > is the use of specifying the on disk code page if not so that it can > be translated to utf8? As I said, the codepage option is used for upper/lower conversion. >>> Also in the process I noticed some odd behavior of ls. If I set >>> my terminal to use cp850 and ls | cat, I see the umlouted A, but >>> without piping the output through cat, it comes out as a question >>> mark. Why is that? >> >> It is what "ls" does. Probably, following option will show raw >> string >> >> $ ls -N --show-control-chars > > What exactly is it doing that causes its output to differ when sent to > a tty vs a pipe? See a man page of "ls". "ls" changes that depending on the output target (tty or not). This is completely about "ls", not fat driver. -- OGAWA Hirofumi