On Friday 11 September 2020 17:10:16 Konstantin Komarov wrote: > +Mount Options > +============= > + > +The list below describes mount options supported by NTFS3 driver in addition to > +generic ones. > + > +=============================================================================== > + > +nls=name This option informs the driver how to interpret path > + strings and translate them to Unicode and back. If > + this option is not set, the default codepage will be > + used (CONFIG_NLS_DEFAULT). > + Examples: > + 'nls=utf8' > + > +nls_alt=name This option extends "nls". It will be used to translate > + path string to Unicode if primary nls failed. > + Examples: > + 'nls_alt=cp1251' Hello! I'm looking at other filesystem drivers and no other with UNICODE semantic (vfat, udf, isofs) has something like nls_alt option. So do we really need it? And if yes, it should be added to all other UNICODE filesystem drivers for consistency. But I'm very sceptical if such thing is really needed. nls= option just said how to convert UNICODE code points for userpace. This option is passed by userspace (when mounting disk), so userspace already know what it wanted. And it should really use this encoding for filenames (e.g. utf8 or cp1251) which already told to kernel.
