Re: [Vimcdoc-translate] Re: Re: 0.8.0-beta1

[Wenzhi L. <wen...@gm...>]

Excellent! Thanks wandys,

On 6/28/05, Alecs King <al...@pe...> wrote:
>=20
> > > ie.
> > >
> > > :h intro@cn (under GBK locale, aka in vim, enc=3Deuc-cn) shows nothin=
g
> > > but malformed characters.
>=20
> I _was_ kinda misleading here.  The truth is that, euc is not gbk but
> gb2312.  Some of our docs contain some 'evil' characters that have been
> converted from gbk.  But these characters are gbk-only [1] and cannot be
> successfully converted to enc-cn (aka gb2312). Hence the problem arises.

That explains why on Slackware if I set LANG to zh_CN.gbk, things are OK. I=
s=20
that a limitation of Vim though?


>=20
> All changes committed to CVS.  I'm about to release a 0.8.0-rc1 which
> you can test to see if this problem still remains and/or there are any
> other problems.
Will test the new tarball.

>=20
> When doing translation, remember to run the following command
>=20
> $ iconv -f utf-8 -t euc-cn file.txt >/dev/null
>=20
> to check if your doc is enc-cn friendly.
Can you add this to the guide.txt? Thanks

Greate job!


lang2