[postgis-devel] PostGIS document translation - where to put them

Sandro Santilli strk at keybit.net
Tue Oct 14 00:46:15 PDT 2014


On Mon, Oct 13, 2014 at 06:33:29PM -0400, Paragon Corporation wrote:
> It's come that time where we have to start autogenerating the PDFs from the
> transifex translations.
> 
> My excursion into this forest was halted by me tripping when I committed po
> transifex files that broke our localize builds. Strk thinks it was a missed
> tag in transifex and assures me it's not just because I'm a windows user.

One case I looked at was a malformed <code> tag,
missing the opening '<' character.
I think I've corrected that specific problem on transifex.

> Right now transifex pulls our pots, but does not commit the pos.
> 
> One option is 
> 
> 1) To just keep it that way but have a job that pulls the pos and builds the
> docs and screams when PDFs can't be built from the pos on transifex. This I
> invision happening daily
> Or whenever a change
> 
> 2) Pull the pos from transifex and commit to a git and job just pulls from
> git. There's something tantalizing about having a git just focused on
> localization though that might prove difficult to manage
> 
> 3) Have some mechanism to get these pos back in our repo perhaps during
> freeze cycles, but that leads to confusion if someone should make the
> mistake of editing them as strk did.

I think getting the pos back in our repo is the way to go.
Confusion is called "conflict" and tools exist to help with resolving them.
The conflict resolution pain could be relieved by getting externally
originated changes into transifex earlier.

> Strk pointed out this thread:
> http://blog.transifex.com/post/65622088435/managing-your-continous-localizat
> ion-project  of which I haven't had the patience to read yet that might give
> us some constructive suggestions on how to move forward.

That tool gives you a pull/push interface into transifex, with configuration
stored in a .tx folder under your project tree, which you can add to the
project repository. Sounds useful to help with both ways sync.

 apt-get install transifex-client # for apt-based systems
 pip install transifex-client # for general pythonists

> Does anyone have any opinions?  Having transifex as the single source of
> translations seems simplest to manage though I don't like the idea of our
> pos not being under a versioning completely under our control and being
> detached from our core source.

My vote goes to maintaining the code repository the real source of
translations, and using transifex as a mean to gather contributions,
periodically accepted (the more of often, the easier to maintain).

--strk;

Please help taking QGIS to the next level of quality. Before November 15 !
http://blog.vitu.ch/10102014-1046/crowdfunding-initiative-automated-testing




More information about the postgis-devel mailing list