Lexical constraints at translation request time?

[Etienne38 (Etienne Monneret)]

I read your documentation, and, as far as I properly understand it, the lexical constraints can only be provided at the ONMT server starting time. Right ? Is it possible to send a list of lexical constraints with a sentence to be translated ?

I think it would be a nice indirect way to solve this request:

Predictive translation server

It would be a great evolution if the translation server would accept an extra "begining" parameter for a sentence, to return with one (or N) possible way(s) of ending its translation. As far as I understand the way it's working, I think this could be done by forcing the first tokens in the beam search.. right ? PS : a bit harder would be to get a predictive post-editing server = knowing a sentence to translate, and an already existing translation with a pointed position in it, in the beam sear…

[jean.senellart]

We are working on improving the API to this feature, so that we can dynamically send additional lexical constraints. keep tuned.

The predictive translation is far simpler than lexical beam search - we should do it too…

[Etienne38 (Etienne Monneret)]

Excellent !

[tel34 (Terence Lewis)]

Until that happens I have introduced a Custom Dictionary feature in our MT Gateway (client) so that the user can force a particular translation. The Network seems to handle these translations acceptably in the case of nouns & noun phrases, which are usually what need to be “pre-translated” in our particular use cases.