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 He <ic...@us...> - 2004-07-16 07:17:46
|
on Wed, 07 Jul 2004 12:40:56 +0100 "Simon Liang" <wzh...@sp...> wrote: > >>>> HILIGHTS <<<< > - µÚÒ»‚€Ö§³Ö Vim 6.3 > µÄ・¢²¼£¬ËùÓÐÓû§ÊÖ²áºÍ²¿・ֲο¼ÊÖ²á¸ù¾Ý > Vim 6.3 What you said is a mess here. How can I solve this problem? Thx a lot! Best regards, -- James He |
|
From: Simon L. <wzh...@sp...> - 2004-07-14 12:34:15
|
> > Besides less typing, is there more reason for this? > > No. Reducing key strokes is the very reason. Not a good idea? The drawback I can see is that a user that is used to the old installation will type 'vimcdoc install' straight away and see an error. But heck. Let's leave it as it is. lang2 -- Simon Liang wzh...@sp... |
|
From: Alecs K. <al...@pe...> - 2004-07-14 11:23:38
|
On Wed, Jul 14, 2004 at 09:52:26AM +0100, Simon Liang wrote: > > > > 1) ./vimcdoc.sh install|uninstall ==> ./vimcdoc.sh -i|-u > > Besides less typing, is there more reason for this? No. Reducing key strokes is the very reason. Not a good idea? -- Alecs King |
|
From: Simon L. <wzh...@sp...> - 2004-07-14 08:52:30
|
> > 1) ./vimcdoc.sh install|uninstall ==> ./vimcdoc.sh -i|-u Besides less typing, is there more reason for this? lang2 -- Simon Liang wzh...@sp... |
|
From: Simon L. <wzh...@sp...> - 2004-07-14 08:50:03
|
> > Ahuh.. This clears my mind. So we can detect $VIM, create $VIM/vimfiles > if it does not exist, and then install the *.cnx files. Yes. lang2 -- Simon Liang wzh...@sp... |
|
From: Alecs K. <al...@pe...> - 2004-07-13 19:09:38
|
On Tue, Jul 13, 2004 at 10:55:50AM +0100, Simon Liang wrote: > > We can set fileenc in the mode line while we transtated the first line. > > Not every person is using utf-8 exclusively. > Bram doesn't like the idea of having 'enc' in status line and said it > wouldn't > work properly. Anyway, translating the very first line into Chinese and > using UTF is fine. Yes. sooo fine.. I just found that even not using utf-8 (enc-cn instead), translated docs could be viewed without any problems. Looks like Vim automatically does the encoding conversion (from utf-8 to enc-cn). This is really GREAT and relieves me a lot. There are so many ppl still using enc-cn. So better not have the 'enc' in the modeline. =) Just make sure our translated docs themselves are in utf-8 encoding and the first line gets translated. Vim ROCKS! :P -- Alecs King |
|
From: Alecs K. <al...@pe...> - 2004-07-13 18:44:21
|
Hi, all After talking with lang2 (see another thread on our ML), i improved the install script for most portability (hopefully works on most UN*X platforms) as well as other tweaks. Highlights: 1) ./vimcdoc.sh install|uninstall ==> ./vimcdoc.sh -i|-u 2) Auto-detect $VIM 3) Echo installing process For details, do a cvs diff. =) Tested on fbsd. Please run it on your system and do tell me if something's wrong or needed to be polished. Thanks & Regards. -- Alecs King |
|
From: Alecs K. <al...@pe...> - 2004-07-13 17:11:59
|
On Tue, Jul 13, 2004 at 05:12:01PM +0100, Simon Liang wrote: > Just curious. What is installed in /usr/ by default on FreeBSD? The base system. $ ls /usr/share bsnmp examples isdn misc pcvt snmp vi calendar games locale mk security syscons zoneinfo dict groff_font man nls sendmail tabset doc info me openssl skel tmac > My idea is that if user uninstall/reinstall/upgrade his/her Vim, vimcdoc > should be left alone. Installing in one of the .../vimfiles directory > have this benifit. Overkill? Ahuh.. This clears my mind. So we can detect $VIM, create $VIM/vimfiles if it does not exist, and then install the *.cnx files. > Can you do that and test it on your BSD system please? Sure. I just waited for an agreement on the VIM_PATH issue. Now it's time to write a new vimcdoc.sh script. :D -- Alecs King |
|
From: Simon L. <wzh...@sp...> - 2004-07-13 16:12:02
|
On Tue, 13 Jul 2004 22:54:42 +0800, "Alecs King" <al...@pe...> said: > On Tue, Jul 13, 2004 at 01:48:13PM +0100, Simon Liang wrote: > > > > > E.g. Here on FreeBSD (5.2-current), vim is installed to > > > /usr/local/share/vim/vim63/ with no 'vimfiles' sub-directory. > > By default or when you compile your own Vim? > > Installed it from ports. Just curious. What is installed in /usr/ by default on FreeBSD? > > :h rt shows that on UNIX $HOME/.vim, $VIM/vimfiles, $VIMRUNTIME, > $VIM/vimfiles/after and $HOME/.vim/after are all okay. > > Correct me if i'm wrong: > All has $VIMRUNTIME, but not all has $VIM/vimfiles. So why not just > detect and use $VIMRUNTIME? My idea is that if user uninstall/reinstall/upgrade his/her Vim, vimcdoc should be left alone. Installing in one of the .../vimfiles directory have this benifit. Overkill? > > I think that would be okay. Can you do that and test it on your BSD system please? Thanks, lang2 -- Simon Liang wzh...@sp... |
|
From: Alecs K. <al...@pe...> - 2004-07-13 14:56:44
|
On Tue, Jul 13, 2004 at 01:49:53PM +0100, Simon Liang wrote: > An OT question to wandys: > > which BSD are you using? FreeBSD 5.2-current. > I think there is a FreeBSD port of the > vimcdoc. Geez.. I didnt even know it.. -- Alecs King |
|
From: Alecs K. <al...@pe...> - 2004-07-13 14:53:41
|
On Tue, Jul 13, 2004 at 01:48:13PM +0100, Simon Liang wrote: > > > E.g. Here on FreeBSD (5.2-current), vim is installed to > > /usr/local/share/vim/vim63/ with no 'vimfiles' sub-directory. > By default or when you compile your own Vim? Installed it from ports. > > > I think > > it's better to check $VIMRUNTIME to support various vim installations. > System wide installation can only reside in $VIM/vimfiles/doc. That is > the only make-sense location. So maybe we can detect whether Vim > is installed in /usr or /usr/local 'Only'? Here on fbsd, the doc path is /usr/local/share/vim/vim63/doc. $VIM: /usr/local/share/vim $VIMRUNTIME: /usr/local/share/vim/vim63 :h rt shows that on UNIX $HOME/.vim, $VIM/vimfiles, $VIMRUNTIME, $VIM/vimfiles/after and $HOME/.vim/after are all okay. Correct me if i'm wrong: All has $VIMRUNTIME, but not all has $VIM/vimfiles. So why not just detect and use $VIMRUNTIME? > do a 'which vim' for auto-detection. Is that OK? Good idea. Anyway, this is for $VIMCDOC_PATH. So it may not be as important as the $VIM_PATH issue above. Just using /usr/share or /usr/local/share without detection also works. > > > > > > > 3) The '-D' option of 'install' is a GNU/Linux style option, whereas > > BSD install does not have this option but '-d' instead. > > (Back to use mkdir & cp?) > > hmm. I never used BSD myself. What if we 'mkdir' explicitely and leave > out the '-D' ? I think that would be okay. Regards, |
|
From: Simon L. <wzh...@sp...> - 2004-07-13 12:49:56
|
An OT question to wandys: which BSD are you using? I think there is a FreeBSD port of the vimcdoc. Someone actually sent me (CCed) patch of the port makefile for vimcdoc-0.7.0. lang2 -- Simon Liang wzh...@sp... |
|
From: Simon L. <wzh...@sp...> - 2004-07-13 12:48:16
|
> E.g. Here on FreeBSD (5.2-current), vim is installed to > /usr/local/share/vim/vim63/ with no 'vimfiles' sub-directory. By default or when you compile your own Vim? > I think > it's better to check $VIMRUNTIME to support various vim installations. System wide installation can only reside in $VIM/vimfiles/doc. That is the only make-sense location. So maybe we can detect whether Vim is installed in /usr or /usr/local > > hmm. The only reason I choosed /usr is because it has a better chance of > > 'work > > out of box'. What would you prefer? Auto-detection? > > > > I dunno if it's a (loose?) convention. But usually all those manually > installed software goes to /usr/local/share. (That is, default prefix is > /usr/local). Not a big deal, anyway. Yes. That is the convention and is exactly the reason why I choose /usr instead of /usr/local: only a small portion of user will compile his own Vim. So the user's Vim is more likely to be in /usr. Anyway, I think it is OK to do a 'which vim' for auto-detection. Is that OK? > > > 3) The '-D' option of 'install' is a GNU/Linux style option, whereas > BSD install does not have this option but '-d' instead. > (Back to use mkdir & cp?) hmm. I never used BSD myself. What if we 'mkdir' explicitely and leave out the '-D' ? lang2 -- Simon Liang wzh...@sp... |
|
From: Alecs K. <al...@pe...> - 2004-07-13 12:01:36
|
On Tue, Jul 13, 2004 at 10:55:11AM +0100, Simon Liang wrote: > On Sat, 10 Jul 2004 16:13:00 +0800, "Alecs King" <al...@pe...> > said: > > 1) Why hard-coded the $VIM_PATH instead of checking $VIMRUNTIME like our > > old script did? > > I'd thought that most of the user uses the vim that came with the > Linux/BSD > distro. And they should reside in /usr/. If not, adding > '/usr/share/vim/vimfiles' isn't > to rtp that hard either. E.g. Here on FreeBSD (5.2-current), vim is installed to /usr/local/share/vim/vim63/ with no 'vimfiles' sub-directory. I think it's better to check $VIMRUNTIME to support various vim installations. > > 2) Not root, you cant install files to $VIMCDOC_PATH. Sorry. I overlooked the $install_dist_files part. > > PS, as for $VIMCDOC_PATH, i prefer to use /usr/local/... instead of > > /usr/share. > hmm. The only reason I choosed /usr is because it has a better chance of > 'work > out of box'. What would you prefer? Auto-detection? > I dunno if it's a (loose?) convention. But usually all those manually installed software goes to /usr/local/share. (That is, default prefix is /usr/local). Not a big deal, anyway. 3) The '-D' option of 'install' is a GNU/Linux style option, whereas BSD install does not have this option but '-d' instead. (Back to use mkdir & cp?) Regards, |
|
From: Simon L. <wzh...@sp...> - 2004-07-13 09:55:52
|
> We can set fileenc in the mode line while we transtated the first line. > Not every person is using utf-8 exclusively. Bram doesn't like the idea of having 'enc' in status line and said it wouldn't work properly. Anyway, translating the very first line into Chinese and using UTF is fine. lang2 -- Simon Liang wzh...@sp... -- Simon Liang wzh...@sp... |
|
From: Simon L. <wzh...@sp...> - 2004-07-13 09:55:13
|
On Sat, 10 Jul 2004 16:13:00 +0800, "Alecs King" <al...@pe...> said: > 1) Why hard-coded the $VIM_PATH instead of checking $VIMRUNTIME like our > old script did? I'd thought that most of the user uses the vim that came with the Linux/BSD distro. And they should reside in /usr/. If not, adding '/usr/share/vim/vimfiles' isn't to rtp that hard either. > > 2) Not root, you cant install files to $VIMCDOC_PATH. > > PS, as for $VIMCDOC_PATH, i prefer to use /usr/local/... instead of > /usr/share. hmm. The only reason I choosed /usr is because it has a better chance of 'work out of box'. What would you prefer? Auto-detection? lang2 -- Simon Liang wzh...@sp... -- Simon Liang wzh...@sp... |
|
From: Simon L. <wzh...@sp...> - 2004-07-13 09:54:08
|
> (What a shame that i've contributed nothing to this release..) No worries. It is not like that there is nothing left to do. ;-) > > Cosoft is not accessbile rite now. I'll upload the new files later. Seen them. Thanks, lang2 -- Simon Liang wzh...@sp... -- Simon Liang wzh...@sp... |
|
From: Simon L. <wzh...@sp...> - 2004-07-13 08:42:54
|
On Tue, 13 Jul 2004 09:38:33 +0100, "Simon Liang" <wzh...@sp...> said: > test hmmm. I replied several of wandys mail yesterday and got rejected. Will try again later. > -- > Simon Liang > wzh...@sp... > > > > ------------------------------------------------------- > This SF.Net email sponsored by Black Hat Briefings & Training. > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > digital self defense, top technical experts, no vendor pitches, > unmatched networking opportunities. Visit www.blackhat.com > _______________________________________________ > Vimcdoc-translate mailing list > Vim...@li... > https://lists.sourceforge.net/lists/listinfo/vimcdoc-translate -- Simon Liang wzh...@sp... |
|
From: Simon L. <wzh...@sp...> - 2004-07-13 08:38:37
|
test -- Simon Liang wzh...@sp... |
|
From: Alecs K. <al...@pe...> - 2004-07-10 08:29:29
|
On Thu, Jun 10, 2004 at 11:09:41AM +0100, Simon Liang wrote: > > > 1. encoding: > > > I'd change the encoding to utf-8 and add 'enc=utf-8' on the > > > status line. I'd like to leave 'For Vim version' string as it is since > > > it is awkward to translate. > > > > Please read the help at ":help help-translated". There must be a > > non-ASCII utf-8 character in the first line, otherwise Vim assumes the > > file is latin1. Setting 'encoding' or 'fileencoding' in a modeline will > > not have the desired effect. > > We can set fileenc in the mode line while we transtated the first line. Not every person is using utf-8 exclusively. -- Alecs King |
|
From: Alecs K. <al...@pe...> - 2004-07-10 08:12:49
|
1) Why hard-coded the $VIM_PATH instead of checking $VIMRUNTIME like our old script did? 2) Not root, you cant install files to $VIMCDOC_PATH. PS, as for $VIMCDOC_PATH, i prefer to use /usr/local/... instead of /usr/share. -- Alecs King |
|
From: Alecs K. <al...@pe...> - 2004-07-10 05:18:08
|
On Sat, Jul 10, 2004 at 12:34:57AM +0800, Alecs King wrote: > I'll upload the new files later. Done. -- Alecs King |
|
From: Alecs K. <al...@pe...> - 2004-07-09 16:34:56
|
On Wed, Jul 07, 2004 at 12:40:56PM +0100, Simon Liang wrote: >[snip] Great work, lang2. (What a shame that i've contributed nothing to this release..) Cosoft is not accessbile rite now. I'll upload the new files later. Regards, |
|
From: Alecs K. <al...@pe...> - 2004-07-09 16:30:22
|
On Fri, Jul 09, 2004 at 03:08:34PM +0100, Simon Liang wrote: > Hello all, > > Hope everything is OK. slimzhao has just joined us! For those > of you who don't know, he single handedly translated all the > Vim user manual and made a very nice PDF file out of it. The > latest file can be downloaed from our web page as well. I am > very glad he is willing to join us. Give the amount of experience > he has, I am sure the vimcdoc project will do much better. > > Please welcome him with me. Welcome aboard, slim. ;-) Regards, |
|
From: Simon L. <wzh...@sp...> - 2004-07-09 14:08:38
|
Hello all, Hope everything is OK. slimzhao has just joined us! For those of you who don't know, he single handedly translated all the Vim user manual and made a very nice PDF file out of it. The latest file can be downloaed from our web page as well. I am very glad he is willing to join us. Give the amount of experience he has, I am sure the vimcdoc project will do much better. Please welcome him with me. Rgds, lang2 -- Simon Liang wzh...@sp... |
357 messages has been excluded from this view by a project administrator.
