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: Simon L. <wzh...@sp...> - 2004-09-07 10:03:25
|
Hello Zhang Lan, On Tue, 7 Sep 2004 09:16:08 +0800 (CST), "lan zhang" <ala...@ya...> said: > Hello, lang2: > Hi, I intend to join your project -- vimcdoc. I learned that you are the > one of administrators, so if you can make me be one of the developers in > your project, I will absolutely appreciate that. In addition, my username > of Sourceforge.net is alan43 and my ID number of Sourceforge.net is > 1116747. You are very welcomed to join us. I've added you to the developer list so that you have shell and CVS access. However, as you might soon find out, the project is actually very quite lately[1]. This shows how stable our project is right now. ;-) Seriously, I do have something on my todo list: there are several files that are never reviewed; mbytes.txt has to be finished and reviewed. I just havn't got around to do those things. If you feel bored or like doing something, you can start on those. Let me know if you are interested. Again, thank you for joining and welcome. lang2 [1] http://vimcdoc.sourceforge.net/cl.html -- Simon Liang wzh...@sp... |
|
From: Simon L. <wzh...@sp...> - 2004-07-27 11:28:43
|
> > Just played with aap for a while. Not quite impressive. :-( > IMHO, make has > better dependency handling and more clearer syntax. Better dependency handling? You mean the lack of auto dependency checking? In fairness, how many time have you wondered: 'am I building everything I should' and do 'make clean && make '? > > As for built-ins, i appreciate the Make's way: let those 'high' level > things be done thru outside tools. The fact that 'make' depends _entirely_ on the shell makes it unportable. IMHO, using a fully-featured language such as python as the engine is a much better choice. But anyways, we degress. As long as there is automation, I wouldn't mind. lang2 -- Simon Liang wzh...@sp... |
|
From: Alecs K. <al...@pe...> - 2004-07-26 16:51:48
|
On Mon, Jul 26, 2004 at 12:25:16PM +0100, Simon Liang wrote: > > > > Just a Makefile and a shell script. I'm not familiar with aap and cant > > view its website (blocked?). Just glanced at the .app files in our > > project and it looked to me much like Makefiles. > > It is a better make at the least. It has buil-in webpage uploading and > ftp uploding, through python. Just played with aap for a while. Not quite impressive. IMHO, make has better dependency handling and more clearer syntax. As for built-ins, i appreciate the Make's way: let those 'high' level things be done thru outside tools. > > You can use makefile if you want to. I remember you had a 'VCD' > module in the repository. If you decided to use makefile, can you > check those scripts in? Just to keep them tracked. Done. Under VCD/VCD/htdocs/doc/, Makefile & upload.sh. PS, for those who cant view http://www.a-a-p.org, try http://a-a-p.sf.net/ Regards, -- Alecs King |
|
From: Simon L. <wzh...@sp...> - 2004-07-26 11:25:23
|
> > Just a Makefile and a shell script. I'm not familiar with aap and cant > view its website (blocked?). Just glanced at the .app files in our > project and it looked to me much like Makefiles. It is a better make at the least. It has buil-in webpage uploading and ftp uploding, through python. You can use makefile if you want to. I remember you had a 'VCD' module in the repository. If you decided to use makefile, can you check those scripts in? Just to keep them tracked. lang2 -- Simon Liang wzh...@sp... |
|
From: Alecs K. <al...@pe...> - 2004-07-24 14:04:05
|
On Sat, Jul 24, 2004 at 01:59:16PM +0100, Simon Liang wrote: > > On Fri, 23 Jul 2004 16:07:47 +0800, "Alecs King" <al...@pe...> > said: > > > > My bad. Cosoft doesnt provide ssh access anymore. Only ftp allowed. I > > had been too lazy to write some scripts to auto upload files since. > > > > Just wrote 2 scripts. Now files uploaded. Check them out: > > > > http://vcd.cosoft.org.cn/doc/usr_toc.html > > http://vcd.cosoft.org.cn/doc/help.html > > Good. I am not sure how the ftp upload work. But it would be nice if > the upload can be integrated with 'aap', as what is done for SF. That > would allow automation of the task and we will never (only cosoft > change its policy again that is) have to worry about it again. Just a Makefile and a shell script. I'm not familiar with aap and cant view its website (blocked?). Just glanced at the .app files in our project and it looked to me much like Makefiles. Maybe I need a proxy.. -- Alecs King |
|
From: Simon L. <wzh...@sp...> - 2004-07-24 12:59:18
|
On Fri, 23 Jul 2004 16:07:47 +0800, "Alecs King" <al...@pe...> said: > > My bad. Cosoft doesnt provide ssh access anymore. Only ftp allowed. I > had been too lazy to write some scripts to auto upload files since. > > Just wrote 2 scripts. Now files uploaded. Check them out: > > http://vcd.cosoft.org.cn/doc/usr_toc.html > http://vcd.cosoft.org.cn/doc/help.html Good. I am not sure how the ftp upload work. But it would be nice if the upload can be integrated with 'aap', as what is done for SF. That would allow automation of the task and we will never (only cosoft change its policy again that is) have to worry about it again. lang2 -- Simon Liang wzh...@sp... |
|
From: Simon L. <wzh...@sp...> - 2004-07-24 12:55:24
|
On Fri, 23 Jul 2004 14:13:43 +0800, "xxxss" <xx...@ms...> said: > change them to UTF-8?? Not only that. The html version is just a conversion from the txt version. I believe what is on cosoft at the moment is based on vimcdoc 0.6.0 (or 0.6.1). 0.7.0 had a lot of changes, including the charset. So it would be nice to get the HTML version in sync with CVS, even those on the wiki page if at all possible. lang2 -- Simon Liang wzh...@sp... |
|
From: Alecs K. <al...@pe...> - 2004-07-23 08:07:13
|
On Thu, Jul 22, 2004 at 06:05:38PM +0100, Simon Liang wrote: > Anybody wants to do this? wandys? > > The html on sf is automatically updated but I believer there > are *much* more reader of the cosoft pages. So it is more > important to keep that up to date. My bad. Cosoft doesnt provide ssh access anymore. Only ftp allowed. I had been too lazy to write some scripts to auto upload files since. Just wrote 2 scripts. Now files uploaded. Check them out: http://vcd.cosoft.org.cn/doc/usr_toc.html http://vcd.cosoft.org.cn/doc/help.html Regards, -- Alecs King |
|
From: xxxss <xx...@ms...> - 2004-07-23 06:26:48
|
change them to UTF-8?? -- xxxss <xx...@ms...> |
|
From: Simon L. <wzh...@sp...> - 2004-07-22 17:05:42
|
Anybody wants to do this? wandys? The html on sf is automatically updated but I believer there are *much* more reader of the cosoft pages. So it is more important to keep that up to date. lang2 -- Simon Liang wzh...@sp... |
|
From: Simon L. <wzh...@sp...> - 2004-07-20 15:41:43
|
Bram has made the patch available for 6.3 by patch 6.3.014. (It was only available for Vim 7). > > > What's it on your systems, pals? Is this a Vim bug? > > > > 'zh'. I suppose if we make a link from 'tags-cn' to 'tags-zh', things > > would work. But it is not ideal. The reason why 'cn' is used is to > > allow a future translation work from 'tw'. > > Yes, from your forwarded mail, Bram said he'd use 'cn' for tags naming. -- Simon Liang wzh...@sp... |
|
From: Simon L. <wzh...@sp...> - 2004-07-19 10:48:49
|
On Sat, 17 Jul 2004 16:02:50 +0200, "Bram Moolenaar"
<Br...@mo...> said:
>
> Simon -
>
> > I have a question about the translated-help system.
> > One of our developer discovered this: if the system locale is set to
> > zh_CN.???, Vim will automatically detect it and set the 'helplang'
> > option to 'zh'. However, as we discussed before, the "vimcdoc"
> > project will use 'cn' as an extention value. So the result is that
> > the automatic detection will not work. The solution (my guess)
> > would be either:
> > a. change "vimcdoc" to use 'zh' or make a link between 'tags-cn'
> > and 'tags-zh'.
> > or:
> > b. change the automatic detection in Vim.
> >
> > I'd like to hear your opinion on this.
>
> Right, the default is not set according to our own ideas.
>
> This patch should make it work as intended:
>
> *** option.c~ Tue Jul 13 10:49:57 2004
> --- option.c Sat Jul 17 16:00:33 2004
> ***************
> *** 3237,3243 ****
> --- 3237,3251 ----
> if (p_hlg == NULL)
> p_hlg = empty_option;
> else
> + {
> + /* zh_CN becomes "cn", zh_TW becomes "tw". */
> + if (STRNICMP(p_hlg, "zh_", 3) == 0 && STRLEN(p_hlg) >= 5)
> + {
> + p_hlg[0] = TOLOWER_ASC(p_hlg[3]);
> + p_hlg[1] = TOLOWER_ASC(p_hlg[4]);
> + }
> p_hlg[2] = NUL;
> + }
> options[idx].flags |= P_ALLOCED;
> }
> }
>
>
> - Bram
>
> --
> hundred-and-one symptoms of being an internet addict:
> 26. You check your mail. It says "no new messages." So you check it
> again.
>
> /// Bram Moolenaar -- Br...@Mo... -- http://www.Moolenaar.net
> \\\
> /// Sponsor Vim, vote for features -- http://www.Vim.org/sponsor/
> \\\
> \\\ Project leader for A-A-P -- http://www.A-A-P.org
> ///
> \\\ Buy at Amazon and help AIDS victims -- http://ICCF.nl/click1.html
> ///
--
Simon Liang
wzh...@sp...
|
|
From: Alecs K. <al...@pe...> - 2004-07-17 21:56:09
|
On Sat, Jul 17, 2004 at 01:26:37PM +0100, Simon Liang wrote:
> >
> > I just thought this question the other day before. :h translated shows,
> > "The 'helplang' option can be set to the preferred language(s). The
> > default is set according to the environment."
> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> >
> > So maybe we shouldnt set it explicitly in our script. But seems under
> > zh_CN.XXX locale, helplang is set to 'zh' instead of 'cn'.
> >
> > What's it on your systems, pals? Is this a Vim bug?
>
> 'zh'. I suppose if we make a link from 'tags-cn' to 'tags-zh', things
> would work. But it is not ideal. The reason why 'cn' is used is to
> allow a future translation work from 'tw'.
Yes, from your forwarded mail, Bram said he'd use 'cn' for tags naming.
I just took a look at the Vim source code, did some grep and found what
possibly caused this bug:
vim63/src/options.c: around the line 3161:
------------------------------------------------------------------
#if defined(FEAT_MULTI_LANG) || defined(PROTO)
/*
* When 'helplang' is still at its default value, set it to "lang".
* Only the first ___TWO___ characters of "lang" are used.
*/ ^^^^^^^^^
void
set_helplang_default(lang)
char_u *lang;
{
int idx;
if (lang == NULL || STRLEN(lang) < 2) /* safety check */
return;
idx = findoption((char_u *)"hlg");
if (!(options[idx].flags & P_WAS_SET))
{
if (options[idx].flags & P_ALLOCED)
free_string_option(p_hlg);
p_hlg = vim_strsave(lang);
if (p_hlg == NULL)
p_hlg = empty_option;
else
p_hlg[2] = NUL;
options[idx].flags |= P_ALLOCED;
}
}
#endif
------------------------------------------------------------------
Easy to apply a dirty patch. But lets wait and see what Bram would say
about this.
Thanks & Regards,
--
Alecs King
|
|
From: Simon L. <wzh...@sp...> - 2004-07-17 12:26:44
|
> > I just thought this question the other day before. :h translated shows, > "The 'helplang' option can be set to the preferred language(s). The > default is set according to the environment." > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > So maybe we shouldnt set it explicitly in our script. But seems under > zh_CN.XXX locale, helplang is set to 'zh' instead of 'cn'. > > What's it on your systems, pals? Is this a Vim bug? 'zh'. I suppose if we make a link from 'tags-cn' to 'tags-zh', things would work. But it is not ideal. The reason why 'cn' is used is to allow a future translation work from 'tw'. But I dout it. I think I will ask Bram. lang2 -- Simon Liang wzh...@sp... |
|
From: Alecs K. <al...@pe...> - 2004-07-16 18:58:01
|
On Fri, Jul 16, 2004 at 03:38:01PM +0800, James He wrote: > Should we supply 'encoding=enc-cn' files together with those utf8 encoded files? > I think some people would have difficulty seeing the utf8 encoded files in some > situations. I am just one of them. :) No worries. Vim will do the conversion for you. -- Alecs King |
|
From: Alecs K. <al...@pe...> - 2004-07-16 18:47:53
|
On Fri, Jul 16, 2004 at 11:56:52AM +0100, Simon Liang wrote: > > 表达的不对，我的意思是说如果*nix的安装脚本自动加入 set helplang=cn 的话 > > windows的安装脚本也应该相应的修改 :) 看来是不必了，呵呵 > > To wandys: Do you agree? I just thought this question the other day before. :h translated shows, "The 'helplang' option can be set to the preferred language(s). The default is set according to the environment." ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ So maybe we shouldnt set it explicitly in our script. But seems under zh_CN.XXX locale, helplang is set to 'zh' instead of 'cn'. What's it on your systems, pals? Is this a Vim bug? -- Alecs King |
|
From: Simon L. <wzh...@sp...> - 2004-07-16 10:56:54
|
> =B1=ED=B4=EF=B5=C4=B2=BB=B6=D4=A3=AC=CE=D2=B5=C4=D2=E2=CB=BC=CA=C7=CB=B5= =C8=E7=B9=FB*nix=B5=C4=B0=B2=D7=B0=BD=C5=B1=BE=D7=D4=B6=AF=BC=D3=C8=EB set = helplang=3Dcn =B5=C4=BB=B0 > windows=B5=C4=B0=B2=D7=B0=BD=C5=B1=BE=D2=B2=D3=A6=B8=C3=CF=E0=D3=A6=B5=C4= =D0=DE=B8=C4 :) =BF=B4=C0=B4=CA=C7=B2=BB=B1=D8=C1=CB=A3=AC=BA=C7=BA=C7 To wandys: Do you agree? lang2 --=20 Simon Liang wzh...@sp... |
|
From: Simon L. <wzh...@sp...> - 2004-07-16 10:55:22
|
> =CE=D2=B5=C4=CE=CA=CC=E2=CA=C7=A3=AC=D4=DAwindows=CF=C2=C3=E6=D3=C3putty= =C0=B4ssh=B5=BDlinux=D6=D0=CA=B1 > =CF=D4=CA=BEutf8=B1=E0=C2=EB=B5=C4=CE=C4=BC=FE=D3=D0=CE=CA=CC=E2=A1=AA=A1= =AA=D7=DC=CA=C7=BB=F2=B6=E0=BB=F2=C9=D9=D3=D0=D0=A9=C2=D2=C2=EB >=20 > =CB=F9=D2=D4=CE=D2=D6=BB=C4=DC=B0=D1=CB=F9=D3=D0=B5=C4=B0=EF=D6=FA=CE=C4= =BC=FE=D7=AA=BB=BB=B3=C9gb2312=B1=E0=C2=EB=B5=C4=B2=C5=C4=DC=BF=B4 > =B2=BB=D6=AA=B5=C0=C6=E4=CB=FB=C8=CB=D3=D0=C3=BB=D3=D0=CF=E0=CB=C6=B5=C4= =C7=E9=BF=F6 >=20 > =BF=C9=C4=DC=D5=E2=CA=C7=C9=D9=CA=FD=C7=E9=BF=F6=A3=AC=B2=BB=D3=C3=BF=BC= =C2=C7=A1=AA=A1=AA=C4=C7=C3=B4=D6=B1=BD=D3=BA=F6=C2=D4=CE=D2=B5=C4=D5=E2=B8= =F6=CC=FB=D7=D3=BA=C3=C1=CB :) That is what I mean. Do ':set enc=3Deuc-cn' before=20 doing :help and Vim will do the conversion for you. No=20 need for the script. lang2 --=20 Simon Liang wzh...@sp... |
|
From: James He <ic...@us...> - 2004-07-16 10:44:31
|
on Fri, 16 Jul 2004 10:25:26 +0100 "Simon Liang" <wzh...@sp...> wrote: > You are not meant to install from a CVS sandbox. It won't work. If you > have aap, do a 'aap release' to generate a release tarball and test from > that. Alternatively, you can download the 0.7.0 release and replace the > vimcdoc.sh script. 哦，我的失误。我从cvs中安装的，改了doc目录的文件名之后 用新的 vimcdoc.sh 可以成功安装 :) > > (the same thing happens on the windows setup script) > ?? hmmm? > No. The windows setup program doens't change the rc file. It only does > :he @cn 表达的不对，我的意思是说如果*nix的安装脚本自动加入 set helplang=cn 的话 windows的安装脚本也应该相应的修改 :) 看来是不必了，呵呵 Best regards, -- James He |
|
From: James He <ic...@us...> - 2004-07-16 10:44:06
|
on Fri, 16 Jul 2004 10:31:32 +0100 "Simon Liang" <wzh...@sp...> wrote: > I didn't fully understand your problem. But try :set enc=euc-cn > in Vim. This (supposedly) will ask Vim to convert utf-8 to euc-cn > on the fly. 我的问题是，在windows下面用putty来ssh到linux中时 显示utf8编码的文件有问题――总是或多或少有些乱码 所以我只能把所有的帮助文件转换成gb2312编码的才能看 不知道其他人有没有相似的情况 可能这是少数情况，不用考虑――那么直接忽略我的这个帖子好了 :) Best regards, -- James He |
|
From: Simon L. <wzh...@sp...> - 2004-07-16 09:31:34
|
On Fri, 16 Jul 2004 15:38:01 +0800, "James He" <ic...@us...> said: > Should we supply 'encoding=enc-cn' files together with those utf8 encoded > files? > I think some people would have difficulty seeing the utf8 encoded files > in some > situations. I am just one of them. :) > > Sometimes, I use Putty to ssh to my Debian box(without X) under Windows > XP. And > then it is difficult to see all the utf8 encoded characters normally on > screen. > I used a simple script to convert all the translated docs to 'enc-cn' > encoding > and everything is okay. The script is as follows and it uses a packaged > named > 'zh-autoconvert' which supplies the tools 'autogb': > > ========================================== > server# cat convert.sh > #!/bin/sh > > for i in doc/*.txt; do > autogb -i utf8 -o gb < $i >$i.tmp > mv $i.tmp $i > done > ========================================== I didn't fully understand your problem. But try :set enc=euc-cn in Vim. This (supposedly) will ask Vim to convert utf-8 to euc-cn on the fly. lang2 -- Simon Liang wzh...@sp... |
|
From: Simon L. <wzh...@sp...> - 2004-07-16 09:26:55
|
On Fri, 16 Jul 2004 15:17:33 +0800, "James He" <ic...@us...> said: > on Wed, 07 Jul 2004 12:40:56 +0100=20 > "Simon Liang" <wzh...@sp...> wrote: >=20 > > >>>> HILIGHTS <<<< > > - µÚÒ»‚€Ö=EF=BF=BD=EF=BF=BD³&= #214; Vim 6.3 > > µÄ=EF=BF=BD=EF=BF=BD¢²¼£¬Ë=EF= =BF=BD=EF=BF=BDÓÐÓû=EF=BF=BD=EF=BF=BDÊÖ= ²=EF=BF=BD=EF=BF=BDºÍ²¿=EF=BF=BD=EF=BF=BDÖ= 78;ο¼ÊÖ²=EF=BF=BD=EF=BF=BD¸=EF=BF=BD=EF= =BF=BD¾Ý > > Vim 6.3=20 >=20 > What you said is a mess here. How can I solve this problem? > Thx a lot! Yeah. I was just experimenting with it. And somehow the encoding is wrong. Guess I will have dual language next time. If you really want to read them, go to the sourceforge project page. Sorry about that. lang2 --=20 Simon Liang wzh...@sp... |
|
From: Simon L. <wzh...@sp...> - 2004-07-16 09:25:29
|
> I have tested the script on my Debian(sid) box. Thanks, > I seems that '.cnx' in > the > script should be changed into '.txt' because we only get *.txt files if > we do > a 'cvs co doc'. You are not meant to install from a CVS sandbox. It won't work. If you have aap, do a 'aap release' to generate a release tarball and test from that. Alternatively, you can download the 0.7.0 release and replace the vimcdoc.sh script. > > Another problem, should we add 'set helplang=cn' automatically for users? I'd say no. > I think those who would like to install our package are willing to use > the > translated documents right after they install them. So why not change > .vimrc > file for them? :) I'd also say if a user is happy enough about Vim, he is happy enough to hack his own .vimrc file, or so he should be. > (the same thing happens on the windows setup script) ?? hmmm? No. The windows setup program doens't change the rc file. It only does :he @cn lang2 -- Simon Liang wzh...@sp... |
|
From: James He <ic...@us...> - 2004-07-16 07:38:13
|
Should we supply 'encoding=enc-cn' files together with those utf8 encoded files?
I think some people would have difficulty seeing the utf8 encoded files in some
situations. I am just one of them. :)
Sometimes, I use Putty to ssh to my Debian box(without X) under Windows XP. And
then it is difficult to see all the utf8 encoded characters normally on screen.
I used a simple script to convert all the translated docs to 'enc-cn' encoding
and everything is okay. The script is as follows and it uses a packaged named
'zh-autoconvert' which supplies the tools 'autogb':
==========================================
server# cat convert.sh
#!/bin/sh
for i in doc/*.txt; do
autogb -i utf8 -o gb < $i >$i.tmp
mv $i.tmp $i
done
==========================================
Still I am not quite sure if it is proper for us to supply author 'enc-cn' encoded
copy of those docs. :)
Best regards,
--
James He
|
|
From: James He <ic...@us...> - 2004-07-16 07:17:46
|
on Wed, 14 Jul 2004 02:45:30 +0800 Alecs King <al...@pe...> wrote: > Please run it on your system and do tell me if something's wrong or > needed to be polished. I have tested the script on my Debian(sid) box. I seems that '.cnx' in the script should be changed into '.txt' because we only get *.txt files if we do a 'cvs co doc'. Also, it seems that we should rename the file 'tags' to 'tags-cn'. Another problem, should we add 'set helplang=cn' automatically for users? I think those who would like to install our package are willing to use the translated documents right after they install them. So why not change .vimrc file for them? :) (the same thing happens on the windows setup script) Best regards, -- James He |
357 messages has been excluded from this view by a project administrator.
