Spend a few hours or up to half a day to investigate how easy it would be to add Microsoft Translator API support in cxserver. Expected output:
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T76456 Language Engineering tracker of trackers (tracking) | |||
| Invalid | None | T76454 [Epic] ContentTranslation - MT support | |||
| Open | None | T86700 Add more machine translation services (tracking) | |||
| Open | None | T279064 Observations from first research study for Section Translation on Bengali Wikipedia | |||
| Open | Feature | None | T90207 MS Bing MT for Content Translation | ||
| Resolved | Nikerabbit | T274147 Technical feasibility investigation for Bing translation support in cxserver |
This API is similar to Google/Yandex. It supports direct HTML translation, though in my short testing I noticed it had moved a link to a wrong word in the translation, so their mapping algorithm is not perfect. I did not compare it to our own mapping algorithm, but I don't expect ours to be better.
There are few language codes that need a code map and should be selected carefully in case of languages with multiple scripts.
Improving the code to a merge-able state should take only an hour or two max.