[josm-dev] Wanted: Plugin Translation With Launchpad HowTo

[Holger Mappt]

On 20.12.2013 10:01, Dirk Stöcker wrote:
> On Thu, 19 Dec 2013, Holger Mappt wrote:
>
>> 3a) My first idea was to check out that branch.  ...  I stopped the "bzr branch
>> lp:~openstreetmap/josm/josm_trans" operation after 600MB were
>> downloaded.  There is no point in downloading and keeping gigabytes of
>> repository data for just a few translations.
>
> Hmm. I get a 149MB directory when using the tools in i18n.

I was referring to "bzr branch lp:~openstreetmap/josm/josm_trans".  That 
command is shown on the Launchpad josm_trans code page. 
i18n/launchpad.pl does a "bzr export -v josm_trans 
lp:~openstreetmap/josm/josm_trans" which exports the data.  The export 
is equivalent to the revision tarball download that I mentioned as best 
way, 3b.

>> This is my translation flow for the PhotoAdjust plugin.
>>
>> ant pot
>> ./poimport.pl 749
>> ./pomerge.pl
>> ant lang
>
> All this is already done in the tasks of i18n.
>
> I added a task "singleplugintrans", which does all this only for a
> single plugin.
>
> ant -Dplugin=gpxfilter singleplugintrans

Ah, thanks.  I fixed build.xml to make it work.  A plugin is translated 
with the commands:

./launchpad.pl bzronly
ant -Dplugin=gpxfilter singleplugintrans

The original i18n tasks did not add the plugin description (property 
plugin.description in plugin build.xml) to the plugin POT/*.lang files. 
  I changed that, the plugin description is now part of the plugin 
template josm.pot.  That translation is used once the plugin is 
installed.  Please revert revision 30143 if that change is not right.

Regards,
Holger