vimcdoc-translate — Translator's place.

[Vimcdoc-translate] questions

[chimin y. <ych...@ya...>]

Can I ask what text editor you use for the work?

YC

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com

[Vimcdoc-translate] Re: vimcdoc

[chimin y. <ych...@ya...>]

> Chimin: Could I ask you to work on usr_20 at the
> moment?

I'll take usr_20. How to post it on the status page?


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com

[Vimcdoc-translate] comments on translation

[lang2 <wzh...@po...>]

I was just browsing through wandys' 'usr_30.txt' and feel
like making some general comments:

1. In the text, when translating quoation marks, you have
both chinese ones and plain  english ones, which isn't 
consistent. I'd suggest using plain english ones always.
What do you guys say?

2. I think it is cleaner to leave a leading and trailing
space when mixing english characters and chinese chars. E.g

CHINESE-CHARACTER Vim MORE-CHINESE-CHARACTERS
instead of
CHINESE-CHARACTERVimMORE-CHINESE-CHARACTERS


Feel free to disagree and discuss with me.


lang2

[Vimcdoc-translate] taking up new task

[lang2 <wzh...@po...>]

Hi all,

As I am about to finish the 'quickref.txt', I think it is 
time to take up some easy ones b4 someone else does ;-).

I am going to take the following:
 help.txt - the main one
 usr_toc.txt - the index
 usr_41.txt - the scripting things. This is not a easy one
but it is interesting!!!

ps. In the future, if anybody is going to take up new 
documents, could you please take a look at the status page
and see if it is free - I.e if the 'by' filed is 'null'. Then
inform me when you start doing the job so that I can update
the status.

Thanks,


lang2

[Vimcdoc-translate] Re: vimcdoc

[lang2 <wzh...@po...>]

Chimin,

Could you ask to post to the mailinglist for this kind 
of matters? Thanks.

> Noticed my vim version 6.1 is newer than what you guys
> based upon (6.0). Please advise.

We will be working on 6.1 documentations. Actually myself
and wandys are doing so already and I've changed the 
project public description to reflect this. I believe Ken
will agree with us and make the shift.


lang2

[Vimcdoc-translate] Re: vimcdoc

[lang2 <wzh...@po...>]

Everybody please welcome our new member!!

> 
>   registered as ychimin2000

Added to team

> 
>    I'll take next 2 slots: usr-12 and usr-20.

Ken and Merlin: Would you have conflits with this?

Chimin: Could I ask you to work on usr_20 at the moment?
As Ken has finished up till usr_11.txt I suspect he *is*
working on usr_12.txt now. We will see what Ken has to
complain though.

> 
> I'll take the completed chapters as the template,
> but if you have some ducumented rules or guidelines
> for the format, it'll be certainly a big help.

There isn't rules except that one is not supposed to change
the layout of the original document as Vim reply on those
for syntax highlighting and tags, etc. The onlything we
have right now is the 'dict.txt' in 'data' directory which
is a list of terminologies Vim uses. It is only a reference
though.


lang2

Re: [Vimcdoc-translate] One thing uncertain: 6.0 vs 6.1

[lang2 <wzh...@po...>]

> 
> And if all agrees to base on 6.1, we probably need to put the original
> English doc onto our site for new translators to work on.

Where would you put it? Is it totally necessary? 
Would a link to cosoft download suffice?

Re: [Vimcdoc-translate] One thing uncertain: 6.0 vs 6.1

[lang2 <wzh...@po...>]

> 
> Have you contacted Ken successfully telling him the 6.0 --> 6.1 issure?
> What did you think about this?? 

Yes. I've cc'ed several of the mail to him but got no 
reply. Guess he is too busy or something. I think we will
just have to make sure that what we translate is from 6.1
and hope Ken will have more time in the future.

Re: [Vimcdoc-translate] One thing uncertain: 6.0 vs 6.1

[Leslie J. <cew...@16...>]

On Mon, 2 Dec 2002 22:07:46 +0800
Leslie Jackson <cew...@16...> wrote:

> Hi, lang2.
> 
> Have you contacted Ken successfully telling him the 6.0 --> 6.1
> issure? What did you think about this??

s/you/he/

And if all agrees to base on 6.1, we probably need to put the original
English doc onto our site for new translators to work on.


-- 
Leslie Jackson

[Vimcdoc-translate] One thing uncertain: 6.0 vs 6.1

[Leslie J. <cew...@16...>]

Hi, lang2.

Have you contacted Ken successfully telling him the 6.0 --> 6.1 issure?
What did you think about this?? 


-- 
Leslie Jackson

Re: [Vimcdoc-translate] first release

[Leslie J. <cew...@16...>]

On Mon, 02 Dec 2002 13:25:29 +0000
"lang2   " <wzh...@po...> wrote:

> I've made a release based on the current cvs status. It is
> labelled 0.1 in hope that on reaching 1.0, we will have all
> the stuff translated. 

Really we can.

-- 
Leslie Jackson

Re: [Vimcdoc-translate] website and other

[Leslie J. <cew...@16...>]

On Mon, 02 Dec 2002 13:19:24 +0000
"lang2   " <wzh...@po...> wrote:

> 
> > _Very_ Clean.
> 
> Yes. But we are not at the phase yet. And we don't have a 
> web developer. I don't do php at all but only a bit perl. 
> Maybe in the future when we have finished all the 
> translation stuff we can look into that. 

As our project matures, i think we can do it better. :-)


> > 
> > We really need more people to join in.  Let me put ads into some of
> > the boards at LinuxForum and contact those interested one by one.
> 

Done.

> Good.
> I have two ppl contacted me during the weekend saying that
> they'd like to join. Hopefully they will keep up the 
> interest.
> 

Good news.  Our project is Growing!


-- 
Leslie Jackson

[Vimcdoc-translate] first release

[lang2 <wzh...@po...>]

I've made a release based on the current cvs status. It is
labelled 0.1 in hope that on reaching 1.0, we will have all
the stuff translated. 

Re: [Vimcdoc-translate] website and other

[lang2 <wzh...@po...>]

> _Very_ Clean.

Yes. But we are not at the phase yet. And we don't have a 
web developer. I don't do php at all but only a bit perl. 
Maybe in the future when we have finished all the 
translation stuff we can look into that. 

> 
> We really need more people to join in.  Let me put ads into some of the
> boards at LinuxForum and contact those interested one by one.

Good.
I have two ppl contacted me during the weekend saying that
they'd like to join. Hopefully they will keep up the 
interest.

Re: [Vimcdoc-translate] website and other

[Leslie J. <cew...@16...>]

On Fri, 29 Nov 2002 14:16:46 +0000
"lang2   " <wzh...@po...> wrote:

> I'd like to introduce a website to you guys:
> 
> http://vimdoc.sf.net

_Very_ Clean.


> What I only noticed today is that there is a link to a site
> containing a Japanese translation of the Vim documents. It
> looks like they've done a lot of work already. (Well, they
> have more people involved than us anyway.) 

We really need more people to join in.  Let me put ads into some of the
boards at LinuxForum and contact those interested one by one.


-- 
Leslie Jackson

Re: [Vimcdoc-translate] webpage up.

[Leslie J. <cew...@16...>]

Clean enough and Pretty Good. :-)

BTW, please change my email address to <wa...@us...>.
Cosoft could not properly forward the mails.

-- 
Leslie Jackson

[Vimcdoc-translate] webpage up.

[lang2 <wzh...@po...>]

Re: [Vimcdoc-translate] 'finished' usr_30.txt

[lang2 <wzh...@po...>]

I've downloaded and will find time to read it.
Well done wandys.

[Vimcdoc-translate] 'finished' usr_30.txt

[Leslie J. <cew...@16...>]

The quotes in the subject mean that it's to be refined. :-)

I've not translated it word by word, cutting/adding some
words/phrases/sentences _trying_ to make it be more fluent and clear.

If you're glad to, i'd request your review of that file.  It would be of
great help if you have time to read the translated text and tell me if
there're any visible mistakes or errors.

I'd be much more appreciate it if you have extra time and would like to
help me revise it by taking a look at parts of the original English
text.

Any suggestions, comments, or criticisms are welcomed as well.  It's
said that it's much easier to find out what others have done wrong than
to make it right oneself.  And you know, translation is not a easy job.

P.S. While polishing this translated file, i'm planning to translate
another two files "usr_29.txt" and "quickfix.txt".  I want to make sure
there's no overlapping effort.



Thanks.

-- 
Leslie Jackson

Re: [Vimcdoc-translate] cvs changes

[Leslie J. <cew...@16...>]

On Fri, 29 Nov 2002 14:04:19 +0000
"lang2   " <wzh...@po...> wrote:


> Thus now we have the following dir structure in CVS:
> 
> ROOT
> |
> +--doc  (where the translated docs are)
> |
> +--data (project related stuff)
>    |
>    +--release
>    |
>    +--www
>       |
>       +--htdocs
>       |
>       +--cgi-bin
> 

Great.  I'm checking it out.


-- 
Leslie Jackson

Re: [Vimcdoc-translate] cvs dir structure

[Leslie J. <cew...@16...>]

On Fri, 29 Nov 2002 13:44:02 +0000
"lang2   " <wzh...@po...> wrote:


> > 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. :-)

Hehe, who's that 'someone'?? 

Someone just made a proposal and another one(s) would make it possible.
;-)

-- 
Leslie Jackson

Re: [Vimcdoc-translate] Working at usr_30.txt and help needed.

[Leslie J. <cew...@16...>]

On Fri, 29 Nov 2002 14:11:40 +0000
"lang2   " <wzh...@po...> wrote:

> It is hard for me to send Chinese character so...

Still haven't make xsim work?

> > 1) Formatting comment 
> pai lie zhushi de geshi

排列注释的格式 (Good enough :-)
 
> > 2) Exploring the GUI
> s/Exploring/exploiting/

Sorry for the typo.  How do you translate this one?

> 
> > 3) Moving through programs
> Programs really mean source code here. 

Yes.
But would these translations be nice enough:

在程序间移动；在代码间移动？  (You have any idea??)

 
> > 4) modifiers(filename-modifiers)
> This is a hard one. I found it hard to translate for my 
> quickref.txt. Let me know if you have it done. :-)
> 

How about "修饰符"，"文件名修饰符" ?? 


I owe you a big thank-you, lang2.  You are a kind nice guy. ;-)

-- 
Leslie Jackson

[Vimcdoc-translate] website and other

[lang2 <wzh...@po...>]

I'd like to introduce a website to you guys:

http://vimdoc.sf.net

I knew this place for long and I suppose Ken knows this
as well (My guess is that the name vimcdoc came out of this).

It is clean and useful, providing search, only reading, 
various formats for download, etc. Maybe we should be doing
things like this as well.

Merlin: There is a PDF copy of the book I mentioned on the
page I suppose you can follow. 

What I only noticed today is that there is a link to a site
containing a Japanese translation of the Vim documents. It
looks like they've done a lot of work already. (Well, they
have more people involved than us anyway.) Please take a 
look at that site if you like. What I want to say is: If 
the Japanese can do it. We can do better!


lang2

Re: [Vimcdoc-translate] Working at usr_30.txt and help needed.

[lang2 <wzh...@po...>]

It is hard for me to send Chinese character so...

> How would you translate these:
> 
> 1) Formatting comment 
pai lie zhushi de geshi

> 2) Exploring the GUI
s/Exploring/exploiting/

> 3) Moving through programs
Programs really mean source code here. 

> 4) modifiers(filename-modifiers)
This is a hard one. I found it hard to translate for my 
quickref.txt. Let me know if you have it done. :-)

[Vimcdoc-translate] cvs changes

[lang2 <wzh...@po...>]

Hi all,

I took that there was no objection to the proposal I put
forward yesterday ;-). So I just did it.

Thus now we have the following dir structure in CVS:

ROOT
|
+--doc  (where the translated docs are)
|
+--data (project related stuff)
   |
   +--release
   |
   +--www
      |
      +--htdocs
      |
      +--cgi-bin

'cvs co data' will check out the project related stuff, 
including a 'dict.txt', the webpage (the old one for vcd),
and some package building scripts.

'cvs co doc' will check out only the docs.

I sugest doing the following:

1. Make a directory somewhere named 'vimcdoc' or whatever
you like as the top-level dir.

2. check out data under 'vimcdoc'.

3. 'cd data' and check out 'doc' in there.

Then you are sorted!

Rgds,


lang2