Translation pointers wanted

This is a generic question for more experienced translation contributors. I use Gallery in production (specifically G1). So when I see a missing entry, I need to fix it in the version used in production first. When such fixes become systematic, I'd love to share it back with the community. But obviously the production site is not using nighly CVS build. Generally speaking, the production could even be a stable releases behind. Even stable releases contain lots of typos, spelling and other grammatic errors in string id's, so I expect these to be changed frequently.

I do use CVS from time to time but I'm not an avid developer. Can you share your experience in regard to how much effort it requires to "migrate" or merge fixes to a nightly build? I know that line numbers change, string ID's change, and strings are added and removed. What steps are involved to do such a merge, if at all possible?

A somewhat related question is: what can I do about the English errors in stable releases? I suppose I can build a "translation" to en_US. Is this the only solution?

I meant exactly what you said. Example of errors in string ID (mostly in less used places and in lengthy strings):

(There are several strings with repeated words, and "album album" appeared multiple times.)

Another example is spelling of "ecard" - very inconsistent. Sometimes it's "ecard", sometimes "eCard", sometimes "eC@rd", other times "e-card" and so on.

Another particular problem I noticed in 1.5.2 (probably since earlier versions; I just didn't pay close enough attention) is that there are duplicate strings in gallery_core and gallery_config (at least). For example, the entire section about html_wrap/frames/ items are repeated in 1.5.2's gallery_config.po, even though gallery-config.pot does not have them. Duplication can cause translation to be inconsistant. There might be simple ways to compare and fix but still painstaking.