Don't know how to document this since it's a language thing but as a multilingual I noticed that English -> Arabic is on par with google translate or worse but DeepL beats them both handily. All of the content below applies to the webpage translate (e.g. !kt wikipedia.com...) and not the normal translate UI which performs similarly to DeepL in my experience.
The issue isn't the "correctness" of the translation, but moreso the context
For example, if I translate
On February 21, 1956, Tokofsky married Myrna Weinstein, and before divorcing they had two sons; in 1970, he married secondly Fiammetta Bettuzzi, and they had a daughter, but this also ended in divorce; thirdly, on October 4, 1981, he married Karen Oliver.[1]
I get a 1-to-1 translation into Arabic (by google translate as well), but DeepL's translation (translated back by me, a little literally) results in:
On February 21st 1956, Tokofsky married Myrna Weinstein, and before they divorced they had two sons. In 1970, he married secondly Fiametta Bettuzzi, and had a daughter, **but this marriage also ended in divorce;** and thirdly on October 4th 1981, he married Karen Oliver.[1]
The ambiguity about the "this also ended in divorce" is a bit harder to trace back in Arabic so the DeepL disambiguation here enhances the translation in a way that is more akin to an actual translator
Not sure if the webpage translator is more restricted but it should be given more freedom in its translation similar to the normal translation UI.
