Import translation files into Launchpad translations.

[Bert Timmerman]

Import translation files (*.po and maybe pcb.pot) into the Launchpad translation system as to benefit from already available translation strings, thus lowering the work load for existing translations and lowering the treshold for new languages translation.

[Peter Clifton (pcjc2)]

I'm of the opinion we _should_ do this, but not right now.

Lets give the LP bugs migration time to settle, and then come back to this. When we release the next gEDA stable point release (1.6.2), I'm going to have to do some work with gEDA's translations from Launchpad, and I'll try and take that oportunity to think about and document the workflow better. Once that is better defined, it will be easier to use it for other projects such as PCB.

[Bert Timmerman (bert-timmerman)]

(ping)

[Traumflug (mah-jump-ing)]

Please keep your fingers off geda-project unless you want to contribute to it.

[Chad Parker (parker-charles)]

A note from the launchpad translations page:

We require that all translations made in Launchpad are BSD licensed. This does not apply to translations imported from elsewhere.

Do we care about this?

[Chad Parker (parker-charles)]

I've uploaded the templates and the current translations. LaunchPad will scrape them from git if we include the template file ".pot" in the source tree. We aren't currently. It's a generated file. Maybe we add it and update it at every release?

A note from the launchpad translations page:

We require that all translations made in Launchpad are BSD licensed. This does not apply to translations imported from elsewhere.

Do we care about this?