committing back to svn

I am not sure I understand correctly, but I'd say you might be suggesting either Launchpad getting translations directly from KDE Subversion repository, or the other way around (Launchpad committing KDE translations directly into KDE Subversion repository).

If it's the first, there are a few obstacles before we can enable something like that. For once, we need to implement direct POT extraction and committing, and that is commonly quite specific to project (i.e. it's different for KDE and GNOME applications, and for any others as well).

Next, to avoid misguiding other translators (eg. non-Israeli) into translating KDE and without their translations being used, or doing work which is already being done elsewhere (eg. upstream in KDE), we'd have to set-up a properly managed translation group and assign translation teams only when they are in sync with upstream teams (i.e. your team would not have any problems). This means there would have to be a person trusted by both KDE community and Launchpad Translations administrators (and we are likely to trust whatever KDE community chooses), who'd assign per-language teams and upload POT files.

Also, important consideration is that we are not anywhere near to automatically importing translations from source code branches (see https://blueprints.launchpad.net/rosetta/+spec/rosetta-translates-branch to track this), nor are we going to implement direct commit of translations to other repositories (mainly because of logistical issues) anytime soon.

So, in essence, while possible, it's going to take quite some development time on our side, and a lot of work on the community side, before this can be put into work. If you are interested in helping with that, though, we'd be happy to start working towards that.

In the meantime, you can still use Ubuntu translations to translate KDE as well, but I understand that there are timing issues in that case.

So where can I get updates about this matter?
I truly believe it is highly important for both the Ubuntu Community and the
KDE Community

Thank you for your quick answer!

On Mon, Sep 29, 2008 at 6:22 PM, Данило Шеган <
<email address hidden>> wrote:

> Your question #46556 on Launchpad itself changed:
> https://answers.edge.launchpad.net/launchpad/+question/46556
>
> Status: Open => Answered
>
> Данило Шеган proposed the following answer:
> I am not sure I understand correctly, but I'd say you might be
> suggesting either Launchpad getting translations directly from KDE
> Subversion repository, or the other way around (Launchpad committing KDE
> translations directly into KDE Subversion repository).
>
> If it's the first, there are a few obstacles before we can enable
> something like that. For once, we need to implement direct POT
> extraction and committing, and that is commonly quite specific to
> project (i.e. it's different for KDE and GNOME applications, and for any
> others as well).
>
> Next, to avoid misguiding other translators (eg. non-Israeli) into
> translating KDE and without their translations being used, or doing work
> which is already being done elsewhere (eg. upstream in KDE), we'd have
> to set-up a properly managed translation group and assign translation
> teams only when they are in sync with upstream teams (i.e. your team
> would not have any problems). This means there would have to be a person
> trusted by both KDE community and Launchpad Translations administrators
> (and we are likely to trust whatever KDE community chooses), who'd
> assign per-language teams and upload POT files.
>
> Also, important consideration is that we are not anywhere near to
> automatically importing translations from source code branches (see
> https://blueprints.launchpad.net/rosetta/+spec/rosetta-translates-branch
> to track this), nor are we going to implement direct commit of
> translations to other repositories (mainly because of logistical issues)
> anytime soon.
>
> So, in essence, while possible, it's going to take quite some
> development time on our side, and a lot of work on the community side,
> before this can be put into work. If you are interested in helping with
> that, though, we'd be happy to start working towards that.
>
> In the meantime, you can still use Ubuntu translations to translate KDE
> as well, but I understand that there are timing issues in that case.

Thanks Данило Шеган, that solved my question.