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 10:00:04 +0900 Message-ID: <87tx0f5kyz.fsf@devron.myhome.or.jp> References: <549DE622.6050504@ubuntu.com> <87zja7so8x.fsf@devron.myhome.or.jp> <54A0807A.8000803@ubuntu.com> <87vbkvs7bx.fsf@devron.myhome.or.jp> <54A0A577.4080806@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]:47351 "EHLO mail.parknet.co.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751476AbaL2BAM (ORCPT ); Sun, 28 Dec 2014 20:00:12 -0500 In-Reply-To: <54A0A577.4080806@ubuntu.com> (Phillip Susi's message of "Sun, 28 Dec 2014 19:51:03 -0500") Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Phillip Susi writes: >>> 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. > > But userspace tools like ls and the terminal expect all filenames to > be in utf8, not in some random codepage that varies from fs to fs, so > how is it not a bug that the names aren't translated? Kernel doesn't know about $LANG at all. utf8 is just in a userland thing, and normal UNIX FSes doesn't care about encoding *at all*, just save as-is. It is why you feel FSes working by utf8. Well, anyway, if you want to add encoding conversion to msdos, we need the patch. -- OGAWA Hirofumi