[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[debian-devel:10839] Re: (fwd) Re: Correct use of UTF-8 under Unix
佐野@浜松です。
vim-multibyte ML からの転送です。参考までに。
In <199911031117.MAA06960@xxxxxxxxxxxxx>,
at Wed, 03 Nov 1999 12:17:03 +0100,
on (fwd) Re: Correct use of UTF-8 under Unix,
Bram Moolenaar <Bram@xxxxxxxxxxxxx> さん writes:
>
> [There is a discussion on the linux-utf8 maillist about file encodings. Here
> is a reply about the 'fileencoding' option in Vim which you might find
> interesting.]
>
> Date: Tue, 2 Nov 1999 20:31:59 +0100 (CET)
> From: PILCH Hartmut <phm@xxxxxx>
> To: linux-utf8@xxxxxxxxxxxx
> cc: perl-unicode@xxxxxxxx
> Subject: Re: Correct use of UTF-8 under Unix
> Message-ID: <Pine.LNX.4.10.9911022028010.7046-100000@xxxxxxxxxxxxxxxxx>
>
> On Tue, 2 Nov 1999, Bram Moolenaar wrote:
>
> > So, what now? I certainly would like Vim to be able to handle multiple
> > encodings. The easy way out is to let the user set the 'fileencoding' option.
> > This is actually already working, with these values:
> > ansi default setting, good for most Western languages
> > japan set to use shift-JIS (Windows CP 932) encoding
> > korea set to use Korean DBCS
> > prc use simplified Chinese encoding
> > taiwan use traditional Chinese encoding
>
> For Japan, Shift-JIS is definitely not enough. You need at least also
> EUC-Japan and iso-2022-jp-2. For the others the situation is similar.
> Emacs uses the MIME names, as does Java.
>
> Also, Emacs subdivides your 'fileencoding' into a
> 'coding-system-for-read' and a 'coding-system-for-write'.
>
> If in doubt, it is a good idea to follow the Emacs naming. Emacs is
> not yet UTF8 based, but it has thouroughly designed multi-coding
> capabilities with many years of experience and it is the only
> multilingual system that has been in use on Linux. Therefore it
> would also be very helpful, if your vim was able to read the
> multilingual encodings used by Emacs: iso-2022-7bit and emacs-mule.
>
> Thanks to Otfried Cheong's conversion frontend, I am currently using
> Emacs with the "unicode-utf8" encoding (is that a MIME name?), but
> the other two multilingual encodings will keep staying around for
> quite a while, since it will take a lot of effort to move the core
> of Emacs to Unicode.
>
> --
> phm
>
> -
> Linux-UTF8: i18n of Linux on all levels
> Archive: http://mail.nl.linux.org/lists/
--
# 11/13 に何かが起きる? > "http://www.szlug.factory.to"
# (わたしのおうちは浜松市、「夜のお菓子」で有名さ。)
<xlj06203@xxxxxxxxxxx> : Taketoshi Sano (佐野 武俊)