- You download your file. - You translate it in several days (say seven days). - Two days after you took the file (five days before you try to commit it) a developer updates the .pot and the .po on the server updates automatically. - You have translated the file an you try to do svn ci. - It fails. -Then you have to do a backup of your file (for when doing svn update your translations doesnt dissapear). - Then you do svn update. - You copy the backup over the .po file downloaded in the previous step from the server using svn update. - You merge it with the latest .pot (remember to checkout it from the server)
What is a merge? An svn operation? There is a command "svn merge". You mean that?
Or do you mean a manual operation, using an editor to mix both files, the one on the server and the one from the translator? That's not my job, I'm not the translator. I'm the commiter. See below.
No, it isn't a svn operation. The merge is the operation of updating a .po file with a newer .pot file. You could do it with a .po editor, like Poedit, or using the gettext tool: msgmerge --update yourpofile.po newerpotfile.pot
- You translate the new strings
Impossible.
It is possible, but if you don't want to do it, no matter.
- You do svn ci (now it works)
You forget that I'm not the translator that translated that file. I'm only the one uploading it. There are two translators involved, using Verbum.
If we don't find an automated procedure soon, what we'll do is commit the translator file deleting the developer file. :-/
You could automate this in some way with a script. See the command above. Bye, Leandro Regueiro --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org