Translations policy

I added a string to Metacity (in trunk, of course, not for the stable release).  If I can translate the string into two of the languages in po/ (cy and en_GB), should I just do the ordinary po-updating work and then translate that one string, and commit that, or should I go and ask the translation team first?

(I’m not exactly completely fluent in Welsh, but good enough to read most of the news; I can at least say “move the window to the centre of the screen”, especially if I already have “move the window to the left of the screen” translated.)

Published by

Thomas Thurman

Mostly themes, triaging, and patch review.

3 thoughts on “Translations policy”

  1. No, please don’t change po files without approval from the translation team, even if you are 100% sure that you’re translation is right. Another translator may already be translating that file, resulting in a conflict and doubled work, or there may be different possible translations of which only one is correct according to the team’s guidelines (just think of Trash, Bin or Recicle Bin for ~/Trash).

  2. Actually you would have to ask the translation team to review your changes. But translation teams handle this in different ways. Normally it should be enough to send a note to the mailing list of the team with a link to the change for such little changes. This way, a review is possible without two much annoying administration work. But as already said, this depends on the translation team.

Leave a Reply

Your email address will not be published. Required fields are marked *