For developers, please add new entry for your plans.

4. Follow the idea from kcwu to adapt some routines of libtabe, and
   seek for better way to share resources.
  a) support same phrase in different phones.
5. Perform optimization on libchewing in the following aspects:
  a) hashed data stored in binary form.
    a-1) Follow kcwu's pack-chewing-dat.txt for compacting.
  b) support memory-limited applications.
7. Migrate to Unicode
8. Auto calculate the size of phrase data base.
9. Provide API for querying Keybaord Mapping information.
  a) provide zh_TW translation of corresponding keybaord mapping.
10. all APIs should have the same namespace Chewing_blah_blah.
11. Abstract the I/O layer
  a) provide thin and efficient I/O helper functions to perform the
     operations, such as open/create specific phrase file, query,
     insert, remove, and bind to some system facilities.
  b) the backend of the I/O layer could be Standard C file operations,
     IIIMF's namespace I/O, and even database, so that we could give
     leverage to incoming 0.3.x branch.
