On 03/08/2002 01:11:37 PM "Chris Pratley" wrote:
>I should point out that Word2002 does not actually support WM_UNICHAR
>(actually no OfficeXP app does).
My mistake (how could I forget -- I was disappointed when it didn't quite
make it). Word 2002 still needs WordLink, but Publisher 2002 does support
WM_UNICHAR.
>However, the recommended method for communicating in Unicode to apps
>including Office is to
>a) use an NT-based OS such as NT4/Win2000/WindowsXP. Everything just
>works.
I quite agree. There are many users who will be on Win98 for a while
though (at least, many that I need to support).
>b) or use the Text Services Framework, which is shipped in WindowsXP and
>also in OfficeXp. This is what, I believe Keyman actually uses now to
>get Unicode in Word2002 on Win98/Me - or the specific Word (object model
>based) method Peter mentions below.
Not yet. It will in Keyman 6.
I'll revise my summary in relation to MS apps and Win9x/Me
Unicode characters that can be input using
Keyman 5 Keyman 6 (when released)
----------------------------------------------------------------------------
Word 2000 limited by limited by
Windows codepages Windows codepages
Word 2000 w/ WordLink all of BMP all (planes 0 - 16)
other Office 2000 apps limited by limited by
Windows codepages Windows codepages
Word 2002 limited by all (planes 0 - 16)
Windows codepages
Word 2002 w/ WordLink all of BMP all (planes 0 - 16)
Publisher 2002 all of BMP all (planes 0 - 16)
other Office XP apps limited by limited by
Windows codepages Windows codepages
- Peter
---------------------------------------------------------------------------
Peter Constable
Non-Roman Script Initiative, SIL International
7500 W. Camp Wisdom Rd., Dallas, TX 75236, USA
Tel: +1 972 708 7485
E-mail: <peter_constable@sil.org>
This archive was generated by hypermail 2.1.2 : Fri Mar 08 2002 - 16:14:24 EST