Creating packages where appropriate (u-d-f, yast) or creating translation bundles suitable for packaging. This is a completely different task, at least thats not what translators think about in the first place.=) But I'd like to get messed with it some time later...
While creating such a tool would be nice, let's not overhead this with enormous functionality, it's not a UNIX-way of things =) It is obvious that we need to split the tasks: 1) Syncing (merging) po's with pot's (this is just technical issue, that needs to be solved on a regular basis) 2) Translation memory tasks (this one is not just technical, but also political, cause we know that not every team wishes to use TM's) 3) Packaging 4) Upstream
Cross-product merging and pulling from and pushing upto upstream where appropriate. I think Stanislav's gnome-patch-translation can do this in a configuarble manner. We raised that question some time ago: files with upstream translations require a completely different workflow for both developers and translators, so that some separate tools (and, as I believe, separate repo branch ;) ), but that definitely deserves a separate discussion at least =) -- Regards, Minton. -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org