437341 - Integrate scripts into Verbatim

Status: RESOLVED FIXED

(Webtools Graveyard :: Verbatim, defect, P1)

Description

[Wil Clouser [:clouserw]]

We're writing .po translation scripts in some other bugs and we need to figure out how to integrate them into Verbatim.  Since these aren't a part of the translate toolkit we'll need to figure out a way to store them separately.  Maybe a config variable and Pootle can look into that directory and the translate toolkit directory?

Comment 1

[Dan Schafer [:dschafer]]

As part of this, we need to figure out how to tell Pootle that the PO file being changed was created from a non-PO file, and thus it needs to update the original file with the new translations in the PO.  My current plan is to just make sure all of the original files are in the same directory as their PO counterparts, and if a file with the same name but different extension exists, convert the PO to that format.  Any thoughts?

Comment 2

[Wil Clouser [:clouserw]]

Seems like we should store the conversion process on a per-project basis since our scripts take different arguments (.po<->.lang and .amopo<->.po is different).  I'd like a default rule for a project type but something we can change if we need to (like if a file isn't named 'messages.po' for instance).

Comment 3

[Dan Schafer [:dschafer]]

A basic foundation for this was included in revision 7750; see attachment 329573 [details] [diff] [review].

Comment 4

[Dan Schafer [:dschafer]]

Attachment: Adds by-project pre/post commit support

This adds a new option to pootle.prefs for "scripts".  Inside the scripts directory are two sub-directories: precommit/ and postcommit/.  If {projectname} exists as an executable script in one of those folders, it will be executed at the requisite time: precommmits before the `svn commit`, postcommits after a successful commit.

Comment 5

[Dan Schafer [:dschafer]]

In revision 7770; tentatively marking this FIXED