Project

General

Profile

Task #2012

Automate pootle to commit translations

Added by Jan Iversen over 1 year ago. Updated 3 days ago.

Status:
Feedback
Priority:
High
Category:
Pootle
Target version:
Team - Q4/2017
Start date:
Due date:
% Done:

0%

Estimated time:
5:00 h
Tags:
URL:

Description

Cloph have already started to automate the pootle integration to git. There is a cron script running every second hour to sync the pootle database with the directories.

Next step, use last modified time (controlled sync script, it only touched files it actually write), copy changed files to a git clone, commit and push.

The automated push, will be done for master (still need to figure out, how to do it for android, iosviewer, and libo_online).

We need to think if we want it done for lib050, lib051 and libO52 as well.


Related issues

Related to Release Engineering - Task #1488: Pootle layout automated prepration to repository-ready filesClosed

History

#1 Updated by Florian Effenberger over 1 year ago

  • Target version set to Pool

#2 Updated by Florian Effenberger 5 months ago

  • Status changed from New to Feedback
  • Assignee changed from Jan Iversen to Christian Lohmaier
  • Priority changed from Normal to High
  • Target version changed from Pool to Q3/2017

Carried out, but needs deployment on our side - blocked by the Pootle back-migration to own infra, which is in progress

#3 Updated by Christian Lohmaier 3 months ago

additional blocking/delaying factor is gettext migration on master - but will be tackled within next two weeks (pootle project split up/master changed to master this week).
Then apply tweaks as necessary to the processing to match the slightly different syntax if necessary (should not be needed, as we had variable size msgctxt before, so just verification that the script works as intended after migration as well).

Would have been nice to have that on our infra, but that seems to be delayed a little further.

#4 Updated by Christian Lohmaier 3 months ago

  • Related to Task #1488: Pootle layout automated prepration to repository-ready files added

#5 Updated by Florian Effenberger 3 months ago

Do you see a chance to have that done by the time of the conference? Would be great to see some result there

#6 Updated by Florian Effenberger about 2 months ago

Any status update on this?

#7 Updated by Christian Lohmaier about 1 month ago

msgfmt (tool used in gettext builds) is very picky about syntax errors (well, not even syntax error, but if e.g. english string has a \n (newline) at end of string, but the translation doesn't, it fails hard and breaks the build (even if the translation has the same number of newlines in total). So needs some more manual runs to fix them before/and additional checks/tweaking in the script to avoid checking in these kind of strings.
Just refusing to use files that have this problem should be easy to do, problem is that with gettext there are fewer files in total, so if messages.po is refused because of one problematic strings, so are all the other strings that changed in that file. Of course much better than breaking the build, so I'll go with that route - at least initially.

#8 Updated by Florian Effenberger about 1 month ago

  • Target version changed from Q3/2017 to Q4/2017

So, what's required then to completely close this ticket?

#9 Updated by Florian Effenberger 15 days ago

Florian Effenberger wrote:

So, what's required then to completely close this ticket?

Ping? :)

#10 Updated by Christian Lohmaier 3 days ago

  • Estimated time set to 5:00 h

ideally our own host, apart from that an additional preprocessing that rejects files with problematic translations - so some time to actually do it.

Also available in: Atom PDF