FST Determinization only works for acceptors and should be enhanced to support transducers

[steveash]

Currently the Determinization implementation only works for acceptors and silently clobbers transducers by overwriting the output symbol table with input symbol ids. Determinization should be extended to support both acceptors and transducers as openfst does.

[steveash]

Re-wrote the implementation of Determinization. This supports FSA and FST Determinization now. As discussed in the OpenFST page on Determinization when determinizing transducers you have to decide what to do when the input FST is not functional (multiple output paths for a given input path. Like in OpenFST, jopenfst offers the same three options which can be configured like:

import com.github.steveash.jopenfst.operations.Determinize
import com.github.steveash.jopenfst.operations.Determinize.DeterminizeMode

new Determinize(DeterminizeMode.FUNCTIONAL).compute(myFst);

There are three DeterminizeMode options mirroring OpenFSTs:

• If FUNCTIONAL (default) then determinize will throw if it encounters nonfunctional input
• If NON_FUNCTIONAL then determinize will keep both paths (but that means the output wont be deterministic
• If DISAMBIGUATE then determinize will keep the min arc of the options and output will still be deterministic