Re: [Vimcdoc-translate] 0.9.0 rc1, please test

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

Thanks for the testing Willis. It is kinda hard to keep up with your pace. =
;-)

The Windows version worked fine for me here. So I've uploaded a .exe
to our website as well to see if other people can test it as well.

Please do try if you are running on Windows and report back. Thanks,

lang2

http://vimcdoc.sourceforge.net/vimcdoc_0.9.0rc1_setup.exe

On 11/03/06, Yi-an Huang <yia...@gm...> wrote:
> Hi,
>
> I tested with
>
> (1) Windows XP: VIM - Vi IMproved 6.4 (2005 Oct 15, compiled Oct 15 2005
> 16:15:14), MS-Windows 32 bit GUI version with OLE support
> +iconv/dyn
> Default codepage: Chinese (PRC)
>
> (2) Linux: VIM - Vi IMproved 6.3 (2004 June 7, compiled Aug 10 2005
> 10:32:00), Huge version with GTK2 GUI
> +iconv
>
> This is what I got. Note that all the files that I am talking about are i=
n
> utf-8 format directly from the link. I do not convert pages to gb encodin=
gs
> by myself.
>
> (1) Windows.
> a. Works if  I manually set 'encoding' to utf-8 (in .vimrc, same hereafte=
r,
> setting after a file was loaded requires reload).
> b. If I manually set 'encoding' to cp936 (euc-cn is not valid in windows)=
,
>   i) Not work (garbled characters) if a page contains "questionable"
> characters, which include
> arabic,digraph,farsi,hebrew,mbyte,options,pattern,pi_netrw,usr_24.
>   ii) Works otherwise.
>
> (2) Linux. same as what happened in Windows (but cp936 can be replaced by
> euc-cn or gb2312 in case 1b). Plus,
> a. Works if I set LANG=3Dzh_CN.UTF-8 (LC_ALL does the same job. When both
> exist, LC_ALL rules) or en_US.UTF-8 (seems the same);
> b. Works partially if I set LANG=3Dzh_CN.GB2312 (same as 1b);
> c. Works *fully* if I manually set 'encoding' to 2byte-gb18030. Even on
> pages with "questionable" characters (you still cannot see these characte=
rs,
> but fine for the remaining of the pages). Some notes:
>    i) I cannot find the corresponding LANG setting. zh_CN.GB18030 does no=
t
> work for me. You have to set the encoding manually.
>    ii) I assume the iconv library does the job in backend. So you should
> make sure that is working for you.
>    iii) The Windows version does not seem to have full GB18030 support ye=
t.
> So it will not work (the only allowed value is 2byte-cp54936. But it is
> worse than you thought) in Windows.
>
> Regards,
> Willis
>
>
> On 3/10/06, Wenzhi Liang <wen...@gm...> wrote:
> >
> > Hi all,
> >
> > I've made a stab at releasing 0.9.0. I'd like as many of you as possibl=
e
> to
> > test it. Please report back broken links, missing files, etc. Please al=
so
> > test under what enviroment can those "gbk-unfriendly" files be viewed.
> > In theory, they should be viewable:
> >
> > 1. If $LC_ALL (or $LANG) is set to zh_CN.UTF-8, please report which one=
.
> > 2. If 'enc' is set the utf-8 in Vim.
> >
> > Right now this is Linux/BSD only. If anybody want to test a Windows
> candidate,
> > put your hands up!
> >
> > Almost forgot the link. Grab it from:
> >
> > vimcdoc.sourceforge.net/vimcdoc-0.9.0-rc1.tar.gz
> >
> > Rgds,
> >
> >
> >
> > lang2
> >
> >
> > -------------------------------------------------------
> > This SF.Net email is sponsored by xPML, a groundbreaking scripting
> language
> > that extends applications into web and mobile media. Attend the live
> webcast
> > and join the prime developer group breaking into this new coding
> territory!
> >
> http://sel.as-us.falkag.net/sel?cmdlnk&kid=110944&bid$1720&dat=121642
> > _______________________________________________
> > Vimcdoc-translate mailing list
> > Vim...@li...
> >
> https://lists.sourceforge.net/lists/listinfo/vimcdoc-translate
> >
>
>