LEAPT: Learning Adaptive Prefix-to-prefix Translation For Simultaneous Machine Translation

Lei Lin, Shuangtao Li, Xiaodong Shi
3/21/2023
cs.CL

No confident code implementation found for this paper.

Abstract

Simultaneous machine translation, which aims at a real-time translation, is useful in many live scenarios but very challenging due to the trade-off between accuracy and latency. To achieve the balance for both, the model needs to wait for appropriate streaming text (READ policy) and then generates its translation (WRITE policy). However, WRITE policies of previous work either are specific to the method itself due to the end-to-end training or suffer from the input mismatch between training and decoding for the non-end-to-end training. Therefore, it is essential to learn a generic and better WRITE policy for simultaneous machine translation. Inspired by strategies utilized by human interpreters and "wait" policies, we propose a novel adaptive prefix-to-prefix training policy called LEAPT, which allows our machine translation model to learn how to translate source sentence prefixes and make use of the future context. Experiments show that our proposed methods greatly outperform competitive baselines and achieve promising results.

View on arXivView PDF

Code Implementations

No confident code match yet

We couldn't find an author-owned or strongly-evidenced community implementation for this paper. Any repos shown below are weak matches — verify before relying on them.

No code implementations found yet.

Know of an implementation? Let us know in the comments below!

Similar Papers

Cite this paper

@article{lin2023leapt,
  title  = {LEAPT: Learning Adaptive Prefix-to-prefix Translation For Simultaneous Machine Translation},
  author = {Lei Lin and Shuangtao Li and Xiaodong Shi},
  year   = {2023},
  eprint = {2303.11750},
  archivePrefix = {arXiv},
  url    = {http://arxiv.org/abs/2303.11750v1}
}

Add a badge to your README

Shows whether official code is linked for this paper.

Code of Paper badge
[![Code of Paper](https://codeofpaper.com/badge/2303.11750.svg)](https://codeofpaper.com/paper/2303.11750)

Discussion