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: lang2 <wzh...@po...> - 2002-11-29 13:44:07
|
> What about being named as 'data'?? I often see projects using this name > for this kind of stuff. So be it. > Yes, indeed. We can make a new (cleaner and more straightforward) one > for both VCD and vimcdoc. (How about VCD being a mirror-like site for > vimcdoc??) Someone is asking for more work. :-) > lang2, i'd say you really did a GOOD JOB for us(and our projects)! At your service. |
From: lang2 <wzh...@po...> - 2002-11-28 18:06:31
|
> Hi, there. Hi, > > How would you translate these: I havn't the immediate answer but will look into it tomorrow: > > 2) We have to contact more often (wait, i know everyone is busy...) with > each other. (and we need more people to join in) We ought to share our > thoughts and tips about our translation work. What's most important, we > should help each other in a cooperative way. That's the essence of > collaboration! Agree. But it looks hard to attract ppl. We have to try harder maybe. > P.S. Ken, are you there? lang2 have suggested that we should base our > work on version 6.1.(in fact, there's not too much work going from 6.0 > to 6.1). Could you set up a new structure of the CVS tree? I personally > think lang2's model on cosoft is actually good enough(maybe we could add > more stuff). Or maybe lang2, since you're granted the project manager's > privileges, could do the effort for us?? > Ken (and Merlin) hasn't subscribe to the list yet. As for CVS, plese refer to the other mail I sent out. > When was your last date with your > girlfriend? ;-) 3 yrs ago? ;-) |
From: Leslie J. <cew...@16...> - 2002-11-28 18:05:20
|
On Thu, 28 Nov 2002 17:08:34 +0000 "lang2 " <wzh...@po...> wrote: > Hi everyone, > > As the current status of the cvs directory stucture stands, > I propose doing the following: Hadn't received this mail before i sent that 'help needed' message. > > 1. add another top level directory -- 'vimcdoc' for > containing stuff other than the translated doucments. What about being named as 'data'?? I often see projects using this name for this kind of stuff. > web page (We are going to have one won't we?) Yes, indeed. We can make a new (cleaner and more straightforward) one for both VCD and vimcdoc. (How about VCD being a mirror-like site for vimcdoc??) > things will be done by the end of this weekend. > lang2, i'd say you really did a GOOD JOB for us(and our projects)! Thanks. -- Leslie Jackson |
From: Leslie J. <cew...@16...> - 2002-11-28 17:50:24
|
Hi, there. I'm just working at the file usr_30.txt. (I know Ken's going on with usr_1?.txt and Merlin started usr_20.txt so i don't want to overlap our effort. :-) I've finished about a third of that file, encountering some difficulties translating some of the words/phrases smoothly. I need your help. How would you translate these: 1) Formatting comment 2) Exploring the GUI 3) Moving through programs 4) modifiers(filename-modifiers) Any insights would be appreciated. Thanks in advance. Some of my other thoughts: 1) As Merlin suggested, i did not (at least _tried_ not to) translate the text word by word. Sometimes i even cut redundant sentences to be clearer and smoother. 2) We have to contact more often (wait, i know everyone is busy...) with each other. (and we need more people to join in) We ought to share our thoughts and tips about our translation work. What's most important, we should help each other in a cooperative way. That's the essence of collaboration! P.S. Ken, are you there? lang2 have suggested that we should base our work on version 6.1.(in fact, there's not too much work going from 6.0 to 6.1). Could you set up a new structure of the CVS tree? I personally think lang2's model on cosoft is actually good enough(maybe we could add more stuff). Or maybe lang2, since you're granted the project manager's privileges, could do the effort for us?? I'm going to finish usr_30.txt by this Sunday. (You know there're a lot of things to do at weekend. When was your last date with your girlfriend? ;-) Wish you all a pleasant weekend! -- Leslie Jackson |
From: lang2 <wzh...@po...> - 2002-11-28 17:08:42
|
Hi everyone, As the current status of the cvs directory stucture stands, I propose doing the following: 1. add another top level directory -- 'vimcdoc' for containing stuff other than the translated doucments. 2. make both 'vimcdoc' and 'doc' cvs modules. 3. In 'vimcdoc', there will be stuff like the word list, web page (We are going to have one won't we?), package generating scripts, etc. This kind of setup is different from what we had for 'vcd' but in a way it is good as well - user who don't care about the web, package building etc can simply checkout the 'doc' module and enjoy the translated documents. I have already made makefiles for building various packages for 'vcd'. They can be used unchanged for 'vimcdoc' provided that we checkout 'vimcdoc' first and then checkout 'doc' inside the 'vimcdoc' directory. If you guys agree, things will be done by the end of this weekend. Rgds, lang2 |
From: lang2 <wzh...@po...> - 2002-11-28 08:53:33
|
> > > > Indeed. > > Not considering much within enough context, i just _try_ to translate > some of them: Thanks. That will help a lot. > BTW, lang2, have you contact the guys who replied to the post on > LinuxForum? Not yet. I'd better do that then. |
From: Leslie J. <cew...@16...> - 2002-11-28 06:19:16
|
On Wed, 27 Nov 2002 13:30:00 +0000 "lang2 " <wzh...@po...> wrote: > It would still be nice though > to have a standard mapping of special terminologies like > 'folding' tec. > Indeed. Not considering much within enough context, i just _try_ to translate some of them: + identifier 标识(符) + word 单词 + sentence 句子 + paragraph 段落;段 + offset 位移量;偏移量 + boolean 布尔变量(or 类型?) + shell shell BTW, lang2, have you contact the guys who replied to the post on LinuxForum? -- Leslie Jackson |
From: lang2 <wzh...@po...> - 2002-11-27 13:41:39
|
> > Note that at the end of 75th line, there's a '>'. If you removed that > '>', there would be no color. Indeed. My apologies. Man, this is tricky. |
From: lang2 <wzh...@po...> - 2002-11-27 13:30:09
|
> i delete them all... The problem is that you know what the English > context means but don't know how to translate it into Chinese in a > neatest way. Totally agree. It would still be nice though to have a standard mapping of special terminologies like 'folding' tec. > > Hope Ken could set a new directory structure for CVS tree. Ken and Merlin: Would you like to subscribe to this list? lang2 |
From: Leslie J. <cew...@16...> - 2002-11-27 12:32:36
|
On Wed, 27 Nov 2002 12:11:04 +0000 "lang2 " <wzh...@po...> wrote: > > I've taken a close look at the original English texts finding that > > there're also '>'s in the context. (often following the colon at the > > end of the line) > > I didn't look into all the occurance but in usr_01.txt. > The oringinal 76-78 doens't have '>' or '<'. While in the > translated text there are in line 68-70. The oringinal > documentation uses <TAB>: for synatx element. > Note that at the end of 75th line, there's a '>'. If you removed that '>', there would be no color. -- Leslie Jackson |
From: Leslie J. <cew...@16...> - 2002-11-27 12:26:46
|
On Wed, 27 Nov 2002 10:32:19 +0000 "lang2 " <wzh...@po...> wrote: > Could I ask you > to take a look and see what you think? What i got on my mind: Translation is harder than expected. It's difficult to find a proper peer in Chinese sometimes. Today i've tried to start translating another file in the Vim Doc. After a couple of hours of efforts, i'm really not satisfied with what i've translated. So i delete them all... The problem is that you know what the English context means but don't know how to translate it into Chinese in a neatest way. > This file, IMHO, should go into CVS at some stage, though > I don't know where. Any suggestions? > Hope Ken could set a new directory structure for CVS tree. -- Leslie Jackson |
From: lang2 <wzh...@po...> - 2002-11-27 12:14:11
|
Hi all, I've setup yet another mailing list for receiving automatic notification of cvs commits. Please go here if you want to sign up. http://lists.sourceforge.net/lists/listinfo/vimcdoc-cvscommit lang2 |
From: lang2 <wzh...@po...> - 2002-11-27 12:11:08
|
particular things > > > used for coloring. It may be somewhat weird but if you removed them > > > the words between that'>' and '<' wouldn't be color-syntaxed any > > > more. > > > > Oops. Indeed they are in Ken's translation. However, > > they are not in the Vim documentation. > > I've taken a close look at the original English texts finding that > there're also '>'s in the context. (often following the colon at the end > of the line) I didn't look into all the occurance but in usr_01.txt. The oringinal 76-78 doens't have '>' or '<'. While in the translated text there are in line 68-70. The oringinal documentation uses <TAB>: for synatx element. |
From: Leslie J. <cew...@16...> - 2002-11-27 12:02:32
|
On Wed, 27 Nov 2002 10:16:57 +0000 "lang2 " <wzh...@po...> wrote: > > > > I've already noticed this. They have been included in Ken's > > original work and they're normally at the beginning of some lines. > > I think they are not the diff stuff but sort of particular things > > used for coloring. It may be somewhat weird but if you removed them > > the words between that'>' and '<' wouldn't be color-syntaxed any > > more. > > Oops. Indeed they are in Ken's translation. However, > they are not in the Vim documentation. I've taken a close look at the original English texts finding that there're also '>'s in the context. (often following the colon at the end of the line) Seems they are necessary for coloring. -- Leslie Jackson |
From: lang2 <wzh...@po...> - 2002-11-27 10:40:05
|
Right. Just as I expected! I will have to attach it then. Don't know how mailman handles attachment. Sorry lads. Won't happen again, I promise. lang2 |
From: lang2 <wzh...@po...> - 2002-11-27 10:32:26
|
Hi all, I've been preparing a list of translation for Vim terminologies, which is pasted below. Could I ask you to take a look and see what you think? It is not complete. There are some words that I just can't find the proper translation (e.g diagraph) or I don't understand the real meaning (alternative file). If you guys can help me finish this (the list will grow during the course), I think I can finish the quickref.txt much easier. This file, IMHO, should go into CVS at some stage, though I don't know where. Any suggestions? Thanks, -------------------------------------------------------- The following table contains the terminologies Vim used in its documentation and The corresponding Chinese frase. +----------------------------------------------------+ | ENGLISH ???? + +----------------------------------------------------+ + text object ??¡À????¨® + shiftwidth + quickfix + mark and tag ¡À¨º????¡À¨º?? + visual mode ???????? + synatx highligh ??¡¤¡§???? + scroll ?¨ª?? + digraph + folding ???? + identifier + atom + append + indent ???? + join + register ?????¡Â + yank + shell + alternative file + key mapping + abbreviations ???? + literally + recall ???? + argument ???? + section + active ?????? + buffer ???? + arg ???? + block ?¨¦ + operator ??¡Á¡Â¡¤? + word + sentence + paragraph + section + inner + cursor ??¡À¨º + tooltip + autocommand ¡Á????¨¹?? + event ???? + swap file ???????? + boolean + offset + column ?? + like ?? + Vi Vi + Vim Vim + Ex Ex + lisp lisp + GUI GUI + UNIX UNIX -------------------------------------------------------- ps. If the encoding of the mail isn't perfect, don't blame me! :-) lang2 |
From: lang2 <wzh...@po...> - 2002-11-27 10:17:03
|
> > I've already noticed this. They have been included in Ken's original > work and they're normally at the beginning of some lines. I think they > are not the diff stuff but sort of particular things used for coloring. > It may be somewhat weird but if you removed them the words between that > '>' and '<' wouldn't be color-syntaxed any more. Oops. Indeed they are in Ken's translation. However, they are not in the Vim documentation. Thus, I'd suggest it should be done away with. I think the syntax hilight work with <TAB>: |
From: Leslie J. <cew...@16...> - 2002-11-26 17:58:48
|
On Tue, 26 Nov 2002 16:31:47 +0000 "lang2 " <wzh...@po...> wrote: > Hi wandys, > > I've noticed that the files you checked in into the cvs > server on cosoft has '>' and '<' which supposely is the > output by diff. Could you fix those. I've already noticed this. They have been included in Ken's original work and they're normally at the beginning of some lines. I think they are not the diff stuff but sort of particular things used for coloring. It may be somewhat weird but if you removed them the words between that '>' and '<' wouldn't be color-syntaxed any more. > > And if Ken agree, could you check those into the SF cvs > repository? Will do. -- Leslie Jackson |
From: lang2 <wzh...@po...> - 2002-11-26 16:32:01
|
Hi wandys, I've noticed that the files you checked in into the cvs server on cosoft has '>' and '<' which supposely is the output by diff. Could you fix those. And if Ken agree, could you check those into the SF cvs repository? Ken, myself and wandys both agree that we should be working on 6.1 documentations as: 1. It is the latest 2. There are very little difference. 3. It is likely that 6.1 will be the official Vim version for a while. Would you agree with that? Thanks lang2 |
From: lang2 <wzh...@po...> - 2002-11-26 10:14:58
|
> > > Whether we use it or not can be decided later. But at > > least it is there if we do. > > Since we all are included in the vimcdoc's members list, I think we can > use SF.net as main development platform. Let's wait and see what Ken and Merlin have to say. I personally agree. |
From: Leslie J. <cew...@16...> - 2002-11-26 06:32:28
|
On Tue, 26 Nov 2002 14:28:01 +0800 Leslie Jackson <cew...@16...> wrote: > Test Okay. -- Leslie Jackson |
From: Leslie J. <cew...@16...> - 2002-11-26 06:28:44
|
Test -- Leslie Jackson |
From: lang2 <wzh...@po...> - 2002-11-25 19:53:55
|
passed. On Mon, 25 Nov 2002 19:47:04 +0000 "lang2 " <wzh...@po...> wrote: > testing. > > > ------------------------------------------------------- > This SF.net email is sponsored by: Get the new Palm Tungsten T > handheld. Power & Color in a compact size! > http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en > _______________________________________________ > Vimcdoc-translate mailing list > Vim...@li... > https://lists.sourceforge.net/lists/listinfo/vimcdoc-translate > |
From: lang2 <wzh...@po...> - 2002-11-25 19:47:23
|
testing. |