Most of it can be done semi-automatically using txclient. Yaron Shahrabani
<Hebrew translator> On Thu, Apr 4, 2013 at 4:39 PM, Oliver Burger <[email protected]> wrote: > Well, it doesn't matter if the translations are in a separate > repository or not and I'm not sure, what it woudl mean for the devs, > to separate them. > The problem with tx is - or at least was - the manual work involved > upon string changes. > > As an example: > When uploading a file into tx, it parses that file and adds the > strings into the database. When the string changes in the original pot > (even it's only a typo), and you reupload the pot file, tx will parse > it and see a new string and one string missing and it will act > accordingly: > It will remove the translations for the old string from its database > and it will add the new untranslated string, since it can not know, > that this was only a string change. > So the task for us (mostly me) was: > - Tell you not to touch certain translation resources in a certain time > span > - Download all files from this resource from tx > - merge them manually with the changed po files (it couldn't be > automated, since TX also had problems fuzzying strings correctly) > - reupload all files to tx and tell you to check > > I would rather have a solution without the need to do so.... > > Cheers, > > Oliver >
