We have had several questions recently about the differences between
NT/Japanese and the US Version of NT. I know that NT is internally Unicode
so I would expect most (all?) the differences to be resource strings.
Things like the Kernel and device drivers I would expect to be the same.
Does anyone know for sure if this is the case? If there are differences,
what are those differences?
That’s basically it. Applications that are written for ANSI need to be
converted to use either MBCS or UNICODE. The biggest difference to the
operation of the OS (esp for the user) is the presence of the IME (Input
Method Editor) which is used to enter the kanji, katakana or hiragana
symbols. What’s cool about these things is that you can type in
“Mitsubishi” (as an example) and the hiragana symbols will appear
automatically. If you subscribe to MSDN, you can get the foreign versions
of MS software. NT drivers will run unmodified on NT-J, but you’ll have to
recompile them if you want them to use any japanese resources. Typically
the registry entries that services/drivers use are the same as the US
version for compatibility purposes.
Regards,
Paul Bunn, UltraBac.com, 425-644-6000
Microsoft MVP - WindowsNT/2000
http://www.ultrabac.com
-----Original Message-----
From: Steve Whitman [mailto:xxxxx@cognex.com]
Sent: Monday, August 07, 2000 11:13 AM
To: NT Developers Interest List
Subject: [ntdev] NT-J Question
We have had several questions recently about the differences between
NT/Japanese and the US Version of NT. I know that NT is internally Unicode
so I would expect most (all?) the differences to be resource strings.
Things like the Kernel and device drivers I would expect to be the same.
Does anyone know for sure if this is the case? If there are differences,
what are those differences?
Thank you everyone for the information. The answers were what I expected
but I needed to verify it. We are currently experiencing a DMA to video
memory problem with one of our products but it only occurs when we boot the
system with NT-J.
BTW, I do subscribe to MSDN and have all the international versions.
-----Original Message-----
From: Paul Bunn [mailto:xxxxx@ultrabac.com]
Sent: Monday, August 07, 2000 2:29 PM
To: NT Developers Interest List
Subject: [ntdev] RE: NT-J QuestionThat’s basically it. Applications that are written for ANSI
need to be
converted to use either MBCS or UNICODE. The biggest
difference to the
operation of the OS (esp for the user) is the presence of the
IME (Input
Method Editor) which is used to enter the kanji, katakana or hiragana
symbols. What’s cool about these things is that you can type in
“Mitsubishi” (as an example) and the hiragana symbols will appear
automatically. If you subscribe to MSDN, you can get the
foreign versions
of MS software. NT drivers will run unmodified on NT-J, but
you’ll have to
recompile them if you want them to use any japanese
resources. Typically
the registry entries that services/drivers use are the same as the US
version for compatibility purposes.Regards,
Paul Bunn, UltraBac.com, 425-644-6000
Microsoft MVP - WindowsNT/2000
http://www.ultrabac.com-----Original Message-----
From: Steve Whitman [mailto:xxxxx@cognex.com]
Sent: Monday, August 07, 2000 11:13 AM
To: NT Developers Interest List
Subject: [ntdev] NT-J QuestionWe have had several questions recently about the differences between
NT/Japanese and the US Version of NT. I know that NT is
internally Unicode
so I would expect most (all?) the differences to be resource strings.
Things like the Kernel and device drivers I would expect to
be the same.
Does anyone know for sure if this is the case? If there are
differences,
what are those differences?
You are currently subscribed to ntdev as: xxxxx@cognex.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)