Hi, I will try with -continue-partial-translation. It seems it could help.
Maybe it is good idea to add to the decoder similar option to <zone> but with restriction that translated phrase cannot overlap boundaries of zone. My experience is that I get usually better quality when tagged items (i.e. UI options) are translated on its own. It also helps to proper recreation of tags in translated text based on phrase alignment. I tried both phrase and word alignment information to recreate tags in translated texts but still have some situations that such information is not enough to proper tags placing. Thank you Jacek -----Oryginalna wiadomość----- From: Ondrej Bojar Sent: Thursday, July 11, 2013 12:52 PM To: Philipp Koehn ; Jacek Skarbek Cc: [email protected] Subject: Re: [Moses-support] Translation of tagged text Hi, if you indeed want to translate a phrase separately (but you will be losing [bilingual] context information, as Philipp suggests), you can translate the original sentence as three separate sentences. The drawback is that you would be also losing the monolingual LM context. Moses has (or had before the refactoring) the option -continue-partial-translation. After translating the first part of the sentence, you could feed it back in with the source of the second part and use this option to make use of the (target-language) monolingual context. If you just want to recover the bold markup, use word alignment information, that will very likely work even for the long phrase that spanned the zone boundary. Cheers, O. "Philipp Koehn" <[email protected]> wrote: >Hi, > >Zones are restrictions on reordering, and their logic is: once you >start translating words in a zone, you have to complete the zone >before you can translate words outside the zone. > >This does allow the use of phrase that partially overlap with the zone >when entering or exiting the zones. This is desirable, since such >longer phrase mappings can use more context. > >-phi > >On Tue, Jul 9, 2013 at 2:56 AM, Jacek Skarbek ><[email protected]> wrote: >> Hello, >> >> >> >> I.e. I have the following original sentence: click <b>printer >> setup</b> >> button >> >> I send to Moses decoder: click <zone>printer setup</zone> button >> >> and receive: Klicken Sie auf Drucker Setup|0-1| Taste|2-2| >> >> and I would expect to receive: Klicken Sie auf |0-0| Drucker Setup|1-1| >> Taste |2-2| >> >> >> >> I would like the phrase “printer setup”, that is originally tagged, to be >> translated and aligned separately to “Drucker Setup” and not aligned as a >> part of longer phrase. >> >> Initially I thought that <zone> markups do the work, but it is only >> reordering constraints option. I wonder if there is any way to force >> Moses >> decoder to translate tagged text as a separate phrase in the way I tried >> to >> explain above. >> >> >> >> Thank you >> >> >> >> Jacek >> >> >> _______________________________________________ >> Moses-support mailing list >> [email protected] >> http://mailman.mit.edu/mailman/listinfo/moses-support >> > >_______________________________________________ >Moses-support mailing list >[email protected] >http://mailman.mit.edu/mailman/listinfo/moses-support > -- Ondrej Bojar http://www.cuni.cz/~obo _______________________________________________ Moses-support mailing list [email protected] http://mailman.mit.edu/mailman/listinfo/moses-support
