--- Forwarded Message from "Kanig, David" <[log in to unmask]> ---

>Subject: Arabic input in Windows XP
>Date: Wed, 24 Sep 2008 12:27:31 -0400
>Thread-Topic: Arabic input in Windows XP
>Thread-Index: AckeYnFK172DuMswSN+4BfW3wpEQpw==
>From: "Kanig, David" <[log in to unmask]>
>To: <[log in to unmask]>

Have you experienced anomalous behavior with enabling input for Arabic
in Windows XP?
 
I'm using Windows XP SP2 on a Mac Intel platform, with Boot Camp, bound
to Active Directory, and held in stasis by DeepFreeze.  Users log in by
authenticating to Active Directory.  Windows then spawns a user home
directory from C:\Documents and Settings\Default User.  That default
user profile has been copied from a local prototype user, for whom input
methods have been enabled for several languages, including Arabic.  In
production, when an AD authenticated user logs in, his spawned profile
is properly enabled for all the languages set up for the prototype user
*except Arabic.*  The AD user can enable Arabic, but this is
impracticable because it has to be done each for every logon to a frozen
machine.  
 
What could be causing Arabic to be dropped from the spawned profile?  

~~~~~~~~~~~~~~~~~~~~~~~ 
David Kanig 
Manager, Technical Services 
Language Resource Center 
Brown University Box 1935 
Providence, RI 02912 
  
(401) 863-7090 office 
(401) 641-0431 cell  



 
***********************************************
LLTI is a service of IALLT, the International Association for
Language Learning (http://iallt.org/), and The Consortium for Language
Teaching
and Learning (http://www.languageconsortium.org/).
Join IALLT at http://iallt.org.
Otmar Foelsche, LLTI-Editor ([log in to unmask])
***********************************************