vimcdoc-translate — Translator's place.

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

[Alecs K. <al...@pe...>]

On Wed, Mar 08, 2006 at 11:01:26PM +0000, Wenzhi Liang wrote:
> So the work around is still a work around.

For GUI Vims in the enc-cn locale (or :enc) that still can show utf-8,
yes.  But i may suggest they use utf-8 in the first place.

> > So there are several options for us:

These options are all (bad) workarounds too.

> > 1) We dont care about euc-cn any more.  utf-8 only, simple and clear.

Which means all the problems are NOT problems any more since there's no
euc-cn concerned.  We only support utf-8 and people must use utf-8 to
view our docs.  This of course will piss off enc-cn users.

> hmmm. How do we achieve that? I tried to set LANG=zh_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=utf-8.  No problems at all.

> > 2) We care about euc-cn by sacrificing utf-8 quality (change/remove
> >    questionable chars).
> 
> Don't think that's a good idea.

Ack.

> > 3) With utf-8 versions being good and untouched, we start maintaining
                                          ^^^^^^^^^
> >    and providing separate euc-cn versions (iconv -c).
                     ^^^^^^^^

> I think 'iconv -c' simply drop the character that it has problem with.

We can change it to something else like ??

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

> > 4) Patch Vim to make it act like iconv -c when it's doing conversion.
> 
> Don't think Vim's maintainer would be happy with this. Same reason as 3.

Pretty hard.  Even if he does accept it, though in little chance,
there might be a long time till people use that patched version, if any.

> If I understand correctly, it is because iconv doesn't support gbk?

No, it's not.  iconv has no problem and it does its job _pretty_ well
in its own right.  The problem is because of the gbk/gb2312 encodings
themselves:  they just dont have those foreign characters and thus the
chars cant be converted to and correctly displayed in gb locale/:enc.


utf-8 rox.  Ken Thompson kicks ass.  But we live in a messy world.

-- 
Alecs King

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

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

Hi wandys,

Long time no see. :-)

On 08/03/06, Alecs King <al...@pe...> wrote:
> On Tue, Mar 07, 2006 at 11:31:40PM +0000, Wenzhi Liang wrote:
> > wandys,  I remember we had this problem before and you fixed it. If you
> > are still around, can you take a look at this?
>
> The problem i 'fixed' falls in the case 2 & 3 as Willis stated. (welcome
> aboard. huge job you did. thanks).
>
> There's no easy and elegant fix for case 1.  It may be not very polite
> to have people's names misspelled as Thunder said in another mail.

I agree with thunder too.

>
> > There is a work around for this: add 'enc=3Dutf-8' to the status line.
>
> This doesnt affect utf-8 users since they already set to use utf8 in the
> first place.  And this does no good for a regular enc-cn user since s/he
> normally cannot view utf-8 in his/her enc-cn environment (ie. in a
> enc-cn locale'd terminal).

Well that's not entirely true. When I said it was a work around, I tested w=
ith
the GUI version (don't use vim on console that often).  And you are right a=
bout
the console side. However, if the console cannot display utf8 character at
all, it is not a problem of the translation then. So the work around is sti=
ll a
work around.

>
>
> So there are several options for us:
>
> 1) We dont care about euc-cn any more.  utf-8 only, simple and clear.

hmmm. How do we achieve that? I tried to set LANG=3Dzh_CN.UTF-8 and
vim still can't display usr_24.txt

>
> 2) We care about euc-cn by sacrificing utf-8 quality (change/remove
>    questionable chars).

Don't think that's a good idea.

>
> 3) With utf-8 versions being good and untouched, we start maintaining
>    and providing separate euc-cn versions (iconv -c).

I think 'iconv -c' simply drop the character that it has problem with. Righ=
t?
Then is this not the same as 2?

>
> 4) Patch Vim to make it act like iconv -c when it's doing conversion.

Don't think Vim's maintainer would be happy with this. Same reason as 3.

>
> Nooooone is perfect.

That seems true. If I understand correctly, it is because iconv doesn't sup=
port
gbk?


lang2

[Vimcdoc-translate] Re: help with iconv

[Alecs K. <al...@pe...>]

On Tue, Mar 07, 2006 at 11:31:40PM +0000, Wenzhi Liang wrote:
> wandys,  I remember we had this problem before and you fixed it. If you
> are still around, can you take a look at this?

The problem i 'fixed' falls in the case 2 & 3 as Willis stated. (welcome
aboard. huge job you did. thanks). 

There's no easy and elegant fix for case 1.  It may be not very polite
to have people's names misspelled as Thunder said in another mail.

> There is a work around for this: add 'enc=utf-8' to the status line.

This doesnt affect utf-8 users since they already set to use utf8 in the
first place.  And this does no good for a regular enc-cn user since s/he
normally cannot view utf-8 in his/her enc-cn environment (ie. in a
enc-cn locale'd terminal).


So there are several options for us:

1) We dont care about euc-cn any more.  utf-8 only, simple and clear.

2) We care about euc-cn by sacrificing utf-8 quality (change/remove
   questionable chars).

3) With utf-8 versions being good and untouched, we start maintaining
   and providing separate euc-cn versions (iconv -c).

4) Patch Vim to make it act like iconv -c when it's doing conversion.

5) ???


Nooooone is perfect.

-- 
Alecs King

Re: [Vimcdoc-translate] help with iconv

[Yi-an H. <yia...@gm...>]

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 eas=
y
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

Re: [Vimcdoc-translate] help with iconv

[<thu...@gm...>]

VW5mb3J0dW5hdGVseSwgaXQgc2VlbXMgdGhhdCB0aGVyZSBpcyBubyAiw7QiIGluIEdCMjMxMiBl
bmNvZGluZy4gVGhlcmUKYXJlICLDqiIsICLDqSIgYW5kICLHkiIgLCB0aG91Z2guCgp0aHVuZGVy
dwoKMjAwNi8zLzgsIOeOi+a0qumbtyA8dGh1bmRlcndAZ21haWwuY29tPjoKPiBUaGVyZSBhcmUg
bmFtZXMgbGlrZSAiSsOpcsO0bWUgQXVnw6kiLgo+IEkgdGhpbmsgdGhlcmUgaXMgbm8gd2F5IGV4
Y2VwdCB0byBjb252ZXJ0IHRoZXNlIG5hbWVzIGludG8gdHdvLWJ5dGUKPiBjaGFyYWN0ZXIgYnkg
aGFuZC4KPiBPciB3ZSBoYXZlIHRvIGFjY2VwdCB1dGY4IGVuY29kaW5nLgo+IFdlIGhhdmUgdG8g
c2hvdyBvdXIgcmVzcGVjdCB0byB0aGVzZSBwZW9wbGUsIGRvbid0IHdlPwo+Cj4gMjAwNi8zLzgs
IFdlbnpoaSBMaWFuZyA8d2VuemhpLmxpYW5nQGdtYWlsLmNvbT46Cj4gPiBIZWxsbyBhbGwsCj4g
Pgo+ID4gSSBhbSBoYXZpbmcgc29tZSBwcm9ibGVtIHdpdGggdGhlIG5ldyBmaWxlcyBXaWxsaXMg
Y2hlY2tlZCBpbi4gV2hlbiBJIGRvCj4gPiAnaWNvbnYgLWYgdXRmLTggLXQgZXVjLWNuJyBvbiBz
b21lIG9mIHRoZW0sIGl0IGZhaWxlZC4gSSBmaXhlZCBvbmUgZmlsZSBidXQgdGhlCj4gPiBvdGhl
ciBmaWxlcyBzZWVtcyB0byBpbmNsdWRlIHRoZSBzby1jYWxsZWQgJ2RpZ3JhcGgnIGxpa2UgJ8Oh
Jy4gaWNvbnYgY291bGRuJ3QKPiA+IGNvbnZlcnQgdGhlbS4KPiA+Cj4gPiB3YW5keXMsICBJIHJl
bWVtYmVyIHdlIGhhZCB0aGlzIHByb2JsZW0gYmVmb3JlIGFuZCB5b3UgZml4ZWQgaXQuIElmIHlv
dQo+ID4gYXJlIHN0aWxsIGFyb3VuZCwgY2FuIHlvdSB0YWtlIGEgbG9vayBhdCB0aGlzPwo+ID4K
PiA+IFRoZXJlIGlzIGEgd29yayBhcm91bmQgZm9yIHRoaXM6IGFkZCAnZW5jPXV0Zi04JyB0byB0
aGUgc3RhdHVzIGxpbmUuIEJ1dCBpdAo+ID4gaXMgbm90IHJlY29tbWVuZGVkLgo+ID4KPiA+IEFu
eSBpbnB1dCBhcHByZWNpYXRlZC4KPiA+Cj4gPiBPaC4gVGhlIGxpc3Qgb2YgcHJvYmxvbWF0aWMg
ZmlsZXM6Cj4gPiB1c3JfMjQKPiA+IGluZGV4LnR4dAo+ID4gdmFyaW91cy50eHQKPiA+IHBhdHRl
cm4udHh0Cj4gPiBkaWdyYXBoCj4gPiBtYnl0ZS50eHQKPiA+IGFyYWJpYy50eHQKPiA+IGZhcnNp
LnR4dAo+ID4gaGVicmV3LnR4dAo+ID4gcGlfbmV0cncudHh0Cj4gPgo+ID4KPiA+IHRoYW5rcyAs
Cj4gPgo+ID4KPiA+IGxhbmcyCj4gPgo+ID4KPiA+IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0KPiA+IFRoaXMgU0YuTmV0IGVtYWlsIGlzIHNw
b25zb3JlZCBieSB4UE1MLCBhIGdyb3VuZGJyZWFraW5nIHNjcmlwdGluZyBsYW5ndWFnZQo+ID4g
dGhhdCBleHRlbmRzIGFwcGxpY2F0aW9ucyBpbnRvIHdlYiBhbmQgbW9iaWxlIG1lZGlhLiBBdHRl
bmQgdGhlIGxpdmUgd2ViY2FzdAo+ID4gYW5kIGpvaW4gdGhlIHByaW1lIGRldmVsb3BlciBncm91
cCBicmVha2luZyBpbnRvIHRoaXMgbmV3IGNvZGluZyB0ZXJyaXRvcnkhCj4gPiBodHRwOi8vc2Vs
LmFzLXVzLmZhbGthZy5uZXQvc2VsP2NtZGxuayZraWQRMDk0NCZiaWQkMTcyMCZkYXQSMTY0Mgo+
ID4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KPiA+IFZp
bWNkb2MtdHJhbnNsYXRlIG1haWxpbmcgbGlzdAo+ID4gVmltY2RvYy10cmFuc2xhdGVAbGlzdHMu
c291cmNlZm9yZ2UubmV0Cj4gPiBodHRwczovL2xpc3RzLnNvdXJjZWZvcmdlLm5ldC9saXN0cy9s
aXN0aW5mby92aW1jZG9jLXRyYW5zbGF0ZQo+ID4KPgo+Cj4gLS0KPiBXYW5nIEhvbmdsZWkKPiB0
aHVuZGVyd0BnbWFpbC5jb20KPiBodHRwOi8vd3d3LmN1bXQub3JnLwo+CgoKLS0KV2FuZyBIb25n
bGVpCnRodW5kZXJ3QGdtYWlsLmNvbQpodHRwOi8vd3d3LmN1bXQub3JnLwo=

Re: [Vimcdoc-translate] help with iconv

[<thu...@gm...>]

There are names like "J=E9r=F4me Aug=E9".
I think there is no way except to convert these names into two-byte
character by hand.
Or we have to accept utf8 encoding.
We have to show our respect to these people, don't we?

2006/3/8, Wenzhi Liang <wen...@gm...>:
> Hello all,
>
> I am having some problem with the new files Willis checked in. When I do
> 'iconv -f utf-8 -t euc-cn' on some of them, it failed. I fixed one file b=
ut the
> other files seems to include the so-called 'digraph' like '=E1'. iconv co=
uldn't
> convert them.
>
> wandys,  I remember we had this problem before and you fixed it. If you
> are still around, can you take a look at this?
>
> There is a work around for this: add 'enc=3Dutf-8' to the status line. Bu=
t it
> is not recommended.
>
> Any input appreciated.
>
> Oh. The list of problomatic files:
> usr_24
> index.txt
> various.txt
> pattern.txt
> digraph
> mbyte.txt
> arabic.txt
> farsi.txt
> hebrew.txt
> pi_netrw.txt
>
>
> thanks ,
>
>
> lang2
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting langua=
ge
> that extends applications into web and mobile media. Attend the live webc=
ast
> and join the prime developer group breaking into this new coding territor=
y!
> 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
>


--
Wang Honglei
thu...@gm...
http://www.cumt.org/

[Vimcdoc-translate] help with iconv

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

Hello all,

I am having some problem with the new files Willis checked in. When I do
'iconv -f utf-8 -t euc-cn' on some of them, it failed. I fixed one file but=
 the
other files seems to include the so-called 'digraph' like '=E1'. iconv coul=
dn't
convert them.

wandys,  I remember we had this problem before and you fixed it. If you
are still around, can you take a look at this?

There is a work around for this: add 'enc=3Dutf-8' to the status line. But =
it
is not recommended.

Any input appreciated.

Oh. The list of problomatic files:
usr_24
index.txt
various.txt
pattern.txt
digraph
mbyte.txt
arabic.txt
farsi.txt
hebrew.txt
pi_netrw.txt


thanks ,


lang2

[Vimcdoc-translate] Re: contribute to vimcdoc

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

Hello Willis,

Yes I've seen those commits. It is amazing the amount of work you put in.
Thanks again.  I will review where the project is after this major contribu=
tion.
I never thought we'd make it all the way to 1.0 release (which I remember
defining it as all the documents translated). But it looks like we are gett=
ing
very close to it, thanks to you. ;-) In a way I feel guilty as I hadn't put=
 much
effort into it lately but it is still very exciting.

Regards,

ps. Can you subscribe to the project mailing list?


On 01/03/06, Yi-an Huang <yia...@gm...> wrote:
> Just to let you know that my changes have been uploaded on CVS today.
>
> On 2/28/06, Wenzhi Liang <wen...@gm... > wrote:
> > Hello there,
> >
> > That is great! I've added you to the developer list on sourceforge. I
> > will take a look
> > at the syntax file you attached when I get home. But may I suggest you
> read the
> > guides.txt from CVS (you might have done that already, in which case,
> please
> > ignore me).
> >
> > Rgds,
> >
> > lang2
> >
> > On 28/02/06, Yi-an Huang <yia...@gm...> wrote:
> > > Hi,
> > >
> > > Greetings!
> > >
> > > Thank you very much for your hard work on the Vim Chinese Documentati=
on
> > > Project, as well as other members.
> > >
> > > I would like to contribute some of my work to this project. I wonder =
how
> I
> > > can be added to the developer list so that I can submit my work on cv=
s.
> My
> > > sourceforge id is yianwillis.
> > >
> > > Here is a list of work that I have completed. Attached is one of the =
new
> > > translations, please examine whether the format is compliant with you=
r
> > > requirement.
> > >
> > > Files that include minor to moderate changes from CVS head (18):
> > >
> > > debugger.txt
> > > diff.txt
> > > fold.txt
> > > help.txt
> > > map.txt
> > > pattern.txt
> > > quickfix.txt
> > > quickref.txt
> > > undo.txt
> > > usr_24.txt
> > > if_cscop.txt
> > > if_perl.txt
> > > if_pyth.txt
> > > os_mac.txt
> > > tips.txt
> > > uganda.txt
> > > usr_05.txt
> > > usr_22.txt
> > >
> > > Files that have been completely rewritten (3):
> > >
> > > autocmd.txt
> > > filetype.txt
> > > mbyte.txt
> > >
> > > Files that are newly added (42):
> > >
> > > arabic.txt
> > > change.txt
> > > digraph.txt
> > >  editing.txt
> > > farsi.txt
> > > gui.txt
> > > hangulin.txt
> > > hebrew.txt
> > > if_ruby.txt
> > > if_sniff.txt
> > > if_tcl.txt
> > > index.txt
> > > insert.txt
> > > message.txt
> > > motion.txt
> > > netbeans.txt
> > > os_390.txt
> > > os_amiga.txt
> > > os_beos.txt
> > > os_os2.txt
> > > os_qnx.txt
> > > os_risc.txt
> > > os_vms.txt
> > > pi_expl.txt
> > > pi_netrw.txt
> > > pi_spec.txt
> > > quotes.txt
> > > remote.txt
> > > repeat.txt
> > > rileft.txt
> > > russian.txt
> > > sign.txt
> > > starting.txt
> > > syntax.txt
> > > tagsrch.txt
> > > term.txt
> > > todo.txt
> > > uganda.nsis.txt
> > > various.txt
> > > version4.txt
> > > vi_diff.txt
> > > workshop.txt
> > >
> > > -Willis
> > >
> > >
> >
>
>

Re: [Vimcdoc-translate] Re: contribute to vimcdoc

[James H. <ic...@gm...>]

Welcome on board, Yi-an Huang! :-)

On 2/28/06, Wenzhi Liang <wen...@gm...> wrote:
> Hello there,
>
> That is great! I've added you to the developer list on sourceforge. I
> will take a look
> at the syntax file you attached when I get home. But may I suggest you re=
ad the
> guides.txt from CVS (you might have done that already, in which case, ple=
ase
> ignore me).

--
Best regards,

James He

[Vimcdoc-translate] Re: contribute to vimcdoc

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

Hello there,

That is great! I've added you to the developer list on sourceforge. I
will take a look
at the syntax file you attached when I get home. But may I suggest you read=
 the
guides.txt from CVS (you might have done that already, in which case, pleas=
e
ignore me).

Rgds,

lang2

On 28/02/06, Yi-an Huang <yia...@gm...> wrote:
> Hi,
>
> Greetings!
>
> Thank you very much for your hard work on the Vim Chinese Documentation
> Project, as well as other members.
>
> I would like to contribute some of my work to this project. I wonder how =
I
> can be added to the developer list so that I can submit my work on cvs. M=
y
> sourceforge id is yianwillis.
>
> Here is a list of work that I have completed. Attached is one of the new
> translations, please examine whether the format is compliant with your
> requirement.
>
> Files that include minor to moderate changes from CVS head (18):
>
> debugger.txt
> diff.txt
> fold.txt
> help.txt
> map.txt
> pattern.txt
> quickfix.txt
> quickref.txt
> undo.txt
> usr_24.txt
> if_cscop.txt
> if_perl.txt
> if_pyth.txt
> os_mac.txt
> tips.txt
> uganda.txt
> usr_05.txt
> usr_22.txt
>
> Files that have been completely rewritten (3):
>
> autocmd.txt
> filetype.txt
> mbyte.txt
>
> Files that are newly added (42):
>
> arabic.txt
> change.txt
> digraph.txt
>  editing.txt
> farsi.txt
> gui.txt
> hangulin.txt
> hebrew.txt
> if_ruby.txt
> if_sniff.txt
> if_tcl.txt
> index.txt
> insert.txt
> message.txt
> motion.txt
> netbeans.txt
> os_390.txt
> os_amiga.txt
> os_beos.txt
> os_os2.txt
> os_qnx.txt
> os_risc.txt
> os_vms.txt
> pi_expl.txt
> pi_netrw.txt
> pi_spec.txt
> quotes.txt
> remote.txt
> repeat.txt
> rileft.txt
> russian.txt
> sign.txt
> starting.txt
> syntax.txt
> tagsrch.txt
> term.txt
> todo.txt
> uganda.nsis.txt
> various.txt
> version4.txt
> vi_diff.txt
> workshop.txt
>
> -Willis
>
>

Re: [Vimcdoc-translate] cmdline.txt finished

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

Thanks Dasn,

It is a quite interesting piece. Will find time to review it. Realistically
in the new year.

lang2

On 02/12/05, Thunder White <thu...@gm...> wrote:
> i.c.
> There is a ^M at the end of every line.
>
> "%s/^M//" will fix this.
>
> On 12/2/05, Thunder White <thu...@gm...> wrote:
> > When I open it, the following error message is shown:
> > <\vimcdoc\doc\cmdline.txt" [converted] 871L, 32120C
> > Error detected while processing modelines:
> > line  871:
> > E518: Unknown option: ^M
> >
> > I am using vim 6.4 on windows. No error on other files.
> > On 12/2/05, cl...@fa... <cl...@fa...> wrote:
> > > cmdline.txt's done. Still not sure about everything.
> > > Please check and help review.
> > >
> > > -Dasn
> > >
> > >
> > > -------------------------------------------------------
> > > This SF.net email is sponsored by: Splunk Inc. Do you grep through lo=
g files
> > > for problems?  Stop!  Download the new AJAX search engine that makes
> > > searching your log files as easy as surfing the  web.  DOWNLOAD SPLUN=
K!
> > > http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick
> > > _______________________________________________
> > > Vimcdoc-translate mailing list
> > > Vim...@li...
> > > https://lists.sourceforge.net/lists/listinfo/vimcdoc-translate
> > >
> >
> >
> > --
> > http://www.cumt.org/
> >
>
>
> --
> http://www.cumt.org/
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log fi=
les
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_idv37&alloc_id=16865&opclick
> _______________________________________________
> Vimcdoc-translate mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vimcdoc-translate
>

Re: [Vimcdoc-translate] cmdline.txt finished

[Thunder W. <thu...@gm...>]

i.c.
There is a ^M at the end of every line.

"%s/^M//" will fix this.

On 12/2/05, Thunder White <thu...@gm...> wrote:
> When I open it, the following error message is shown:
> <\vimcdoc\doc\cmdline.txt" [converted] 871L, 32120C
> Error detected while processing modelines:
> line  871:
> E518: Unknown option: ^M
>
> I am using vim 6.4 on windows. No error on other files.
> On 12/2/05, cl...@fa... <cl...@fa...> wrote:
> > cmdline.txt's done. Still not sure about everything.
> > Please check and help review.
> >
> > -Dasn
> >
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc. Do you grep through log =
files
> > for problems?  Stop!  Download the new AJAX search engine that makes
> > searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> > http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick
> > _______________________________________________
> > Vimcdoc-translate mailing list
> > Vim...@li...
> > https://lists.sourceforge.net/lists/listinfo/vimcdoc-translate
> >
>
>
> --
> http://www.cumt.org/
>


--
http://www.cumt.org/

Re: [Vimcdoc-translate] cmdline.txt finished

[Thunder W. <thu...@gm...>]

When I open it, the following error message is shown:
<\vimcdoc\doc\cmdline.txt" [converted] 871L, 32120C
Error detected while processing modelines:
line  871:
E518: Unknown option: ^M

I am using vim 6.4 on windows. No error on other files.
On 12/2/05, cl...@fa... <cl...@fa...> wrote:
> cmdline.txt's done. Still not sure about everything.
> Please check and help review.
>
> -Dasn
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log fi=
les
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick
> _______________________________________________
> Vimcdoc-translate mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vimcdoc-translate
>


--
http://www.cumt.org/

[Vimcdoc-translate] cmdline.txt finished

[<cl...@fa...>]

cmdline.txt's done. Still not sure about everything.
Please check and help review.

-Dasn

Re: [Vimcdoc-translate] Fwd: a suggest for vim help doc

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

0LvQu8TjtcS72Li0o6EKCnZpbcrHuPa6w7arzvejrLrHusejrNOmuMO088Gmzca54woKxOPDx7XE
uaTX99XmtcTKx7rc1tjSqqOs0ru2qLvhttS63LbgyMvT0LrctPO1xLDv1vqhowoK09DBvbj20KG9
qNLpo7oKMS4g0vLOqtPQtcRoZWxwwO88VGFiPtPDtcTKx7/Y1sbX1rf7XkmjrMv50tS+zbTm1Nq2
1MbrzsrM4gogIMjnufu/ycTctcS7sNPDv9W48bbUxuu4/LrDo6zV4tH5vs2yu7vhs/bP1tLyzqrJ
6NbDsrvNrLbUxuvH6b/2srvNrMHLCgoyLiBtb3Rpb24udHh0yse49tbY0qq1xLDv1vqjrM+jzfvU
58jVzeqzyaGjCgq3x7OjuNDQu8Tjw8e1xM7ey7237s/Xo6zSu9axz+vOqnZpbbXExtW8sLmk1/fX
9tCpysLH6aOs0rK/vMLHvNPI67W9xOPDxwq1xLbTzunW0Milo6y/ycrH0vLOqrmk1/fBy6Os1NPK
wrHIvc+24KOsw7vT0LPJ0M6howoKxOPDx8Tc1NpodHRwOi8vdmltY2RvYy5zb3VyY2Vmb3JnZS5u
ZXQvwdCz9rWxx7C1xHN0YXR1c8Lwo7/V4tH5sfDIy7/J0tQKwcu94sO/uPbOxLz+tPO4xbXEvfi2
yKOsv7S/tMrHt/HKyrrPvNPI66Gju/LV387Sv8nS1M2ouf1DVlOy6b+0zsS8/rXEt60K0uu9+LbI
o7/E48PHzai5/U5ld3MgUlNTwLS3orK80MXPoqO/CgrQwb/gwcujoQoK1Nm0ztbCvrSjoQo=

Re: [Vimcdoc-translate] Fwd: a suggest for vim help doc

[James He <ic...@gm...>]

No "-Show quoted text-" link for that post. :-(
Please see the attachment.

On 11/25/05, Wenzhi Liang <wen...@gm...> wrote:
> Press the "-Show quoted text-" link. They are light blue ;-)

--
Best regards,

James He

Re: [Vimcdoc-translate] Fwd: a suggest for vim help doc

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

Press the "-Show quoted text-" link. They are light blue ;-)

On 25/11/05, James He <ic...@gm...> wrote:
> Is the content of your last email empty?
> I can see nothing in my gmail account. :-(
>
> On 11/25/05, Wenzhi Liang <wen...@gm...> wrote:
> >
>
>
> --
> Best regards,
>
> James He
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log fi=
les
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_idv37&alloc_id=16865&opclick
> _______________________________________________
> Vimcdoc-translate mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vimcdoc-translate
>

Re: [Vimcdoc-translate] Fwd: a suggest for vim help doc

[James He <ic...@gm...>]

Is the content of your last email empty?
I can see nothing in my gmail account. :-(

On 11/25/05, Wenzhi Liang <wen...@gm...> wrote:
>


--
Best regards,

James He

[Vimcdoc-translate] Fwd: a suggest for vim help doc

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

LS0tLS0tLS0tLSBGb3J3YXJkZWQgbWVzc2FnZSAtLS0tLS0tLS0tCkZyb206IHpodW05OSA8emh1
bTk5QG1haWxzLnRzaW5naHVhLmVkdS5jbj4KRGF0ZTogMjUtTm92LTIwMDUgMDE6MzIKU3ViamVj
dDogUmU6IGEgc3VnZ2VzdCBmb3IgdmltIGhlbHAgZG9jClRvOiBXZW56aGkgTGlhbmcgPHdlbnpo
aS5saWFuZ0BnbWFpbC5jb20+CgoKCtC70LvE47XEu9i4tKOhCgp2aW3Kx7j2usO2q873o6y6x7rH
o6zTprjDtPPBps3GueMKCsTjw8e1xLmk1/fV5rXEyse63NbY0qqjrNK7tqi74bbUuty24MjL09C6
3LTztcSw79b6oaMKCtPQwb249tChvajS6aO6CjEuINLyzqrT0LXEaGVscMDvPFRhYj7Tw7XEyse/
2NbG19a3+15Jo6zL+dLUvs205tTattTG687KzOIKICAgyOe5+7/JxNy1xLuw08O/1bjxttTG67j8
usOjrNXi0fm+zbK7u+Gz9s/W0vLOqsno1sOyu82sttTG68fpv/ayu82swcsKCjIuIG1vdGlvbi50
eHTKx7j21tjSqrXEsO/W+qOsz6PN+9TnyNXN6rPJoaMKCrfHs6O40NC7xOPDx7XEzt7Lvbfuz9ej
rNK71rHP686qdmlttcTG1bywuaTX99f20KnKwsfpo6zSsr+8wse808jrtb3E48PHCrXEttPO6dbQ
yKWjrL/JysfS8s6quaTX98HLo6zU08rCsci9z7bgo6zDu9PQs8nQzqGjCgrE48PHxNzU2mh0dHA6
Ly92aW1jZG9jLnNvdXJjZWZvcmdlLm5ldC/B0LP2tbHHsLXEc3RhdHVzwvCjv9Xi0fmx8MjLv8nS
1ArBy73iw7+49s7EvP6087jFtcS9+LbIo6y/tL+0yse38crKus+808jroaO78tXfztK/ydLUzai5
/UNWU7Lpv7TOxLz+tcS3rQrS6734tsijv8Tjw8fNqLn9TmV3cyBSU1PAtLeisrzQxc+io78KCtDB
v+DBy6OhCgrU2bTO1sK+tKOhCgpPbiBUaHUsIDI0IE5vdiAyMDA1IDEwOjI5OjQ3ICswMDAwCldl
bnpoaSBMaWFuZyA8d2VuemhpLmxpYW5nQGdtYWlsLmNvbT4gd3JvdGU6Cgo+IEhlbGxvIHRoZXJl
LAo+Cj4gT24gMjEvMTEvMDUsIHpodW05OSA8emh1bTk5QG1haWxzLnRzaW5naHVhLmVkdS5jbj4g
d3JvdGU6Cj4gPgo+ID4gICAgICAgICBGaXJzdCBwbGVhc2UgYWxsb3cgbWUgdG8gc2hvdyBteSBn
cmVhdCBhcHByZWNpYXRpb24gZm9yIHlvdXIKPiA+IGV4Y2VsbGVudCB3b3JrIQo+Cj4gR2xhZCB5
b3UgbGlrZWQgaXQuCj4KPiA+Cj4gPiAgICAgICAgIFdoZW4gSSByZWFkIHRoZSBDaGluZXNlIGhl
bHAsIEkgZm91bmQgc29tZSBzcGVjaWFsIGNoYXJzICggaXQgc2hvdWxkCj4gPiBiZSAiIG9yICKj
qMur0v26xaOpIGluIENoaW5lc2UgZm9udCBjaGFyYWN0ZXIsIGFuZCBpdCBjYW4gbm90IGJlCj4g
PiBzaG93biBjb3JyZWN0bHkgaW4gRW5nbGlzaCB2ZXJzaW9uIHdpbmRvd3Mgd2l0aCBDaGluZXNl
IGZvbnQpLgo+ID4KPiA+ICAgICAgICAgQ2FuIHlvdSB1c2UgIiB0byBpbnN0ZWFkIG9mICIgKMur
0v26xSkgYW5kICIgPwo+IEkndmUgZGlzY3Vzc2VkIHdpdGggdGhlIHRlYW0uIFdlIGFncmVlZCB0
aGlzIHRpbWUgKHdlIGhhZCBhIGRlYmF0ZSBhYm91dAo+IHRoaXMgcHJldmlvdXNseSBhbmQgc2V0
dGxlZCBmb3IgQ2hpbmVzZSBvbmVzKSB0byB1c2UgRW5nbGlzaCB2ZXJzaW9uLiBTbyB5ZXMsCj4g
dGhlIGNoYW5nZSB5b3Ugd2FudCBpcyBpbiBDVlMuIEVpdGhlciBncmFiIGl0IG9yIHdhaXQgZm9y
IGFub3RoZXIgcmVsZWFzZS4KPgo+IFRoYW5rcyBmb3IgdGhlIGZlZWRiYWNrLiBJZiB5b3UgaGF2
ZSBhbnkgb3RoZXIgZW5xdWlyeSwgcGxlYXNlIGRvIGxldCBtZQo+IGtub3cuCj4KPgo+IGxhbmcy
CgotLQogPD4K

Re: [Vimcdoc-translate] Re: Re: Fwd: a suggest for vim help doc

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

On 24/11/05, Alecs King <al...@pe...> wrote:
> On Wed, Nov 23, 2005 at 09:33:34AM +0000, Wenzhi Liang wrote:
> > OK. I seems like nobody is against it this time. :-) We'll do it then.
> > I think it is cleaner and easier for pattern matching anyway. So wandys=
,
> > maybe you can take on this task? ;-)
>
> Sure, my pleasure :^)

Thanks wandys.

>
> Files committed to our CVS.  Please check if there are any problems.
> data/guides.txt updated accordingly.
>
> --
> Alecs King
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log fi=
les
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick
> _______________________________________________
> Vimcdoc-translate mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vimcdoc-translate
>

[Vimcdoc-translate] Re: Re: Fwd: a suggest for vim help doc

[Alecs K. <al...@pe...>]

On Wed, Nov 23, 2005 at 09:33:34AM +0000, Wenzhi Liang wrote:
> OK. I seems like nobody is against it this time. :-) We'll do it then.
> I think it is cleaner and easier for pattern matching anyway. So wandys,
> maybe you can take on this task? ;-)

Sure, my pleasure :^) 

Files committed to our CVS.  Please check if there are any problems. 
data/guides.txt updated accordingly.

-- 
Alecs King

Re: [Vimcdoc-translate] Re: Fwd: a suggest for vim help doc

[James He <ic...@gm...>]

Actually, I prefer the English ones. :-)

On 11/22/05, Wenzhi Liang <wen...@gm...> wrote:
> Anybody has a *strong* opinion for not using English ones? If nobody
> has, I think we'll just do it and change the guides.txt accordingly.

--
Best regards,

James He

Re: [Vimcdoc-translate] Re: Fwd: a suggest for vim help doc

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

OK. I seems like nobody is against it this time. :-) We'll do it then.
I think it is cleaner and easier for pattern matching anyway. So wandys,
maybe you can take on this task? ;-)

Thanks,

On 22/11/05, Wenzhi Liang <wen...@gm...> wrote:
> Anybody has a *strong* opinion for not using English ones? If nobody
> has, I think we'll just do it and change the guides.txt accordingly.
>
> On 22/11/05, Alecs King <al...@gm...> wrote:
> > On Mon, Nov 21, 2005 at 06:25:15PM +0000, Wenzhi Liang wrote:
> > > Hi all,
> > >
> > > I got a mail from a vimcdoc user basically complaining about the
> > > usage of Chinese quotation mark in the translated text. I remember
> > > in the beginning I was against using Chinese quoatation mark
> > > myself but got convinced by somebody. Anyways, the guides.txt
> > > says to use them. Does anyone still having this problem or similiar
> > > ones?
> >
> > I dunno why Chinese quotations would hurt (that user).  Vim can display
> > other Chinese characters but why cant it display Chinese quotations?  I
> > suspect there might be some configuration problems.
> >
> > However i myself always use English quotes in the doc.  And i think it'=
s
> > better if we have an unified standard WRT punctuations.
> >
> > FYI, following is a list of files containing Chinese quotations.  If
> > necessary, we can replace them with English ones easily with a perl
> > script.
> >
> >  cmdline.txt
> >  develop.txt
> >  gui_w16.txt
> >  gui_w32.txt
> >  if_ole.txt
> >  if_perl.txt
> >  intro.txt
> >  os_dos.txt
> >  os_mac.txt
> >  os_msdos.txt
> >  os_win32.txt
> >  recover.txt
> >  scroll.txt
> >  sponsor.txt
> >  tips.txt
> >  uganda.txt
> >  usr_02.txt
> >  usr_03.txt
> >  windows.txt
> >
> > That user said the double Chinese quotations are the cause of the
> > problem.  Just in case single Chinese quotations are also 'evil':
> >
> >  gui_w32.txt
> >  if_perl.txt
> >  os_win32.txt
> >  windows.txt
> >
> > --
> > Alecs King
> >
> >
> > -------------------------------------------------------
> > This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
> > Register for a JBoss Training Course.  Free Certification Exam
> > for All Training Attendees Through End of 2005. For more info visit:
> > http://ads.osdn.com/?ad_id=3D7628&alloc_id=3D16845&op=3Dclick
> > _______________________________________________
> > Vimcdoc-translate mailing list
> > Vim...@li...
> > https://lists.sourceforge.net/lists/listinfo/vimcdoc-translate
> >
>

Re: [Vimcdoc-translate] Re: Fwd: a suggest for vim help doc

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

Anybody has a *strong* opinion for not using English ones? If nobody
has, I think we'll just do it and change the guides.txt accordingly.

On 22/11/05, Alecs King <al...@gm...> wrote:
> On Mon, Nov 21, 2005 at 06:25:15PM +0000, Wenzhi Liang wrote:
> > Hi all,
> >
> > I got a mail from a vimcdoc user basically complaining about the
> > usage of Chinese quotation mark in the translated text. I remember
> > in the beginning I was against using Chinese quoatation mark
> > myself but got convinced by somebody. Anyways, the guides.txt
> > says to use them. Does anyone still having this problem or similiar
> > ones?
>
> I dunno why Chinese quotations would hurt (that user).  Vim can display
> other Chinese characters but why cant it display Chinese quotations?  I
> suspect there might be some configuration problems.
>
> However i myself always use English quotes in the doc.  And i think it's
> better if we have an unified standard WRT punctuations.
>
> FYI, following is a list of files containing Chinese quotations.  If
> necessary, we can replace them with English ones easily with a perl
> script.
>
>  cmdline.txt
>  develop.txt
>  gui_w16.txt
>  gui_w32.txt
>  if_ole.txt
>  if_perl.txt
>  intro.txt
>  os_dos.txt
>  os_mac.txt
>  os_msdos.txt
>  os_win32.txt
>  recover.txt
>  scroll.txt
>  sponsor.txt
>  tips.txt
>  uganda.txt
>  usr_02.txt
>  usr_03.txt
>  windows.txt
>
> That user said the double Chinese quotations are the cause of the
> problem.  Just in case single Chinese quotations are also 'evil':
>
>  gui_w32.txt
>  if_perl.txt
>  os_win32.txt
>  windows.txt
>
> --
> Alecs King
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
> Register for a JBoss Training Course.  Free Certification Exam
> for All Training Attendees Through End of 2005. For more info visit:
> http://ads.osdn.com/?ad_id=3D7628&alloc_id=3D16845&op=3Dclick
> _______________________________________________
> Vimcdoc-translate mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vimcdoc-translate
>

[Vimcdoc-translate] Re: Fwd: a suggest for vim help doc

[Alecs K. <al...@gm...>]

On Mon, Nov 21, 2005 at 06:25:15PM +0000, Wenzhi Liang wrote:
> Hi all,
> 
> I got a mail from a vimcdoc user basically complaining about the
> usage of Chinese quotation mark in the translated text. I remember
> in the beginning I was against using Chinese quoatation mark
> myself but got convinced by somebody. Anyways, the guides.txt
> says to use them. Does anyone still having this problem or similiar
> ones?

I dunno why Chinese quotations would hurt (that user).  Vim can display
other Chinese characters but why cant it display Chinese quotations?  I
suspect there might be some configuration problems.

However i myself always use English quotes in the doc.  And i think it's
better if we have an unified standard WRT punctuations. 

FYI, following is a list of files containing Chinese quotations.  If
necessary, we can replace them with English ones easily with a perl
script.  

 cmdline.txt
 develop.txt
 gui_w16.txt
 gui_w32.txt
 if_ole.txt
 if_perl.txt
 intro.txt
 os_dos.txt
 os_mac.txt
 os_msdos.txt
 os_win32.txt
 recover.txt
 scroll.txt
 sponsor.txt
 tips.txt
 uganda.txt
 usr_02.txt
 usr_03.txt
 windows.txt

That user said the double Chinese quotations are the cause of the
problem.  Just in case single Chinese quotations are also 'evil':

 gui_w32.txt
 if_perl.txt
 os_win32.txt
 windows.txt

-- 
Alecs King