Last July, I posted a blog about the current state of our Unicode support. Here it is…
We had planned to wait until the next major release of GroupWise to finish enabling the Windows Client for Unicode. Thanks to some excellent team work by the Windows Client team, we are happy to report that the Windows Client will be unicode enabled for 8.0.1.
Here are the changes that have happened for 8.0.1.
– We are now compiling Unicode for all components of the Windows Client
– All input points are now Unicode enabled
– File System access, read/write/paths, mixed os/client issues are now all resolved
– mixed language issues in the same message are resolved
– mixed os/client language issued resolved. running OS in one language and GW in another
– searching messages, address book data is resolved
– Entire interface is now unicode enabled
– The correct fonts are being used to display unicode characters
– characters passing into the GroupWise system are properly handled
Linux/Mac Clients as well as WebAccess are already unicode enabled.
What is missing?
There are a few areas of GroupWise that we are not planning on enabling for unicode. The administrative piece – using ConsoleOne – is not and we are not planning on making this piece unicode enabled.
The MAPI providers are not unicode enabled. These are the providers that facilitate our Outlook Connector technology. There is still significant work to be done in order to enable this component. Making this unicode enabled is not part of our current plans either.
So – given what we have accomplished and what we have decided not to do 🙂 We will declare when 8.0.1 ships to be Unicode enabled!!