Bug#663916: New phonetisaurus package available
* Giulio Paci <firstname.lastname@example.org>, 2012-10-20, 00:00:
I just had a look to the already opened bugs and I found that there is
an RFP bug for utfcpp:
Do you think I should do anything else (e.g., reply to the bug with the
maintainers of the packages you identified in CC)?
I think reply+cc would be a good idea, but I won't insist.
If I run phonetisaurus-align without arguments, it segfaults:
| $ phonetisaurus-align
| Loading input file:
| Starting EM...
| Finished first iter...
| Iteration: 1 Change: nan
| Iteration: 2 Change: nan
| Iteration: 3 Change: nan
| Iteration: 4 Change: nan
| Iteration: 5 Change: nan
| Iteration: 6 Change: nan
| Iteration: 7 Change: nan
| Iteration: 8 Change: nan
| Iteration: 9 Change: nan
| Iteration: 10 Change: nan
| Iteration: 11 Change: nan
| Last iteration:
| Segmentation fault
The manpage seems to imply that --input and --ofile options are
mandatory, so I'm not sure what it is even trying to do... But it
certainly shouldn't segfault.
Shouldn't phonetisaurus-align input format be documented somewhere? BTW,
it aborts without any helpful error message if the input file is not
| $ echo foobar > invalid.txt
| $ phonetisaurus-align --input=invalid.txt --ofile=invalid.corpus
| Loading input file: tiny.bsf
| terminate called after throwing an instance of 'std::out_of_range'
| what(): vector::_M_range_check
What does --fst_field_separator exactly do? In my experiments it did not
affect phonetisaurus-align in any way.