Re: [Vimcdoc-translate] Re: Re: help with iconv

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

wandys,

>
> > hmmm. How do we achieve that? I tried to set LANG=3Dzh_CN.UTF-8 and
> > vim still can't display usr_24.txt
>
> Thats weird.  utf-8 files cant be viewed in the utf-8 environment?  Your
> :enc is?  I tested gvim with :enc=3Dutf-8.  No problems at all.

It turns out that (on my sytem at least), vim ignores the $LANG env var and
set the 'enc' option based on $LC_ALL. So if I have $LC_ALL=3Dzh_CN.UTF-8 i=
t
is OK.  So there are two ways to do this:
1) in the shell, set LC_ALL=3Dzh_CN.UTF-8, which might not be ideal for som=
e user,
me included.
2) in vim, set 'enc' to utf-8.

This actually sounds OK to me. The euc-cn users will actually not miss out
big because it is only a small portion of the whole translation that won't =
be
viewed easily. If we can fix two more (as Willis suggested?), it looks like=
 a
good compromise.

But I think this is easier for the GUI user and not so much for the console
user? What do you think wandys?

> > Then is this not the same as 2?
>
> No.  The utf-8 version remains good and utf-8 users are happy as ever.
> And for enc-cn users, we provide a compromised version to avoid junk
> files.  This is IMHO by far the most possible workaround if we still
> consider enc-cn people.  We can detect or let user specify locale/:enc
> in our install script.  Or, we can directly provide two tarballs to let
> users choose to download and install whichever suits them.

This sounds OK too and it would definitely please both crowds. But it doens=
't
please me. :-). It just feels strange to have two releases for one thing. B=
ut
then again, who am I asking to be pleased? Pondering...

So right now, I'd lean towards an all utf solution.

Any more inputs?

lang2