Change Details

Apertium language pairs in Content Translation mostly gets outdated quickly, we need solution that quickly updates language pairs: a. Fetch Apertium language pairs data from upstream, b. Put data into WMF git repo (probably as submodule?) c. Either build automatic packages or d. Put data directly to use for Content Translation. This should be approved by TechOps to avoid security/other issues.

Apertium language pairs in Content Translation mostly gets outdated quickly, we need solution that quickly updates language pairs: a. Fetch Apertium language pairs data from upstream, b. Put data into WMF git repo (probably as submodule?) c. Either build automatic packages out of fetch data or d. Put apertium language pairs data directly to use for Content Translation. This should be approved by TechOps to avoid security/other issues.

Apertium language pairs in Content Translation mostly gets outdated quickly, we need solution that quickly updates language pairs: a. Fetch Apertium language pairs data from upstream, b. Put data into WMF git repo (probably as submodule?) c. Either build automatic packages out of fetch data or d. Put apertium language pairs data directly to use for Content Translation. This should be approved by TechOps to avoid security/other issues.