Don't know what you mean by this, the "InputLanguageChanged" event is raised
when the *user* changes the input language at the system level, all windows
application running in the users login session will get this event (a
windows message WM_INPUTLANGCHANGE) when the user changes the input
language.

Consider following sample:

using System;
using System.Drawing;
using System.ComponentModel;
using System.Windows.Forms;
using System.Threading;

public class Form1 : System.Windows.Forms.Form
{
   Label lbl = new Label();
   public Form1()
   {
       this.Controls.Add(lbl);
       lbl.Size = new Size(400, 48);
       lbl.Padding = new Padding(5);
       // uncomment if you want to handle the event in the
InputLanguageChangedEventHandler
       //this.InputLanguageChanged += new
InputLanguageChangedEventHandler(languageChange);
   }
   private void languageChange(Object sender, InputLanguageChangedEventArgs
e)
   {
       lbl.Text = e.InputLanguage.Culture.ToString();
   }
   protected override void WndProc(ref Message m)
       {
           if(m.Msg == 0x0051) // WM_INPUTLANGCHANGE
           {
               lbl.Text = string.Format("Posting Thread: {0} \n{1}",
Thread.CurrentThread.ManagedThreadId, m);
           }
           base.WndProc(ref m);
       }
   public static void Main(string[] args)
   {
       Application.Run(new Form1());
   }
}

This illustrates how you can add your own handler by overriding WndProc, or
using the predefined handler for this message, however, both handle the same
message!.

Willy.

Sorry.  I didn't see anything in your original message that said that.

You may have to go with p/invoke.  I'm not really sure.  I don't know of a  
managed way to hook window messages generally.

If there's a way to do it in managed code, there are at least a couple of  
other people who read this newsgroup that are more familiar with such  
things and would know.  Hopefully they'll see this thread and reply.

Pete