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: Wenzhi L. <wen...@gm...> - 2005-06-29 08:39:06
|
Excellent! Thanks wandys, On 6/28/05, Alecs King <al...@pe...> wrote: >=20 > > > ie. > > > > > > :h intro@cn (under GBK locale, aka in vim, enc=3Deuc-cn) shows nothin= g > > > but malformed characters. >=20 > 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. I= s=20 that a limitation of Vim though? >=20 > All changes committed to CVS. I'm about to release a 0.8.0-rc1 which > you can test to see if this problem still remains and/or there are any > other problems. Will test the new tarball. >=20 > When doing translation, remember to run the following command >=20 > $ iconv -f utf-8 -t euc-cn file.txt >/dev/null >=20 > to check if your doc is enc-cn friendly. Can you add this to the guide.txt? Thanks Greate job! lang2 |
|
From: Alecs K. <al...@pe...> - 2005-06-28 23:06:51
|
Hi, all With the euc-cn glitch fixed and no other problems known so far, this test release is made as a rc instead of beta. 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 I hope you can test it to make a better 0.8.0. Thanks & Regards, -- Alecs King |
|
From: Alecs K. <al...@pe...> - 2005-06-28 22:49:34
|
On Tue, Jun 28, 2005 at 09:38:21AM +0100, Wenzhi Liang wrote: > Tested on Slackware last night and the installation went fine (as root). I did > see the problem you had tough, and on more files. Here is my list: > usr_02.txt > sponsor.txt > uganda.txt > usr_10.txt > intro.txt > pattern.txt > map.txt > windows.txt > mbyte.txt > gui_w16.txt > gui_w32.txt > if_ole.txt > os_dos.txt > os_msdos.txt > os_win32.txt > I think the actual encoding of the files are (probably) correct. We just > need to help Vim to detect it. Will look into it but it will take time. After playing around with gdb & vim, i just find the cause is indeed of the files themselves. > > 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. I followed the execution of vim and replaced all those 'evil' characters with enc-cn friendly ones. Most of them are gbk punctuation, some of them are traditional Chinese characters, others are unknown invalid chars. All changes committed to CVS. I'm about to release a 0.8.0-rc1 which you can test to see if this problem still remains and/or there are any other problems. 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. [1] One exception is pattern.txt, of which the 'evil' chars are not from gbk conversion but from the original English doc. They are not evil of themselves but are evil to enc-cn. -- Alecs King |
|
From: Wenzhi L. <wen...@gm...> - 2005-06-28 09:02:22
|
Installation on NT seems fine too. On 6/27/05, Wenzhi Liang <wen...@gm...> wrote: > Looks Ok this time. Will test it on NT tomorrow. >=20 > On 6/27/05, Alecs King <al...@pe...> wrote: > > On Mon, Jun 27, 2005 at 05:39:38PM +0100, Wenzhi Liang wrote: > > > The setup program works OK but it appears to create a directory under > > > $VIMFILES\doc\vimcdoc-0.8.0-beta1. This is not desirable. > > > > sorry. my fault. fixed now. > > > > > > done. it's created with wine + nsis: > > > > http://vcd.gro.clinux.org/vimcdoc-0.8.0-beta1-setup.exe > > > > please re-download & test it. > > > > -- > > Alecs King > > > > > > ------------------------------------------------------- > > 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=3Dcl= ick > > _______________________________________________ > > Vimcdoc-translate mailing list > > Vim...@li... > > https://lists.sourceforge.net/lists/listinfo/vimcdoc-translate > > > |
|
From: Wenzhi L. <wen...@gm...> - 2005-06-28 08:38:25
|
wandys, Tested on Slackware last night and the installation went fine (as root). I = did see the problem you had tough, and on more files. Here is my list: usr_02.txt sponsor.txt uganda.txt usr_10.txt intro.txt pattern.txt map.txt windows.txt mbyte.txt gui_w16.txt gui_w32.txt if_ole.txt os_dos.txt os_msdos.txt os_win32.txt I think the actual encoding of the files are (probably) correct. We just need to help Vim to detect it. Will look into it but it will take time. For everyone else, if you are still on the lis and listening, please try the tarball/exe file yourself and play around with it. The more problem we found the better. Thanks, lang2 On 6/27/05, Alecs King <al...@pe...> wrote: > > > 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? >=20 > 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 >=20 >=20 > ie. >=20 > :h intro@cn (under GBK locale, aka in vim, enc=3Deuc-cn) shows nothing > but malformed characters. >=20 > though ok when euc=3Dutf-8. >=20 >=20 > other files like usr_*.txt dont have this problem. >=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: Wenzhi L. <wen...@gm...> - 2005-06-27 17:51:47
|
Looks Ok this time. Will test it on NT tomorrow. On 6/27/05, Alecs King <al...@pe...> wrote: > On Mon, Jun 27, 2005 at 05:39:38PM +0100, Wenzhi Liang wrote: > > The setup program works OK but it appears to create a directory under > > $VIMFILES\doc\vimcdoc-0.8.0-beta1. This is not desirable. >=20 > sorry. my fault. fixed now. >=20 > > > done. it's created with wine + nsis: > > > http://vcd.gro.clinux.org/vimcdoc-0.8.0-beta1-setup.exe >=20 > please re-download & test it. >=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-27 17:34:54
|
On Mon, Jun 27, 2005 at 05:39:38PM +0100, Wenzhi Liang wrote: > The setup program works OK but it appears to create a directory under > $VIMFILES\doc\vimcdoc-0.8.0-beta1. This is not desirable. sorry. my fault. fixed now. > > done. it's created with wine + nsis: > > http://vcd.gro.clinux.org/vimcdoc-0.8.0-beta1-setup.exe please re-download & test it. -- Alecs King |
|
From: Wenzhi L. <wen...@gm...> - 2005-06-27 16:39:44
|
Thanks wandys, The setup program works OK but it appears to create a directory under $VIMFILES\doc\vimcdoc-0.8.0-beta1. This is not desirable. Maybe it is to do with the latest version of nsis. Can you check it (or ask your friend to check it) again and see if it happens on your side? >=20 > done. it's created with wine + nsis: > http://vcd.gro.clinux.org/vimcdoc-0.8.0-beta1-setup.exe >=20 >=20 > A friend of mine has successfully tested it on winxp. Tell me if you > get any problem. >=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-27 14:31:14
|
> > I'm sorry but i've got no access to any M$s and i dunno how to make a > > 'windows setup.exe'... > You only need the nsis compiler (http://nsis.sourceforge.net/), the > latest will > do. Or I can make it when I find a bit of free time. It can be done > using wine > under Linux/BSD, which is what I do. done. it's created with wine + nsis: http://vcd.gro.clinux.org/vimcdoc-0.8.0-beta1-setup.exe A friend of mine has successfully tested it on winxp. Tell me if you get any problem. -- Alecs King |
|
From: Alecs K. <al...@pe...> - 2005-06-27 12:17:47
|
> > 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 ie. :h intro@cn (under GBK locale, aka in vim, enc=euc-cn) shows nothing but malformed characters. though ok when euc=utf-8. other files like usr_*.txt dont have this problem. -- Alecs King |
|
From: Wenzhi L. <wen...@gm...> - 2005-06-27 09:05:39
|
Hi wandys, Thanks for covering my *ss and sorry about the absence. Still v busy though.=20 >=20 > You can download the tarball at: > http://vcd.gro.clinux.org/vimcdoc-0.8.0-beta1.tar.gz I will test the tarball on Slackware and Hiweed (debian base) and maybe Mandrake as well. >=20 > I'm sorry but i've got no access to any M$s and i dunno how to make a > 'windows setup.exe'... You only need the nsis compiler (http://nsis.sourceforge.net/), the latest= will do. Or I can make it when I find a bit of free time. It can be done using w= ine under Linux/BSD, which is what I do. >=20 > I did rough tests on debian, crux, & fbsd. And it all worked fine. I'd > like you to test it on your favorite platforms and do tell me if > something goes wrong. >=20 > 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? Thanks again. lang2 |
|
From: Alecs K. <al...@pe...> - 2005-06-27 07:34:42
|
Hi, all ESR tells us, 'Release early, release often'. But it's quite long since our last release. lang2's been busy these days. So i'm just trying to release our long-waited 0.8.0. But before the formal public release is out, i made out a beta for you guys to test. You can download the tarball at: http://vcd.gro.clinux.org/vimcdoc-0.8.0-beta1.tar.gz I'm sorry but i've got no access to any M$s and i dunno how to make a 'windows setup.exe'... I did rough tests on debian, crux, & fbsd. And it all worked fine. I'd like you to test it on your favorite platforms and do tell me if something goes wrong. 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. Attached are the changes since our last 0.7.0 release. Thanks & Regards, -- Alecs King |
|
From: Carlos Z.F. L. <car...@us...> - 2005-04-08 13:20:03
|
On Thu, Apr 07, 2005 at 02:12:58PM +0100, Wenzhi Liang wrote: > Carlos Z.F. Liu wrote: > > In Debian system, /usr/share/vim/vimfiles is a link to /etc/vim > > directory. According Debian Policy Manual, documents shouldn't be > > installed in /etc. > > That seems to me an mistake. The location is one of the vim 'rtp'. > I don't see why that should be in /etc. > I think the reason is FHS [1] compliance. According FHS, host-specific configuration files (such as vimrc and gvimrc) should be put in /etc or one of its subdirectories. But vim's default 'rtp' doesn't contain such a path. A link from /usr/share/vim/vimfiles to /etc/vim would resolve this problem. [1] http://www.pathname.com/fhs/ -- Best Regards, Carlos |
|
From: Wenzhi L. <wen...@gm...> - 2005-04-07 12:12:40
|
Carlos Z.F. Liu wrote: > On Thu, Apr 07, 2005 at 10:10:23AM +0100, Wenzhi Liang wrote: > >>Hello Carlos, > > In Debian system, /usr/share/vim/vimfiles is a link to /etc/vim > directory. According Debian Policy Manual, documents shouldn't be > installed in /etc. That seems to me an mistake. The location is one of the vim 'rtp'. I don't see why that should be in /etc. >> > > It's done automatically by Debian packaging system. I think it's because > guides.txt is larger than others, and the size trigger the compressing > process to save disk space [1]. IIRC, in the VIM5.x era, even vimdoc > itself is gzip compressed. OK. I have no idea how Debian packages are made. That's fine. > > Thanks. > > BTW, after I put my intention of packaging vimcdoc in the debian mailing > list, I received some feedbacks [2]. > > 1. The name is quite misleading to English speaking people, they suggest > me to rename it to vimdoc-cn. The first guy who replied to me thought > it's VIMDOC already. (In Debian, it's quite common to use another name > for the binary package, because there are more than 10000 packages in > the archive, a clearer name will make things easier.) The naming is confusing I must admit. Ken had the name in the first place. So it is not my fault (although the name I came up with was the most confusing of all) ;-). You can of course choose the name you think aproprite. The BSD port uses 'vim-scdoc', which I think is OK but not technically correct: if a FanTi font is used the text would show up as FanTi. > > 2. Changing the license. We should be happy on this issue, because this > means people are care on our work. Most Debian developers normally > didn't reply to a non-free package at all. I have told them that I > intent to put it in non-free section at current stage, and switch to > main section [3] once the author change the license. Since GFDL is > non-free in Debian world, a crazy debian-legal guy suggest us to use > Academic Free License v2.1 [4]. You can read his mail in [2]. I'm not a > lawyer, and don't understand those triky things, so I leave them to you. > Hope they are helpful and useful. This is not going to change in the near future. At least not with 0.8.0. We probably need to discuss this in the group. Actually, if anybody has some strong feeling about this, let him speak. Rgds, lang2 |
|
From: Carlos Z.F. L. <car...@us...> - 2005-04-07 10:33:07
|
On Thu, Apr 07, 2005 at 10:10:23AM +0100, Wenzhi Liang wrote: > Hello Carlos, > > I took a quick look at the debian package and they are fine. However > I have two questions for you: > 1. Why are the cnx files installed in /usr/share/vim/vim63? This > restricts the vim version to be vim63. By default, vimcdoc is > installed in /usr/share/vim/vimfiles. I guess for the moment, it > is the same as vimcdoc is only compatible with vim 6.3. But just > a question. In Debian system, /usr/share/vim/vimfiles is a link to /etc/vim directory. According Debian Policy Manual, documents shouldn't be installed in /etc. > 2. Why is guides.txt compressed and the likes of README and dict.txt > are not? > It's done automatically by Debian packaging system. I think it's because guides.txt is larger than others, and the size trigger the compressing process to save disk space [1]. IIRC, in the VIM5.x era, even vimdoc itself is gzip compressed. > ps. I've added the link to vimcdoc.sf.net > Thanks. BTW, after I put my intention of packaging vimcdoc in the debian mailing list, I received some feedbacks [2]. 1. The name is quite misleading to English speaking people, they suggest me to rename it to vimdoc-cn. The first guy who replied to me thought it's VIMDOC already. (In Debian, it's quite common to use another name for the binary package, because there are more than 10000 packages in the archive, a clearer name will make things easier.) 2. Changing the license. We should be happy on this issue, because this means people are care on our work. Most Debian developers normally didn't reply to a non-free package at all. I have told them that I intent to put it in non-free section at current stage, and switch to main section [3] once the author change the license. Since GFDL is non-free in Debian world, a crazy debian-legal guy suggest us to use Academic Free License v2.1 [4]. You can read his mail in [2]. I'm not a lawyer, and don't understand those triky things, so I leave them to you. Hope they are helpful and useful. [1] http://www.debian.org/doc/debian-policy/ch-docs.html#s12.3 [2] http://bugs.debian.org/303366 [3] Main section is against non-free section. Only pure free software can be put in this section. Another section is contrib, it means software itself is free, but it need some non-free things to run properly, such as those softwares need SUN's JRE. [4] http://www.opensource.org/licenses/afl-2.1.php -- Best Regards, Carlos |
|
From: Wenzhi L. <wen...@gm...> - 2005-04-07 08:09:54
|
Hello Carlos, I took a quick look at the debian package and they are fine. However I have two questions for you: 1. Why are the cnx files installed in /usr/share/vim/vim63? This restricts the vim version to be vim63. By default, vimcdoc is installed in /usr/share/vim/vimfiles. I guess for the moment, it is the same as vimcdoc is only compatible with vim 6.3. But just a question. 2. Why is guides.txt compressed and the likes of README and dict.txt are not? ps. I've added the link to vimcdoc.sf.net Carlos Z.F. Liu wrote: > Hello, vimcdoc crew > > First, introduce myself. I'm Carlos Liu, an active Debian maintainer > (not a developer yet) in Debian Chinese community. > > To make our Chinese Debian users' life easier, I have made a deb package > for vimcdoc [1]. You can put it in your website if you want. I also want > to ask your approval to let me upload it to official Debian archive. > > Due to the clause 2 of vimcdoc license, I think this software isn't a > free software according our DFSG definition[1]. So I put it in non-free > section. After upload, it will sit in Debian ftp mirrors, but won't be a > part of any offical Debian release. > > Thanks for your work. > > > [1] http://chinese.alioth.debian.org/vimcdoc > [2] http://www.debian.org/social_contract#guidelines > |
|
From: Carlos Z.F. L. <car...@us...> - 2005-04-06 13:12:59
|
On Wed, Apr 06, 2005 at 02:09:31PM +0100, Wenzhi Liang wrote: > Please don't use the 0.7.9 release. It is an internal testing > release that is not ready for the mass. Unfortunately, I am very busy > at the moment so the planed 0.8.0 release will be delayed! > OK, I will wait the next release. -- Best Regards, Carlos |
|
From: Wenzhi L. <wen...@gm...> - 2005-04-06 12:09:12
|
Hello Carlos, Carlos Z.F. Liu wrote: > > Ok, I'm happy that I can contribute something to this project since I > like vim and like vimcdoc even more. :) > This URL is just an place in Debian > Chinese community. I will put the newest unoffical packages in there > (such as 0.7.9, I found it in list 2 min ago ^_^). Once the package is > uploaded to official Debian archive, I will notify you in the list. Please don't use the 0.7.9 release. It is an internal testing release that is not ready for the mass. Unfortunately, I am very busy at the moment so the planed 0.8.0 release will be delayed! lang2 |
|
From: Carlos Z.F. L. <car...@us...> - 2005-04-06 10:57:57
|
On Wed, Apr 06, 2005 at 09:24:21AM +0800, James He wrote: > I am a Debian user myself and have seen you post in debian-user-chinese > mailing list. :) > It's nice to see Debian users in every corner in the world! Haha... If you get some free time, welcome to #debian-zh on irc.freenode.net. > I think it is very helpful if you make a debian package of vimcdoc. > Thanks! Unfortunately, the package would be in the non-free section. > Not that bad, I think Hiweed or other Debian derived distro can include it in their installation CD. At least, I hope so. -- Best Regards, Carlos |
|
From: Carlos Z.F. L. <car...@us...> - 2005-04-06 10:53:07
|
On Wed, Apr 06, 2005 at 10:49:50AM +0100, Wenzhi Liang wrote: > That's good news. We've already have a BSD port and now a debian > package. Very good. I'll include a link to it on our website > shortly. Is [1] the final URL? Of course you can upload it to the > official Debian archive. I havn't had a chance to look at the > package myself but I will. > Ok, I'm happy that I can contribute something to this project since I like vim and like vimcdoc even more. This URL is just an place in Debian Chinese community. I will put the newest unoffical packages in there (such as 0.7.9, I found it in list 2 min ago ^_^). Once the package is uploaded to official Debian archive, I will notify you in the list. > Yes. License. Not familiar with the DFSG (you meant 2. yes?). So I > don't know what the definition of free there is. I have been > thinking about license myself lately, mainly the possibility and > impact of changing it to an existing free license (FDL or > something). But I've been lazy about this I guess. But I suppose > you can put it under non-free until things changed. > In Debian community, the definition of free documents is already very problematic. Currently, even GFDL is considered as non-free. @_@ I'm happy with vimcdoc, but as what you said, I think it's better to switch to an existing full-bloated lawyer-writed license. :) -- Best Regards, Carlos |
|
From: Wenzhi L. <wen...@gm...> - 2005-04-06 08:49:26
|
Hello Carlos, Carlos Z.F. Liu wrote: > Hello, vimcdoc crew > > First, introduce myself. I'm Carlos Liu, an active Debian maintainer > (not a developer yet) in Debian Chinese community. > > To make our Chinese Debian users' life easier, I have made a deb package > for vimcdoc [1]. You can put it in your website if you want. I also want > to ask your approval to let me upload it to official Debian archive. That's good news. We've already have a BSD port and now a debian package. Very good. I'll include a link to it on our website shortly. Is [1] the final URL? Of course you can upload it to the official Debian archive. I havn't had a chance to look at the package myself but I will. > > Due to the clause 2 of vimcdoc license, I think this software isn't a > free software according our DFSG definition[1]. So I put it in non-free > section. After upload, it will sit in Debian ftp mirrors, but won't be a > part of any offical Debian release. Yes. License. Not familiar with the DFSG (you meant 2. yes?). So I don't know what the definition of free there is. I have been thinking about license myself lately, mainly the possibility and impact of changing it to an existing free license (FDL or something). But I've been lazy about this I guess. But I suppose you can put it under non-free until things changed. Thanks again. Rgds, lang2 |
|
From: James He <ic...@us...> - 2005-04-06 01:24:58
|
on Wed, 6 Apr 2005 04:10:37 +1200 "Carlos Z.F. Liu" <car...@us...> wrote: > To make our Chinese Debian users' life easier, I have made a deb package > for vimcdoc [1]. You can put it in your website if you want. I also want > to ask your approval to let me upload it to official Debian archive. > > Due to the clause 2 of vimcdoc license, I think this software isn't a > free software according our DFSG definition[1]. So I put it in non-free > section. After upload, it will sit in Debian ftp mirrors, but won't be a > part of any offical Debian release. Hi, Carlos Liu I am a Debian user myself and have seen you post in debian-user-chinese mailing list. :) I think it is very helpful if you make a debian package of vimcdoc. Thanks! Unfortunately, the package would be in the non-free section. Best regards, -- James He |
|
From: Carlos Z.F. L. <car...@us...> - 2005-04-05 16:10:49
|
Hello, vimcdoc crew First, introduce myself. I'm Carlos Liu, an active Debian maintainer (not a developer yet) in Debian Chinese community. To make our Chinese Debian users' life easier, I have made a deb package for vimcdoc [1]. You can put it in your website if you want. I also want to ask your approval to let me upload it to official Debian archive. Due to the clause 2 of vimcdoc license, I think this software isn't a free software according our DFSG definition[1]. So I put it in non-free section. After upload, it will sit in Debian ftp mirrors, but won't be a part of any offical Debian release. Thanks for your work. [1] http://chinese.alioth.debian.org/vimcdoc [2] http://www.debian.org/social_contract#guidelines -- Best Regards, Carlos |
|
From: Wenzhi L. <wen...@gm...> - 2005-03-29 11:50:27
|
James He wrote: > on Tue, 29 Mar 2005 09:41:31 +0100 > Wenzhi Liang <wen...@gm...> wrote: > > >>What were you trying to post James? Is it a big attachment? > > > 原文如下(不知道列表有mail大小的限制，附件有2个图片)： > > 更新了help_cn.vim，发现很多文件还是没有效果，有的是字符串不匹配，另外一 > 些不知道是怎么回事 > > 请看附件中的截图： > Snap1.gif : 上面的窗口“译者”没有高亮，下面的窗口“注意”没有高亮 > > Snap2.gif : 上面的窗口“译者”没有高亮，“VIM 用户手册”高亮了，下面的窗 > 口“Vim用户手册”不匹配，“译者”还是没有高亮 > > Best regards, Yes. I see something similiar: some of them hilighted and some of them not. You can send the snapshot to me directly if you want to. lang2 |
|
From: James He <ic...@us...> - 2005-03-29 10:16:22
|
on Tue, 29 Mar 2005 09:41:31 +0100 Wenzhi Liang <wen...@gm...> wrote: > What were you trying to post James? Is it a big attachment? 原文如下(不知道列表有mail大小的限制，附件有2个图片)： 更新了help_cn.vim，发现很多文件还是没有效果，有的是字符串不匹配，另外一 些不知道是怎么回事 请看附件中的截图： Snap1.gif : 上面的窗口“译者”没有高亮，下面的窗口“注意”没有高亮 Snap2.gif : 上面的窗口“译者”没有高亮，“VIM 用户手册”高亮了，下面的窗 口“Vim用户手册”不匹配，“译者”还是没有高亮 Best regards, -- James He |
357 messages has been excluded from this view by a project administrator.
