libgeda translation

Hello Abdellah,

I'm one one of the gEDA developers.

Libgeda packages have their library SOVERSION appended, so for exampel libgeda38 belongs to the the latest gEDA version - 1.6.0 which is in lucid. This allows (in theory, but it is never done in practice) multiple versions of libgeda to be installed on the same system.

gEDA 1.4.x uses libgeda33. As far as I can tell, libgeda 34-37 belonged to development versions - and it would not be best use of your time to translate those.

Do you want to use Launchpad to translate, or would you be happy translating direcltly upstream? We often use a work-flow where translators commit directly into our main repository.

Otherwise, I can see about getting the new translation templates uploaded onto Launchpad. Unfortunately, due to the BSD Licensing of launchpad translations - and other technical issues regarding changes in launchpad conflicting with upstream source translation changes, we've not been very good about merging these translations back into the upstream repository.

Presumably for them to be useful, we have to do that... or do they get sucked into some Ubuntu launguage-pack automatically?

Either way, I'm happy to help as much as I can to facilitate getting your translations into gEDA.

Best wishes,

Peter Clifton

Hi again Peter,

- Aright for libgeda, Thank you.

- 1st My self, I prefer GPL license for translation of at least LGPL.
- Upstream! Yeah, of course this is the best way. I'll be very happy for that.
Could you rearrange it for me? Or How could I get into the process?

- But wait a minute! Where are the templates?
I hope you haven't deleted them totally. So I don't want to start from Zero.

Hi, I just uploaded the new templates, but I marked the old ones as not accepting translations any more.

Launchpad translations are a bit of a mess in my opinion - and not brilliantly well suited to a project which doesn't use Bazar or code-host on Launchpad. When we set geda up on launchpad - everything was in the "trunk" series, so it was always confusing to know what version you're translating - or what version those translations should be imported into.

Since there was no way to move the temptates out of "trunk", I marked them as not accepting translations anymore. (Something I can change back if necessary).

I've uploaded the .po and .pot files from the geda 1.6.0 tarball to the "stable-1.6" series translations, but they are stuck in the import queue (and will proabably require admin intervention - this is one of the things I hate most about Rosetta!)

I've also uploaded a new xgsch2pcb .pot file from git, which has gone into the "trunk" section. xgsch2pcb is not shipped in the same tarball as geda-gaf, and has (very) different release numbers. I don't want to add release series for xgsch2pcb to the "geda" project in launchpad, so for now - I'll keep those translations in the "trunk" series. (xgsch2pcb tends to release incremental snapshots, rather than stable / development series anyway).

Launchpad (I'm told) should be pretty smart about offering suggestions / finding strings whcih have already been translated, so your existing work is definately not lost. Where the gEDA 1.6.0 translations differ though, you might have to re-translate a string, or be offered a slightly incorrect suggestion.

Regarding direct upstream translations, you can contact the gEDA developers here:

http://www.gpleda.org/mailinglists.html

geda-dev is a closed mailing list, so geda-user is probably the easiest way to make first contact.

For geda-dev (which you'd be welcome to join as a translator), look here (archives only):
http://www.gpleda.org/developer.html
You'd have to email the mailing list manager, Ales Havezda to get access. (ahvezdaATgeda.seul.org)

I presume you're already a gEDA user?

Upstream translators tend to checkout our git repository: git clone git://git.gpleda.org/gaf.git
(See http://geda.seul.org/wiki/geda:scm)

You might need to "make update-po" in the various po directories if the sources are far from a release. Typically translators who prefer the upstream workflow will be aware of an impending release (possibly through the geda-dev mailing list), and would upload translations to git HEAD prior to final tarball release.

Alternatively, you could translate after a tagged release - and we could back-port the translation commits onto the appropriate stable branch. (Or you could translate directly for the stable branches - if git HEAD has seen lots of development). Lots of possible options!
I guess it depends on your ultimate goal - do you want to translate for the latest version shipped in Ubuntu, or for the next upstream version which will be releasted?

The developers are only to happy to take patches formatted with git-format-patch and push them upstream for you.

Let me know if you want any further assistance, and whether you'd prefer the upstream or launchpad work-flows. The main thing is to try not to mix them for a given language - otherwise people duplicate work, and it will lead to merge conflicts.

Hi Peter,

There is no ar.po in import queue of gEDA stable-1.6 series!
In trunk, there is only template of geda-xgsch2pcb. As you said.

Launchpad is really weird.
OK, Could you please make the previous launchpad templates show back. So I could download them.
or Just update the ar.po (Arabic) from .pot file so I can continue translation by working directly upstream.

Thank you Peter, I will move to upstream.

I've written previous reply before reading your last reply. So Could you please make the previous launchpad templates show back. So I could download them.

I will try to translate the next coming release. Only if there is not too much changes in the stable release strings, then I can translate first the stable and update it to the development one.

Thank you very much Peter, You was very helpful.

I can see the translations.. can you not? They aren't removed, just marked as inactive.

https://translations.edge.launchpad.net/geda/trunk/+templates

There are download links from that page, if you wanted to download all the .po / .pot files.

If you can't see the above page, try:

https://translations.edge.launchpad.net/geda/trunk/+pots/geda-gschem
https://translations.edge.launchpad.net/geda/trunk/+pots/geda-gschem/ar/

Etc..

I am an admin, but I don't think that means I'll see any more than you.. the data is just slightly hidden from view (for everyone).

If you have difficulties, let me know and I'll just re-activate the translations. The stable-1.6 import has stalled waiting for human review. (As I expected)

Yeah, through the 1st link, I could only see geda-xgsch2pcb.
The other two, They gave me an oops error msg, as some thing doesn't exist. So only for Admin's

Ok, another irritation in Launchpad.. it isn't explicit about which bits you require admin rights to edit - or how to go about requesting them if you want / need them.

I've marked the trunk translations as "active" again for now. Please let me know when you've grabbed what you need. Once the 1.6.0 translations are imported, I would like to make the "trunk" ones inactive again.

OK, Done. Thank you.

Hi/Salam Peter,

geda-user mailing list is not known by "majordomoseulorg" just geda-pt.

Could you tell me what the admin mail for geda-user? I have tried geda-admin! It's not mentioned at http://www.gpleda.org/mailinglists.html.

Thanks Peter Clifton, that solved my question.