When translating this article from es to ca using apertium, the reference changes place and stops making sense.
This does not happen with any other MT engine.
Description
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Open | None | T200786 Better support for References in Content Translation (epic) | |||
Open | None | T314127 Improve approach to re-apply rich text elements on content from plain-text translation services | |||
Open | None | T228940 References change place during translation |
Event Timeline
Unlike other engines, Apertium supports only plain text translation. Since it does not support HTML markup the process of translation involves removing the markup and applying it again to the translated contents. Reapplying the markup to a translated text is a process that cannot be 100% accurate and sometimes references and links may be applied to the wrong place.
Since for this particular case the target location seems quite obvious, it may be a good example to improve the algorithm. But I'd defer to @santhosh who knows the internals better to decide if this is a useful example to improve the algorithm or not really worth it.
Update: We have not looked into this lately. Partly due to less complaints regarding this issue and hence its relatively low priority.