Why is there no operation to see if a string represented as FSA1 is accepted by an acceptor FSA2?
This is equivalent to seeing if their intersection is non-empty. • How can I test if an acceptor/transducer corresponds to the empty language/transduction? This is equivalent to checking if the output of fsmconnect has no states. This can be tested using fsmconnect -t, which returns exit status 1 if its output has no states. • Why is there no operation for converting an acceptor into the corresponding transducer (i.e., the identity transducer restricted to the strings in the acceptor)? It is not needed; the FSM library automatically intreprets any acceptor argument as the corresponding transducer where appropriate. • Why is there no operation to transduce acceptor FSA by transducer FST? This is equivalent to composing FSA with FST and then projecting on to the output side. • I built an acceptor/tranducer, but it does not accept/transduce anything! Did you forget to specify the final states? • I can build acceptors fine, but my transducers don’t compile correctly! Did you forget the “-