Thanks for your passionate concerns. On Aug 3, 11:32 pm, "Shawn Y. Kim" <[EMAIL PROTECTED]> wrote: > On 8월3일, 오후6시16분, "Edward L. Fox" <[EMAIL PROTECTED]> wrote: > > > > > Hi Kiwon, > > > On 8/3/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > > Thanks Edward. > > > > It works just in compiling manner, not actual. > > > Hangul inputting is incorrect, all is shown as broken characters. > > > Sorry but I know nothing about Hangul input. Could you give me a brief > > introduction of the basic usage of Hangul input? That is, how do I set > > up the Hangul input and what result is expected? Then I could do some > > basic debugging about this problem. > > > Any way, as the Vim build-in Hangul input conflicts with XIM > > interface, I think you'd better enable XIM interface rather than > > Hangul interface, then you could use some more powerful input method > > engine such as SCIM instead. > > > > By the way, what does the "bottom-posting or interlaced-posting" mean? > > > Is it "Reply to Author"? > > > FYI > > >http://en.wikipedia.org/wiki/Posting_style > > > > Sorry for bothering you. I'm just first time here. > > > Just feel free to post any thing here. All people here are very > > friendly. But you should obey the basic rules and the principles here. > > For example, bottom-posting. :-) > > > > Best regards, > > > Kiwon Um > > > [...] > > > Cheers, > > > Edward L. Fox > > Hi, Kiwon. > > It seems that you were trying to compile vim using following options > combined together: > > --enable-hangulinput > --enable-xim=no > --enable-gui=gtk2 > --enable-fontset > --enable-multibyte > --enable-multilang > > The problem that caused the compile error is that the hangulinput > module depends on xfontset. > And the fontset feature causes sort of "conflict" with gtk2. > Gtk2 has whole different font system than that of gtk1.2. > > I've also been through the same what you're going through. > > There could be a couple of solutions : > > 1. You could just use your xim. Try to configure vim with these > options : > --enable-xim --enable-gui=gtk2 --enable-multibyte --enable-multilang > 2. If you really hate XIMs like SCIM and nabi, > 2-1. you coluld choose to use gtk instead of gtk2 > --enable-hangulinput --enable-gui=gtk --enable-multibyte --enable- > multilang --enable-xim=no --enable-fontset > 2-2. If you want to use the built-in hangulinput module with GTK2, > there's a way. I'm gonna describe how to do that later. > These solutions worked well. Now I'm just using VIM with SCIM.
But still one more question... I've tested something more with Hangul i.e. Korean text. I have some 'euckr' encoded text files but my VIMs (such gvim or vim) cannot read/show these files correctly. Although I set 'encoding=euckr' and 'fileencoding=euckr or utf8', it show me some broken characters. I think it might be a quite different problem with --enable- hangulinput. Anyhow I just want to resolve Hangul-cencerned problems. > Above, I can see Mr.Fox has posted a solution about this. Frankly, I > didn't really tried that one out. > I, however, got another one, though it has a "critical" limitation. > Here it is: > > shawn.ygdrasil:~/work/vim7/src$ svn diff feature.h > Index: feature.h > =================================================================== > --- feature.h (revision 392) > +++ feature.h (working copy) > @@ -674,7 +674,10 @@ > * turn to english mode > */ > # if !defined(FEAT_XFONTSET) && defined(HAVE_X11) > -# define FEAT_XFONTSET /* Hangul input > requires xfontset */ > +# if !defined(HAVE_GTK2) > +# define FEAT_XFONTSET /* Hangul input > requires xfontset > + only if not featured with > gtk2 */ > +#endif > # endif > # if defined(FEAT_XIM) && !defined(LINT) > Error: You should select only ONE of XIM and HANGUL INPUT > shawn.ygdrasil:~/work/vim7/src$ > > The one thing that may be bothering you when you use this patch is > that you HAVE TO always useeuc-kras your encoding. > If the locale settings of your machine is UTF-8, you've gotta add > these lines to your .vimrc file : > > set encoding=euc-kr > set fileencoding=utf-8 > > As to the details of encoding and fileencoding, refer to the vim help > page. > > Except for that, it works great with GTK+2 with alti-aliased fonts, > easy to set font, huh? > But, personally, I prefer to use GTK+1.2 with rasterized, highly- > optimized fonts like sun-gothic + fixed combination. > I didn't try these yet. > Any way, good look. > > BRGD. > Shawn from Seoul ;-) It was my extremely short thought to get rid of the --enable- hangulnput fixture. I didn't care about persons who should use that. Thanks again for your cares. Best regards, Kiwon Um --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
