From: Jan Kara <jack@suse.cz>
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-ntfs-dev@lists.sourceforge.net, linux-cifs@vger.kernel.org,
Alexander Viro <viro@zeniv.linux.org.uk>,
Luis de Bethencourt <luisbg@kernel.org>,
Salah Triki <salah.triki@gmail.com>,
Steve French <sfrench@samba.org>,
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
David Sterba <dsterba@suse.com>,
Dave Kleikamp <shaggy@kernel.org>,
Anton Altaparmakov <anton@tuxera.com>, Jan Kara <jack@suse.com>,
"Theodore Y. Ts'o" <tytso@mit.edu>,
Eric Sandeen <sandeen@redhat.com>,
Namjae Jeon <linkinjeon@gmail.com>, Pavel Machek <pavel@ucw.cz>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: Unification of filesystem encoding options
Date: Tue, 7 Jan 2020 14:32:33 +0100 [thread overview]
Message-ID: <20200107133233.GC25547@quack2.suse.cz> (raw)
In-Reply-To: <20200102211855.gg62r7jshp742d6i@pali>
On Thu 02-01-20 22:18:55, Pali Rohár wrote:
> 1) Unify mount options for specifying charset.
>
> Currently all filesystems except msdos and hfsplus have mount option
> iocharset=<charset>. hfsplus has nls=<charset> and msdos does not
> implement re-encoding support. Plus vfat, udf and isofs have broken
> iocharset=utf8 option (but working utf8 option) And ntfs has deprecated
> iocharset=<charset> option.
>
> I would suggest following changes for unification:
>
> * Add a new alias iocharset= for hfsplus which would do same as nls=
> * Make iocharset=utf8 option for vfat, udf and isofs to do same as utf8
> * Un-deprecate iocharset=<charset> option for ntfs
>
> This would cause that all filesystems would have iocharset=<charset>
> option which would work for any charset, including iocharset=utf8.
> And it would fix also broken iocharset=utf8 for vfat, udf and isofs.
Makes sense to me.
> 2) Add support for Unicode code points above U+FFFF for filesystems
> befs, hfs, hfsplus, jfs and ntfs, so iocharset=utf8 option would work
> also with filenames in userspace which would be 4 bytes long UTF-8.
Also looks good but when doing this, I'd suggest we extend NLS to support
full UTF-8 rather than implementing it by hand like e.g. we did for UDF.
> 3) Add support for iocharset= and codepage= options for msdos
> filesystem. It shares lot of pars of code with vfat driver.
I guess this is for msdos filesystem maintainers to decide.
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2020-01-07 13:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-02 21:18 Unification of filesystem encoding options Pali Rohár
2020-01-07 13:32 ` Jan Kara [this message]
2020-01-07 17:38 ` Pali Rohár
2020-01-07 20:03 ` Theodore Y. Ts'o
2020-01-07 20:37 ` Pali Rohár
2020-01-08 7:13 ` OGAWA Hirofumi
2020-01-08 7: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=20200107133233.GC25547@quack2.suse.cz \
--to=jack@suse.cz \
--cc=anton@tuxera.com \
--cc=dsterba@suse.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@infradead.org \
--cc=hirofumi@mail.parknet.co.jp \
--cc=jack@suse.com \
--cc=linkinjeon@gmail.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ntfs-dev@lists.sourceforge.net \
--cc=luisbg@kernel.org \
--cc=pali.rohar@gmail.com \
--cc=pavel@ucw.cz \
--cc=salah.triki@gmail.com \
--cc=sandeen@redhat.com \
--cc=sfrench@samba.org \
--cc=shaggy@kernel.org \
--cc=tglx@linutronix.de \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).