I'm not sure this is wise.

My view is that all translations to trunk would be prohibited.  Translators
should only update branches, instead.

Update trunk translations just before a branch from trunk.

Right now, there are a couple of translators that *only* make their updates
to trunk, as I recently discovered.  Sadly, this is a waste of time, as the
shipping translations are from S2_1.  We never update 2.1 from trunk.

For S2_2, I had to merge from trunk, then merge from S2_1, then re-merge from
trunk (this was a consequence of the msgmerge internal processing).  A PITA,
requiring much experimentation and line-by-line comparisons.

Trunk is supposed to change frequently, and programmers shouldn't have to
worry about the translation state.  Branches are supposed to be more stable,
and any changes to translations are (usually) announced.  At least, that's
been the practice during my time around here.


_______________________________________________
Freeciv-i18n mailing list
[email protected]
https://mail.gna.org/listinfo/freeciv-i18n

Reply via email to