On Wed, 6 Oct 2010, [email protected] wrote:
Hi, All.
# I changed the subject.
# (it was: [patch] Add an option to specify filename encoding.)
I'm very sad because nobody reply to this topic... ;p
This is not only a problem for CJK people.
You can't handle filename properly in Vim when filename encoding is
different than 'encoding'.
# at least on Unix like systems.
This problem affects people who are using latin1 (or whatever)
encoding for filename and UTF8 for internal Vim 'encoding'.
... Or, no one use non-unicode encoding for filename in the 21st
century?
Pretty much. :-)
Can you describe your system setup? Trying to create a test case for
this, I made a tiny vfat filesystem, but then found that the mount
options for 'VFAT' state that long filenames are stored in Unicode (I
believe as UTF-16). Short filenames depend on a codepage, but the
utility of a feature like this, just to fix 8.3 filenames seems dubious.
Not that I fully support UTF-8 monoculture[1], but right now, it's by
far the best option. Better to use something like "convmv"[3] to
convert non-UTF-8 filenames to UTF-8.
[1]
http://web.archive.org/web/20070213204402/modeemi.fi/~tuomov/b/archives/2006/08/26/T20_16_06/
[*] above written by the "controversial" Tuomo Valkonen -- his writings
tend to be a bit over-the-top, but present a good counterpoint to the
"FOSScracy" [his term]
http://en.wikipedia.org/wiki/Ion_(window_manager)#Controversy
[2] http://www.j3e.de/linux/convmv/man/
The patch I posted here before adds a new feature to convert filenames
between filename encoding on filesystem and internal 'encoding'.
I'm not sure but this problem may not happen on Windows, because I
found a lot of Unicode stuff in os_win32.c, and maybe do the same
thing with a different way (Win32 Wide APIs).
The feature should simply convert filenames only when 'systemencoding'
is set, and if 'systemencoding' is not set, it should do nothing as
usual.
I think 'filenameencoding' (though long) would be a better name.
'systemencoding' sounds like what the current 'encoding' option does.
("system" to me implies the computing environment, not the filesystem.)
So, if people doesn't use non-unicode encoding for filename anymore,
the feature doesn't affect the people.
What do you think about this feature / problem, everyone?
Bram, could you add this *feature* to Vim if you think it's good,
please?
# ofcourse, you don't have to use the patch.
And, let me know if there's something I can do.
Thanks in advance.
Best Regards,
Kikuchan
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
