I think this is an issue for the kernel only when it comes to foreign
filesystems like VFAT and NTFS for which character set handling is
required at the filesystem level. VFAT and NTFS use UCS-2 as their
native charset, which cannot be brought to user space in Linux. The
logical thing to do is to convert UCS-2 to UTF-8 and back for those
systems.
For any POSIX-compilant filesystem this is a non-issue, since only the
null byte and the '/' byte matter. Any character set which keeps
those bytes safe is OK to use.
The console is a different issue. It currently uses Unicode as a
"lingua franca" -- converting whatever 8-bit character set it is
currently displaying to Unicode (stage 1), then map Unicode to the
appropriate font (stage 2). This is the Right Thing[TM] to do,
although the handling of non-built-in stage 1 maps is inadequate, and
we need more fonts with stage 2 maps built-in, so that one doesn't
need to load it separately.
-hpa
-- PGP: 2047/2A960705 BA 03 D3 2C 14 A8 A8 BD 1E DF FE 69 EE 35 BD 74 See http://www.zytor.com/~hpa/ for web page and full PGP public key Always looking for a few good BOsFH. ** Linux - the OS of global cooperation I am Baha'i -- ask me about it or see http://www.bahai.org/