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: Alecs K. <al...@gm...> - 2005-11-22 07:35:11
|
On Sun, Nov 20, 2005 at 04:26:49AM -0500, James He wrote: > [snip] > Should we add this guide line to data/guides.txt? :-) Hmm. They are mainly already put in the guides.txt (Comp. Rule 8). I think many ppl have their own custom enc/fenc/fencs settings. :set fencs=utf8 almost hurts no one but better leave that to ppl themselves. -- Alecs King |
|
From: Wenzhi L. <wen...@gm...> - 2005-11-21 18:25:21
|
SGkgYWxsLAoKSSBnb3QgYSBtYWlsIGZyb20gYSB2aW1jZG9jIHVzZXIgYmFzaWNhbGx5IGNvbXBs YWluaW5nIGFib3V0IHRoZQp1c2FnZSBvZiBDaGluZXNlIHF1b3RhdGlvbiBtYXJrIGluIHRoZSB0 cmFuc2xhdGVkIHRleHQuIEkgcmVtZW1iZXIKaW4gdGhlIGJlZ2lubmluZyBJIHdhcyBhZ2FpbnN0 IHVzaW5nIENoaW5lc2UgcXVvYXRhdGlvbiBtYXJrCm15c2VsZiBidXQgZ290IGNvbnZpbmNlZCBi eSBzb21lYm9keS4gQW55d2F5cywgdGhlIGd1aWRlcy50eHQKc2F5cyB0byB1c2UgdGhlbS4gRG9l cyBhbnlvbmUgc3RpbGwgaGF2aW5nIHRoaXMgcHJvYmxlbSBvciBzaW1pbGlhcgpvbmVzPwoKLS0t LS0tLS0tLSBGb3J3YXJkZWQgbWVzc2FnZSAtLS0tLS0tLS0tCkZyb206IHpodW05OSA8emh1bTk5 QG1haWxzLnRzaW5naHVhLmVkdS5jbj4KRGF0ZTogMjEtTm92LTIwMDUgMDQ6NDEKU3ViamVjdDog YSBzdWdnZXN0IGZvciB2aW0gaGVscCBkb2MKVG86ICJsYW5nMiBAIHVzZXJzLiBzb3VyY2Vmb3Jn ZS4gbmV0IiA8bGFuZzJAdXNlcnMuc291cmNlZm9yZ2UubmV0PgoKCgogICAgICAgIEZpcnN0IHBs ZWFzZSBhbGxvdyBtZSB0byBzaG93IG15IGdyZWF0IGFwcHJlY2lhdGlvbiBmb3IgeW91cgpleGNl bGxlbnQgd29yayEKCiAgICAgICAgV2hlbiBJIHJlYWQgdGhlIENoaW5lc2UgaGVscCwgSSBmb3Vu ZCBzb21lIHNwZWNpYWwgY2hhcnMgKCBpdCBzaG91bGQKYmUgIiBvciAio6jLq9L9usWjqSBpbiBD aGluZXNlIGZvbnQgY2hhcmFjdGVyLCBhbmQgaXQgY2FuIG5vdCBiZQpzaG93biBjb3JyZWN0bHkg aW4gRW5nbGlzaCB2ZXJzaW9uIHdpbmRvd3Mgd2l0aCBDaGluZXNlIGZvbnQpLgoKICAgICAgICBD YW4geW91IHVzZSAiIHRvIGluc3RlYWQgb2YgIiAoy6vS/brFKSBhbmQgIiA/CgogICAgICAgIFRo YW5rcy4KCgotLQpraW5kZ3Jhc3MgPGtpbmRncmFzc0AxNjMuY29tPgotLQogPD4K |
|
From: James He <ic...@gm...> - 2005-11-20 09:27:06
|
On 11/20/05, Alecs King <al...@pe...> wrote: > This means we translators have to > 1) edit our file utf-8 native. we dont manually do any conversion > whatsoever. > 2) make sure the utf8-encoded file _can_ be successfully converted to > gb2312, since gb2312 is the very subset. > > I think fileencodings=3Dutf8 is the rite way to go. FYI, it does not > treat _all_ files as utf-8. It just treats utf8 (which includes ascii) > files as utf8. > > Well, this only ensures the condition 1) above. If you write some 'evil' > characters, the file still cannot be converted to gb2312. > > I wonder if there are similar tools on Windoze like this: > $ iconv -f utf-8 -t euc-cn file > /dev/null > which can help you check the validity. Should we add this guide line to data/guides.txt? :-) -- Best regards, James He |
|
From: Alecs K. <al...@pe...> - 2005-11-20 06:38:03
|
On Sat, Nov 19, 2005 at 05:23:34AM +0800, Dasn wrote: > Hi, list! > I just found this thread via Web and was sorry for coming back that > late. Welcome back. > 'fileencoding' option is null. The most tricky stuff comes when you edit > the files with "notepad.exe", all things look fine in Notepad, then I > "save as..." the file in UTF-8 format. Open it again with gvim, now, Vim > can recognize the file encoding and auto convert to cp936. The files I > had commited were formated like this. Yeah, this indeed causes the problem. utf8->cp936->utf8. As we have discussed in this thread, cp936 is in fact gbk, which sometimes is not friendly to our enc-cn (aka gb2312) users when your file contains a gbk-only character that does not exist in the gb2312 encoding. We want our vimcdoc as much encoding-independent as possible. Users can use euc-cn/gb2312, gbk/cp936, utf8 and they dont have to know about the underlying conversion that Vim itself has done when displaying the help file. We make this transparent to users and they dont have to bother doing any conversion themselves. They just :help and see. This means we translators have to 1) edit our file utf-8 native. we dont manually do any conversion whatsoever. 2) make sure the utf8-encoded file _can_ be successfully converted to gb2312, since gb2312 is the very subset. > Recently, I have to use "fileencodings=utf8" in _vimrc to force Vim to > treat all kinds of files as UTF-8 encoding. I think fileencodings=utf8 is the rite way to go. FYI, it does not treat _all_ files as utf-8. It just treats utf8 (which includes ascii) files as utf8. Well, this only ensures the condition 1) above. If you write some 'evil' characters, the file still cannot be converted to gb2312. I wonder if there are similar tools on Windoze like this: $ iconv -f utf-8 -t euc-cn file > /dev/null which can help you check the validity. > The newly 'cmdline.txt' was > generated this way, I wonder whether it'll be okay for other platforms. Checked, ok. -- Alecs King |
|
From: Dasn <da...@us...> - 2005-11-18 21:24:21
|
Hi, list! I just found this thread via Web and was sorry for coming back that late. > > > FYI, there"s a known glitch: some files worked by dasn (ie. > > > if_ole.txt, > > > gui_w32.txt, os_msdos.txt, etc.) couldnt be properly viewed under the > > > GBK locale. I dunno how to fix it so far. It might have something > > > to do with the (incorrect/corrupted) utf-8 conversion. > > hmmm. Can you provide a full list of files? What is the symptom? Can > > you read them at all? > > gui_w16.txt, gui_w32.txt, if_ole.txt, intro.txt, map.txt, > os_dos.txt, os_msdos.txt, os_win32.txt, sponsor.txt, > uganda.txt, windows.txt > The encoding problem is interesting: In Win32 enviroment (I do translations under Win2K), if you edit files which come from our repository with gvim DIRECTLY, you'll got all "junky characters". It seems that gvim miss some info to recognize the file encoding, as the 'fileencoding' option is null. The most tricky stuff comes when you edit the files with "notepad.exe", all things look fine in Notepad, then I "save as..." the file in UTF-8 format. Open it again with gvim, now, Vim can recognize the file encoding and auto convert to cp936. The files I had commited were formated like this. According to *help-translated* : [quote] Help files must use latin1 or utf-8 encoding. Vim assumes the encoding is utf-8 when finding non-ASCII characters in the first line. Thus you must translate the header with "For Vim version". [/quote] That means our files are either treated as latin1 encoding or utf-8 encoding when opened as [help] files, so they look fine in the help screen. What if we opened them directly? (I was used to working this way :) So, first I tried adding "enc=utf8" to the modelines of each files I translated, but as lang2 said, that was not recommended and Vim can recognize UTF-8 encoding automatically (I just wondered how? Cause all of our works in UTF-8 encoding look errant to me), then I tried to use notepad as metioned above. I appologize that the files I commited had not been tested on other platforms, and that probably bugs all my friends here. I feel so sorry. Forgive. Recently, I have to use "fileencodings=utf8" in _vimrc to force Vim to treat all kinds of files as UTF-8 encoding. The newly 'cmdline.txt' was generated this way, I wonder whether it'll be okay for other platforms. -Dasn |
|
From: Alecs K. <al...@pe...> - 2005-07-28 13:42:38
|
On Thu, Jul 28, 2005 at 11:39:46AM +0100, Wenzhi Liang wrote: > wandys, > > Can you send a mail to the announce list as well, since you are basically > doing the whole lot. glad to. will do. -- Alecs King |
|
From: Wenzhi L. <wen...@gm...> - 2005-07-28 10:40:48
|
wandys, Can you send a mail to the announce list as well, since you are basically doing the whole lot.=20 On 7/27/05, Wenzhi Liang <wen...@gm...> wrote: > On 7/27/05, Alecs King <al...@pe...> wrote: > > > > > > Just not familiar with the SF release cycle. Let me try.. > > > > Done. > Thanks a million. >=20 > > > > Files released to SF. And as for the vimcdoc.sf.net, i simply manually > > changed/added some bits. You can refine that when you get the chance. > For the homepage, I normally change the NEWS file under CVS and run > the vimcdoc-sf.py under data/www/ and then check them in. But it looks > OK anyway. >=20 > Thanks again and very well done. >=20 >=20 > lang2 > |
|
From: Wenzhi L. <wen...@gm...> - 2005-07-27 09:06:26
|
On 7/27/05, Alecs King <al...@pe...> wrote: > > > > Just not familiar with the SF release cycle. Let me try.. >=20 > Done. Thanks a million. >=20 > Files released to SF. And as for the vimcdoc.sf.net, i simply manually > changed/added some bits. You can refine that when you get the chance. For the homepage, I normally change the NEWS file under CVS and run=20 the vimcdoc-sf.py under data/www/ and then check them in. But it looks=20 OK anyway. Thanks again and very well done. lang2 |
|
From: Alecs K. <al...@pe...> - 2005-07-27 02:59:52
|
On Wed, Jul 27, 2005 at 09:55:13AM +0800, Alecs King wrote: > I can do the SF part (and spread some news =) if you are not very > convenient. > > Just not familiar with the SF release cycle. Let me try.. Done. Files released to SF. And as for the vimcdoc.sf.net, i simply manually changed/added some bits. You can refine that when you get the chance. -- Alecs King |
|
From: Alecs K. <al...@pe...> - 2005-07-27 01:55:29
|
On Tue, Jul 26, 2005 at 02:00:43PM +0100, Wenzhi Liang wrote: > Will do some annoucing when I get a chance. > > lang2, can you have some time to update the SF part and make the > > (official =) announcement? I can do the SF part (and spread some news =) if you are not very convenient. Just not familiar with the SF release cycle. Let me try.. -- Alecs King |
|
From: Wenzhi L. <wen...@gm...> - 2005-07-26 13:00:55
|
Thanks wandys and well done.=20 Will do some annoucing when I get a chance.=20 On 7/25/05, Alecs King <al...@pe...> wrote: > Hello there, >=20 > vimcdoc 0.8.0 (cvs tagged) is out: > http://gro.clinux.org/frs/?group_id=3D667 > changes since last release: > http://vcd.gro.clinux.org/changes > full ChangeLog: > http://vcd.gro.clinux.org/ChangeLog >=20 > all bits on the gro mirror are updated accordingly. >=20 > lang2, can you have some time to update the SF part and make the > (official =3D) announcement? >=20 >=20 > Time to spread the news.. :^) >=20 >=20 > Thanks & Regards, >=20 > -- > Alecs King >=20 >=20 > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=3D7477&alloc_id=3D16492&op=3Dclic= k > _______________________________________________ > Vimcdoc-translate mailing list > Vim...@li... > https://lists.sourceforge.net/lists/listinfo/vimcdoc-translate > |
|
From: Alecs K. <al...@pe...> - 2005-07-25 04:45:46
|
Hello there, vimcdoc 0.8.0 (cvs tagged) is out: http://gro.clinux.org/frs/?group_id=667 changes since last release: http://vcd.gro.clinux.org/changes full ChangeLog: http://vcd.gro.clinux.org/ChangeLog all bits on the gro mirror are updated accordingly. lang2, can you have some time to update the SF part and make the (official =) announcement? Time to spread the news.. :^) Thanks & Regards, -- Alecs King |
|
From: Alecs K. <al...@pe...> - 2005-07-14 01:23:13
|
On Wed, Jul 13, 2005 at 09:16:36PM +0100, Wenzhi Liang wrote: > I'd like to suggest > release 0.8.0 as is now, if wandys is free to take this task. Sure. > syntax hilighting > problem is half cosmetic and can be fixed in the next release. The > only thing to be > a bit cautious is to exclude some of the half-baked file (mbyte.txt > comes to my mind). > wandys, if you can take a quick look at the new files that are added > since last release > and have yet to be reviewed just to see if they are OK for publication. Will do. Hope i can release the 0.8 in the next week. > If there is any small thing that I can help with, please do ask. > Apologize again. Looking forward to the new release. Never mind. Good luck to your work. :) -- Alecs King |
|
From: Wenzhi L. <wen...@gm...> - 2005-07-13 20:17:36
|
Hi all, Sorry about my inactiveness. Very hard for me these days to conentrate on vimcdoc. I don't think the situation will change in the comming two month. So I'd like to suggest release 0.8.0 as is now, if wandys is free to take this task. The syntax hilighting problem is half cosmetic and can be fixed in the next release. The only thing to be a bit cautious is to exclude some of the half-baked file (mbyte.txt comes to my mind). wandys, if you can take a quick look at the new files that are added since last release and have yet to be reviewed just to see if they are OK for publication.=20 If there is any small thing that I can help with, please do ask. Apologize again. Looking forward to the new release. lang2 |
|
From: Carlos Z.F. L. <car...@us...> - 2005-07-01 10:42:39
|
On Fri, Jul 01, 2005 at 09:45:27AM +0100, Wenzhi Liang wrote: > On 6/30/05, Carlos Z.F. Liu <car...@us...> wrote: > > > Install vimcdoc. Do 'help' and read the files with 'ZhuYi', 'BeiZhu', > > > or 'YiZhe'. > > > Some of them doens't get hilighted. But if you manually edit that file using > > > ':e' command, it shows up OK. > > > > > I just made an experimental debian package for this new rc release. > > In my system (Debian sid), all those words are highlighted properly. > Including YiZhe? Confused. It still doesn't work for me and I am using > 6.3-patch71. > Oh, sorry, I checked only 'ZhuYi' and 'BeiZhu'. -- Best Regards, Carlos |
|
From: Wenzhi L. <wen...@gm...> - 2005-07-01 08:47:43
|
On 6/30/05, Alecs King <al...@pe...> wrote: > On Thu, Jun 30, 2005 at 05:14:44PM +0100, Wenzhi Liang wrote: > > Install vimcdoc. Do 'help' and read the files with 'ZhuYi', 'BeiZhu', > > or 'YiZhe'. > > Some of them doens't get hilighted. But if you manually edit that file = using > > ':e' command, it shows up OK. >=20 > This problem's gone if we add extra spaces before and after those > keywords, ie. <sp>YiZhe<sp>. But in theory it doesn't need to does it? lang2 |
|
From: Wenzhi L. <wen...@gm...> - 2005-07-01 08:45:36
|
On 6/30/05, Carlos Z.F. Liu <car...@us...> wrote: > > Install vimcdoc. Do 'help' and read the files with 'ZhuYi', 'BeiZhu', > > or 'YiZhe'. > > Some of them doens't get hilighted. But if you manually edit that file = using > > ':e' command, it shows up OK. > > > I just made an experimental debian package for this new rc release. > In my system (Debian sid), all those words are highlighted properly. Including YiZhe? Confused. It still doesn't work for me and I am using 6.3-patch71. lang2 |
|
From: Alecs K. <al...@pe...> - 2005-06-30 17:40:28
|
On Thu, Jun 30, 2005 at 05:14:44PM +0100, Wenzhi Liang wrote: > Install vimcdoc. Do 'help' and read the files with 'ZhuYi', 'BeiZhu', > or 'YiZhe'. > Some of them doens't get hilighted. But if you manually edit that file using > ':e' command, it shows up OK. This problem's gone if we add extra spaces before and after those keywords, ie. <sp>YiZhe<sp>. -- Alecs King |
|
From: Alecs K. <al...@pe...> - 2005-06-30 17:33:00
|
On Fri, Jul 01, 2005 at 03:30:26AM +1200, Carlos Z.F. Liu wrote:
> In GBK environment, users can get GBK support for vim by "enc=cp936".
> It works in both *nix and windows. But if you search on internet, most
> documents and tutorials suggest only "euc-cn".
At least in mbyte.txt:
>2 cp936 simplified Chinese (Windows only)
>2 euc-cn simplified Chinese (Unix only)
>...
>2 2byte-{name} Unix: any double-byte encoding (Vim specific name)
So i think the rite/safe/official way to use GBK on Unix is to set
enc=2byte-gbk. Vim will strip the leading '2byte-' and then pass 'gbk'
to iconv_open(). Tested. Worked fine.
Anyway, too many ppl are using euc-cn, so it's better to always keep our
docs enc-cn friendly.
--
Alecs King
|
|
From: Carlos Z.F. L. <car...@us...> - 2005-06-30 17:13:25
|
On Thu, Jun 30, 2005 at 05:14:44PM +0100, Wenzhi Liang wrote: > On 6/30/05, Alecs King <al...@pe...> wrote: > > On Thu, Jun 30, 2005 at 09:34:38AM +0100, Wenzhi Liang wrote: > > > The tarball works OK! The only thing I am not happy with is the effect of > > > help_cn.vim. It works some time but not always. What's more, if I > > > manually *edit* a file, it would work but not through *:help bla*. Any > > > clue? > > > > I dont have this problem here. More details of when & how it failed to > > work? > > Install vimcdoc. Do 'help' and read the files with 'ZhuYi', 'BeiZhu', > or 'YiZhe'. > Some of them doens't get hilighted. But if you manually edit that file using > ':e' command, it shows up OK. > I just made an experimental debian package for this new rc release. In my system (Debian sid), all those words are highlighted properly. > > > > > > Both tarball and windows installer are available: > > > > http://vcd.gro.clinux.org/vimcdoc-0.8.0-rc1.tar.gz > > > > http://vcd.gro.clinux.org/vimcdoc-0.8.0-rc1-setup.exe > > > > Hmm.. only me & lang2 here at the list? Anybody else? > :-( :-) -- Best Regards, Carlos |
|
From: Wenzhi L. <wen...@gm...> - 2005-06-30 16:14:54
|
On 6/30/05, Alecs King <al...@pe...> wrote: > On Thu, Jun 30, 2005 at 09:34:38AM +0100, Wenzhi Liang wrote: > > The tarball works OK! The only thing I am not happy with is the effect = of > > help_cn.vim. It works some time but not always. What's more, if I > > manually *edit* a file, it would work but not through *:help bla*. Any > > clue? >=20 > I dont have this problem here. More details of when & how it failed to > work? Install vimcdoc. Do 'help' and read the files with 'ZhuYi', 'BeiZhu', or 'YiZhe'. Some of them doens't get hilighted. But if you manually edit that file usin= g ':e' command, it shows up OK. >=20 > > > Both tarball and windows installer are available: > > > http://vcd.gro.clinux.org/vimcdoc-0.8.0-rc1.tar.gz > > > http://vcd.gro.clinux.org/vimcdoc-0.8.0-rc1-setup.exe >=20 > Hmm.. only me & lang2 here at the list? Anybody else? :-( lang2 |
|
From: Carlos Z.F. L. <car...@us...> - 2005-06-30 15:30:35
|
On Wed, Jun 29, 2005 at 09:38:56AM +0100, Wenzhi Liang wrote: > Excellent! Thanks wandys, > > On 6/28/05, Alecs King <al...@pe...> wrote: > > > > > > ie. > > > > > > > > :h intro@cn (under GBK locale, aka in vim, enc=euc-cn) shows nothing > > > > but malformed characters. > > > > I _was_ kinda misleading here. The truth is that, euc is not gbk but > > gb2312. Some of our docs contain some 'evil' characters that have been > > converted from gbk. But these characters are gbk-only [1] and cannot be > > successfully converted to enc-cn (aka gb2312). Hence the problem arises. > > That explains why on Slackware if I set LANG to zh_CN.gbk, things are OK. Is > that a limitation of Vim though? > In GBK environment, users can get GBK support for vim by "enc=cp936". It works in both *nix and windows. But if you search on internet, most documents and tutorials suggest only "euc-cn". -- Best Regards, Carlos |
|
From: Alecs K. <al...@pe...> - 2005-06-30 12:50:56
|
On Thu, Jun 30, 2005 at 09:34:38AM +0100, Wenzhi Liang wrote: > The tarball works OK! The only thing I am not happy with is the effect of > help_cn.vim. It works some time but not always. What's more, if I > manually *edit* a file, it would work but not through *:help bla*. Any > clue? I dont have this problem here. More details of when & how it failed to work? > > Both tarball and windows installer are available: > > http://vcd.gro.clinux.org/vimcdoc-0.8.0-rc1.tar.gz > > http://vcd.gro.clinux.org/vimcdoc-0.8.0-rc1-setup.exe Hmm.. only me & lang2 here at the list? Anybody else? -- Alecs King |
|
From: Wenzhi L. <wen...@gm...> - 2005-06-30 08:34:45
|
The tarball works OK! The only thing I am not happy with is the effect of help_cn.vim. It works some time but not always. What's more, if I=20 manually *edit* a file, it would work but not through *:help bla*. Any=20 clue? On 6/29/05, Alecs King <al...@pe...> wrote: > Hi, all >=20 > With the euc-cn glitch fixed and no other problems known so far, this > test release is made as a rc instead of beta. >=20 > Both tarball and windows installer are available: > http://vcd.gro.clinux.org/vimcdoc-0.8.0-rc1.tar.gz > http://vcd.gro.clinux.org/vimcdoc-0.8.0-rc1-setup.exe >=20 > I hope you can test it to make a better 0.8.0. >=20 > Thanks & Regards, >=20 > -- > Alecs King >=20 >=20 > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=3D7477&alloc_id=3D16492&op=3Dclic= k > _______________________________________________ > Vimcdoc-translate mailing list > Vim...@li... > https://lists.sourceforge.net/lists/listinfo/vimcdoc-translate > |
|
From: Alecs K. <al...@pe...> - 2005-06-29 16:14:47
|
On Wed, Jun 29, 2005 at 09:38:56AM +0100, Wenzhi Liang wrote: > > I _was_ kinda misleading here. The truth is that, euc is not gbk but > > gb2312. Some of our docs contain some 'evil' characters that have been > > converted from gbk. But these characters are gbk-only [1] and cannot be > > successfully converted to enc-cn (aka gb2312). Hence the problem arises. > > That explains why on Slackware if I set LANG to zh_CN.gbk, things are OK. Is > that a limitation of Vim though? Kind of. Vim doesnt have a 'gbk' for 'enc' option now. Before that and before everyone's using utf-8, we are better off keeping our files enc-cn friendly. > > When doing translation, remember to run the following command > > > > $ iconv -f utf-8 -t euc-cn file.txt >/dev/null > > > > to check if your doc is enc-cn friendly. > Can you add this to the guide.txt? Thanks Will do. -- Alecs King |
357 messages has been excluded from this view by a project administrator.
