Project

General

Profile

Task #1913

Pootle – add local translation memory for existing strings (TM)

Added by Florian Effenberger over 1 year ago. Updated 5 months ago.

Status:
Closed
Priority:
Normal
Category:
Pootle
Target version:
Team - Qlater
Start date:
2016-08-01
Due date:
% Done:

70%

Estimated time:
Tags:
URL:

Description

We got a report about some Pootle improvements:

  1. Out of date stats: https://translations.documentfoundation.org/projects/ - usually some stats job failed. There are steps to clean these up. Pootle master is much better at this
  2. Local TM. Setting up Local TM on Elasticsearch will give live up-to-date TM based on the projects in Pootle. This doesn't seem to be setup or running at the moment and Pootle is only giving amaGama TM results. POOTLE_TM_SERVER needs to be setup. This might obviate the post I see about new master not containing someones 5.1 translations and then them not having TM results for those previous translations.

History

#1 Updated by Christian Lohmaier over 1 year ago

  • Subject changed from Pootle improvements to Pootle – add local translation memory for existing strings (TM)
  • Start date set to 2016-08-01

Talked with Dwayne who offered to give a shot at local TM - our codebase is too large for that to go smooth without interrupting, so that won't be tackled before 5.2.0 is out, and probably also not before we upgrade pootle (as the idea is to improve the import instead of taking down pootle). But he did clean up the stats not updating, so that's clean now :-)

He also checked that the config is done so new stuff gets added to the tm

#2 Updated by Florian Effenberger over 1 year ago

  • Target version changed from Pool to Qlater

#3 Updated by Florian Effenberger about 1 year ago

Is there any update on this? Will it be done alongside the next Pootle rollouts?

#4 Updated by Christian Lohmaier 11 months ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 70

is in progress, elasticsearch has been deployed/is running on new host, but still using amagama as source atm.

#5 Updated by Florian Effenberger 10 months ago

Christian Lohmaier wrote:

is in progress, elasticsearch has been deployed/is running on new host, but still using amagama as source atm.

Any update?

#6 Updated by Christian Lohmaier 10 months ago

inplace / availble in currently instance. Problem with updating the TM though, that likes to read in the whole database at once, and thus is prone to triggering out-of-memory kills..

#7 Updated by Florian Effenberger 7 months ago

Cloph:
As discussed in-person in Munich - can you give a status update, if this is done, dealt with otherwise or pending?

#8 Updated by Christian Lohmaier 6 months ago

  • Status changed from In Progress to Resolved

this had been implemented based on elasticsearch by translatehouse folks - atm both amagama (remote) as well as local TM are enabled on pootle instance.

#9 Updated by Florian Effenberger 5 months ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF