attempt to transliterate english not working, despite flite being installed properly

[dmort27]

attempt to transliterate english not working, despite flite being installed properly

[dmort27]

This is perplexing. For some reason, lex_lookup is producing output with newlines. Can you try entering the following at the command line and reporting the output?

lex_lookup 'berkeley'

I want to rule out the possibility that this has something to do with the lex_lookup binary on your system. It should output (b er1 k l iy0)

[brisvag]

Interesting. I get a repetition:

$ lex_lookup 'berkeley'
(b er1 k l iy0)
(b er1 k l iy0)

I suppose this means somehow my lex_lookup binary is misbehaving.

[dmort27]

Indeed, your lex_lookup is not behaving as expected. What platform and what OS version are you on?

There is an easy, if kludgy, fix for this (within Epitran): split the output of lex_lookup on '\n' and take the first element in the resulting list. I'll implement this and make a new release today.

[dmort27]

Try the new release (0.60) and see if it fixes the problem.

[brisvag]

Indeed, your lex_lookup is not behaving as expected. What platform and what OS version are you on?

I'm on ArchLinux, and I built flite from the source on github. This might be some problem/change with the latest upstream... I really doubt I did anything strange, since the installation process is quite easy and streamlined.

Anyways, your quick-and-dirty fix works just fine, thank you!

[dmort27]

You built flite from the GitHub source, then? This probably explains the problem. I think Alan Black, author of flite, may have changed the behavior of lex_lookup since the non-release release that is recommended in the README for Epitran. I'll talk to @awbcmu and @saikrishnarallabandi to see if there are any other interface changes to the lex_lookup interface that I should accomodate. Then perhaps I can start directing people to the GitHub source rather than the package linked from the README.

[dmort27]

I just talked to @awbcmu and apparently there was a change in behavior in lex_lookup. He said epitran should take the first transcription, so the current behavior is right.

[brisvag]

Good, glad this helped to solve something! I'd say this can be closed for good now.

[WhiteFu]

@brisvag
Have you solved this problem? Is there a viable solution?

[brisvag]

Yes. As I said in my last message, dmort's upstream fix was enough.

[WhiteFu]

Thank you very much:)