Hi, Mechelynck:

	 I installed the patch, and add below code to my _vimrc file:

set termencoding=cp936
set encoding=UTF-8
set fileencodings=ucs-bom,utf-8,cp936
setg bomb
set guifont=NSimsun:h12:cDEFAULT

     and the symdrone now is still the same as what I depict in my last post.

======= 2005-04-29 17:00:20 A. J. Mechelynck wrote: =======

>Bruce Who wrote:
>> Strohhaecker, Bernd:
>>
>>
>>
>> ======= 2005-04-29 16:31:25 Strohhaecker, Bernd wrote: =======
>>
>>
>>>Bruce Who wrote:
>>>
>>>
>>>> thanks for the explanation, but how to view this kind of files?
>>>>
>>>
>>>For me "gvim xx.reg" works fine. Dito with "gvim -u NONE -U NONE
>>>--noplugin xx.reg".
>>
>>
>>     I tried both, and it still behaved like before.
>>
>>
>>>Same with vim (MS-Windows 32 Bit Konsolen Version) and also with vi
>>>under cygwin & zsh.
>>>
>>>Did you look at Tony's link ?
>>>
>>>BTW, which vim-version and is multi-byte enabled at all ?
>>
>>
>>     It's gVim63 and multi-byte enabled. I downloaded the self-installing 
.exe file and installed gvim.
>>
>>
>>>Try :ver or :echo has("multi_byte")
>>>
>>>Regards, Bernd
>>>.
>>
>>
>> = = = = = = = = = = = = = = = = = = = =
>>
>>
>> 　　　　　　　　Bruce Who
>> 　　　　　　　　　　2005-04-29
>>
>>
>>
>>
>When you type
>
> :version
>
>do you see near the top a line beginning with "Included patches:"? If
>you don't, it means you have gvim 6.3.000. In that case, try installing
>gvim 6.3.071 from my site
>http://users.skynet.be/antoine.mechelynck/vim/#ajm and see if anything
>changes.
>
>
>Best regards,
>Tony.
>
>.

= = = = = = = = = = = = = = = = = = = =


　　　　　　　　Bruce Who
　　　　　　　　　　2005-04-30

Bruce Who wrote:
> Hi, Mechelynck:
>
>  I add below code to my _vimrc file:
>
> set termencoding=cp936
> set encoding=UTF-8
> set fileencodings=ucs-bom,utf-8,cp936
> setg bomb
> set guifont=NSimsun:h12:cDEFAULT
>
>     and now it can display the .reg file and files containing chinese
characters correctly,:-)
> , but the chinese characters of gVim GUI are still gibberishes, :-<

Ah, it seems we are making progress. Do you mean the Chinese-language
menus are displayed incorrectly, or the Chinese-language messages, or both?

If it's the menus, try

	 aunmenu *
	 runtime! menu.vim

after setting 'encoding' to UTF-8.

If it's the messages, the solution is trickier. First make gvim show the
current "messages language":

	 :language messages

You may have to change the setting, but I'm not sure what to set: you
will have to proceed by trial and error. Try one or more of the following:

	 :language messages zh_CN.ISO-10646-1
	 :language messages Chinese_China.UTF-8
	 :language messages Chinese_Simplified.Unicode

or any variations of it. If nothing avails,

	 :language messages en

will give you English messages. You may have to put that "language"
command at the very beginning of your vimrc (after "set nocompatible" if
present, but before all the rest including, if present, "source
$VIMRUNTIME/vimrc_example.vim") -- in some cases it will work there but
not farther down.


Best regards,
Tony.

P.S. Do you prefer being called Bruce or Xuzhao (then in both cases you
can call me Tony -- I suppose that's Douni in pinyin) or Hu-chan (then
you can call me Mr. Mechelynck -- but that's harder to transliterate
into Chinese)?

Hi, Tony:

======= 2005-04-30 10:43:08 A. J. Mechelynck wrote: =======

>Bruce Who wrote:
>> Mechelynck:
>>
>>  I tried these:
>>
>>  :set guifont=NSimSun:h12:cDEFAULT
>>
>>     :set guifont=卜悶:h12:cDEFAULT
>>
>>     but the chinese characters of gVim's GUI are all still gibberishes.
>> After opening files containing chinese characters, all charaters are
>> gibberishes too.
>>
>There are two possible causes to that problem.
>
>Possibility 1. Your Chinese (Simplified) is not properly detected. To
>see if that is the case, do:

after I add following code to _vimrc:

set termencoding=cp936
set encoding=UTF-8
set fileencodings=ucs-bom,utf-8,cp936
setg bomb
set guifont=NSimsun:h12:cDEFAULT

     gVim can display .reg file and files containing chinese now. But the GUI is
full of gibberishes.

> :set encoding?
> " the answer should be "  encoding=utf-8"

     yes,
> :e filename.ext
> :verbose setlocal fileencoding? bomb?

     fileencoding is cp936 and nobomb when I edit files contaning chinese
characters, and ucs-2le, bomb when .reg file.
> " the values should correspond to the file's charset;
> " 'bomb' should normally not be set for non-Unicode encodings.
>
>If the values shown are correct, proceed to Possibility 2 below.

      So, it's not Possibility 1.

>Otherwise, you may want to either:
>
>a) specify the charset manually whenever you read the file:
>
> :e ++enc=cp936 filename.ext
>or
> :e ++enc=euc-cn filename.ext
>
>etc.; or
>
>b) change the settings for the 'fileencodings' option. However:
> - ucs-bom must be first (to detect a Unicode BOM correctly at start of
>file;
> - if there is an 8-bit charset in the lot, it must come last (and there
>must never be two or more), because detection of an 8-bit charset cannot
>generate a "failure" signal, which means that anything after it will
>never be used.
>
>Possibility 2. Your Chinese charset is correctly detected, but gvim does
>not find the required glyphs in the 'guifont'.
>
>See my tip http://vim.sourceforge.net/tips/tip.php?tip_id=632 "Setting
>the font in the GUI".
>
>You may try one or more of the following, in any order:
>
> - Replace :cDEFAULT by :cGB3212 in the 'guifont' option to see if
>anything changes. If it doesn't work, put :cDEFAULT back into it. If it
>works for Chinese text files, check if it works also for .reg files.

     I did it. After I run gVim withou opening any files yet, all chinese
characters of the gVim GUI are gibberishes.

>
> - Use ":set guifont=*" and choose the font in a menu. This way you
>won't run the risk of setting a font which is not present on your system.

     before I add the code to _vimrc the gVim's GUI(menu item mainly) can display
chinese correctly, and the default guifont is

     guifont=Fixedsys:h9:cGB2312

     After I change my code to:

set termencoding=cp936
set encoding=UTF-8
set fileencodings=ucs-bom,utf-8,cp936
setg bomb
set guifont=Fixedsys:h9:cGB2312

     the GUI is still full of gibberishes.
>
> - after using the font menu, you may want to use ":set guifont=<Tab>"
>to edit the current value (change what you want to change then hit Enter
>to accept the changes or Escape to abandon the changes): in particular,
>:cDEFAULT is often the best choice because it usually allows gvim to
>choose among the various "localised" variants of a single font,
>depending on what needs to be displayed (a Unicode page may contain
>Chinese, Latin and Cyrillic text on the same page; in that case,
>:cGB3212, :cRUSSIAN and :cANSI would each allow some characters to be
>visible but not all of them).
>
>
>Best regards,
>Tony.
>

= = = = = = = = = = = = = = = = = = = =


　　　　　　　　Bruce Who
　　　　　　　　　　2005-04-30

Hi, Douni:



======= 2005-04-30 11:04:15 A. J. Mechelynck wrote: =======

>Bruce Who wrote:
>> Hi, Mechelynck:
>>
>>  I add below code to my _vimrc file:
>>
>> set termencoding=cp936
>> set encoding=UTF-8
>> set fileencodings=ucs-bom,utf-8,cp936
>> setg bomb
>> set guifont=NSimsun:h12:cDEFAULT
>>
>>     and now it can display the .reg file and files containing chinese
characters correctly,:-)
>> , but the chinese characters of gVim GUI are still gibberishes, :-<
>
>Ah, it seems we are making progress. Do you mean the Chinese-language
>menus are displayed incorrectly, or the Chinese-language messages, or both?

    both

>
>If it's the menus, try
>
> aunmenu *
> runtime! menu.vim
>
>after setting 'encoding' to UTF-8.

     I have just looked at the menu.vim file. I added

	     echomsg "s:lang is".s:lang

     to the script and found s:lang is zh_CN, so I directly inserted this to the
menu.vim file:

   	     let s:lang = "zh_cn.utf-8"

     before the statement:

  	     exe "runtime! lang/menu_" . s:lang . "*.vim"

     but it doesn't work, I also tried

	     let s:lang = "zh_cn.gb2312"
 	     let s:lang = "zh_cn"

     but they donnot work either.

     at last I removed the "let s:lang" statement, and added

	     let did_menu_trans=1

     to my _vimrc file, and I got an English version menubar.
>
>If it's the messages, the solution is trickier. First make gvim show the
>current "messages language":
>
> :language messages
>
>You may have to change the setting, but I'm not sure what to set: you
>will have to proceed by trial and error. Try one or more of the following:
>
> :language messages zh_CN.ISO-10646-1
> :language messages Chinese_China.UTF-8
> :language messages Chinese_Simplified.Unicode

     I add

	     language messages zh_CN.UTF-8

     to my _vimrc, and all messages are correct now!

     At last, I can view .reg files and files containning chinese using gVim, all
messages are chinese, and get an English menubar. No gibberishes any more!

>or any variations of it. If nothing avails,
>
> :language messages en
>
>will give you English messages. You may have to put that "language"
>command at the very beginning of your vimrc (after "set nocompatible" if
>present, but before all the rest including, if present, "source
>$VIMRUNTIME/vimrc_example.vim") -- in some cases it will work there but
>not farther down.
>
>
>Best regards,
>Tony.
>
>P.S. Do you prefer being called Bruce or Xuzhao (then in both cases you
>can call me Tony -- I suppose that's Douni in pinyin) or Hu-chan (then
>you can call me Mr. Mechelynck -- but that's harder to transliterate
>into Chinese)?

Just call me Bruce. Xuzhao is my chinese name in pinyin and is only used in my
family, not my real name.

Tony is not Douni in pinyi, I'm sorry for the mistake.  I visit this page given
by you just now:

http://vim.sourceforge.net/tips/tip.php?tip_id=632

and found author is Tony Mechelynck, so I thought you are Tony subjectively, :-P
. I don't know how to pronounce Douni and Mechelynck in English, maybe Douni can
be translate to Daoni in pinyin, ^_^?

>
>.

= = = = = = = = = = = = = = = = = = = =

Best regards,

　　　　　　　　Bruce Who
　　　　　　　　　　2005-04-30

How do I set the $VIMRUNTIME variable?


--
  Lennart Andersen
  St Thomas, Ontario
  lennart at rogers dot com
--------------------------
   - Human knowledge belongs to the world
       [From the movie "Antitrust"]

Hi,

:h $VIMRUNTIME

This variable is already set by VIM. If you want to set it from vim, do

	 :let $VIMRUNTIME = "/home/piet/vim/vim54"

Or set the $VIMRUNTIME in the shell or dos prompt and invoke gvim, the
environment variables set in the shell or dos prompt is taken.

~Vishnu.

-----Original Message-----
From: Lennart Andersen [mailto:lennart@...]
Sent: Saturday, April 30, 2005 11:06 AM
To: vim dot org
Subject: :let $VIMRUNTIME

How do I set the $VIMRUNTIME variable?


--
  Lennart Andersen
  St Thomas, Ontario
  lennart at rogers dot com
--------------------------
   - Human knowledge belongs to the world
       [From the movie "Antitrust"]

Bruce Who wrote:
> Hi, Douni:

Hi Bruce

>
>
>
> ======= 2005-04-30 11:04:15 A. J. Mechelynck wrote: =======
>
>
>>Bruce Who wrote:
>>
>>>Hi, Mechelynck:
>>>
>>> I add below code to my _vimrc file:
>>>
>>>set termencoding=cp936
>>>set encoding=UTF-8
>>>set fileencodings=ucs-bom,utf-8,cp936
>>>setg bomb
>>>set guifont=NSimsun:h12:cDEFAULT
>>>
>>>    and now it can display the .reg file and files containing chinese
characters correctly,:-)
>>>, but the chinese characters of gVim GUI are still gibberishes, :-<
>>
>>Ah, it seems we are making progress. Do you mean the Chinese-language
>>menus are displayed incorrectly, or the Chinese-language messages, or both?
>
>
>    both
>
>
>>If it's the menus, try
>>
>> aunmenu *
>> runtime! menu.vim
>>
>>after setting 'encoding' to UTF-8.
>
>
>     I have just looked at the menu.vim file. I added
>
> 	    echomsg "s:lang is".s:lang
>
>     to the script and found s:lang is zh_CN, so I directly inserted this to
the menu.vim file:
>
>    	    let s:lang = "zh_cn.utf-8"
>
>     before the statement:
>
>   	    exe "runtime! lang/menu_" . s:lang . "*.vim"
>
>     but it doesn't work, I also tried
>
> 	    let s:lang = "zh_cn.gb2312"
>  	    let s:lang = "zh_cn"
>
>     but they donnot work either.
>
>     at last I removed the "let s:lang" statement, and added
>
> 	    let did_menu_trans=1
>
>     to my _vimrc file, and I got an English version menubar. [...]

Altering files in $VIMRUNTIME or in its subdirectories is always a bad
idea, because any upgrade can silently replace any such file.

What happens when you do manually

	 :runtime! delmenu.vim
	 :menutrans clear
	 :set langmenu=utf-8
	 :runtime! menu.vim

? If it doesn't work, try ":set langmenu=cp936" in the 3rd line above
instead.

If one of them works, set the 'langmenu' option accordingly in your
vimrc. That ought to give you menus in Simplified Chinese script.

> Just call me Bruce. Xuzhao is my chinese name in pinyin and is only
> used in my family, not my real name.
>
> Tony is not Douni in pinyi, I'm sorry for the mistake.  I visit this
> page given by you just now:
>
> http://vim.sourceforge.net/tips/tip.php?tip_id=632
>
> and found author is Tony Mechelynck, so I thought you are Tony
> subjectively, :-P . I don't know how to pronounce Douni and Mechelynck
> in English, maybe Douni can be translate to Daoni in pinyin, ^_^?
>
>
Yes, Tony is the English equivalent of my given name (Antoine in French,
hence the A [for Antoine or Anthony] in A.J.). Mechelynck is my family
name. It is a Flemish name (from the Dutch dialect spoken in Ghent,
Belgium), derived from the name "Michael". In English it can be
pronounced as "Meckling". (I translate it into Ukrainian as Mikhalenko
or into Arabic as Mahlank. Since Chinese family names are usually
monosyllabic I suppose I could "sinify" it as Ma as in horse -- one of
the few hanzi I can recognise.)


Best regards,
Tony.

A. J. Mechelynck wrote:
[...]
>  :set langmenu=utf-8
[...]


Oops. :set langmenu=zh_cn.utf-8
or :set langmenu=zh_cn.cp936


Best regards,
Tony.

Lennart Andersen wrote:
> How do I set the $VIMRUNTIME variable?
>
>
You don't. You may or may not set the $VIM variable, and Vim sets
$VIMRUNTIME based on it, or if not found, based (on Windows) on the
directory for the Vim executable, (on Windows or Unix) on the directory
for the help files, (on Unix) on the compiled-in default. For instance,
on W32, if your gvim.exe and your runtime files are in C:\Program
Files\Vim\vim63\ you may leave $VIM unset, or you might use

	 set VIM=C:\PROGRA~1\vim

and gvim (6.3) will set $VIMRUNTIME to C:\PROGRA~1\vim\vim63 -- you may
install gvim 7.0 alpha in parallel and it will set $VIMRUNTIME to
C:\PROGRA~1\vim\vim70aa

On Unix, if your vim executable is in /usr/bin and your runtime files in
/usr/share/vim/vim63/ you may (IIUC) leave $VIM unset, or use (in bash)

	 export VIM=/usr/share/vim

and vim (6.3) will set $VIMRUNTIME to /usr/share/vim/vim63 -- you may
install vim 7.0 alpha in parallel and it will set $VIMRUNTIME to
/usr/share/vim/vim70aa

That way, even with more than one version installed, each version will
have its own runtime files and not disturb the other version.

In both example cases above, leaving $VIM unset is OK because Vim can
reconstruct it. Setting it nevertheless has the advantage that you can
use it even in the shell without loading Vim. So if you have both 6.3
and 7.0 installed, and 6.3 (but not 7.0) is in the $PATH, you can invoke
the other by using (on Windows): %VIM%\vim70aa\gvim


See
	 :help $VIM
	 :help $VIMRUNTIME


Best regards,
Tony.

Hi, Tony:


======= 2005-04-30 13:57:59 A. J. Mechelynck wrote: =======

>Bruce Who wrote:
>> Hi, Douni:
>
>Hi Bruce
>
>>
>>
>>
>> ======= 2005-04-30 11:04:15 A. J. Mechelynck wrote: =======
>>
>>
>>>Bruce Who wrote:
>>>
>>>>Hi, Mechelynck:
>>>>
>>>> I add below code to my _vimrc file:
>>>>
>>>>set termencoding=cp936
>>>>set encoding=UTF-8
>>>>set fileencodings=ucs-bom,utf-8,cp936
>>>>setg bomb
>>>>set guifont=NSimsun:h12:cDEFAULT
>>>>
>>>>    and now it can display the .reg file and files containing chinese
characters correctly,:-)
>>>>, but the chinese characters of gVim GUI are still gibberishes, :-<
>>>
>>>Ah, it seems we are making progress. Do you mean the Chinese-language
>>>menus are displayed incorrectly, or the Chinese-language messages, or both?
>>
>>
>>    both
>>
>>
>>>If it's the menus, try
>>>
>>> aunmenu *
>>> runtime! menu.vim
>>>
>>>after setting 'encoding' to UTF-8.
>>
>>
>>     I have just looked at the menu.vim file. I added
>>
>> 	    echomsg "s:lang is".s:lang
>>
>>     to the script and found s:lang is zh_CN, so I directly inserted this to
the menu.vim file:
>>
>>    	    let s:lang = "zh_cn.utf-8"
>>
>>     before the statement:
>>
>>   	    exe "runtime! lang/menu_" . s:lang . "*.vim"
>>
>>     but it doesn't work, I also tried
>>
>> 	    let s:lang = "zh_cn.gb2312"
>>  	    let s:lang = "zh_cn"
>>
>>     but they donnot work either.
>>
>>     at last I removed the "let s:lang" statement, and added
>>
>> 	    let did_menu_trans=1
>>
>>     to my _vimrc file, and I got an English version menubar. [...]
>
>Altering files in $VIMRUNTIME or in its subdirectories is always a bad
>idea, because any upgrade can silently replace any such file.
>
>What happens when you do manually
>
> :runtime! delmenu.vim
> :menutrans clear
> :set langmenu=utf-8
> :runtime! menu.vim
>
>? If it doesn't work, try ":set langmenu=cp936" in the 3rd line above
>instead.
>
>If one of them works, set the 'langmenu' option accordingly in your
>vimrc. That ought to give you menus in Simplified Chinese script.

      Thanks for your help! Everything is Ok now!

      I add below code to the _vimrc file:

language messages zh_CN.UTF-8

set termencoding=UTF-8
set encoding=UTF-8
set fileencodings=ucs-bom,utf-8,cp936
setg bomb

runtime! delmenu.vim
menutrans clear
set langmenu=zh_cn.utf-8
runtime! menu.vim

      and it's not enough to only ":set langmenu=zh_cn.utf-8", I guess gVim
create the menu before it load the _vimrc file, so we have to delete the menu
and recreate it.


>> Just call me Bruce. Xuzhao is my chinese name in pinyin and is only
>> used in my family, not my real name.
>>
>> Tony is not Douni in pinyi, I'm sorry for the mistake.  I visit this
>> page given by you just now:
>>
>> http://vim.sourceforge.net/tips/tip.php?tip_id=632
>>
>> and found author is Tony Mechelynck, so I thought you are Tony
>> subjectively, :-P . I don't know how to pronounce Douni and Mechelynck
>> in English, maybe Douni can be translate to Daoni in pinyin, ^_^?
>>
>>
>Yes, Tony is the English equivalent of my given name (Antoine in French,
>hence the A [for Antoine or Anthony] in A.J.). Mechelynck is my family
>name. It is a Flemish name (from the Dutch dialect spoken in Ghent,
>Belgium), derived from the name "Michael". In English it can be
>pronounced as "Meckling". (I translate it into Ukrainian as Mikhalenko
>or into Arabic as Mahlank. Since Chinese family names are usually
>monosyllabic I suppose I could "sinify" it as Ma as in horse -- one of
>the few hanzi I can recognise.)

      It's interesting! So I could call you "析瀧", ^_^。

>
>
>Best regards,
>Tony.
>
>.

= = = = = = = = = = = = = = = = = = = =

Best regards,

　　　　　　　　Bruce Who
　　　　　　　　　　2005-04-30

Hi All

I am relatively new to VIM . Recently downloaded the
VIM 6.3 .... Now I am facing some probs with ncurse n
termcap lib .

I downloaded these libs as well. n installed them .
But I still get errors during make .

I am attaching a copy of the configuartion log .

I'll be really grateful if someone could help me out
in this regard .

Best Regards

Varun

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

Thanks, Bruce, for finding out language messages zh_CN.UTF-8. I have had
troubles with Chinese messages when encoding is UTF-8. Now it
is a decent solution.

The only problem is that I cannot put it in _vimrc. Gvim 6.3.67 that I use
will crash on this, even when it is the only line in _vimrc :-(. Anyone
has a clue?

I have had no problems with Chinese and UTF-8 support in other aspects. I
simply need these lines in _vimrc:

   set ambiwidth=double                  " I bet you want this. :h
ambiwidth for details
   set fileencodings=ucs-bom,utf-8,chinese
   set encoding=UTF-8
   language messages en                  " I really hope zh_CN.UTF-8 can
work here

The default font in my Chinese Windows 2000 works quite well for Chinese
files. I would execute the following lines (in a function) if
Western-language files are read:

     set ambiwidth=single
     set encoding=utf-8
     if has('gui_running')
       set guifont=Courier_New:h10:cDEFAULT
     endif

By the way, the pinyin for Tony is Tuo1 Ni2. So maybe I should later call
Tony "Ma Tuoni" :-).

Best regards,

Yongwei





"Bruce Who" <HuXuZhao@...>



         To:     "A. J. Mechelynck" <antoine.mechelynck@...>, "vim"
<vim@...>
         CC:
         Subject:        Re: How to edit .reg files

     I add

                      language messages zh_CN.UTF-8

     to my _vimrc, and all messages are correct now!

     At last, I can view .reg files and files containning chinese using
gVim, all messages are chinese, and get an English menubar. No gibberishes
any more!


Just call me Bruce. Xuzhao is my chinese name in pinyin and is only used
in my family, not my real name.

Tony is not Douni in pinyi, I'm sorry for the mistake.  I visit this page
given by you just now:

http://vim.sourceforge.net/tips/tip.php?tip_id=632

and found author is Tony Mechelynck, so I thought you are Tony
subjectively, :-P . I don't know how to pronounce Douni and Mechelynck in
English, maybe Douni can be translate to Daoni in pinyin, ^_^?

adah:

	 You can add the code to your _vimrc:

language messages zh_CN.UTF-8

set termencoding=UTF-8
set encoding=UTF-8
set fileencodings=ucs-bom,utf-8,cp936
setg bomb

runtime! delmenu.vim
menutrans clear
set langmenu=zh_cn.utf-8
runtime! menu.vim

      It works fine for me except a slight flaw with status line.

======= 2005-04-30 15:36:18 adah wrote: =======

>Thanks, Bruce, for finding out language messages zh_CN.UTF-8. I have had
troubles with Chinese messages when encoding is UTF-8. Now it
>is a decent solution.
>
>The only problem is that I cannot put it in _vimrc. Gvim 6.3.67 that I use
>will crash on this, even when it is the only line in _vimrc :-(. Anyone
>has a clue?
>
>I have had no problems with Chinese and UTF-8 support in other aspects. I
>simply need these lines in _vimrc:
>
>  set ambiwidth=double                  " I bet you want this. :h
>ambiwidth for details
>  set fileencodings=ucs-bom,utf-8,chinese
>  set encoding=UTF-8
>  language messages en                  " I really hope zh_CN.UTF-8 can
>work here
>
>The default font in my Chinese Windows 2000 works quite well for Chinese
>files. I would execute the following lines (in a function) if
>Western-language files are read:
>
>    set ambiwidth=single
>    set encoding=utf-8
>    if has('gui_running')
>      set guifont=Courier_New:h10:cDEFAULT
>    endif
>
>By the way, the pinyin for Tony is Tuo1 Ni2. So maybe I should later call
>Tony "Ma Tuoni" :-).
>
>Best regards,
>
>Yongwei
>
>
>
>
>
>"Bruce Who" <HuXuZhao@...>
>
>
>
>        To:     "A. J. Mechelynck" <antoine.mechelynck@...>, "vim"
<vim@...>
>        CC:
>        Subject:        Re: How to edit .reg files
>
>    I add
>
>                     language messages zh_CN.UTF-8
>
>    to my _vimrc, and all messages are correct now!
>
>    At last, I can view .reg files and files containning chinese using
>gVim, all messages are chinese, and get an English menubar. No gibberishes
>any more!
>
>
>Just call me Bruce. Xuzhao is my chinese name in pinyin and is only used
>in my family, not my real name.
>
>Tony is not Douni in pinyi, I'm sorry for the mistake.  I visit this page
>given by you just now:
>
>http://vim.sourceforge.net/tips/tip.php?tip_id=632
>
>and found author is Tony Mechelynck, so I thought you are Tony
>subjectively, :-P . I don't know how to pronounce Douni and Mechelynck in
>English, maybe Douni can be translate to Daoni in pinyin, ^_^?
>
>
>

= = = = = = = = = = = = = = = = = = = =

Best regards,

　　　　　　　　Bruce Who
　　　　　　　　　　2005-04-30

Hi, Tony:

	 I found it's still not perfect. There is something wrong with the status line
at the bottom of the gVim window which displays filenames, stuff like
75%,Top/Bot.

     I installed a plugin for python and C called ctags.vim. After a .py or .c
file is opened, the plugin try to display the function or class's name which the
cursor is in. And it write the statuslien:

     let &statusline='%<%f %(%h%m%r %)%=%{TagName()} %-15.15(%l,%c%V%)%P'

     it make some gibberishes in the statusline. Maybe it should translate the
string into utf-8 first. But how to? Any hints?

======= 2005-04-30 15:01:36 Bruce Who wrote: =======

>     Thanks for your help! Everything is Ok now!
>
>     I add below code to the _vimrc file:
>
>language messages zh_CN.UTF-8
>
>set termencoding=UTF-8
>set encoding=UTF-8
>set fileencodings=ucs-bom,utf-8,cp936
>setg bomb
>
>runtime! delmenu.vim
>menutrans clear
>set langmenu=zh_cn.utf-8
>runtime! menu.vim
>

= = = = = = = = = = = = = = = = = = = =

Best regards,

　　　　　　　　Bruce Who
　　　　　　　　　　2005-04-30

No, the only thing I need currently is "language messages zh_CN.UTF-8", which
crashes my gvim when put in _vimrc. However, it works OK when I
type it after gvim starts up. I will try other gvim versions later.

Best regards,

Yongwei





"Bruce Who" <HuXuZhao@...>



         To:     "adah@..." <adah@...>, "vim" <vim@...>
         CC:
         Subject:        Re: How to edit .reg files

adah:

                  You can add the code to your _vimrc:

language messages zh_CN.UTF-8

set termencoding=UTF-8
set encoding=UTF-8
set fileencodings=ucs-bom,utf-8,cp936
setg bomb

runtime! delmenu.vim
menutrans clear
set langmenu=zh_cn.utf-8
runtime! menu.vim

      It works fine for me except a slight flaw with status line.

Bruce Who wrote:
> Hi, Tony:
>
>
> ======= 2005-04-30 13:57:59 A. J. Mechelynck wrote: =======
[...]
>
>
>      Thanks for your help! Everything is Ok now!

Good!

>
>      I add below code to the _vimrc file:
>
> language messages zh_CN.UTF-8
>
> set termencoding=UTF-8
> set encoding=UTF-8
> set fileencodings=ucs-bom,utf-8,cp936
> setg bomb
>
> runtime! delmenu.vim
> menutrans clear
> set langmenu=zh_cn.utf-8
> runtime! menu.vim
>
>      and it's not enough to only ":set langmenu=zh_cn.utf-8", I guess gVim
create the menu before it load the _vimrc file, so we have to delete the menu
and recreate it.

Interesting. I wouldn't have guessed it without trying.

[...]
>>Yes, Tony is the English equivalent of my given name (Antoine in French,
>>hence the A [for Antoine or Anthony] in A.J.). Mechelynck is my family
>>name. It is a Flemish name (from the Dutch dialect spoken in Ghent,
>>Belgium), derived from the name "Michael". In English it can be
>>pronounced as "Meckling". (I translate it into Ukrainian as Mikhalenko
>>or into Arabic as Mahlank. Since Chinese family names are usually
>>monosyllabic I suppose I could "sinify" it as Ma as in horse -- one of
>>the few hanzi I can recognise.)
>
>
>      It's interesting! So I could call you "���薊�", ^_^���

I notice that "horse" character at right. But don't family names come
first in Chinese? And how do you pronounce that other character? Wait --
maybe I can find it... Is that upper half (4 strokes) a radical?... Yes,
alias of #125... whose full form is the character in question. R125+0
La嘆 (in Couvreur's dictionary, spelling of the ��cole fran巽aise
d'Extr棚me-Orient -- pinyin tone representation may be different), as in
Laozi (in Couvreur's spelling: La嘆 tz竪u). Aging, old age, also a term of
respect as in laoye "Mister", laodaren "Your Excellency", wfw. "old big
man". Hm, I feel honored, but not sure I deserve it, I'm only 54 after
all -- or should I call you Lao Hu?


Best regards,
Tony.

Bruce Who wrote:
> Hi, Tony:
>
>  I found it's still not perfect. There is something wrong with the status line
at the bottom of the gVim window which displays filenames, stuff like
75%,Top/Bot.
>
>     I installed a plugin for python and C called ctags.vim. After a .py or .c
file is opened, the plugin try to display the function or class's name which the
cursor is in. And it write the statuslien:
>
>     let &statusline='%<%f %(%h%m%r %)%=%{TagName()} %-15.15(%l,%c%V%)%P'
>
>     it make some gibberishes in the statusline. Maybe it should translate the
string into utf-8 first. But how to? Any hints?
>
[...]

I don't know. I don't display function names in the status line, but
encodings, using

	 :set statusline=%<%f\
%h%m%r%=%k[%{(&fenc==\"\")?&enc:&fenc}%{(&bomb?\",BOM\":\"\")}]\
%-14.(%l,%c%V%)\ %P

(all on one line, and there are 3 spaces in it). I guess when using
non-standard status lines we're on our own; but I see you use a
user-defined function TagName(). If the error is in the output of that
function, maybe it should be enough to modify the function?


Best regards,
Tony.

Hello,

I have two Vims installed on my machine: Version 5.7 & Version 6.2

I generally use version 5.7 because of its speed advantages over version
6.2. But if i need to use specific features/command dof version 6.2
while running version 5.7. is it possible...?
eg version 5.7 does not support vertical split, which is there in 6.2.
SO how can i do vertical spit in version 5.7.
Are there any files/variables which i can source/set in 5.7 to use
specific 6.2 features.

Regards
Yogesh

--
==================================
Yogesh Sharma

5F267,Extn 2606
Texas Instrument
Bangalore, INDIA
E - yogeshsharma@...
O - +91 80 2504 8606
M - +91 93 4220 1936
==================================

Yogesh Sharma wrote:
> Hello,
>
> I have two Vims installed on my machine: Version 5.7 & Version 6.2
>
> I generally use version 5.7 because of its speed advantages over version
> 6.2. But if i need to use specific features/command dof version 6.2
> while running version 5.7. is it possible...?
> eg version 5.7 does not support vertical split, which is there in 6.2.
> SO how can i do vertical spit in version 5.7.
> Are there any files/variables which i can source/set in 5.7 to use
> specific 6.2 features.
>
> Regards
> Yogesh
>
To get specific version 6 features you need to have them compiled-in, so
sourcing the version 6 scripts won't be enough. The version 5 executable
cannot do vertically split windows no matter which scripts you source or
which variables you set -- the feature is just not compiled in it.
Similarly, to get lists or dictionaries you need a version 7 executable,
sourcing version 7 scripts isn't enough.

BTW, even version 6.2 is outdated by some six hundred bugfixes or so.
You might try installing the current 6.3.071 and see how it compares
with it.


Best regards,
Tony.

Tony :



======= 2005-04-30 17:04:49 A. J. Mechelynck wrote: =======

>Bruce Who wrote:
>> Hi, Tony:
>>
>>  I found it's still not perfect. There is something wrong with the status
line at the bottom of the gVim window which displays filenames, stuff like
75%,Top/Bot.
>>
>>     I installed a plugin for python and C called ctags.vim. After a .py or .c
file is opened, the plugin try to display the function or class's name which the
cursor is in. And it write the statuslien:
>>
>>     let &statusline='%<%f %(%h%m%r %)%=%{TagName()} %-15.15(%l,%c%V%)%P'
>>
>>     it make some gibberishes in the statusline. Maybe it should translate the
string into utf-8 first. But how to? Any hints?
>>
>[...]
>
>I don't know. I don't display function names in the status line, but
>encodings, using
>
> :set statusline=%<%f\
>%h%m%r%=%k[%{(&fenc==\"\")?&enc:&fenc}%{(&bomb?\",BOM\":\"\")}]\
>%-14.(%l,%c%V%)\ %P
>
>(all on one line, and there are 3 spaces in it). I guess when using
>non-standard status lines we're on our own; but I see you use a
>user-defined function TagName(). If the error is in the output of that
>function, maybe it should be enough to modify the function?

      Thanks for your hint! It seems a daunting job for me. TagName() is a
function defined in ctags.vim distributed by another vim user. When I have
enough time I'll look into it.

>
>Best regards,
>Tony.
>
>.

= = = = = = = = = = = = = = = = = = = =

Best regards,

　　　　　　　　Bruce Who
　　　　　　　　　　2005-04-30

My test shows that a single line of

language messages zh_CN.UTF-8

in _vimrc will crash gvim.exe 6.3, 6.3.67, and 6.3.71 on Chinese Windows
2000.  The patched versions were downloaded from Antoine's site.

When testing with gvimd.exe 6.3.71 (from Antoine's site), I got the
following information (output from Dr MinGW).  Hope the Vim developers
will find it useful.

My msvcrt.dll is dated 2003-6-19, sized 286,773 bytes, and versioned
6.1.9844.0.

Anyone else found the same crash problem?

Best regards,

Yongwei

---------------------------------------

gvimd.exe caused an Access Violation at location 7800fa97 in module
msvcrt.dll Reading from location 00000005.

Registers:
eax=00000005 ebx=00000073 ecx=00000005 edx=7fffffff esi=7ffffffe
edi=00000800
eip=7800fa97 esp=0022e018 ebp=0022e270 iopl=0         nv up ei pl nz na po
nc
cs=001b  ss=0023  ds=0023  es=0023  fs=0038  gs=0000 efl=00000206

Call stack:
7800FA97  msvcrt.dll:7800FA97  setvbuf
780238DC  msvcrt.dll:780238DC  sprintf
0042E006  gvimd.exe:0042E006  do_sub_msg  ex_cmds.c:4289
0042DE3C  gvimd.exe:0042DE3C  do_sub  ex_cmds.c:4243
00439990  gvimd.exe:00439990  do_one_cmd  ex_docmd.c:2474
00437582  gvimd.exe:00437582  do_cmdline  ex_docmd.c:991
00424C84  gvimd.exe:00424C84  ex_execute  eval.c:8727
00439990  gvimd.exe:00439990  do_one_cmd  ex_docmd.c:2474
00437582  gvimd.exe:00437582  do_cmdline  ex_docmd.c:991
0042671D  gvimd.exe:0042671D  call_user_func  eval.c:9562
0041E1B6  gvimd.exe:0041E1B6  call_func  eval.c:3192
0041DEB0  gvimd.exe:0041DEB0  get_func_var  eval.c:3051
0041BBCF  gvimd.exe:0041BBCF  ex_call  eval.c:1345
00439990  gvimd.exe:00439990  do_one_cmd  ex_docmd.c:2474
00437582  gvimd.exe:00437582  do_cmdline  ex_docmd.c:991
0042671D  gvimd.exe:0042671D  call_user_func  eval.c:9562
0041E1B6  gvimd.exe:0041E1B6  call_func  eval.c:3192
0041DEB0  gvimd.exe:0041DEB0  get_func_var  eval.c:3051
0041BBCF  gvimd.exe:0041BBCF  ex_call  eval.c:1345
00439990  gvimd.exe:00439990  do_one_cmd  ex_docmd.c:2474
00437582  gvimd.exe:00437582  do_cmdline  ex_docmd.c:991
00434A63  gvimd.exe:00434A63  do_source  ex_cmds2.c:2353
0043417B  gvimd.exe:0043417B  source_callback  ex_cmds2.c:1852
00434372  gvimd.exe:00434372  do_in_runtimepath  ex_cmds2.c:1936
004341A6  gvimd.exe:004341A6  cmd_runtime  ex_cmds2.c:1866
00466BF9  gvimd.exe:00466BF9  VimMain  main.c:1467
0052A8FD  gvimd.exe:0052A8FD
0052D23A  gvimd.exe:0052D23A
004011E7  gvimd.exe:004011E7
00401238  gvimd.exe:00401238
77E8893D  KERNEL32.dll:77E8893D  ProcessIdToSessionId

Hi Tony,

Prefixing Lao before a family name is somehow similar to calling a person
"Old Chap". It is generally used when calling a person older than the
speaker, or at least a person that looks like older than the speaker. So I
think most Chinese here could call you "Lao Ma" :-). As a phrase "Lao Ma"
also means "old horse", probably a precise description for someone as
hard-working as you.

Some friends used to call me "Lao Wu" jokingly, even when they are really
older than me. I am just above 30, a generation before you indeed.
However, an old person in your age will never call me "Lao Wu", even in
kidding. They will probably call me "Xiao Wu" (絨����), i.e. "Little Wu".

Best regards,

Yongwei





"A. J. Mechelynck" <antoine.mechelynck@...>
2005-04-30 16:50


         To:     HuXuZhao@...
         CC:     vim <vim@...>
         Subject:        Re: How to edit .reg files

>      It's interesting! So I could call you "���薊�", ^_^���

I notice that "horse" character at right. But don't family names come
first in Chinese? And how do you pronounce that other character? Wait --
maybe I can find it... Is that upper half (4 strokes) a radical?... Yes,
alias of #125... whose full form is the character in question. R125+0
La嘆 (in Couvreur's dictionary, spelling of the ��cole fran巽aise
d'Extr棚me-Orient -- pinyin tone representation may be different), as in
Laozi (in Couvreur's spelling: La嘆 tz竪u). Aging, old age, also a term of
respect as in laoye "Mister", laodaren "Your Excellency", wfw. "old big
man". Hm, I feel honored, but not sure I deserve it, I'm only 54 after
all -- or should I call you Lao Hu?


Best regards,
Tony.

adah@... wrote:
> Hi Tony,
>
> Prefixing Lao before a family name is somehow similar to calling a person
> "Old Chap". It is generally used when calling a person older than the
> speaker, or at least a person that looks like older than the speaker. So I
> think most Chinese here could call you "Lao Ma" :-). As a phrase "Lao Ma"
> also means "old horse", probably a precise description for someone as
> hard-working as you.

:-D lol.

>
> Some friends used to call me "Lao Wu" jokingly, even when they are really
> older than me. I am just above 30, a generation before you indeed.
> However, an old person in your age will never call me "Lao Wu", even in
> kidding. They will probably call me "Xiao Wu" (絨����), i.e. "Little Wu".
>
> Best regards,
>
> Yongwei
[...]

At 54, I don't feel old yet, thank you. Both my parents are still alive,
and when I meet someone your age, I prefer to approach him on a level
footing. So, my dear Yongwei, we may call each other Lao Ma "Old horse"
and Xiao Wu "Little Boast" in kidding ;-) ; but most of the time you can
call me Tony. -- BTW, one of my nephews is a year or two out of college
and the other is still studying, meaning they are still some years
younger than you. (And if I read the definition of the "three classes of
old people", the San Lao, in my Classical Chinese dictionary, it applies
to people of ages 80, 100 and 120. I'm not there yet, thank you ;-) .)


Best regards,
Tony.

The configure is not finding your ncurses library, but it appears
the result is cached from a previous configure attempt.

Did you do a "make distclean" in the src/ directory after installing
the libraries?  Try that and then try the configure again.

gm

On Sat, Apr 30, 2005 at 12:26:20AM -0700, Varun Gupta wrote:
> Hi All
>
> I am relatively new to VIM . Recently downloaded the
> VIM 6.3 .... Now I am facing some probs with ncurse n
> termcap lib .
>
> I downloaded these libs as well. n installed them .
> But I still get errors during make .
>
> I am attaching a copy of the configuartion log .
>
> I'll be really grateful if someone could help me out
> in this regard .
>
> Best Regards
>
> Varun

--
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Gregory H. Margo
Home: greg at margofamily dot org, gmargo at yahoo dot com or pacbell dot net

On Sat, Apr 30, 2005 at 02:42:31PM +0530, Yogesh Sharma wrote:
> Hello,
>
> I have two Vims installed on my machine: Version 5.7 & Version 6.2
>
> I generally use version 5.7 because of its speed advantages over version
> 6.2. But if i need to use specific features/command dof version 6.2
> while running version 5.7. is it possible...?
> eg version 5.7 does not support vertical split, which is there in 6.2.
> SO how can i do vertical spit in version 5.7.
> Are there any files/variables which i can source/set in 5.7 to use
> specific 6.2 features.
>
> Regards
> Yogesh

You don't say what kind of speed problems you're having, but I suspect
it's start-up speed.  Best bet is to load the latest (6.3.71) and
optimize that for speed by using "set noloadplugins" and manually
loading only the plugins you want with the "runtime" command.
Also you can use the -u command line option to avoid loading any
system-level vimrc file.  And -X to avoid any attempt to contact
the X server.

gm

--
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Gregory H. Margo
Home: greg at margofamily dot org, gmargo at yahoo dot com or pacbell dot net

Is it possible to use the set the statusline option differently for each window?


Scott Cegielski
scegielski@...



__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

Yes, but you must code an autocmd to do this.
BufEnter event should work.
Defining a funtion to do this would give you the flexibility you need.

HTH,
Dave





----- Original Message -----
From: Scott Cegielski [scegielski@...]
Sent: 04/30/2005 02:50 PM
To: Vim List <vim@...>
Subject: Setting local status lines

Is it possible to use the set the statusline option differently for each window?


Scott Cegielski
scegielski@...



__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

Hi,

In many cases, the comments posted for a tip are as useful and
informative as the tip itself. In this regard, it would also be very
helpful to have the additional notes also as part of the download
vimtips.txt) Even more helpful would be the addition of the tip karma
too.

Also for the same reason it would be very useful to have a link on the
tips search page which
will sort the tips based on the most recently posted comments
(activity based sort)

Thanks and regards,
Rajkiran

PS: This is probably not the right place to post this request but the
feature request page at http://vimonline.sourceforge.net/ seems to be
rather inactive

Hi,

On 4/30/05, Scott Cegielski <scegielski@...> wrote:
> Is it possible to use the set the statusline option differently for each
window?
>
>

In Vim7, the 'statusline' option is a global option with a local value.
It can be set either globally or locally to a specific window.

- Yegappan

What does it mean when

	 :echo bufnr("file1")

returns, say, 20, and

	 :echo bufnr("file2")

also returns 20, while
	 :ls!
says

   2  a   "file1"                        line 47
  20 %a + "file2"                        line 169

that "file1" is 2, and "file2" is 20?  The rest of the function calls
also seem to be confused about it, i.e.  bufwinnr("file1") and
bufwinnr("file2") both return the same window # 2.  Only typing

	 echo bufname("%")

from each window yields the right answer.  Aren't buffer numbers supposed to
be unique?

I have a script which uses async background events to keep hopping from
a user's window to it's own window, where it does an update, then hops
back to the user's window until the next cycle.  It seems to be
confusing something ( in addition to me ).