| |
Unicode - What is it, and how can I take advantage of it?
This is just a short note to describe the status of the Unicode work which is coming up soon in the FirstClass 9.0 release.
First, a bit of review:
"Traditionally, FirstClass (like most operating systems) has used multiple character sets to support non-English languages. This has led to various limitations, including difficulty supporting multiple character sets in a single document and difficulty in viewing multiple character sets on different operating systems. As a result of these problems, operating systems have adopted a new unified character encoding called Unicode, which allows all possible national characters to be viewed on all platforms.
The new Unicode support in FirstClass 9 will enable all FirstClass applications to include all possible national characters. This will include message, document bodies, forms fields, and even system data such as names, User IDs, and passwords. Unicode support will be fully integrated into FirstClass Internet Services for seamless inbound and outbound mail and web publishing with non-English characters."
The good news is that FirstClass 9.0 is the first release that includes Unicode functionality. All of the major FirstClass applications and services have been updated to fully support Unicode, in all areas of the product. This includes message bodies, conference and mailbox listings, user names, and even user IDs and passwords. Since Unicode content consumes more bytes to store the more complex data, we have also extended the allowable length for names, user IDs, and passwords.
However, in the process of building Unicode into FirstClass, we have also run into a number of complications, which we would like to explain thoroughly.
First, Unicode is not particularly well supported in older versions of the operating systems which FirstClass runs on. Speaking broadly, Unicode will require us to run on Windows 2000 or newer (Windows) and OS 10.3 or later (Mac). Linux users generally run very recent builds, so this should not be a problem for them. Therefore,
There is no Unicode solution for users on Windows 95, Windows 98, Windows NT 4, and Mac OS 8 or OS 9.
Second, Unicode content in system data such as the user ID and password will make fundamental changes in logins, etc. Therefore,
You will need to ensure that all of the services modules in your FirstClass system are upgraded to Unicode-aware versions before enabling Unicode.
This includes not just Internet Services but Voice Services, Directory Services, Synchronization Services and Application Services. In some cases (e.g. Voice Services) the required changes are in the 8.3 versions, but we suggest that you check your particular configuration with FirstClass Support.
Third, because the numerical values of the extended characters have changed, the saved password authentication data has also changed. Therefore
User IDs and passwords with extended (non-English) characters saved with old versions of the client must be reentered the first time a user logs in with the FirstClass 9.0 client.
As you can see, if you are planning to use Unicode support right away, the deployment of FirstClass 9 will require substantial planning and care. We highly recommend that you stage your deployment of FirstClass 9 so that all components are upgraded simultaneously.
All of the changes described above are independent of actually creating and using Unicode content inside of FirstClass. If you are satisfied with the current handling of character sets in FirstClass (e.g. you use English) then the following probably does not apply to you, and you can breath a sigh of relief. You may continue to use any vintage client you want, with a few restrictions (a long user ID or a Unicode password, for example, would require a FirstClass 9 client).
If, however, you wish to actually use Unicode content on your server (e.g. you use a language other than English, or you run an English server with multilingual users), there are an additional set of complex issues you must consider.
It is important to understand that FirstClass 9 is the first release of the client to support Unicode. To put this another way, all versions of the FirstClass Client which are 8.3 or older have no way to display, edit, or compose Unicode content. So, while you will be able to use a FirstClass 9 client to add Unicode content to fields in forms (for example, you can enter Unicode in conference names, in the subject of a message, in the Company name of a contact, etc.) you will only be able to see that Unicode content if you use a FirstClass 9 or later client. In the case of web/POP/IMAP clients, you will need to make sure that Internet Services is upgraded to FirstClass 9.0 as well.
If a user does log in with an older client and sees Unicode forms data, the FirstClass server will do it's very best to translate that forms data into the older client's native character set. The quick rule of thumb is that characters which displayed correctly in the 8.3 or older clients will continue to display correctly, but new Unicode-only characters will not be displayed on older clients. Therefore,
Users must be running the FirstClass 9 client to see Unicode data in forms, names, directories, mailbox listing and conference listings.
Finally, there is the issue of Unicode data in the body of messages and documents. Once again, this will require a FirstClass 9 or later client to create the Unicode content. However, unlike field data and listings, the server is unable to translate document and message content back into non-Unicode. If a user with a pre-9 client opens a Unicode message or document, the message display will be corrupted. Furthermore, if a user with a pre-9 client opens an editable Unicode message or document (e.g. an unsent message) then the user will be prevented from making any changes.
So, this means that if you create Unicode content on your server, users with version 8.3 and older clients will have no way to read messages which have been posted in Unicode and no way of editing Unicode content. Therefore,
If you wish to create Unicode content on your server you will first need to ensure that all of your users have upgraded to FirstClass 9.0 clients.
Obviously, this is a complex step, and is not to be taken lightly. To ensure that this is carefully managed, all FirstClass 9.0 upgrade servers will ship with the ability to create Unicode switched off. We recommend that this only be switched on after consultation with the FirstClass Support Team.
| ||