Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#20583 - [kernel26] Change NLS_DEFAULT to utf8

Attached to Project: Arch Linux
Opened by Bernhard Walle (bwalle) - Monday, 23 August 2010, 21:21 GMT
Last edited by Tobias Powalowski (tpowa) - Sunday, 31 October 2010, 06:29 GMT
Task Type Feature Request
Category Packages: Core
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 7
Private No

Details

Description:
NLS_DEFAULT affects file systems that need a character set conversion and that have a defined encoding in the file system. For example cifs mounts (new Samba versions always use Unicode internally to represent the file name and it's up to the client to convert it to the right character set), not the classical Unix file systems that don't care about file systems at all.

Of course it's possible to overwrite it in the fstab, but since the default encoding is utf-8 nowadays on most systems, I don't think that the default of latin1 is still the right choice. With utf-8, I have working umlauts in Samba shares across Linux, Windows 7 and Mac OS 10.6 "out of the box".

The i386_defconfig and x86_64_defconfig in the kernel tree have "utf8" and openSUSE / SUSE Linux Enterprise have also utf8. I didn't check Debian or Red Hat. My request would to change it to "utf8" to save some users some minutes of work.
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Sunday, 31 October 2010, 06:29 GMT
Reason for closing:  Implemented
Comment by Mario Figueiredo (marfig) - Wednesday, 01 September 2010, 12:12 GMT
NLS_DEFAULT also affects FAT, VFAT and NTFS filesystems. Changing the default to utf-8 will, I believe, create some problems accessing these file systems (and their historic incarnations). Since iso-88591 guarantees a wider and historical access to different filesystems, seems to me a safer default value. As you say, the user can always change this...
Comment by Benjamin Richter (Waldteufel) - Wednesday, 01 September 2010, 14:47 GMT
Isn’t that what CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1" is for?
Comment by Tobias Powalowski (tpowa) - Thursday, 02 September 2010, 13:35 GMT
changed for normal and lts kernel in svn trunk, next kernels will use it.

Loading...