I don't have time to commit right now, I'm off to work.. But I can do it later, or someone else can :-)
Personally I think just update the two keys, then mail amsn-lang telling them what needs to be changed.. - Tom On 3 Dec 2006, at 14:08, Arieh Schneier wrote: >>> This may be more work than I initially thought, because we'd need to >>> update each lang file to reflect the changes.. >>> Hmm, better to do it sooner rather than later I guess! >> >> Well, if I were in you, I'd just edit the English, and then let the > language >> Maintainer do the rest :) > > The correct way to do it is to delete the old 'key' and create a > new 1, that > way all the translators will realise there is a 'new translation'. > However > the 'meaning' here is the same so may not require retranslating, so > may not > need a new key? > > > ---------------------------------------------------------------------- > --- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to > share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php? > page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Amsn-devel mailing list > Amsn-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/amsn-devel ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
