Menu
▾
▴
vimcdoc-translate — Translator's place.
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(30) |
Dec
(124) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(67) |
Feb
(9) |
Mar
(22) |
Apr
(1) |
May
(14) |
Jun
(8) |
Jul
|
Aug
(20) |
Sep
(120) |
Oct
(49) |
Nov
(11) |
Dec
(12) |
| 2004 |
Jan
(7) |
Feb
|
Mar
(61) |
Apr
(11) |
May
(30) |
Jun
(11) |
Jul
(50) |
Aug
|
Sep
(2) |
Oct
(6) |
Nov
(3) |
Dec
(13) |
| 2005 |
Jan
(29) |
Feb
(1) |
Mar
(24) |
Apr
(11) |
May
|
Jun
(20) |
Jul
(12) |
Aug
|
Sep
|
Oct
|
Nov
(16) |
Dec
(4) |
| 2006 |
Jan
|
Feb
(2) |
Mar
(21) |
Apr
(5) |
May
(21) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2008 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(1) |
Jun
|
Jul
(7) |
Aug
(3) |
Sep
(11) |
Oct
(5) |
Nov
(27) |
Dec
(29) |
| 2009 |
Jan
(10) |
Feb
(17) |
Mar
(13) |
Apr
(20) |
May
(40) |
Jun
(28) |
Jul
(22) |
Aug
(6) |
Sep
(3) |
Oct
|
Nov
|
Dec
(9) |
| 2010 |
Jan
(6) |
Feb
(3) |
Mar
(8) |
Apr
|
May
(2) |
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(1) |
Dec
(2) |
| 2011 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
(1) |
May
(2) |
Jun
|
Jul
(2) |
Aug
(1) |
Sep
|
Oct
(1) |
Nov
(1) |
Dec
(2) |
| 2012 |
Jan
|
Feb
(1) |
Mar
(9) |
Apr
(3) |
May
(1) |
Jun
(1) |
Jul
(6) |
Aug
(1) |
Sep
|
Oct
|
Nov
(1) |
Dec
(2) |
| 2013 |
Jan
|
Feb
(1) |
Mar
(9) |
Apr
(4) |
May
(2) |
Jun
(5) |
Jul
(3) |
Aug
(10) |
Sep
(4) |
Oct
(2) |
Nov
(3) |
Dec
(3) |
| 2014 |
Jan
(4) |
Feb
(2) |
Mar
(5) |
Apr
(3) |
May
(2) |
Jun
(5) |
Jul
(1) |
Aug
(2) |
Sep
(2) |
Oct
(3) |
Nov
(5) |
Dec
|
| 2015 |
Jan
|
Feb
|
Mar
(1) |
Apr
(1) |
May
|
Jun
(1) |
Jul
(1) |
Aug
(1) |
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2016 |
Jan
(1) |
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2017 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
(3) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: James H. <ic...@gm...> - 2006-05-03 21:02:35
|
On 5/3/06, Yi-an Huang <yia...@gm...> wrote: > Fourth try. > > Sounds a good idea. But maybe we should create a branch for 6.4 instead? = By > definition, the trunk should follow the latest trend.:) Anyway 7.0 is > supposed to be out soon. Keeping two branches (6.4 and 7.x) sounds a good idea to me. :) test~ -- Best regards, James He |
|
From: Yi-an H. <yia...@gm...> - 2006-05-03 18:36:53
|
Fourth try. Sounds a good idea. But maybe we should create a branch for 6.4 instead? By definition, the trunk should follow the latest trend.:) Anyway 7.0 is supposed to be out soon. Edit: very soon. On 4/25/06, tocer <toc...@gm...> wrote: |
|
From: Wenzhi L. <wen...@gm...> - 2006-05-03 15:41:20
|
how come my test didn't get through???? On 03/05/06, tocer <toc...@gm...> wrote: > test by tocer > > > ------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job ea= sier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronim= o > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat= =3D121642 > _______________________________________________ > Vimcdoc-translate mailing list > Vim...@li... > https://lists.sourceforge.net/lists/listinfo/vimcdoc-translate > |
|
From: tocer <toc...@gm...> - 2006-05-03 13:21:06
|
test by tocer |
|
From: Wenzhi L. <wen...@gm...> - 2006-05-03 13:17:29
|
........................... I am not spam! |
|
From: Wenzhi L. <wen...@gm...> - 2006-05-03 07:45:11
|
T24gMDMvMDUvMDYsIHRvY2VyIDx0b2Nlci5kZW5nQGdtYWlsLmNvbT4gd3JvdGU6Cj4gTGlhbmc6 Cj4gx7C8uMzsuPjE47eiwcu34tDFo6zM4sS/ysciaGVscC5jbni4/NDCtb03LjBmIizKx7fxytW1 vaO/CgrV4ry4zOwgbWFpbGluZyBsaXN0INK71rHT0M7KzOKjrLeiyrLDtLa8y7XKxyBzcGFtoaPO 0s2o1qogc2YguvPX8szsssUKu9a4tKGjz9bU2tOmuMMgv8nS1MHLoaMKCsTHt+LQxcrVtb3By6Gj V2lsbGlz0rLWp7PWIGJyYW5jaGluZ6GjtPO80r/J0tTM1sLbINK7z8KhowoKPgo+Cj4KPiBXZW56 aGkgTGlhbmcg0LS1wDoKPiAgPiB0ZXN0aW5nLi4uCj4gID4KPiAgPgo+ICA+IC0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0KPiAgPiBVc2luZyBU b21jYXQgYnV0IG5lZWQgdG8gZG8gbW9yZT8gTmVlZCB0byBzdXBwb3J0IHdlYiBzZXJ2aWNlcywg c2VjdXJpdHk/Cj4gID4gR2V0IHN0dWZmIGRvbmUgcXVpY2tseSB3aXRoIHByZS1pbnRlZ3JhdGVk IHRlY2hub2xvZ3kgdG8gbWFrZSB5b3VyIGpvYgo+ICA+IGVhc2llcgo+ICA+IERvd25sb2FkIElC TSBXZWJTcGhlcmUgQXBwbGljYXRpb24gU2VydmVyIHYuMS4wLjEgYmFzZWQgb24gQXBhY2hlCj4g R2Vyb25pbW8KPiAgPiBodHRwOi8vc2VsLmFzLXVzLmZhbGthZy5uZXQvc2VsP2NtZD1rJmtpZBIw NzA5JmJpZCYzMDU3JmRhdBIxNjQyCj4gID4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX18KPiAgPiBWaW1jZG9jLXRyYW5zbGF0ZSBtYWlsaW5nIGxpc3QKPiAg PiBWaW1jZG9jLXRyYW5zbGF0ZUBsaXN0cy5zb3VyY2Vmb3JnZS5uZXQKPiAgPiBodHRwczovL2xp c3RzLnNvdXJjZWZvcmdlLm5ldC9saXN0cy9saXN0aW5mby92aW1jZG9jLXRyYW5zbGF0ZQo+ICA+ Cj4KPgo+IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0KPiBVc2luZyBUb21jYXQgYnV0IG5lZWQgdG8gZG8gbW9yZT8gTmVlZCB0byBzdXBwb3J0 IHdlYiBzZXJ2aWNlcywgc2VjdXJpdHk/Cj4gR2V0IHN0dWZmIGRvbmUgcXVpY2tseSB3aXRoIHBy ZS1pbnRlZ3JhdGVkIHRlY2hub2xvZ3kgdG8gbWFrZSB5b3VyIGpvYiBlYXNpZXIKPiBEb3dubG9h ZCBJQk0gV2ViU3BoZXJlIEFwcGxpY2F0aW9uIFNlcnZlciB2LjEuMC4xIGJhc2VkIG9uIEFwYWNo ZSBHZXJvbmltbwo+IGh0dHA6Ly9zZWwuYXMtdXMuZmFsa2FnLm5ldC9zZWw/Y21kPWxuayZraWQ9 MTIwNzA5JmJpZD0yNjMwNTcmZGF0PTEyMTY0Mgo+IF9fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fCj4gVmltY2RvYy10cmFuc2xhdGUgbWFpbGluZyBsaXN0Cj4g VmltY2RvYy10cmFuc2xhdGVAbGlzdHMuc291cmNlZm9yZ2UubmV0Cj4gaHR0cHM6Ly9saXN0cy5z b3VyY2Vmb3JnZS5uZXQvbGlzdHMvbGlzdGluZm8vdmltY2RvYy10cmFuc2xhdGUKPgo= |
|
From: tocer <toc...@gm...> - 2006-05-03 00:13:04
|
Liang: 前几天给你发了封信，题目是“help.cnx更新到7.0f”,是否收到？ Wenzhi Liang 写道: > testing... > > > ------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job > easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=k&kid0709&bid&3057&dat1642 > _______________________________________________ > Vimcdoc-translate mailing list > Vim...@li... > https://lists.sourceforge.net/lists/listinfo/vimcdoc-translate > |
|
From: Wenzhi L. <wen...@gm...> - 2006-05-02 21:56:30
|
testing... |
|
From: Wenzhi L. <wen...@gm...> - 2006-04-25 08:50:39
|
please ignore. |
|
From: Wenzhi L. <wen...@gm...> - 2006-04-10 19:19:49
|
Hi Tocer, I've added you to the developer list. Welcome to the team! You might want t= o subscribe to the translator mailing list. lang2 |
|
From: Wenzhi L. <wen...@gm...> - 2006-04-09 11:01:15
|
Thanks Willis for the reminder. It is a very good idea. I actually had some= one (tocer) sending me patch for if_pyth.txt of version 7.0c. I havn't read all about the new features myself yet and they sure sounds very exicting. Because they = are new, they might be a moving target and hence a bit tricky to translate. But= I could be wrong. What also is very important is to review the work that has been translated against 6.4 and constantly improve the quality of them. One'd thought usr_1 through usr_25 would be perfect given that they've had so long to mature. And yet bugs were still found in them. It just shows how important reviewin= g is. Must do some when I find some time. Man I sound bossy. Even I hate it. ;-) Rgds, On 09/04/06, Yi-an Huang <yia...@gm...> wrote: > Hi, > > For those who are interested in recent vim development, Vim 7 beta (the m= ost > recent 7.0c) has been released last week. Many new features have been add= ed, > among them spell checking, tabbed interface, undo branches, internal grep > are fairly interesting, at least to me. I would suggest you guys to take = a > look. > > Willis > |
|
From: Yi-an H. <yia...@gm...> - 2006-04-09 00:51:19
|
Hi, For those who are interested in recent vim development, Vim 7 beta (the mos= t recent 7.0c) has been released last week. Many new features have been added= , among them spell checking, tabbed interface, undo branches, internal grep are fairly interesting, at least to me. I would suggest you guys to take a look. Willis |
|
From: Alecs K. <al...@pe...> - 2006-03-21 05:45:13
|
On Sun, Mar 19, 2006 at 11:29:19PM +0000, Wenzhi Liang wrote: > Just pushed 0.9.0 out of the door! Many thanks for Willis for his > great contribution. Kudos! > We now have a complete base that we can improve on, towards an 1.0 release. > So let's get reviewing! Go wild! > Wandys, can you update the gro mirror? We have to update the HTML page as > well as it looks like to me that more ppl read online than actually > installing it. Done. -- Alecs King |
|
From: Wenzhi L. <wen...@gm...> - 2006-03-19 23:29:24
|
Hello all, Just pushed 0.9.0 out of the door! Many thanks for Willis for his great contribution. We now have a complete base that we can improve on, towards an 1.0 release. So let's get reviewing! Wandys, can you update the gro mirror? We have to update the HTML page as well as it looks like to me that more ppl read online than actually installing it. Will get around to do that myself for the SF site if you can take care of g= ro. Rgds, lang2 |
|
From: Wenzhi L. <wen...@gm...> - 2006-03-19 23:21:26
|
This is a major milestone release! All Vim documentation are now translated and updated against Vim 6.4. This release is almost single-handedly made possible by Willis, who has only joined us for no more than a month. Everyb= ody is encouraged to upgrade (hint: read the INSTALL file). Online HTML version= will be updated shortly. lang2 |
|
From: Wenzhi L. <wen...@gm...> - 2006-03-11 11:37:06
|
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 > > > > |
|
From: Yi-an H. <yia...@gm...> - 2006-03-11 07:37:49
|
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 in utf-8 format directly from the link. I do not convert pages to gb encodings by myself. (1) Windows. a. Works if I manually set 'encoding' to utf-8 (in .vimrc, same hereafter, 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 characters= , but fine for the remaining of the pages). Some notes: i) I cannot find the corresponding LANG setting. zh_CN.GB18030 does not 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 yet. 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 possible > to > test it. Please report back broken links, missing files, etc. Please also > 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 > |
|
From: Wenzhi L. <wen...@gm...> - 2006-03-11 00:37:00
|
Hi all, I've made a stab at releasing 0.9.0. I'd like as many of you as possible to test it. Please report back broken links, missing files, etc. Please also 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 candida= te, put your hands up! Almost forgot the link. Grab it from: vimcdoc.sourceforge.net/vimcdoc-0.9.0-rc1.tar.gz Rgds, lang2 |
|
From: Wenzhi L. <wen...@gm...> - 2006-03-10 10:29:43
|
On 10/03/06, Alecs King <al...@pe...> wrote: > On Thu, Mar 09, 2006 at 11:40:22PM +0000, Wenzhi Liang wrote: > > 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 it > > is OK. So there are two ways to do this: > > FYI, here on my box, Vim does honor the $LANG env var. I tried on another box and the gvim still ignores $LANG. Can you check your LC_ALL? We need to be careful what to say here. > > So right now, I'd lean towards an all utf solution. > > Ack. OK. This is what we are going to do then. lang2 |
|
From: å¤©é¢ æ¨ <cn_...@ho...> - 2006-03-10 04:24:09
|
<html><div style='background-color:'><DIV class=RTE> <P>Ôõô·¢µ½ÎÒÕâÀïÀ´ÁË$&*%(^()<BR><BR></P></DIV> <DIV></DIV> <BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #a0c6e5 2px solid; MARGIN-RIGHT: 0px"><FONT style="FONT-SIZE: 11px; FONT-FAMILY: tahoma,sans-serif"> <HR color=#a0c6e5 SIZE=1> <DIV></DIV>From: <I>"hai xie" <xx...@ms...></I><BR>Reply-To: <I>vim...@li...</I><BR>To: <I>vim...@li...</I><BR>Subject: <I>Re: [Vimcdoc-translate] help with iconv</I><BR>Date: <I>Thu, 09 Mar 2006 18:31:01 +0000</I><BR>>Is it OK I commited two files ?<BR>><BR>><BR>>>From: "Yi-an Huang" <yia...@gm...><BR>>>Reply-To: vim...@li...<BR>>>To: vim...@li...<BR>>>Subject: Re: [Vimcdoc-translate] help with iconv<BR>>>Date: Wed, 8 Mar 2006 01:52:56 -0500<BR>>><BR>>>Hi lang2,<BR>>><BR>>>For your list of problematic files, there are a few different <BR>>>cases.<BR>>><BR>>>Case 1, digraph, arabic, hebrew, mbyte, farsi, usr_24: foreign <BR>>>alphabets<BR>>><BR>>>utf-8 are designed to incorporate characters from different <BR>>>languages,<BR>>>enc-cn/cp936/gb2312/gb18030 is not, so in a few special cases some<BR>>>characters cannot be converted correctly and there are <BR>>>unfortunately no easy<BR>>>fix. In my opinion, utf-8 is the better form for translations for <BR>>>at least<BR>>>those documents that discuss digraphs and a few foreign languages. <BR>>>Likely,<BR>>>people who only read gb encodings will not care about these <BR>>>documents<BR>>>anyway, but we never know for sure...<BR>>><BR>>>Add "-c" parameter to iconv can work around the problem and iconv <BR>>>would<BR>>>succeed by not translating these characters. But it is better for <BR>>>us to<BR>>>leave unfixable characters with question marks. So for gb <BR>>>translations some<BR>>>manual work is needed, but i would still argue that the utf-8 <BR>>>versions<BR>>>should be the primary ones.<BR>>><BR>>>Case 2, pi_netrw, pattern: small nuisance<BR>>><BR>>>pi_netrw.txt: the name of a French author near the end of the file<BR>>>pattern.txt: "a" with a hat on top of it (actually reverting to <BR>>>the<BR>>>previous version fixes the problem. but I wonder whether people <BR>>>reading<BR>>>utf-8 may feel the current way is cleaner)<BR>>><BR>>>Case 3, various, index: incorrect characters in use and they should <BR>>>be<BR>>>fixed.<BR>>><BR>>>netbean used to have this problem too with two unusual dashes (-), <BR>>>a recent<BR>>>update fixed it, thanks.<BR>>><BR>>>I can upload the fixes of case 2 and 3.<BR>>><BR>>>Willlis<BR>><BR>><BR>><BR>><BR>>-------------------------------------------------------<BR>>This SF.Net email is sponsored by xPML, a groundbreaking scripting <BR>>language<BR>>that extends applications into web and mobile media. Attend the live <BR>>webcast<BR>>and join the prime developer group breaking into this new coding <BR>>territory!<BR>>http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642<BR>>_______________________________________________<BR>>Vimcdoc-translate mailing list<BR>>Vim...@li...<BR>>https://lists.sourceforge.net/lists/listinfo/vimcdoc-translate<BR></FONT></BLOCKQUOTE></div><br clear=all><hr> <a href="http://g.msn.com/8HMAENUS/2749??PS=47575" target="_top">Make FREE PC-to-PC calls with MSN Messenger. Get it now! </a> </html> |
|
From: Alecs K. <al...@pe...> - 2006-03-10 02:37:32
|
On Thu, Mar 09, 2006 at 11:40:22PM +0000, Wenzhi Liang wrote:
> 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=zh_CN.UTF-8 it
> is OK. So there are two ways to do this:
FYI, here on my box, Vim does honor the $LANG env var.
> But I think this is easier for the GUI user and not so much for the console
> user? What do you think wandys?
Yes, terminal euc-cn users would frown at it but i'm okay with that.
> 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. But
> then again, who am I asking to be pleased? Pondering...
I dunno about the windoze/DOS side but for Linux/*BSDs, we can do the
conversion on-the-fly in our install script and this is transparent to
users. But heck, i doubt it's worth all the effort.
> So right now, I'd lean towards an all utf solution.
Ack.
One of my favorite quotes is:
What the standard is does not matter (in fact all standards suck), as
long as we _have a standard_ to follow.
-- Anonymous
So hope we can settle this enc-cn thing ASAP and get to improve our
docs. It's good to see our ML gets noisy again and welcome new members
as well as old friends to 'Go Wild'.
Will do some review later on if time permits.
Thanks & Regards,
--
Alecs King
|
|
From: Yi-an H. <yia...@gm...> - 2006-03-10 01:07:39
|
I think there is a "nearly" perfect solution. Use iconv with gb18030 as the "to" encoding works exactly as we want. You don't need the -c flag. There will be no error, all questionable characters are marked as ??. What is more, it is in fact "lossless". When you convert it back to utf-8, it is identical to the original file. I say it is "nearly" perfect because you still cannot read them correctly i= n gb encodings. But one can keep only copies from one encoding and convert it "losslessly" to the other encoding, if necessary. I have not tested under all environments. Your environment may not support gb18030. But maybe we can try. On 3/9/06, Wenzhi Liang <wen...@gm...> wrote: > > 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? You= r > > :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= it > 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 s= ome > 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 ou= t > 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. > But > 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 > > > ------------------------------------------------------- > 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 > |
|
From: Wenzhi L. <wen...@gm...> - 2006-03-09 23:40:24
|
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 |
|
From: Yi-an H. <yia...@gm...> - 2006-03-09 19:58:28
|
Sure, thanks. On 3/9/06, hai xie <xx...@ms...> wrote: > > Is it OK I commited two files ? > > > >From: "Yi-an Huang" <yia...@gm...> > >Reply-To: vim...@li... > >To: vim...@li... > >Subject: Re: [Vimcdoc-translate] help with iconv > >Date: Wed, 8 Mar 2006 01:52:56 -0500 > > > >Hi lang2, > > > >For your list of problematic files, there are a few different cases. > > > >Case 1, digraph, arabic, hebrew, mbyte, farsi, usr_24: foreign alphabets > > > >utf-8 are designed to incorporate characters from different languages, > >enc-cn/cp936/gb2312/gb18030 is not, so in a few special cases some > >characters cannot be converted correctly and there are unfortunately no > >easy > >fix. In my opinion, utf-8 is the better form for translations for at > least > >those documents that discuss digraphs and a few foreign languages. > Likely, > >people who only read gb encodings will not care about these documents > >anyway, but we never know for sure... > > > >Add "-c" parameter to iconv can work around the problem and iconv would > >succeed by not translating these characters. But it is better for us to > >leave unfixable characters with question marks. So for gb translations > some > >manual work is needed, but i would still argue that the utf-8 versions > >should be the primary ones. > > > >Case 2, pi_netrw, pattern: small nuisance > > > >pi_netrw.txt: the name of a French author near the end of the file > >pattern.txt: "a" with a hat on top of it (actually reverting to the > >previous version fixes the problem. but I wonder whether people reading > >utf-8 may feel the current way is cleaner) > > > >Case 3, various, index: incorrect characters in use and they should be > >fixed. > > > >netbean used to have this problem too with two unusual dashes (-), a > recent > >update fixed it, thanks. > > > >I can upload the fixes of case 2 and 3. > > > >Willlis > > > > > ------------------------------------------------------- > 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?cmd=3Dlnk&kid=3D110944&bid=3D241720&dat= =3D121642 > _______________________________________________ > Vimcdoc-translate mailing list > Vim...@li... > https://lists.sourceforge.net/lists/listinfo/vimcdoc-translate > |
|
From: hai x. <xx...@ms...> - 2006-03-09 18:31:12
|
Is it OK I commited two files ? >From: "Yi-an Huang" <yia...@gm...> >Reply-To: vim...@li... >To: vim...@li... >Subject: Re: [Vimcdoc-translate] help with iconv >Date: Wed, 8 Mar 2006 01:52:56 -0500 > >Hi lang2, > >For your list of problematic files, there are a few different cases. > >Case 1, digraph, arabic, hebrew, mbyte, farsi, usr_24: foreign alphabets > >utf-8 are designed to incorporate characters from different languages, >enc-cn/cp936/gb2312/gb18030 is not, so in a few special cases some >characters cannot be converted correctly and there are unfortunately no >easy >fix. In my opinion, utf-8 is the better form for translations for at least >those documents that discuss digraphs and a few foreign languages. Likely, >people who only read gb encodings will not care about these documents >anyway, but we never know for sure... > >Add "-c" parameter to iconv can work around the problem and iconv would >succeed by not translating these characters. But it is better for us to >leave unfixable characters with question marks. So for gb translations some >manual work is needed, but i would still argue that the utf-8 versions >should be the primary ones. > >Case 2, pi_netrw, pattern: small nuisance > >pi_netrw.txt: the name of a French author near the end of the file >pattern.txt: "a" with a hat on top of it (actually reverting to the >previous version fixes the problem. but I wonder whether people reading >utf-8 may feel the current way is cleaner) > >Case 3, various, index: incorrect characters in use and they should be >fixed. > >netbean used to have this problem too with two unusual dashes (-), a recent >update fixed it, thanks. > >I can upload the fixes of case 2 and 3. > >Willlis |
357 messages has been excluded from this view by a project administrator.
