If you send it this afternoon I will finish it :-) Strange though, I searched i the CVS to fix it there, but found no fuzzies ... Håvard: Is everythinbg sent upstream? Or did I make a mistake?
In the case of shadow, which I now nearly personnally maintain in Debian, notices are sent to translators when a translation is needed. If possible, I Cc the translation team, but this fails often as they are usually mailing lists with non opened posting policy (for the i18n-no, that's different as I'm subscribed to your list...and anyway, postings from non subscribed memebers are moderated).
So, after that of course, this is up to you to update your team's CVS...which may then become outdated, if the translator (who is the one receiving the request for update) cannot update it him/herself.
Here, I'm not sure whether you missed the call for update I sent first, or never received it...or whatever.
About the real upstream for shadow, I, as the Debian maintainer, send the new/updated translations to him. He already adopted those I sent.
We are however currently a few releases after him (shadow in Debian is 4.0.3 and he is preparing 4.0.7). After the release of sarge I will bump the Debian package to 4.0.7 (I hope to get some help for that from other Debian developers) which will certainly need more translation updates.
For this particular package, being clear is not easy as the situation is quite complicated (Debian maintainer missing in action, upstream inactive for a long time in the past.....). I hope I made it clearer...:-)
(and for Petter who is maybe listening : what happens is exactly what we talked about at Debconf4 when you suggested me to take over the package...-)))