Mdthbs

Due to a lot of file exchange works between Windows (GBK encoding) and Linux (UTF-8 encoding), it will encounter character encoding issues easily, such as:

• zip/tar files whose name contains chinese characters on Windows system, unzip/untar it in Linux system.


• run migrated legacy java web application (designed on Windows system, using GBK encoding in JSP) which write GBK-encoding-named files to disk.


• ftp get/put GBK-encoding-named files between Windows FTP server and Linux client.


• switch LANG environment in Linux.

The common issue of the previous mentioned are file locating/naming. After googled, I got an article Using Unicode in Linux
http://www.linux.com/archive/feed/39912, it said:

the operating system and many utilities do not realize what characters the bytes in file names represent.

So, it's possible to have 2 中文.txt files with different encoding:

[root@fedora test]# ls

????  中文

[root@fedora test]# ls | iconv -f GBK

中文

涓iconv: illegal input sequence at position 7

[root@fedora test]# ls 中文 && ls $'xd6xd0xcexc4'|iconv -f gbk

中文

中文

Questions:

1. Is it possible to config linux filesystem use fixed character encoding (like NTFS use UTF-16 internally) to store file names regardless of LANG/LC_ALL environment?


2. Or, what I actually want ask is: Is it possible to let file name 中文.txt ($'xe4xb8xadxe6x96x87.txt') in zh_CN.UTF-8 environment and file name 中文.txt ($'xd6xd0xcexc4.txt') in zh_CN.GBK environment refer to same file?


3. If it's not configurable, then is it possible to patch kernel to translate character encoding between file-system and current environment (just a question, not request implementation)? and how much performance con effect if it's possible?

I have reformulated your questions a bit, for reasons that should
appear evident when you read them in sequence.

1. Is it possible to config linux filesystem use fixed character encoding to store file names regardless of LANG/LC_ALL environment?

No, this is not possible: as you mention in your question, a UNIX file
name is just a sequence of bytes; the kernel knows nothing about
the encoding, which entirely a user-space (i.e., application-level)
concept.

In other words, the kernel knows nothing about LANG/LC_*, so it cannot
translate.

2. Is it possible to let different file names refer to same file?

You can have multiple directory entries referring to the same file;
you can make that through hard links or symbolic links.

Be aware, however, that the file names that are not valid in the
current encoding (e.g., your GBK character string when you're working
in a UTF-8 locale) will display badly, if at all.

3. Is it possible to patch the kernel to translate character encoding between file-system and current environment?

You cannot patch the kernel to do this (see 1.), but you could -in
theory- patch the C library (e.g., glibc) to perform this translation,
and always convert file names to UTF-8 when it calls the kernel, and
convert them back to the current encoding when it reads a file name
from the kernel.

A simpler approach could be to write an overlay filesystem with FUSE,
that just redirects any filesystem request to another location after
converting the file name to/from UTF-8. Ideally you could mount this
filesystem in ~/trans, and when an access is made to
~/trans/a/GBK/encoded/path then the FUSE filesystem really accesses
/a/UTF-8/encoded/path.

However, the problem with these approaches is: what do you do with
files that already exist on your filesystem and are not UTF-8 encoded?
You cannot just simply pass them untranslated, because then you don't
know how to convert them; you cannot mangle them by translating
invalid character sequences to ? because that could create
conflicts...

What you can do is limit the amount of supported locales to only UTF-8 locales.

http://www.fifi.org/cgi-bin/man2html/usr/share/man/man5/locale.gen.5