Phillip Susi <psusi@xxxxxxxxxx> 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@xxxxxxxxxxxxxxxxxx> -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
