Hi Hieu: Thanks for the response! I would like to look into adding this functionality myself.
After a first pass, it looks like a good starting point would be adding functionality for interpreting XML (e.g., where an input line could contain a single XML tag rather than a word column) to the ConfusionNet class, and then adding functionality to enforce the decoding constraints to the TranslationOptionCollectionConfusionNet class. Let me know if this impression seems correct to you. Any other advice or caveats regarding this undertaking would also be much appreciated! Thanks, James On Wed, Jul 22, 2015 at 5:22 AM, Hieu Hoang <[email protected]> wrote: > i guess lack of interest. XML markup is usually used by more > application-focused users who don't usually use complicated things like > confusion networks, and confusion networks are used mainly by researchers > who don't use xml markups > > > On 18/07/2015 00:35, James H. Cross III wrote: >> >> Hi: >> >> Is it still the case that XML markup is not supported for confusion >> network (or lattice) input? If not, are the reasons for not supporting >> this feature because implementing it imposes particular difficulties >> or simply due to lack of interest? >> >> Thanks, >> James >> _______________________________________________ >> Moses-support mailing list >> [email protected] >> http://mailman.mit.edu/mailman/listinfo/moses-support >> > > -- > Hieu Hoang > Researcher > New York University, Abu Dhabi > http://www.hoang.co.uk/hieu > _______________________________________________ Moses-support mailing list [email protected] http://mailman.mit.edu/mailman/listinfo/moses-support
