bashareteam team mailing list archive

[Emilien Klein <emilien@xxxxxxxx>]

Hi Guido,

I wanted to ask you how you were doing with setting up the
translations in Launchpad for BaShare. As you are the project owner,
only you can set that up.

You can find the documentation about setting up the translations at
the following address:
https://help.launchpad.net/Translations

I think that it is particularly important to read
https://help.launchpad.net/Translations/YourProject
and
https://help.launchpad.net/Translations/YourProject/ImportingTemplates

The ideal solution would be to have automatic imports of our .pot
translation template. By default our file is located at
"BaShare/.lang/.pot" (this is where Gambas puts the template that gets
generated each time you launch the project). From what I've
understood, for Launchpad to accept the first automatic import it
should be named as "<translation domain>.pot", so I've created a
symbolic link:
bashare.pot -> BaShare/.lang/.pot

I hope this will do the trick: in theory, Launchpad should accept this
template and create the appropriate translation domain called
"bashare". The condition for this to work is that the translation
domain must not exist.

Once we have the first import of our translation template, we will put
the other languages in Launchpad. The only thing is that I have
modified some strings to remove string concatenation (bug #426017), so
we might not be able to directly import all the strings for all the
languages. Guido, do you have a way to contact the people that have
helped you translate the software? We should maybe create a new group
(~bashare-translators) and invite those people to help us translate
BaShare in Launchpad... What do you think about that?

Please keep me updated on how things are going.

Thanks,
Emilien.

P.S.: From now on, we should use this mailing list (bashareteam) for
our BaShare-related communication.