Important: The information in this document is obsolete and should not be used for new development.
Dictionary Manager Limitations
Consider these limitations before using the Dictionary Manager:
In summary, the Dictionary Manager is best for constructing user dictionaries of moderate size. Nevertheless, it is possible and in some cases it may be practical to use the Dictionary Manager for a main dictionary also.
- The Dictionary Manager does not perform data compression. Your input method can compress part of the information before submitting it to the Dictionary Manager--but such compression would make your dictionary nontransferable and thus defeat a major purpose of using the Dictionary Manager.
- The Dictionary Manager utilizes partial resource reading and writing to manipulate the actual data in a dictionary. Hence, each dictionary may not exceed 16 MB, a Resource Manager limitation.
- The user cannot edit an active dictionary (one currently being used by an input method). This also is a Resource Manager limitation.
- If you are developing a sophisticated input method, you may decide not to convert your main dictionaries into the Dictionary Manager format, because you may not want to publicize the keys and associated data in your main dictionaries.
- It may not even be practical to convert your main dictionaries. For example, several input methods contain gigantic--and significantly compressed--main dictionaries. In such cases, the conversion and decompression of dictionaries into Dictionary Manager format might greatly increase the size of your dictionary.