From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Phillip Susi <psusi@ubuntu.com>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: msdos filesystem ignores codepage argument?
Date: Mon, 29 Dec 2014 08:06:10 +0900 [thread overview]
Message-ID: <87vbkvs7bx.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <54A0807A.8000803@ubuntu.com> (Phillip Susi's message of "Sun, 28 Dec 2014 17:13:14 -0500")
Phillip Susi <psusi@ubuntu.com> 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 <hirofumi@mail.parknet.co.jp>
next prev parent reply other threads:[~2014-12-28 23:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-26 22:50 msdos filesystem ignores codepage argument? Phillip Susi
2014-12-28 17:00 ` OGAWA Hirofumi
2014-12-28 22:13 ` Phillip Susi
2014-12-28 23:06 ` OGAWA Hirofumi [this message]
2014-12-29 0:51 ` Phillip Susi
2014-12-29 1:00 ` OGAWA Hirofumi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vbkvs7bx.fsf@devron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=linux-fsdevel@vger.kernel.org \
--cc=psusi@ubuntu.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.