This page contains plans for a future release of HFST python API.

Currently, we have HfstBasicTransducer, but a more descriptive name would be HfstMutableTransducer.

Maybe not a separate class for each exception but subclass(es) of RuntimeError?

A more coherent way of handling and special characters (epsilon, unknown, identity, flag diacritics, space, colon) when converting between text and binary formats. Could long names, e.g. (@_UNKNOWN_SYMBOL_@) be always short (?) by default?

Also, default for handling flag diacritics varies among the python API functions as well as between python API and command line tools.

They currently differ between HFST command line tools (options) and python API. Should they be the same?

• Three or four digits?
• Semantic versioning?
• Version numbers separate from HFST command line tools?