From: James He <ic...@gm...> - 2005-11-20 09:27:06
|
On 11/20/05, Alecs King <al...@pe...> wrote: > This means we translators have to > 1) edit our file utf-8 native. we dont manually do any conversion > whatsoever. > 2) make sure the utf8-encoded file _can_ be successfully converted to > gb2312, since gb2312 is the very subset. > > I think fileencodings=3Dutf8 is the rite way to go. FYI, it does not > treat _all_ files as utf-8. It just treats utf8 (which includes ascii) > files as utf8. > > Well, this only ensures the condition 1) above. If you write some 'evil' > characters, the file still cannot be converted to gb2312. > > I wonder if there are similar tools on Windoze like this: > $ iconv -f utf-8 -t euc-cn file > /dev/null > which can help you check the validity. Should we add this guide line to data/guides.txt? :-) -- Best regards, James He |